Policy endorsement: carrier chase, premium recalculation and notice to both sides

Outcome. A mid term policy change is tracked from request to issued document: the carrier gets chased on a schedule, the policy record carries the new premium instead of last year's, and the producer and the insured are both told what changed.

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

flowchart TD
    A[Enroll: endorsement requested] --> B{Cancellation?}
    B -->|yes| C[High priority call task to producer, exit]
    B -->|no| D[Priority from effective date]
    D --> E[Task to desk, notify producer]
    E --> F[Wait for carrier, max 3 days]
    F --> G{Still pending?}
    G -->|yes| H[Chase task]
    G -->|no| I[Wait for carrier, max 7 more days]
    H --> I
    I --> J{Issued?}
    J -->|declined or withdrawn| K[Notify producer, close]
    J -->|still pending| L[Escalate, leave open]
    J -->|yes| M[Custom code: recalculate policy premium]
    M --> N[Confirmation email to the insured]
    N --> O[Close ticket]

When to use it, when not to

• UseUse it on any book where policies change between renewals, which is every commercial book and most personal auto books. Added vehicles, new locations and limit changes are the everyday traffic of a service desk.
• UseUse it when the agency has discovered, at renewal, that its own records show a premium the insured stopped paying eight months ago.
• SkipDo not use it for a cancellation. Cancel policy is in the dropdown so the request can be caught, but the branch sends it to a retention conversation instead of processing it quietly. Cancelling on autopilot is how an agency loses an account it could have kept.
• SkipDo not use it as a substitute for the agency management system. This tracks the request and stamps the outcome. The carrier portal is still where the endorsement is actually issued.