Flag rules define when a metric raises a diagnostic flag — the amber and red thresholds that tell clients and partners something needs attention. You configure these per pillar in the framework editor. This guide covers flag rule configuration.
💡 Tip — Who can use this For platform admins, in a system framework's editor.
Quick reference
| Step | Action |
|---|---|
| 1 | Add or edit flag rules per pillar |
Step 1 — Configure flag rules
In the framework editor, each pillar has a Flag Rules section. Each rule defines:
- The metric it watches (chosen from scoreable keys).
- The amber threshold — the value at which a "watch" flag is raised.
- The red threshold — the value at which an "act now" flag is raised.
- The direction — whether the flag triggers when the metric is below (e.g. margin) or above (e.g. churn) the threshold.
- The benchmark reference value.
- The unit and a commentary string shown on the client dashboard when the flag fires.
You can add new rules or remove existing ones per pillar.
📝 Note — Rules drive the flags clients see These rules are what produce the amber and red flags on client dashboards. A rule with a poorly-set threshold will either cry wolf (too sensitive) or miss real issues (too lenient). Tune them based on what's genuinely concerning for each metric.
💡 Tip — Direction matters Most health metrics flag when they drop below a threshold (lower is worse). But metrics like churn, attrition, or time-to-fill flag when they rise above a threshold (higher is worse). Double-check the direction when you create a rule — a reversed direction will silently suppress real flags.