=OR(Value1 [, Value2, Value3 ...])

The square brackets indicate optional arguments in the official syntax; do not type them. The PlanMaker OR reference does not publish a numeric maximum argument count, so Excel’s limits are not presented as PlanMaker limits. OR(TRUE,FALSE) is TRUE; OR(FALSE,FALSE) is FALSE.

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. Create the practice table. Put TRUE and FALSE in column D as logical values.

2. Select blank cell G3.

3. Enter:

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

4. Expected G3: TRUE. Row 3 has 3 units against 6 needed: B3<C3 is TRUE. NOT(D3) is FALSE because the order is approved. At least one is TRUE, so OR is TRUE.

5. For row 2, change references to 2; both shortage and missing approval are FALSE, so the result is expected FALSE.

Manual check: =OR(FALSE,FALSE) is expected FALSE and =OR(TRUE,FALSE) is expected TRUE, agreeing with SoftMaker’s official examples.

Create an explicit review label rather than leaving a standalone TRUE/FALSE value:

=IF(OR(B3<C3,NOT(D3)),"Review order","No exception")

Expected: Review order for Adapter (row 3). Copy down using relative references. On Cable (row 2), the analogous formula is expected No exception. This makes the output understandable in an operations queue, but it is a demonstration and not an automatic approval decision.

A second use is checking membership in a small allowed-region list:

=OR(E2="North",E2="East")

Expected TRUE for row 2 (North); expected FALSE for row 5 (West). For longer lists, a lookup or counting method may be easier to maintain; this example only illustrates two allowed values.

• OR means one or more, not exactly one. =OR(TRUE,TRUE) is TRUE. Don’t use OR to assert that exactly one condition applies.
• Write separate complete expressions: =OR(E2="North",E2="East"), not =OR(E2="North" OR "East").
• For an issue flag based on a missing approval, use NOT(D3) only when D3 contains an actual TRUE/FALSE value. Do not assume text flags or blanks are coerced identically across spreadsheet programs.
• OR is a logical test, not a sum or count. To count rows satisfying conditions, a different aggregation function and carefully defined logic are needed.

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
• OR — PlanMaker 2024
• OR — 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.