The Workflow Library

Library / Deal hygiene / deal-hygiene-044

Manual probability override flagged for review

Deal hygieneDealSales Hub ProfessionalIntermediate~35 min to buildFull spec

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.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-044
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]
action or delay branch public on every spec, paid or not

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.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.5 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

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.