RANK.EQ in SoftMaker PlanMaker: Ranking Direction and Equal Values

Use RANK.EQ in SoftMaker PlanMaker to assign an observation its position in a numeric list, giving tied values the same best position. The working example below describes weekly dispatch quantities; it returns a position, not boxes. The official reference supports the function’s identity and purpose.

This guide separates documentation review from application testing. The expected numbers are independently calculated, not screenshots or results captured from SoftMaker PlanMaker.

RANK.EQ(Number, Range [, Ascending])

Value: the measurement whose rank is required, here an observation already present in the register.

Reference range: the comparison group. Lock its row and column coordinates when copying a ranking formula.

Direction: descending for highest-first ranking, ascending for lowest-first ranking. The examples state the direction explicitly and use the parameter form documented for this program.

Use RANK.EQ when every row needs a position against the same comparison group. Unlike LARGE or SMALL, which return a value when given a position, ranking starts with a value and returns its position. Keep an ordinary record identifier as well; a rank is not a stable ID.

The EQ tie rule is competition ranking: if two records share second place, both receive 2 and the next record receives 4. It is neither average ranking nor dense ranking. A leaderboard that must award a unique position to every row needs a separate, documented tie-break rule rather than an assumption that this function resolves ties.

A desktop dispatch workbook with one row per completed week provides the scenario. Enter the following numeric observations into A2:A7, one per row, with a header in A1. Use a spare result cell outside the input range.

Download the SoftMaker PlanMaker RANK.EQ practice data (CSV). Import it into a new, blank sheet starting at A1, with a comma as the file delimiter and the header row retained. The CSV contains input values only, not formulas or native test results. Blank spacer columns place the requested position in D2 and any additional test data in column F. Keep observations numeric rather than importing them as text.

Example 1: Rank a row with the highest value first

=RANK.EQ(A2,$A$2:$A$7,FALSE)

Expected result: 6.

A2 contains 3. There are 5 observations greater than 3, so its descending position is one plus that count. The reference range stays fixed when this formula is copied down.

Example 2: Make the equal-value rule explicit

=RANK.EQ(5,A2:A7,FALSE)

Expected result: 4.

The value 5 occurs 2 times. Each occurrence receives rank 4; a lower distinct value follows those tied positions rather than receiving the next dense rank. Duplicate measurements remain separate observations.

Example 3: Switch to lowest-value-first ranking

=RANK.EQ(A2,$A$2:$A$7,TRUE)

Expected result: 1.

The nonzero/true direction switches to ascending order. There are 0 observations below 3, so its ascending rank is one plus that count. Choose this direction when a lower measurement should receive rank 1.

For a value present in the list, descending rank equals one plus the count of observations strictly greater than it. Ascending rank uses the count strictly below it. This explains equal ranks without choosing a particular tied row or sorting only part of a record. Keep stored results at full available precision and round only the final presentation when a report requires it. The displayed expectations above are rounded where necessary; a different number of displayed decimal places is not by itself a calculation error.

There are gaps after a tie. That is the intended best-position rule, not a missing result. Do not renumber the remaining rows unless your report deliberately uses a different ranking scheme.

The apparent best record ranks last. Check the direction. Descending order gives the highest number rank 1; ascending order gives the lowest number rank 1. Use an explicit direction in shared workbooks instead of leaving the interpretation implicit.

Displayed values look tied but ranks differ. Formatting can hide differences in the underlying numbers. Decide whether the ranking rule should use full precision or deliberately rounded measurements, then create the intended numeric input before ranking. Keep the comparison range fixed when copying down.

This guide is scoped to the PlanMaker 2026 English reference. SoftMaker names the optional ranking direction Ascending and describes it as a logical value. The examples therefore use FALSE for descending order and TRUE for ascending order, rather than silently copying another program’s parameter labels.

For the dispatch workbook, each row describes a completed reporting week. Keep partial weeks separately or document why they belong in the same group. A smaller quantity in a partial week can affect a rank, median or dispersion measure even though the formula itself is functioning correctly.

When a workbook is shared with someone using an older office suite, preserve the original file and verify a small numeric example in the destination. Notes about a function’s history in Excel are not evidence of its first supported PlanMaker version.

The displayed syntax is a readable range-capable form; square brackets mark optional arguments and are not characters to type. Formula examples use commas as in the English help. Follow the argument separator used by your PlanMaker installation.

For the same statistical question in other programs, see RANK.EQ in Microsoft Excel, RANK.EQ in Google Sheets, RANK.EQ in ONLYOFFICE. These links identify corresponding measures, not a guarantee that names, mixed-data rules, error codes or file conversions are identical.

MEDIAN, LARGE, SMALL, STDEV.S, STDEV.P, VAR.S, VAR.P. Browse the SoftMaker PlanMaker function library for the other published guides.

Editorial verification: The vendor documentation was reviewed on 2026-10-12. Scope: PlanMaker 2026 English help. This is a documentation scope, not a first-release claim or a test of every PlanMaker edition. Three numeric examples were checked with an independent arithmetic model. No native application run was performed. Single-value population edge cases, mixed-data coercion, exact error-code parity and round-trip workbook compatibility remain untested; they are not labelled application-verified.