Claims-Made vs. Occurrence Policies: What’s the Difference?
If you’ve ever looked at a liability policy and felt confused by terms like claims‑made and occurrence, you’re not alone. These two policy types determine when coverage applies—and getting it wrong can leave you with an unexpected gap in protection. Let’s walk through how each works, highlight the key differences, and use a few real‑world examples to make things clearer.
Both policy types are designed to protect against similar risks. The main difference comes down to timing—specifically when an incident happens and when a claim is reported.
Occurrence Policies
An occurrence policy covers incidents that happen during the policy period, regardless of when the claim is filed—even years later. Even if the policy has expired, coverage still applies if the incident itself occurred while the policy was active.
General liability, auto liability, homeowners, and workers’ compensation policies are typically written as occurrence policies, as the covered causes of loss are generally distinct events.
Example:
A customer slips and falls in your store in 2026 while your occurrence policy is in force. The lawsuit isn’t filed until 2027, after the policy has expired. Because the incident occurred during the policy period, the claim is covered.
Claims-Made Policies
A claims‑made policy covers claims that are reported during the policy period if the incident happened on or after the retroactive date. Once the policy ends, coverage typically stops unless you’ve purchased an Extended Reporting Period (ERP). Professional liability (errors & omissions) and management liability (employment practices, directors & officers, fiduciary) policies are commonly written as claims-made as losses may be discovered in the future or over a period of time.
Example:
You have a claims‑made policy in place for 2025 with a retroactive date of 2023. A client later allegedly committed an error from 2025 but files the claim in 2026 after you canceled the policy and did not purchase an ERP. Because the claim was reported after the policy ended, it is not covered.
What is an Extended Reporting Period (ERP)?
An ERP, often called “tail coverage,” allows claims to be reported after a claims‑made policy has ended. ERPs can range from 30 days—sometimes included at no additional cost—to multiple years for an extra premium. Some insurance companies offer unlimited tails. ERPs are commonly purchased when a business closes, is sold, or changes insurance companies. They protect against claims stemming from past work that weren’t discovered until after coverage ended.
Key Dates That Matter
With claims‑made coverage, certain dates can make or break a claim. Understanding them is critical.
Prior Knowledge Date
The Prior Knowledge Date refers to any situation the insured knew—or should reasonably have known—could lead to a claim before the policy took effect. If a known issue isn’t disclosed, coverage may be denied, even if the claim is reported during the policy period.
Example:
You receive a client complaint in March then purchase a claims-made policy in April but don’t disclose the issue. If the complaint later becomes a lawsuit, coverage may be denied due to prior knowledge.
Prior & Pending Date
This date excludes any claims, lawsuits, or proceedings that began before a specified point in time—even if you weren’t aware of them at the time.
Example:
Your policy has a prior & pending date of January 1, 2022. A lawsuit filed in December 2021 is excluded, even if you weren’t served until later.
Retroactive Date
The retroactive date is the earliest point at which an incident can occur and still be eligible for coverage if the claim is reported during the policy period.
Example:
Your retroactive date is January 1, 2020. An error that occurred in 2019 will not be covered, even if the claim is reported today.
Full Prior Acts
When a policy includes Full Prior Acts, there is no retroactive date. Coverage can apply to claims arising from acts that occurred at any time in the past if all other policy conditions are met.
Example:
You purchase a claims‑made policy in 2026 with Full Prior Acts coverage. A claim arises from work you did in 2016. Because there’s no retroactive date restriction—and the claim is properly reported—it’s covered.
Important note: Full Prior Acts coverage still depends on meeting the Prior Knowledge and Prior & Pending requirements. Any known issues must be disclosed during the application process.
Important Considerations for Claims-Made Policies
Claims‑made policies can be an effective risk‑management tool—but only when their requirements are clearly understood and followed. One of the most critical responsibilities is disclosing any known circumstances that could reasonably result in a claim. Failing to do so can jeopardize coverage when you need it most.
Timely reporting is equally important. Even a small issue can escalate and waiting too long to report it may result in a denied claim. When in doubt, it’s always safer to report sooner rather than later.
Finally, think carefully about an Extended Reporting Period if claims‑made coverage is canceled, non‑renewed, or replaced. Without an ERP, claims that arise from past work—but are reported after coverage ends—may not be covered at all.
Understanding these details helps prevent coverage gaps and unpleasant surprises. Working closely with a knowledgeable, independent insurance agent can make all the difference in ensuring disclosures are complete, reporting requirements are met, and key decisions—like whether to purchase an ERP—are made with confidence.
To download a PDF version of this blog, please click here:
