The Workflow Library

Library / Deal hygiene / deal-hygiene-045

Closed-lost deals excluded from active forecast rollup

Deal hygieneDealSales Hub ProfessionalSimple~20 min to buildalso needs Marketing Hub ProfessionalFull spec

This spec is filed under Sales Hub Professional, and one of its steps belongs to another subscription: remove from static list needs Marketing Hub Professional. Both are required to build it as written.

Outcome. The moment a deal closes lost, it drops out of the active-forecast static list and any "included in forecast" flag clears, so a dashboard or export built on list membership does not keep counting it after the fact.

Workflow map Enrollment, branches and actions at a glance deal-hygiene-045
flowchart TD
    A[Deal stage becomes Closed Lost] --> B[Remove from Active forecast static list]
    B --> C[Set Excluded From Forecast Rollup = true]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it if any report, dashboard, or export in your portal reads from static list membership rather than filtering live on Deal stage, list membership does not update itself just because a deal's stage changed.
  • UseUse it together with deal-hygiene-039's quarter-end snapshot, a deal captured mid-quarter and then lost before the next snapshot should not still read as "active" in whatever downstream view consumes that snapshot.
  • SkipDo not build this if every forecast view in your portal already filters live on Deal stage directly (excluding Closed Lost natively), in that case there is no static list to maintain and this fiche adds nothing.
  • SkipDo not confuse this with deal-hygiene-005's forecast category field, that fiche sets a category label on every stage change, this fiche specifically manages list membership for tools that need it.
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.2 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.2 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.