Outcome. An account whose contract end date has passed without a closed-won renewal enters a tracked grace period with a clear end date, instead of quietly staying active (or getting cut off) with no record of the decision.
Workflow map
Enrollment, branches and actions at a glance
renewal-expansion-036
flowchart TD
A[Contract End Date passed, no resolution yet] --> B[Set Grace Period Status = Active]
B --> C[Set Grace Period End Date = Contract End Date + 30 days]
C --> D[Create task + notify owner]
D --> E[Wait until Renewal deal Closed Won, cap = Grace Period End Date]
E --> F{Closed Won in time?}
F -->|Yes| G[Set Grace Period Status = Resolved - Renewed]
F -->|No| H[Set Grace Period Status = Expired - Deactivated]
H --> I[Create deactivation task, notify manager]
When to use it, when not to
- UseUse it for accounts where product or service access is not cut off the instant a contract expires, and the business allows a defined grace window to finish the renewal conversation.
- UseUse it as the natural follow-on to renewal-expansion-001: once a renewal deal exists but has not closed by the contract end date, this fiche tracks what happens next.
- SkipDo not use it for accounts on strict prepaid or auto-cutoff models where access ends automatically at the contract date; there is no grace period to track.
- SkipDo not use it as a substitute for renewal-expansion-018's Closed Lost automation; that one reacts to a confirmed non-renewal, this one reacts to an unresolved renewal that is running late.
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.5 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.10 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 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.
