Policy X date renewal cascade at 90, 60 and 30 days before expiration

Outcome. Every policy in force works its own renewal calendar: the producer gets three tasks timed off the policy expiration date, the path changes with the line of business, and the insured hears from the agency before the carrier's renewal offer lands in their mailbox.

Workflow map Enrollment, branches and actions at a glance insurance-001

flowchart TD
    A[Enroll: in force policy with an expiration date] --> B[Delay to 90 days before]
    B --> C{Line of business}
    C -->|commercial| D[Review task to producer]
    C -->|personal| E[Re rate task to producer]
    D --> F[Flag contact for renewal notice email]
    E --> F
    F --> G[Delay to 60 days before]
    G --> H{Renewal settled?}
    H -->|yes| Z1[Exit]
    H -->|no| I{Loss ratio above 60?}
    I -->|yes| J[Remarket task and notify producer]
    I -->|no| K[Follow up task]
    J --> L[Delay to 30 days before]
    K --> L
    L --> M{Quoted or settled?}
    M -->|yes| Z2[Exit]
    M -->|no| N[Urgent call task, notify principal]
    N --> O[Delay to expiration date]
    O --> P{Renewed?}
    P -->|yes| Z3[Exit]
    P -->|no| Q[Set status Expired, notify principal]

When to use it, when not to

• UseUse it as the backbone of the kit. Each policy has its own expiration date, so a renewal cadence anchored on the company record is wrong as soon as a household holds two policies with different X dates.
• UseUse it on an agency with more than a few hundred policies in force, where a spreadsheet of expiration dates is already out of date.
• SkipDo not use it to talk to a prospect about their current carrier's expiry. That is a different date, competitor_renewal_date on the contact, and a different workflow (lead-nurturing-035).
• SkipDo not run it on Professional without the Policy object. There is a workable Professional shape in Variants, but it trades one policy per renewal for one account per renewal, and every multi policy household will feel it.