A renewal window is a sequence of owned states.
A calendar reminder says a date is approaching. A renewal workflow says what has happened, what is missing, who owns it, and what must happen next. Use states such as upcoming, data requested, waiting on insured, ready for review, marketing or carrier action, proposal ready, producer review, presented, decision pending, bound, lost, and closed.
Set the renewal window by line, account complexity, carrier lead time, and agency practice. One universal "60-day reminder" is simple but often wrong. The trigger should create a work plan and evidence checklist, not just an email.
| State | System work | Owned decision |
|---|---|---|
| Upcoming | Create the renewal record from current policy facts | Assign account owner and review due date |
| Waiting on insured | Track requested items and send approved reminders | Staff resolves unclear or changed operations |
| Ready for review | Assemble current terms, changes, claims data, and missing items | Licensed staff confirms the path |
| Proposal ready | Prepare versioned presentation materials | Producer approves what is presented |
| Decision pending | Record open questions and next contact date | Producer handles advice and client decision |
Ask for changed facts, not the entire account again.
Use the current record to prefill what the agency already knows, then ask the insured to confirm or update the facts relevant to the renewal. Track each requested item separately. "Waiting on client" is not useful when nobody can see whether the missing item is payroll, locations, drivers, certificates, loss runs, or a signature.
Responses that indicate changed operations, new locations, material growth, a claim concern, or an unclear answer should enter an exception queue. The workflow can highlight the change. Licensed staff decides what it means and what additional information or coverage discussion is required.
Keep producer control visible.
Automation can prepare the file, schedule tasks, draft factual reminders, and show aging. It should not choose coverage, promise terms, compare options as advice, or bind anything. The producer needs the original data, a clear change summary, document versions, carrier status, and the client's open questions.
Build stop rules for bound, lost, non-renewed, moved, or manually paused accounts. If a producer is actively working an issue, ordinary reminders should stop. The system should not compete with the relationship owner.
Owner view: Organize renewals by state and risk: files not started inside the required window, missing client information, carrier action overdue, proposals awaiting producer approval, and decisions approaching expiration.
Prove one renewal lane end to end.
- Select one line or account segment with consistent milestones.
- Map current renewal states, evidence, owners, and carrier handoffs.
- Define the facts to confirm and the conditions that require licensed review.
- Create a versioned renewal record tied to the existing account and policy identifiers.
- Add client requests and reminders that stop when the item is accepted.
- Build producer approval and exception handling before any automatic delivery.
- Compare the workflow against a small set of real renewals through close-out.
Measure renewals entering the window on time, days waiting by owner, incomplete files, remarketing or carrier deadlines missed, proposals ready before presentation, rework, and close-out reasons. A faster reminder cadence is not progress if licensed staff still receives an incomplete file at the last minute.