Table of Contents

Written by Justin Goodman, CIC, CISC, CLCS, CEO and Co-Founder, Total CSR Published: October 2, 2026 · Last reviewed: October 2, 2026

In plain language: Occurrence describes the accident that causes injury or damage and sets off a liability claim. It can be a single sudden event, like a fall, or harm that builds up over months or years, like mold exposure. The policy in place when the harm actually happens is the one that responds.

Technical definition: Occurrence is defined in standard CGL forms as an accident, including continuous or repeated exposure to substantially the same general harmful conditions, resulting in bodily injury or property damage neither expected nor intended by the insured. It determines which policy period responds and anchors the per-occurrence limit.

Occurrence at a Glance

AttributeDetail
Also known asOccurrence trigger, occurrence-based coverage trigger
CategoryLiability policy coverage trigger
Lines of businessCommercial General Liability, Personal Umbrella, Commercial Umbrella, Products Liability
Industries most affectedConstruction, manufacturing, habitational, environmental services
Related forms or endorsementsISO CGL Coverage Form CG 00 01
Who bears the riskThe insured and the carrier on the risk when the injury or damage actually occurred
Common solutionOccurrence-based CGL policy paired with adequate per-occurrence and aggregate limits
Also interacts withClaims-made trigger, aggregate limit, trigger of coverage doctrine, continuous trigger theory

Key Takeaways

  • Occurrence is the accident or ongoing harmful exposure that causes bodily injury or property damage and activates a liability policy.
  • Agencies rely on the occurrence definition daily to determine which policy year responds to a claim, especially on construction defect and product liability files spanning multiple years.
  • The most common misunderstanding is treating “occurrence” and “claim” as the same thing. A claim can surface years after the occurrence happened, and courts often look to when the damage manifested, not when the claim was filed.
  • Agencies reduce E&O exposure by keeping complete historical policy records so an old occurrence-based policy can be located and tendered even a decade after it expired.

What Is Occurrence in Insurance?

Occurrence is the operative word that separates accidental harm from something the insured intended or controlled, and it sits at the center of every CGL coverage form. Carriers built the definition around the idea of fortuity: insurance pays for unexpected accidents, not for damage an insured planned or should have anticipated as a natural result of its own actions. The phrase “continuous or repeated exposure to substantially the same general harmful conditions” was added specifically to capture slow-building harm, like asbestos exposure or water intrusion, that no single moment can pinpoint.

This matters because general liability policies are typically occurrence-based, meaning the policy in force when the injury or damage actually happened responds, regardless of when the claim gets reported. A worked example makes this concrete. A contractor installs defective windows in 2019 under a policy that expires in 2020. Water intrusion damages the building’s framing slowly over several years, and the owner does not discover rot until 2024. Courts in most states will look to when the damage actually occurred or manifested, which could pull in the 2019-2020 policy, later policies, or several policies at once under a continuous trigger theory.

Agencies that work construction and habitational accounts see this doctrine collide with real claims constantly. A single construction defect claim can implicate four or five consecutive annual policies, each with its own per-occurrence and aggregate limits, which is why completed operations exposure and long-tail risk drive so much underwriting scrutiny in those industries.

How Does Occurrence Work?

  1. The exposure begins. A harmful condition starts, whether a single sudden event like a vehicle collision or a slow process like mold growth behind a wall.
  2. The damage occurs. Bodily injury or property damage actually happens, which may be instantaneous or may unfold over months or years under continuous exposure.
  3. The policy period is identified. The carrier and the insured’s agent work to determine which policy, or policies, were in force when the occurrence took place, not when it was discovered.
  4. The claim is tendered. The insured reports the loss, often years after the underlying occurrence, and the agent locates the applicable historical policy to tender the claim.
  5. Coverage is confirmed or disputed. The carrier applies the occurrence definition, trigger theory under applicable state law, and policy limits to determine what responds, and disputes over timing often end up in coverage litigation.

Real Claim Examples Involving Occurrence

Water intrusion discovered years after construction

A general contractor built a condominium complex between 2017 and 2018. Owners did not notice water staining and structural rot until 2023, five years after substantial completion. The carrier that wrote the contractor’s CGL policy during the construction years was tendered the claim because the occurrence, the actual water intrusion, took place during that earlier policy period even though the damage was not discovered until much later.

Product liability claim from a component sold years earlier

A manufacturer sold a defective valve in 2015 that was installed into industrial equipment. The valve failed and caused a fire in 2024, nine years later. Because the CGL policy was occurrence-based, the 2015 policy responded to the claim, requiring the agency to pull archived policy records to confirm coverage limits and carrier information from nearly a decade prior.

Scaffolding fall with an immediate, single occurrence

A subcontractor’s worker fell from scaffolding on a jobsite and suffered injuries the same day. The occurrence was instantaneous and undisputed, the claim was reported within the policy period in force, and coverage applied cleanly under the current year’s CGL policy with no trigger dispute at all.

Occurrence vs. Claims-Made Trigger: What Is the Difference?

Occurrence and claims-made trigger are the two coverage trigger models used in liability insurance, and confusing them is one of the most consequential mistakes an agency can make. An occurrence policy responds based on when the damage happened; a claims-made policy responds based on when the claim is reported, subject to a retroactive date.

Comparison areaOccurrenceClaims-Made Trigger
Primary use caseGeneral liability, most property-casualty linesProfessional liability, management liability, environmental, cyber
Coverage / concept typeCoverage attaches to the policy in force when damage occurredCoverage attaches to the policy in force when the claim is first reported
Typical exclusionsIntentional acts, expected or intended damageClaims with dates of loss before the retroactive date
Who is most affected by errorsLong-tail industries like construction, products, environmentalProfessionals needing tail coverage after switching carriers or retiring
Common mistakesFailing to retain old policies to respond to late-discovered claimsLetting a policy lapse without purchasing extended reporting period coverage

What Are the Most Common Mistakes With Occurrence?

  • Treating “occurrence” and “claim” as interchangeable, which leads agents to tell clients the wrong policy year will respond to a loss.
  • Discarding expired occurrence-based policies after a few years, leaving the agency unable to locate coverage information when a long-tail claim surfaces a decade later.
  • Assuming a single harmful event always means a single occurrence, when continuous exposure language can split one ongoing condition into multiple occurrences or combine years of damage into one.
  • Failing to explain to clients that reporting a claim promptly does not change which policy year actually provides coverage under an occurrence trigger.
  • Overlooking how state-specific trigger theories, such as manifestation, exposure, or continuous trigger, change which policies respond on multi-year construction defect and environmental claims.

How to Explain Occurrence to a Client

Explaining Occurrence to a personal lines client

Your homeowners or auto policy pays for accidents, not for things you planned or expected to happen. If your dog bites a visitor or a tree falls on a neighbor’s fence, that event is the occurrence, and it’s covered as long as it happened while your policy was active.

Explaining Occurrence to a small business owner

Your general liability policy responds based on when the actual damage happened, not when someone files a claim against you. That means if a defect from work you did years ago causes damage that’s just now being discovered, we may need to look at an old policy, which is exactly why we keep your coverage history on file.

Explaining Occurrence to a CFO or risk manager

Your occurrence-based CGL program ties coverage to the policy period in which bodily injury or property damage actually took place, which creates long-tail exposure on construction, products, and environmental risk. We recommend maintaining a complete historical policy archive and reviewing aggregate limit erosion across multiple triggered years whenever a long-tail claim surfaces.

Frequently Asked Questions About Occurrence

What counts as an occurrence under a general liability policy?

An occurrence is an accident, including continuous or repeated exposure to substantially the same general harmful conditions, that results in bodily injury or property damage the insured did not expect or intend. It covers both sudden events, like a slip and fall, and gradual harm, like long-term water intrusion. Intentional acts generally fall outside the definition entirely.

Can one event create multiple occurrences?

Yes, depending on policy language and state law, a series of related incidents can sometimes be treated as separate occurrences, which affects how per-occurrence limits apply. Courts often apply a “cause” test, asking whether one proximate, uninterrupted cause produced all the damage. This determination can significantly change how much coverage is available for a large loss.

Does occurrence mean the same thing as claim?

No, an occurrence is the actual accident or harmful event, while a claim is the formal demand for payment that may come years later. A single occurrence can generate a claim reported long after the underlying policy expired. This gap is why occurrence-based policies require agencies to retain old policy records.

Why do construction accounts rely so heavily on occurrence-based coverage?

Construction defects often take years to manifest, since water intrusion, foundation settling, and material failures develop slowly after substantial completion. An occurrence trigger ensures the policy active during actual construction responds to the damage, even if discovery happens a decade later. This is why completed operations exposure and historical coverage records matter so much on these accounts.

What happens if an agency cannot locate an old occurrence-based policy?

The insured may have no way to prove coverage existed for a claim arising from an occurrence that happened years earlier. Total CSR sees this gap repeatedly in CSR training assessments, where agencies without a strong document retention and archival process struggle to respond to decade-old construction and product claims. Carrying a documented retention policy for expired commercial policies is one of the simplest ways to close this risk.

How does state law affect which policy responds to a long-tail occurrence?

States apply different trigger theories, including exposure, manifestation, injury-in-fact, and continuous trigger, to decide which policy years respond when damage develops gradually. Some states pull in every policy on the risk during the entire exposure period, spreading one loss across several years of coverage. Agencies working multi-state construction or environmental accounts need to understand which theory applies in each jurisdiction.

  • Claims-Made Trigger: a coverage trigger that attaches based on when a claim is reported rather than when the underlying damage occurred, commonly paired with a retroactive date and often confused with occurrence-based coverage.
  • Aggregate Limit: the total amount a liability policy will pay for all occurrences within a single policy period, which can be eroded quickly when one continuous occurrence spans multiple claims.
  • Per Occurrence Limit: the maximum amount payable for damages arising from a single occurrence, distinct from the aggregate limit and central to how occurrence-based claims are adjusted.
  • Trigger of Coverage: the legal doctrine courts use to decide which policy period responds to a loss, directly built around how occurrence is defined and interpreted.
  • Bodily Injury: one of the two harm types, along with property damage, that an occurrence must cause in order to activate liability coverage.
  • Continuous Trigger Theory: a legal doctrine holding that every policy in force during an ongoing, continuous occurrence may be triggered, often applied in environmental and construction defect litigation.
  • Completed Operations: the liability exposure a contractor retains after finishing a job, frequently the source of long-tail occurrences that surface years after project completion.

Sources and References

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.

Connect with Justin on LinkedIn