Outcome. When a rep manually sets
Deal Probability (Custom) to a value that does not match
deal-hygiene-011's stage-based mapping, the deal gets flagged for a
manager's review, so forecast rollups do not quietly absorb an
unexplained override.
flowchart TD
A[Deal Probability (Custom) changes, not yet reviewed] --> B{Matches expected value for current stage?}
B -->|no, mismatch| C[Set Probability Override Flag = true]
C --> D[Notify manager]
D --> E[Create review task for manager]
B -->|yes, matches| F[Set Probability Override Flag = false, exit]

When to use it, when not to
- UseUse it once deal-hygiene-011 is live and reliably setting probability by stage, this fiche exists to catch deviations from that mapping.
- UseUse it as a review trigger, not a block, a rep may have a legitimate reason to override probability for a specific deal, this fiche surfaces the override, it does not reverse it.
- SkipDo not use it if reps are expected to freely adjust probability as part of normal forecasting judgment, in that case an override is the intended workflow, not an exception, and this fiche will generate constant noise.
- SkipDo not use it without first documenting the stage-to-probability mapping the same way deal-hygiene-011 does, this fiche's detection logic depends on knowing exactly what "expected" looks like for each stage.
or the deal hygiene pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





