Occurrence-based Policy
Written by Justin Goodman, CIC, CLCS, CISC, CEO and Co-Founder, Total CSR
Published: October 2, 2026 · Last reviewed: October 2, 2026
In plain language: An occurrence-based policy pays for injuries or damage that happen while the policy is active, even if the claim shows up years later. The key moment is when the harm occurred, not when the lawsuit lands on the insured's desk.
Technical definition: An occurrence-based policy, found in forms like ISO's CG 00 01, triggers coverage based on the date of the bodily injury or property damage, provided that date falls within the policy period. The carrier remains on the hook indefinitely for that occurrence, regardless of when the claim is reported.
Occurrence-based Policy at a Glance
| Attribute | Detail |
|---|---|
| Also known as | Occurrence form, occurrence policy, CGL occurrence coverage |
| Category | Liability policy trigger |
| Lines of business | Commercial General Liability, Umbrella/Excess Liability, Personal Liability |
| Industries most affected | Construction, manufacturing, real estate/habitational, product manufacturing |
| Related forms or endorsements | ISO CG 00 01 (Commercial General Liability Coverage Form) |
| Who bears the risk | The carrier on the risk during the policy period when injury or damage occurred |
| Common solution | Maintaining continuous occurrence coverage year over year with no coverage gaps |
| Also interacts with | Claims-made policies, retroactive dates, tail coverage, additional insured endorsements |
Key Takeaways
- An occurrence-based policy covers bodily injury or property damage that happens during the policy period, no matter when the claim is actually filed.
- Agencies rely on occurrence triggers constantly in construction and habitational risk, where latent damage like mold or structural defects can surface years after the work was completed.
- The most common misunderstanding is assuming a lapsed or non-renewed occurrence policy leaves a client without coverage; the old policy can still respond if the injury occurred while it was in force.
- A best practice is to document policy periods and carrier history carefully for every client, since proving which policy was in force on the date of injury can take years of retrieval work during a long-tail claim.
What Is an Occurrence-based Policy in Insurance?
An occurrence-based policy is the dominant form of commercial general liability coverage sold to businesses in the United States, built around ISO's standard CG 00 01 form. The policy exists to protect against the reality that many injuries do not announce themselves immediately. A worker exposed to asbestos, a building with hidden water intrusion, or a defective product sitting on a shelf can all cause harm long before anyone files a claim.
The legal doctrine behind this is straightforward: liability attaches when the injury or damage actually takes place, not when someone notices it or sues over it. Courts have wrestled for decades with when exactly an "occurrence" happens in cases involving gradual or repeated exposure, but the core principle holds. The policy in force on the date of injury is the policy that responds.
Consider a general contractor who completed a commercial building in 2018 under an occurrence policy with Carrier A. In 2026, a tenant discovers structural cracking traced back to faulty concrete work performed during that 2018 project. Even though the contractor has since switched to Carrier B and the original policy expired years ago, Carrier A's 2018 occurrence policy is the one that must respond, because the damage occurred while that policy was active.
This is fundamentally different from a claims-made policy, where the trigger depends on when the claim is reported rather than when the harm occurred. Total CSR's training assessments consistently show that CSRs confuse these two triggers more than almost any other coverage concept, often telling clients that a non-renewed policy offers "no more protection," which is incorrect for occurrence forms and creates real E&O exposure when the advice gets repeated to a client in writing.
How Does an Occurrence-based Policy Work?
- The occurrence. Bodily injury or property damage takes place while the policy is in force, whether or not anyone is aware of it yet.
- The discovery. The injured party, property owner, or business eventually identifies the harm and connects it to the insured's work, product, or premises.
- The claim filing. The claimant files a claim or lawsuit, sometimes years or decades after the original occurrence.
- The coverage search. The insured and their agency identify which policy was in force on the date of the occurrence, pulling historical policy records if needed.
- The response. The carrier that was on the risk during the occurrence date investigates, defends, and potentially pays the claim under that historical policy, even if it expired long ago.
Real Claim Examples Involving Occurrence-based Policy
Mold damage discovered years after a roofing job
A roofing contractor completed a repair in 2020 under an occurrence-based CGL policy. In 2026, the property owner discovers mold growth traced to improper flashing installed during that repair. Because the damage began during the 2020 occurrence, the contractor's 2020 carrier handles the claim, even though the contractor has since changed insurers twice.
Product liability from a manufacturing defect
A parts manufacturer sold a component in 2019 that failed and caused injury to a worker in 2025. The manufacturer's 2019 occurrence policy responds because the product defect and resulting injury are tied to that policy period, not the policy the manufacturer carries today. The manufacturer's current carrier has no obligation to the claim.
Scaffolding collapse with delayed lawsuit
A subcontractor's scaffolding partially collapsed on a jobsite in 2022, injuring a passerby who did not file suit until 2026 due to a lengthy medical recovery and investigation. The subcontractor's occurrence policy from 2022 still responds despite the four-year gap between injury and lawsuit, because the trigger is the date of injury rather than the date the claim was reported.
Occurrence-based Policy vs. Claims-Made Policy: What Is the Difference?
An occurrence-based policy and a claims-made policy both provide liability coverage, but they trigger on different events entirely. Understanding the distinction matters most when a client switches carriers or lets coverage lapse, since the two trigger types behave very differently in that scenario.
| Comparison area | Occurrence-based Policy | Claims-Made Policy |
|---|---|---|
| Primary use case | General liability for contractors, manufacturers, property owners | Professional liability, D&O, E&O, cyber |
| Coverage / concept type | Triggered by date of injury or damage | Triggered by date claim is reported |
| Typical exclusions | Known occurrences before policy inception | Claims before the retroactive date |
| Who is most affected by errors | Long-tail industries like construction and manufacturing | Professional service firms switching carriers |
| Common mistakes | Assuming an expired policy offers no protection | Forgetting to secure tail coverage after cancellation |
What Are the Most Common Mistakes With Occurrence-based Policy?
- Advising a client that a non-renewed or canceled occurrence policy no longer offers protection, which is false if the injury occurred during the policy period, and this misstatement in an email becomes a documented E&O error.
- Failing to retain historical policy records, leaving an agency unable to prove which carrier was on the risk when an old claim surfaces years later.
- Confusing occurrence triggers with claims-made triggers when explaining coverage to clients, especially for businesses carrying both a CGL occurrence policy and a claims-made professional liability policy.
- Assuming continuous coverage with the same carrier is required for occurrence protection to apply, when in fact each individual policy period stands on its own regardless of carrier changes.
- Overlooking additional insured endorsements tied to a specific occurrence policy period, which can leave a general contractor without the protection they assumed a subcontractor's policy provided.
How to Explain Occurrence-based Policy to a Client
Explaining Occurrence-based Policy to a personal lines client
Your homeowners policy covers damage that happens while the policy is active, even if you do not discover it until later. If a pipe bursts behind a wall during your coverage term but you do not notice the damage for several months, your policy at the time of the leak is the one that responds. That is why it matters which policy was in force, not just which one you have today.
Explaining Occurrence-based Policy to a small business owner
Your general liability policy covers injuries or damage that happen while the policy is active, even if someone does not file a claim until years later. If you switch carriers next year, your old carrier still owes coverage for anything that happened while you were insured with them. That is good news if an old job comes back to haunt you, but it also means you need to keep records of every policy you have ever carried.
Explaining Occurrence-based Policy to a CFO or risk manager
Your CGL program is occurrence-based, meaning the trigger is the date of injury or property damage rather than the date a claim is made. This creates long-tail exposure for your organization, particularly in construction and manufacturing, where latent defects can surface a decade later. We recommend maintaining a complete historical policy archive, since proving coverage on an old occurrence can require pulling records from carriers you have not used in years.
Frequently Asked Questions About Occurrence-based Policy
Does an occurrence-based policy cover claims filed after the policy expires?
Yes. An occurrence-based policy covers any bodily injury or property damage that happened during the policy period, even if the claim is filed years or decades after expiration. The expired policy remains legally obligated to respond as long as the injury date falls within its original term.
What happens if a client cancels their occurrence policy and does not replace it?
Coverage for anything that occurred while the policy was in force still applies, even after cancellation. The client has no ongoing protection for new occurrences after the cancellation date, but prior occurrences remain covered by the canceled policy.
Is tail coverage necessary for an occurrence-based policy?
No. Tail coverage is a claims-made concept used to extend the reporting period after a policy ends. Occurrence-based policies do not need tail coverage because the trigger is the date of injury, not the date the claim is reported.
Can two different carriers both be responsible for the same claim under occurrence triggers?
Yes, in cases of continuous or progressive damage, such as ongoing water intrusion or gradual pollution, multiple occurrence policies across several years can each be triggered. Courts in these situations often apply allocation methods to divide responsibility among the carriers on the risk during the damage period.
Why do most CGL policies use an occurrence trigger instead of claims-made?
Occurrence triggers better match the nature of physical injury and property damage, which can take years to manifest or be discovered. ISO's standard CG 00 01 form uses occurrence as the default trigger for exactly this reason, protecting insureds against long-tail risks like construction defects or product failures.
How does an agency verify which occurrence policy applies to an old claim?
The agency pulls historical declarations pages and policy periods for every carrier the client has used, then matches the date of injury to the correct policy term. Total CSR's training work shows this historical document retrieval is one of the most frequently mishandled tasks in long-tail claims, often delaying claim resolution by months.
Related Insurance Terms
- Claims-Made Policy: A liability policy trigger based on when a claim is reported to the carrier rather than when the injury occurred, commonly used for professional liability and cyber coverage.
- Retroactive Date: The date on a claims-made policy before which no coverage applies, functioning as the claims-made equivalent of an occurrence policy's injury-date trigger.
- Tail Coverage: An extended reporting period purchased on a claims-made policy to cover claims reported after cancellation, unnecessary under occurrence-based policies since the trigger is the injury date.
- Occurrence: The specific event, or continuous exposure to harmful conditions, that causes bodily injury or property damage and activates coverage under an occurrence-based policy.
- Trigger of Coverage: The legal mechanism determining which policy responds to a claim, with occurrence and claims-made representing the two dominant trigger types in liability insurance.
- Long-Tail Claim: A claim arising many years after the underlying occurrence, a pattern especially common under occurrence-based policies in construction and product liability.
Sources and References
- IRMI. Occurrence Policy.
- IRMI. Claims-Made Policy.
About the Author
Justin Goodman, CIC, CCIP, CISC, CLCS, CRIS, PCIA, QCLS, MFHR CEO and Co-Founder, Total CSR, Inc.
Justin Goodman is a third-generation insurance broker with over two decades in agency operations. He has trained more than 100,000 CSRs, account managers, and producers in commercial and personal lines coverage, from workers' compensation to construction risk. He was named 2024 Insurance Journal Agent of the Year and one of the nation's top five construction insurance experts by Risk & Insurance. He is the author of Retain, which applies cognitive science research on memory and knowledge transfer to insurance training, and speaks nationally on how agencies build durable technical expertise in their teams.