PlanMaker PERCENTRANK.INC: Percent Positions versus Ordinal Ranks
Compare PlanMaker percentile positions, ascending ranks and numeric range fractions with reproducible score examples and explicit calculation limits.
Verification status: See the evidence and test scope described in this guide. How formula examples are checked
PERCENTRANK.INC expresses a value’s position in a dataset on an inclusive 0-to-1 scale. SoftMaker documents the minimum as 0, the maximum as 1 and the middle value in its nine-number example as 0.5. It returns the same result as the still-documented PERCENTRANK name.
Availability and version history
- Introduced: Documented by the PlanMaker 2018 manual; the original introduction release and date are not established.
- Availability: Documented in PlanMaker 2026. This checked version is not a final supported-version endpoint.
- Scope: Current reference belongs to the PlanMaker 2026/NX manual family. FreeOffice and individual mobile-build availability are not established here.
- Checked: October 14, 2026, against the official PERCENTRANK.INC reference and historical manual. Additional calculations are explicitly scoped models; no native PlanMaker test was performed.
Syntax, interpolation and precision
PERCENTRANK.INC(Range, Number [, Digits])
The official entry requires the numeric range and the query value. A query not present in the data is interpolated. The optional Digits argument defaults to 3, described in current help as decimal places in the calculated result.
The 2018 manual instead says significant digits and specifies at least one. This wording difference does not establish when behavior changed. The current short entry does not define truncation versus rounding, fractional counts or a complete error domain. The examples use positive integer digit counts and terminating fractions.
Check the official minimum, median and maximum
On VendorInclusive, put 1 through 9 in A1:A9 without a header. Enter =PERCENTRANK.INC(A1:A9,1) in C1, =PERCENTRANK.INC(A1:A9,5) in C2 and =PERCENTRANK.INC(A1:A9,9) in C3. The documented results are 0,0.5,1.
A result of 0.5 can display as 50%. Applying a percentage format does not mean the function returned 50, and changing display decimals does not redefine Digits.
Compare percent positions with ordinal ranks
Create ScorePositions, using A1:H13. Put Score, Inclusive position, Ascending rank and Position control in A1:D1. Enter nine distinct numeric scores in A2:A10:
| Row | A: Score | B: independent model expectation | C: ascending rank |
|---|---|---|---|
| 2 | 42 | 0 | 1 |
| 3 | 50 | 0.125 | 2 |
| 4 | 57 | 0.25 | 3 |
| 5 | 61 | 0.375 | 4 |
| 6 | 68 | 0.5 | 5 |
| 7 | 74 | 0.625 | 6 |
| 8 | 80 | 0.75 | 7 |
| 9 | 89 | 0.875 | 8 |
| 10 | 95 | 1 | 9 |
Enter =COUNT(A2:A10) in H2 for 9. In B2 enter =PERCENTRANK.INC($A$2:$A$10,A2,4), C2 =RANK.EQ(A2,$A$2:$A$10,TRUE) and D2 =(C2-1)/($H$2-1). Fill B2:D2 through row 10. The logical TRUE explicitly requests ascending rank in PlanMaker’s RANK.EQ reference.
For these unique observations, the independent position model is (rank-1)/(N-1). It is the inverse of NIST’s inclusive percentile position. The current PlanMaker entry supplies interpolation and endpoint examples, not its complete algorithm; B’s additional outputs are model expectations. D is an arithmetic control, not a universal replacement for the function, particularly with ties or a query absent from the data.
Interpolate a query that is not a score
On the same table, enter 71 in F2. In F3 enter =PERCENTRANK.INC(A2:A10,F2,4). Its independent model target is 0.5625: 71 is halfway between 68 and 74, whose positions are 0.5 and 0.625.
F4 =0.5+(F2-68)/(74-68)*(0.625-0.5) gives 0.5625 directly. F5 =PERCENTRANK(A2:A10,F2,4) is a documented-name comparison. Do not use RANK.EQ on 71 as the interpolation control: its entry documents #N/A when the query does not occur in the range.
Advanced: relative order is different from a percentage of the value range
Create DifferentScales, with A1:F6. Enter the known minimum 42 in B2, maximum 95 in C2 and query 68 in A2. In D2 enter =(A2-B2)/(C2-B2) for approximately 0.4905660377.
That is the query’s distance from the minimum divided by the total numeric span, 26/53. The independent percentile-position model gives 0.5 because 68 is the fifth of nine ordered observations. The two quantities differ because the scores are not evenly spaced.
For the separate query 71, use A3=71, B3=42 and C3=95. D3 =(A3-B3)/(C3-B3) is approximately 0.5471698113, while the interpolated percentile-position model is 0.5625. Keep both interpretations explicit when labeling a dashboard; neither is automatically an empirical probability or an assessment threshold.
Limits and related functions
Duplicate scores, all-equal data, one-item ranges, queries outside the numeric span, mixed types and exact runtime error tokens remain unverified. In particular, a tied RANK.EQ control cannot be assumed to reproduce PERCENTRANK.INC’s undisclosed tie treatment.
PERCENTRANK is documented as equivalent; PERCENTRANK.EXC assigns different endpoint fractions. PERCENTILE.INC goes in the other direction, from a chosen fraction to a data value. Only the stated complete numeric examples are checked here, without a native PlanMaker run.
Use the target locale’s separators. The official Excel 2010 compatibility note is scoped to Excel, not evidence of a PlanMaker introduction release or of identical precision in every imported workbook.