Contact
12 programs
Explore the site

IFS in SoftMaker PlanMaker: Test Multiple Conditions in Order

Logical Intermediate SoftMaker PlanMaker 2026

Learn IFS with ordered conditions, a TRUE default, stock status classifications, #N/A troubleshooting and version-specific SoftMaker notes.

Verification status: Official documentation referenced; example outcomes independently reasoned or arithmetically checked where stated. Not executed in SoftMaker PlanMaker 2026. How formula examples are checked

Quick answer: =IFS(B2>=C2,"Complete",B2>0,"Partial",TRUE,"Not started") has expected result Partial for B2=8 and C2=10: the first condition is false, the second is true, and the function returns that branch. IFS checks test/result pairs in order and chooses the first match. SoftMaker PlanMaker 2026 IFS reference.

IFS is useful for turning numerical measurements into understandable categories such as stock status, performance tier or review priority. Order the rules intentionally: a broad earlier condition can prevent a later, more specific condition from ever being selected.

Exact official syntax and parameter order

=IFS(Condition1, Value1 [, Condition2, Value2 ...])
Argument Required? Type / practical meaning Default
Condition1 Yes A logical condition or expression, such as C2=0 or B2>=C2. None.
Value1 Yes Text, number, or result that should be returned when Condition1 is true, such as "Invalid target". None.
Condition2, Value2 Optional pair Second test and its associated return value. Every additional condition must be paired with its result. No extra test if omitted.
Further pairs Optional More ordered tests and results. SoftMaker’s individual function page does not specify a numeric pair limit. None.

Critical rule: the function returns the first Value whose matching Condition is true. If none of the provided tests succeeds, the official PlanMaker documentation says IFS returns #N/A. There is no automatic “otherwise” branch. You can add TRUE,"Other" last to supply your own default, because that condition is always satisfied if earlier tests fail.

Square brackets in the manual are notation for optional arguments, not characters to enter. A leading = starts a cell formula. The commas reflect SoftMaker’s English-language syntax; regional settings, decimal separators and argument entry should be checked in your actual installation’s Function dialog. Native locale combinations have not been tested in this batch.

Practice dataset: delivery-status classification

Create a blank worksheet and enter the following values in columns A–C.

Row A: Item B: Delivered C: Ordered
2 Pens 8 10
3 Paper 6 0
4 Tape 12 12
5 Clips 3 5
6 Folders 0 4

Our policy classifies orders with a zero target as invalid, fully delivered orders as complete, partially delivered orders as partial, and otherwise as not started. This is a business rule created for the tutorial, not a universal PlanMaker rule.

Example 1: test the first satisfied rule

  1. Enter the sample table.

  2. Select E2 and type:

    =IFS(C2=0,"Invalid target",B2>=C2,"Complete",B2>0,"Partial",TRUE,"Not started")

  3. Compare each condition in sequence: C2=0 is false (10≠0); B2>=C2 is false (8<10); B2>0 is true (8>0).

  4. Expected E2: Partial. The final TRUE branch is not selected because an earlier condition has matched.

Example 2: copy down and check the order of tests

Copy the formula from E2 through E6 so references update by row. The outputs below are independently calculated expected outcomes.

Row Check in the rule order Expected E-cell result
2 Target 10, delivered 8; partial match Partial
3 Target 0; first condition immediately true Invalid target
4 Target 12, delivered 12; second condition true Complete
5 Target 5, delivered 3; third condition true Partial
6 Target 4, delivered 0; earlier tests false; fallback TRUE Not started

Put the invalid-target check before the Delivered >= Ordered check. If C3=0 were tested by a B3>=C3 rule first, the row would be incorrectly labeled complete under this example’s policy (6>=0 is true).

Example 3: understand the #N/A case

In F6, omit the always-true fallback and use:

=IFS(C6=0,"Invalid target",B6>=C6,"Complete",B6>0,"Partial")

With B6=0 and C6=4, no condition is true, so the expected result is #N/A. This is the documented normal outcome when all IFS conditions fail—not necessarily a corrupt spreadsheet. Restoring TRUE,"Not started" provides an explicit default. You could also wrap IFS with IFNA where a missing match truly means “unclassified,” but this guide uses the vendor’s recommended TRUE branch instead.

Advanced example: prioritize exceptions over regular scoring

Suppose you must assign review priorities to orders using two columns. The rule is: invalid or missing targets first; then completed orders; then in-progress orders; finally untouched orders. Use:

=IFS(C2<=0,"Fix order target",B2>=C2,"Close order",B2>0,"Follow up",TRUE,"Not started")

This differs from the earlier formula because it treats negative order targets as invalid too. With C3=0, expected Fix order target. With B4=12 and C4=12, expected Close order. With B6=0 and C6=4, expected Not started. If your source can also contain blank or text values, add explicit validation to your data-entry process; these sample cases assume real numbers.

Why condition order changes results

Consider B4=12, C4=12 and this poorly ordered rule:

=IFS(B4>0,"Anything delivered",B4>=C4,"Complete",TRUE,"Other")

Expected result: Anything delivered, not Complete: the broad first test 12>0 succeeds, so the later completion rule is never chosen. Put the more specific rule first:

=IFS(B4>=C4,"Complete",B4>0,"Anything delivered",TRUE,"Other")

Expected result: Complete. This behavior is the core reason to review IFS conditions in their exact order.

Common mistakes, limitations and fixes

Symptom Why it happens Correction
#N/A when the input appears valid All supplied conditions are false; there is no matching rule. Provide an explicit final TRUE,"Other" pair when a fallback is appropriate.
Unexpected category despite later true condition A broader earlier test already matched. Reorder rules from exceptional/specific to ordinary/general.
#NULL! Incomplete argument pair, wrong punctuation, misspelled function or invalid parentheses. Check pairs, straight quotation marks, and the PlanMaker Function dialog; see the official error guide.
Complete shown for a zero target A test like B2>=C2 counts nonnegative delivered quantity as at least zero. Put C2=0 or C2<=0 validation before completion.
A quoted condition seems not to test anything Boolean expressions such as B2>0 should be written as tests, not arbitrary descriptive text. Use a valid logical expression and quote output labels such as "Partial".
Copy-down results refer to row 2 Absolute references or copied constants froze the input. Use row-relative references B2, C2 when filling down.
Works in new Excel but fails in older Excel Excel introduced IFS later than many familiar formulas. Consult version compatibility below or use a compatible nested-IF design where required.

Other cautions: the individual SoftMaker manual does not specify an argument-count ceiling, so this page does not invent one. IFS by itself is not an error trap for malformed input or for unrelated expression errors. It chooses conditions, not data cleansing. A value such as 0 may be valid input even though some policy uses it as a special case.

PlanMaker releases, platform scope and Excel differences

Product or format Authoritative documentation finding Unknown / caution
PlanMaker 2021 Official help has an IFS entry and examples calling IFS(...), with the same first-match and no-match behaviors. The syntax line on that 2021 help page begins IF(, contradicting its IFS heading and worked examples. This appears to be a documentation typo; we do not treat IF(...) with many pairs as supported IFS syntax.
PlanMaker 2024 The help syntax line correctly shows IFS(Condition1, Value1 [, Condition2, Value2 ...]). Native version/build and platform-specific runs not performed.
PlanMaker 2026 The same IFS syntax, first true branch, #N/A on no match, and TRUE default are documented. Exact edition/mobile behavior and first-ever PlanMaker release are not established.
Microsoft Excel 2019 and later SoftMaker’s official compatibility note says Excel supports IFS only starting with Excel 2019. Do not assume identical locale settings or all export behavior.
Excel before 2019 The manual says IFS is unknown to earlier Excel releases. Use a deliberately tested alternative, such as nested IF, if older Excel compatibility is required.

Important 2021 editorial finding: The official 2021 IFS help page has the printed syntax IF(Condition1, Value1 [, Condition2, Value2 ...]), but its title, description, examples and all later manuals consistently identify IFS. This guide reproduces the correct 2024/2026 syntax and records the 2021 inconsistency openly rather than silently claiming that 2021 had a different named function. The availability of a 2021 help entry is not proof of its initial release year.

Official sources accessed October 11, 2026:

Official reference and verification

Verification status: Official documentation checked; example outcomes were independently reasoned or arithmetically checked where applicable. Not executed in SoftMaker PlanMaker.

  • No genuine SoftMaker PlanMaker screenshots are included; this guide does not use mock application images.