| John Bosman | 1,050 words
Two liability policies can carry identical limits, identical premiums, and the same carrier name on the declarations page — and still respond in completely different ways to the exact same incident, because of one structural difference most business owners never think about until it matters: whether the policy is written on a claims-made basis or an occurrence basis. This distinction shows up constantly in professional liability, EPLI, cyber liability, and management liability lines, and it's one of the most common sources of an unpleasant surprise — not because the coverage was bad, but because the timing rules weren't understood before a policy changed.
Short answer
Claims-made and occurrence policies respond to the same incident differently depending on timing — and that difference only becomes visible at the worst possible moment, when a claim is filed after a policy has changed.
Reader checkpoint
- Do you know whether your professional liability, EPLI, or cyber policy is written claims-made or occurrence — not just "covered," but which structure?
- If you switched carriers or let a claims-made policy lapse, do you know what would happen to a claim filed today about something that happened two years ago?
- Do you know what your policy's retroactive date is, and whether it's ever been reset by a coverage change?
Quick answer
An occurrence policy covers incidents that happened during the policy period, no matter when the claim is filed — even years later. A claims-made policy covers claims filed while the policy is active (or during an extended reporting period), regardless of when the underlying incident occurred — which means switching carriers, letting a policy lapse, or simply not renewing can leave past conduct completely uncovered unless tail coverage is in place.
At a glance
| Main issue | Claims-made and occurrence policies respond to the same incident differently depending on timing — and that difference only becomes visible at the worst possible moment, when a claim is filed after a policy has changed. |
|---|---|
| Common blind spot | Assuming a policy is "covered" without knowing which structure applies — the two aren't interchangeable, and a gap in coverage type can mean a legitimate claim gets denied entirely. |
| Useful document | The current policy's declarations page, specifically looking for the words "claims-made" or "occurrence," plus the retroactive date if the policy is claims-made. |
| Best next step | Ask your agent to confirm, in writing, which structure applies to each liability policy you carry — and if any are claims-made, what happens to coverage if that policy is ever replaced or not renewed. |
Defined Q&A
Claims-Made vs. Occurrence Coverage Explained: Why the Trigger Date Matters More Than the Premium: common questions
Is claims-made coverage worse than occurrence coverage?
Not inherently — many important lines like professional liability, EPLI, and cyber are commonly written claims-made, and that's standard, not a red flag. The risk isn't the structure itself, it's not understanding the timing rules before a policy changes.
What happens if I switch carriers on a claims-made policy?
It depends on whether the new policy's retroactive date reaches back far enough to cover prior incidents, or whether tail coverage is purchased on the old policy. Without one of those, a claim about something that happened under the old policy could have no coverage to respond to it.
Do I need tail coverage if I'm just retiring or closing my business?
Often yes, if any of your liability coverage is claims-made — closing the business doesn't stop a claim from potentially being filed later about past work. This is worth discussing specifically as part of any wind-down or ownership transition.
How do I know if my policy is claims-made or occurrence?
It should be stated clearly on the declarations page or in the policy form itself — if it's not obvious, that's a direct question worth asking your agent rather than assuming.
Start a coverage review, or read about professional liability and EPLI for the two lines where this distinction shows up most often.
What each structure actually means
An occurrence policy is tied to when the underlying incident happened, not when the claim shows up. If a covered incident occurred while the policy was active, that policy responds — even if the claim is filed five or ten years later, and even if the business no longer carries that policy or that carrier at all. A claims-made policy works differently: it responds to claims filed while the policy is active (or during a specific extended reporting window), based on when the claim is reported, not when the incident happened. A claims-made policy typically only covers incidents that occurred on or after its "retroactive date" — so both the filing timing and the incident timing matter, in different ways, for the two structures.
Why this matters most at the moment of change
The real risk with claims-made coverage isn't while the policy is active and unchanged — it's at the transition points. Switching carriers, letting a policy lapse, retiring, closing a business, or simply choosing not to renew can all leave a gap: if a claim about past conduct is filed after a claims-made policy ends, and no tail coverage or new policy's retroactive date reaches back far enough to cover it, that claim may have nowhere to land. This is precisely the scenario an occurrence policy doesn't create, since it stays tied to the incident date regardless of what happens to the policy afterward.
What tail coverage actually does
Tail coverage — formally an "extended reporting period" endorsement — extends the window during which claims can still be filed against a claims-made policy that has ended, for incidents that occurred while it was active. It doesn't extend the policy itself or add new coverage going forward; it only preserves the ability to report claims about the past. This becomes directly relevant at business transitions: selling a business, retiring, switching to an occurrence-based carrier, or simply changing professional liability carriers can all leave a gap in the window that a prior claims-made policy would have covered, unless tail coverage is purchased to bridge it.
Where this shows up most often
This distinction is most relevant on professional liability, where claims-made forms are common and the gap between when advice is given and when a claim is filed can be years. It's also directly relevant to EPLI — many employment practices policies are written on a claims-made basis, and an employment-related claim can surface long after an employee has left. Cyber liability is another common claims-made line, since a data breach or intrusion is sometimes discovered long after it actually occurred. General liability, by contrast, is typically written on an occurrence basis — which is part of why this distinction can feel unfamiliar even to business owners who understand their other coverage well.
What to actually check, and when
The useful trigger isn't renewal — it's any point where a policy might change. Before switching carriers on a claims-made line, before letting any policy lapse, before retiring or selling a business, and before simply assuming a "gap year" without coverage is harmless, it's worth confirming: is this policy claims-made or occurrence, what's the retroactive date, and if it's ending, does tail coverage need to be part of that conversation. A program review that only confirms coverage limits without confirming this structural detail hasn't actually closed the loop on a claims-made line.
What to do next
Use the related tool or ask for a review before you make coverage changes.
Commercial Renewal Readiness Score | Start a Coverage Review | Professional Liability Insurance