GESTEP in WPS Spreadsheet: Count Inclusive Thresholds and Build Nonoverlapping Bands

• Introduced: documented by 2019-05-06 in WPS material; the first release is not established.
• Availability: the Windows Personal lesson explicitly demonstrates WPS 2019.
• Scope: exact supported builds and other WPS clients remain unverified.
• Checked: October 14, 2026. Documentation and independent examples; no native WPS execution.

=GESTEP(number,[step])

Number is required; step is optional and defaults to zero. The May 6, 2019 Windows Personal lesson explicitly demonstrates WPS 2019 and a passing score threshold of sixty.

Although one sentence describes counting values “over” a threshold, the formal definition and walkthrough both include equality. This guide therefore treats the test as greater than or equal to, not strictly greater than.

The returned flag is numeric one or zero. It does not modify the input, round it to an integer or supply a verbal pass/fail label by itself.

Enter 59, 60, 72, 85 and 100 in A2:A6. Put the threshold 60 in F2. In B2 enter:

=GESTEP(A2,$F$2)

Fill through B6. Expected results are:

The dollar signs keep F2 fixed when the formula is copied. Without them, the threshold reference would shift to F3, F4 and later cells, no longer testing every row against the same stated value.

=SUM(B2:B6) gives four qualifying records. =IF(B2=1,"Pass","Review") filled down produces Review, Pass, Pass, Pass and Pass.

Change F2 to 75. Expected flags become 0, 0, 0, 1 and 1, and their sum becomes two. The input scores stay unchanged.

This is a useful separation between data and policy: the threshold lives in one labelled cell, and every copied formula refers to it. Keep the threshold’s meaning visible rather than embedding an unexplained constant in many different formulas.

The IF labels are an optional presentation layer. Numeric flags remain convenient for a separate count with SUM.

For actual numeric inputs −2, 0 and 3, =GESTEP(value) has expected results 0, 1 and 1, respectively. Writing =GESTEP(value,0) makes the same documented threshold explicit.

Zero itself qualifies because the comparison is inclusive. This is a sign-threshold test, not a count of nonzero values.

These controls use real numeric values. They do not infer how a blank reference, the text “0” or a logical value is coerced.

A band should include scores from sixty up to, but not including, eighty-five. For the original A2:A6 data, use:

=GESTEP(A2,60)-GESTEP(A2,85)

Filled down, expected flags are 0, 1, 1, 0 and 0, counting two records. The first step turns on at sixty; the second removes the values at or above eighty-five.

Explicit boundary controls make the interval clear:

The upper endpoint is excluded even though both individual GESTEP tests use inclusive comparisons. Use an ordered lower and upper threshold; reversing them can create negative differences rather than a sensible band indicator.

Restore F2 to sixty. Enter weights 2, 3, 1, 4 and 2 in C2:C6. In D2 calculate =B2*C2 and fill down.

The expected weighted contributions are 0, 3, 1, 4 and 2, summing to ten. There are still only four qualifying rows. The weighted total describes the associated quantities, not the number of qualifying records.

Keep the flag and weight in separate columns so the calculation is auditable. If a weight is missing, negative or otherwise invalid for the business purpose, GESTEP’s score comparison alone will not validate that weight.

The official lesson explicitly assigns #VALUE! when either argument is nonnumeric. It does not separately settle every numeric-looking text, Boolean, empty-reference or competing-error case, so those conversions are not assumed here.

The formulas compare stored numeric values. Display rounding can make two nearby values look equal even when a threshold comparison distinguishes them. These examples avoid a native floating-point boundary dispute and retain actual numeric inputs.

The historical WPS 2019 demonstration is documented availability, not proof of the original introduction or the final supported version. All new outputs are independently calculated expectations, with no native WPS execution.

• WPS Academy: GESTEP, 2019-05-06 (Chinese).
• Editorial testing standards.

Complete function-specific sources reviewed. Expected results are independently derived controls, not native application captures. Formulas use English names and comma separators; check the installed locale.