Good news can hide a problem. This workers’ compensation renewal is better for the client in every way the comparison can measure: employers liability limits doubled, the experience mod fell, the premium went down. Twenty-one of twenty-one checks match. And forty days after inception the carrier still hasn’t issued the policy — the client is holding a binder.
This post follows an illustrative check that has no issued policy yet, and the control that keeps it in view Illustrative.
| Insured | Penrose Botanical Gardens — a public garden with seasonal staff (illustrative) |
|---|---|
| Line | Workers’ compensation and employers liability, renewal |
| Documents | Expiring policy, quote, binder — no issued policy yet |
| Proofing | 21 of 21 checks match: the binder against the quote, its subjectivities, its term and continuity |
| Renewal changes | Employers liability each accident, disease each employee and disease policy limit $500,000 → $1,000,000; experience mod 0.96 → 0.91; premium $24,100 → $22,640 (−6.1%) |
| Control | Policy not delivered 30 days after inception — warn |
| Outcome | The check stays on the account executive’s home as late, with the carrier chased for the policy |
Proofing without a policy
Until the policy arrives, the engine proofs what it has: the binder against the quote, the binder’s subjectivities, and the derived checks run on the binder — term and continuity with the expiring. When the policy arrives, it is proofed against the binder and the check moves on.
term, continuity"] EX["Expiring"] --> C["Comparison"] B --> C POL["Issued policy
(not yet)"] -.-> P2{"Policy vs binder"} B -.-> P2 L["Days since effective > 30
and undelivered"] --> W["Late delivery
control: warn"] style POL fill:#fff8e8,stroke:#f4c77a,stroke-dasharray: 5 5 style W fill:#fff4e2,stroke:#e0851f
Step by step
Three documents in the file: expiring, quote and binder. The issued policy has not arrived.
21 of 21: employers liability limits, covered state, experience mod and premium all match between quote and binder; the payroll-by-class subjectivity is received.
Six changes, four broader (the three employers liability limits and the mod), two costing less.
The policy took effect more than 30 days ago and hasn’t reached the client: warn. The queue shows the effective date in red with the days undelivered.
Asks the carrier for the policy. When it arrives it is proofed against the binder before anything is delivered.
What the screens show
In the queue the first row is this check: Sep 19, 2026 · 40 days, undelivered — dates in the demo book are generated relative to the day it was seeded.
| Section | Hit | Outcome |
|---|---|---|
| Proofing control | Policy not delivered 30 days after inception | warn |
| Proofing control | Cover narrowed at renewal | pass |
| Proofing control | A high-severity check failed and is unresolved | pass |
For the account team
A late policy is a line on your home page, not a memory.
For broker IT
Proofing runs on whatever documents exist; the late-delivery control reads the days since the effective date.
For practice leadership
Undelivered policies are an E&O exposure of their own. This one is measured.
Questions we get asked
Can we deliver the binder summary instead?
The account team decides. The control’s own message says: chase the carrier or deliver what is checked.
Keep reading
The carrier correction loop
Four requests, one overdue, one acknowledged — and an endorsement that closes them.
Read article
Where InsightProofing sits in the broker suite
Placement hands it the binder; Xtract reads the PDFs; Pulse knows the client; Advocate inherits the policy.
Read article
The first ninety days, and how to measure it
One team, one renewal month, every action at ask first.
Read article