=NOT(Value)

SoftMaker explicitly states that Value must be a logical value or a calculation producing one. There is no optional second argument in the documented syntax. NOT(TRUE) is FALSE and NOT(FALSE) is TRUE. For multiple tests first combine them using AND or OR, then apply NOT to the combined result.

Enter the following records into a new, empty PlanMaker worksheet, with headers in row 1. Put real numeric values in B and C and actual logical values TRUE or FALSE in D (not quoted text). All formulas below refer to these exact positions.

1. Enter the worksheet shown above, ensuring D2:D7 contain Boolean constants, not words stored as text.

2. Select an empty result cell, for example G4.

3. Enter:

   =NOT(D4)
   

4. Expected G4: TRUE. Charger is marked FALSE in D4, so logical negation is TRUE.

5. Repeat with the other rows:

Second direct check: =NOT(B2<C2) is expected TRUE, because 8<5 is FALSE. This is not the same as asking whether the order is approved.

=IF(AND(NOT(D4),B4>=C4),"Manager approval required","Other")

Expected result: Manager approval required for Charger. Reason: NOT(D4) is TRUE (not approved), and 12>=8 is TRUE (sufficient stock), so AND returns TRUE and IF selects the manager-review message. For row 3 the analogous formula is expected Other, because D3 is TRUE and the shortage does not satisfy both conditions.

Negating a compound statement: if you need to ask whether an order has no exception, combine OR then negate:

=NOT(OR(B3<C3,NOT(D3)))

Expected FALSE for Adapter because a shortage exists. In contrast, for Cable use row-2 references and the result is expected TRUE (no shortage and approved). This is the practical relationship between NOT, AND and OR; grouping parentheses matter.

• NOT does not mean the text "not". The argument must evaluate to a logical condition; a quoted string is not automatically a boolean test.
• Do not supply two conditions as =NOT(B4<C4,D4). It has only one argument. Combine the conditions inside AND(...) or OR(...) first.
• =NOT(B2<C2) inverts a comparison, but if the underlying cell has an imported error, it is not a magic error-repair function.

1. Start with =. Without it, PlanMaker may interpret the entry as text. See SoftMaker’s formula basics.
2. Use comparisons that return logical values. For example, B2>=C2 is a test; writing "B2>=C2" is only a text string. TRUE and FALSE are logical constants, while "TRUE" and "FALSE" are text. This tutorial uses tested-by-reasoning comparisons and literal logical cells; it does not assert how arbitrary text is coerced.
3. Check row alignment and boundaries. B2>=C3 accidentally compares different orders. Verify cell addresses before assuming the formula is wrong.
4. Use English-manual argument separators as shown. The documented function syntax and examples use commas. The input/array separators shown in other manual sections can depend on regional configuration. For a different locale, use the installed PlanMaker function dialog to confirm the expected separator; no localized configuration was executed for this guide.
5. Keep calculations and business policy distinct. A logical result answers exactly the expression you wrote, not whether your workflow is sensible. Row 5 has no requested units, so a production release rule should also check C5>0.
6. Do not guess a precise error message for unchecked input. If a formula produces an error instead of TRUE/FALSE, test each referenced comparison in its own blank cell, inspect types and references, and use PlanMaker’s formula-auditing tools. Exact errors for malformed text or platform-specific coercion were not observed in native PlanMaker.

Cross-software caution: Microsoft Excel, Google Sheets and LibreOffice Calc also implement logical AND/OR/NOT patterns, but exact local separators, text-coercion, blank-cell behavior, argument ceilings, and imported workbook fidelity require testing in each application. Avoid claiming a complete compatibility guarantee from similarly named functions.

• IF guide in the owner’s 2026-10-10

• SoftMaker PlanMaker — function documentation
• SoftMaker’s formula basics
• PlanMaker’s formula-auditing tools
• NOT — PlanMaker 2024
• NOT — PlanMaker 2021

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.