Outcome. When a renewal deal's contract value tier changes mid-cycle, the owner gets a task to re-forecast the deal, so the number carried into pipeline reviews reflects the account's current standing instead of a stale tier set at deal creation.
Workflow map
Enrollment, branches and actions at a glance
renewal-expansion-047
flowchart TD
A[Contract Value Tier changes on an open Renewal deal] --> B[Set Re-forecast Requested Date = today]
B --> C[Create re-forecast task for owner]
C --> D[Notify owner]
When to use it, when not to
- UseUse it when accounts are grouped into value tiers (for reporting, for support SLAs, or for pricing bands) and a tier change mid-renewal-cycle should prompt a manual amount review rather than being silently absorbed into the existing forecast.
- UseUse it alongside renewal-expansion-040's weighted forecast rollup; this fiche is the trigger that catches a tier change, that one is the ongoing calculated number.
- SkipDo not use it if
Contract Value Tiernever changes after a deal is created in your process; a property that is set once and never revisited does not need a change-triggered workflow. - SkipDo not use it as an automatic amount correction; this fiche flags the need for a human to re-forecast, it does not recalculate the amount itself, since a tier change does not map to a single deterministic dollar figure without a person's judgment.
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.3 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 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 renewal and expansion 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.
