Browse

PlanMaker 2026 · Formatting and validation · Beginner

Highlight Values Above a Threshold in PlanMaker

Create a PlanMaker 2026 conditional formatting rule for numeric thresholds and troubleshoot rules that do not apply.

Official documentation reviewed; native application verification pending · Updated 10 October 2026 · Editorial standards

Conditional formatting changes the appearance of cells without changing their underlying values. It’s useful for flagging expensive orders or stock levels outside a normal operating range.

Example: flag amounts above 100

Enter the following values in B2:B5: 92, 105, 130, and 87. Only 105 and 130 should receive the highlighted style when the rule is greater than 100. The boundary matters: 100 itself would not match a strict greater-than rule.

Create and inspect the rule

  1. Select the four numeric cells; do not include a text heading.
  2. Open Home → Format → Conditional formatting → New rule.
  3. Choose a condition equivalent to cell value greater than 100 and select a readable highlight (such as a pale red fill with dark text).
  4. Confirm and verify that 105 and 130 change appearance, but 92 and 87 do not.
  5. To adjust it, open Conditional formatting → Manage rules. SoftMaker documents an Apply to range, rule priority, and a dropdown that can show all rules for the current worksheet.

Two mistakes that cause confusion

Numeric text: A value that only looks like 105 may have been imported as text. Check its data type before assuming the rule is broken.

Conflicting rules: A second rule may request a different fill or text color. The rules manager has a priority order; use it to see which rule takes precedence.

Accessibility and readability

Avoid communicating critical information solely through red/green colors. Add a simple status column such as Over limit / Within limit if the value must also be readable by users with color-vision differences or when printed in grayscale.

See PlanMaker input validation for restricting entries rather than just highlighting them.

Verification: Boundary values were checked independently; ribbon and rule-manager behavior are supported by the vendor manual. Native screenshot confirmation is still pending.

Official documentation: Software manual or vendor release notes. This article is part of a staged content batch; confirm the interface and output in the stated software before public deployment.