The mental model

A coverage trigger is the policy's answer to the question: of all the policies the insured has ever bought, which one responds to this claim? The trigger fixes the answer to a specific event in time — an injury, a report, an occurrence, a manifestation — and then the policy that was in force at that moment becomes the policy that pays. Everything that follows in a claim — the limits available, the deductibles applied, the exclusions in effect, the defense obligations — flows from the trigger determination.

There are two families of triggers in commercial liability: occurrence and claims-made. Within each family there are variants, and the variants matter. For most lines, the trigger is fixed by industry convention — general liability is occurrence, D&O is claims-made — but the buyer can sometimes choose between them, and the choice has consequences that compound over decades. The mistake that practitioners make most often is treating triggers as administrative when they are existential: an occurrence policy from 1985 may still be responding to a claim asserted in 2025, while a claims-made policy from last year may have already locked out coverage for a claim the insured did not know about at renewal.

Occurrence triggers

An occurrence policy responds to bodily injury, property damage, or personal injury caused by an "occurrence" that takes place during the policy period, regardless of when the claim is made. The policy in force when the injury happens is the policy that responds — even if the claim is made decades later.

The standard CGL occurrence form

The ISO Commercial General Liability form (CGL) is the canonical occurrence policy. It covers bodily injury and property damage caused by an occurrence that takes place during the policy period, where the bodily injury or property damage occurs during the policy period. Note the two requirements: the occurrence must be during the period, and the injury must occur during the period. For most losses these coincide. For long-developing injuries — asbestos, pollution, latent disease — they do not.

What "occurrence" means

The standard definition: "an accident, including continuous or repeated exposure to substantially the same general harmful conditions." Three things matter:

• Accident. The harm must be unintended from the standpoint of the insured. Intentional acts are not occurrences (with carve-outs for self-defense and certain assault scenarios).
• Continuous or repeated exposure. This phrase covers latent injuries — repeated exposure to chemicals, ongoing noise, continuous pollution. It also creates allocation problems when the exposure spans multiple policy periods.
• Substantially the same general harmful conditions. Multiple injuries from one course of exposure are typically treated as a single occurrence. This affects how limits apply.

The long tail

Occurrence policies have very long tails. A worker exposed to asbestos in 1972 can file a claim in 2025 against the policy in force in 1972. Carriers that wrote occurrence policies in the 1970s are still paying claims today. This is the structural reason that "long-tail" lines are difficult to reserve and price — the carrier's exposure persists for decades.

Advantages and disadvantages

• For the insured: Buying occurrence coverage means the policy in force today will respond to claims asserted any time in the future, regardless of whether the insured still has insurance. This is valuable certainty.
• For the carrier: Occurrence exposure is hard to estimate and hard to close out. Reserves can develop adversely for decades. This is why most specialty lines — D&O, E&O, professional liability — moved off occurrence in the 1980s.

Claims-made triggers

A claims-made policy responds to claims first made against the insured during the policy period, regardless of when the underlying wrongful act occurred (subject to a retroactive date). The policy in force when the claim is made is the policy that responds — not the policy in force when the harm occurred.

How claims-made works

The mechanics are straightforward in operation, subtle in implication:

1. A wrongful act, error, or omission occurs at some point in time. This is the "wrongful act date."
2. The claim is asserted against the insured at a later point — the "claim made date."
3. The policy that responds is the one in force on the claim made date.
4. The policy will respond only if the wrongful act occurred on or after the retroactive date.

Why the industry moved to claims-made

The mid-1980s liability crisis was the precipitating event. Asbestos, pollution, and other latent-injury claims under occurrence policies developed adversely for decades, with no way for carriers to close out their exposure. Reinsurance dried up. The industry's response was to migrate specialty lines from occurrence to claims-made, where exposure ends when the policy period ends (subject to ERP — see below). D&O, E&O, professional liability, cyber, EPLI, and most other specialty lines are now uniformly claims-made.

Continuity matters

The single biggest risk with claims-made coverage is a gap in continuity. If a claims-made policy is allowed to lapse — even by a day — claims for prior acts asserted after the lapse may not be covered by any policy. The new policy will not cover them (the claim was not made during its period, or the retroactive date does not reach back far enough), and the old policy will not cover them (the claim was not made during its period either). This is the canonical "tail gap" that produces uninsured claims even when the insured has continuously bought insurance.

Claims-made-and-reported

A variant of claims-made that adds a second requirement: the claim must not only be made against the insured during the policy period but also reported to the carrier during the policy period (or within a short grace period after expiration, usually 30–60 days).

Why this matters

A pure claims-made policy responds if the claim is made during the period, even if the insured does not report it until later (subject to the duty to notify in a timely manner). A claims-made-and-reported policy requires both — made and reported in the same period.

The reporting trap

The trap is straightforward but catches buyers regularly:

• A claim is asserted against the insured in November of a policy year.
• The insured does not report it until February of the following year — after the policy has expired.
• Under a pure claims-made form, coverage may still respond because the claim was made during the prior period.
• Under a claims-made-and-reported form, coverage does not respond — neither the prior policy (claim was not reported during its period) nor the current policy (claim was not made during its period).

Where you see it

Medical professional liability is most often written on a claims-made-and-reported basis. Some D&O forms use it. Most modern E&O and professional liability forms have moved back to pure claims-made because the reporting trap is too easy to fall into.

Other triggers

Beyond occurrence and claims-made, several other trigger theories appear in case law and in specific policy forms. They matter mostly in long-tail coverage disputes where the basic triggers do not produce a clean answer.

Manifestation trigger

Used in some property and pollution policies. The trigger is the moment the injury or damage becomes manifest — when it could reasonably be discovered. Useful in cases where the exposure is continuous but the harm crystallizes at a discrete point.

Exposure trigger

Used in asbestos and similar latent-injury cases. The trigger is the moment of exposure to the harmful condition. Each policy in force during the exposure period is potentially responsive. This produces the multi-year allocation problem that defines asbestos coverage litigation.

Injury-in-fact trigger

The trigger is the moment of actual cellular or physical injury, regardless of when symptoms appear or claims are made. Used by some courts in latent-disease cases. Hard to apply because medical testimony is required to establish when injury actually occurred.

Continuous trigger (triple trigger)

The trigger is every year from exposure to manifestation — exposure year, every year of progression, and the year of manifestation. Each policy in force during any of those years is potentially on the risk. This produces the largest universe of responding policies and the most complex allocation. Used heavily in asbestos and environmental coverage litigation, especially in New Jersey (Owens-Illinois) and California.

Why these matter

For a normal commercial loss — a slip-and-fall, a fender bender, a discrete property loss — the standard occurrence or claims-made trigger answers cleanly. The exotic triggers appear when:

• The harm developed over years or decades.
• Multiple policy periods are potentially on the risk.
• Some of the responding policies have been exhausted, rescinded, or have insolvent carriers.
• The buyer needs to maximize the recovery pool.

Retroactive dates and ERPs

The retroactive date and the extended reporting period are the two clauses that make claims-made coverage workable across renewals.

The retroactive date

A claims-made policy covers claims made during the policy period, but only for wrongful acts that occurred on or after the retroactive date. The retroactive date is typically set at the inception of the first claims-made policy the insured purchased and rolls forward unchanged at each renewal. It is the boundary that distinguishes "prior acts coverage" (acts before the retro date — not covered) from "covered acts" (acts on or after the retro date).

The trap: if the retroactive date is moved forward at renewal — by accident, by carrier change, or by oversight — claims for acts that occurred between the old retro date and the new retro date become uncovered. Buyers who change carriers must verify that the new policy maintains the prior retro date, or they will lose coverage for a slice of prior acts.

The Extended Reporting Period (ERP)

An ERP is a tail-coverage extension that allows claims to be reported after the claims-made policy has expired. It comes in several forms:

• Basic ERP / Automatic tail. A short tail (typically 30–60 days) automatically provided at no additional charge. Useful for routine timing slips but inadequate for a real coverage gap.
• Supplemental ERP / Purchased tail. A longer tail (typically 1, 3, 5, or unlimited years) purchased at expiration for a percentage of the expiring premium (often 75–200% for a 3–5 year tail).
• Run-off coverage. A purchased tail that runs concurrent with the wind-down of the insured (after a merger, dissolution, or change in control). Often purchased as a multi-year prepaid tail to protect against future claims for prior acts.

When ERPs matter most

• At carrier change. When moving from carrier A to carrier B on a claims-made policy, the new carrier provides prior-acts coverage going forward, eliminating the need for ERP. But the prior retro date must transfer.
• At policy non-renewal. When a claims-made policy expires and is not renewed (the carrier exits, the insured dissolves, the line is no longer purchased), an ERP is essential to maintain coverage for prior acts that may produce future claims.
• At change of control. M&A transactions almost always trigger ERP purchases on the target company's claims-made policies. The acquirer wants assurance that pre-closing acts are insured.

Allocation across years

When multiple policy periods are potentially on the risk — typical of long-tail occurrence claims — courts must decide how to allocate the loss across the responding policies. The allocation rule chosen has billion-dollar consequences in major coverage litigation.

Pro rata allocation

The loss is divided among responding policies proportionally, typically by years of exposure. If a worker was exposed to asbestos for 30 years across 30 different policies, each policy might bear 1/30th of the loss (or some weighted variant). This is the majority rule in most US jurisdictions.

All sums / joint-and-several allocation

The insured can collect the entire loss from any one responding policy, and that carrier can then seek contribution from the other carriers. Functionally treats the responding policies as joint-and-several obligors. Adopted in some jurisdictions (notably parts of New York and Pennsylvania) under specific circumstances.

The Owens-Illinois rule

The New Jersey allocation rule, established by Owens-Illinois v. United Insurance, that allocates by years of exposure to the policy periods of each carrier, treating the insured as self-insured for years without coverage. Strict and unforgiving — gaps in coverage become the insured's problem.

The Stonewall rule

The New York continuous-trigger allocation rule. Allocates pro rata across all triggered policies in a continuous-injury scenario. Frequently cited in environmental and asbestos litigation.

Why this matters operationally

Allocation rules determine the actual recovery in long-tail claims. A buyer with $1B in aggregate limits across thirty policy years might recover the full $1B under all-sums and only a fraction under pro rata if some of those years had reduced limits or insolvent carriers. The allocation rule is also the reason coverage counsel matters in long-tail claims — small wording differences and forum choices change the math significantly.

Notice and the duty to report

The trigger determines which policy responds; the notice provisions determine whether that response actually happens. Most policies condition coverage on timely notice of claims, and late notice can void coverage even when the trigger clearly applies.

What counts as notice

• Notice of claim. A formal written communication to the carrier reporting that a claim has been made against the insured. Required by every standard form.
• Notice of circumstances. A formal report that an incident has occurred that could reasonably give rise to a future claim. Many claims-made policies allow notice of circumstances to "lock in" the current policy for any subsequent claim arising from that incident.
• Constructive notice. Some forms treat the insured as having notice when a senior officer or claim-handling employee learned of the incident, even if formal notice was not given.

Timeliness

Policies typically require notice "as soon as practicable," "promptly," or "immediately." The actual requirement varies by jurisdiction and policy form. Late notice is one of the most heavily litigated coverage issues. Most jurisdictions require the carrier to prove prejudice from late notice to deny coverage; some (like New York historically) allowed denial based on late notice alone without prejudice.

The duty to defend versus duty to indemnify

Notice triggers the duty to defend, which is broader than the duty to indemnify. The duty to defend attaches whenever the allegations potentially fall within coverage; the duty to indemnify attaches only to claims actually within coverage. Reservation of rights letters preserve the duty to defend while reserving the right to dispute indemnity.

Notice of circumstances as a strategic tool

Sophisticated buyers and brokers use notice of circumstances aggressively, particularly near policy expiration. Reporting an incident as a circumstance before the policy ends ensures that any future claim arising from that incident attaches to the reporting policy — even if the actual claim is asserted years later. The new carrier (with a later retro date) is off the hook; the reporting carrier is on. This is a routine renewal-year hygiene practice in D&O, E&O, and professional liability.

Where IDP earns its keep

Coverage trigger analysis is concentrated in claims-handling and complex underwriting workflows, both of which involve heavy document review and prior-policy reconciliation.

Indico use cases

• Policy schedule reconstruction. For long-tail claims potentially triggering decades of prior policies, extract the schedule of all responding policies — periods, limits, retentions, retro dates, forms — into a single comparative view.
• Wrongful act / claim made date extraction. Pull the relevant dates from claim documents, complaints, and notices to populate the trigger analysis automatically.
• Retroactive date verification. At each renewal of a claims-made policy, verify that the proposed retroactive date matches the prior policy's retro and flag any retro-date movement that creates a coverage gap.
• Notice of circumstances drafting. Generate notice-of-circumstances letters from incident reports near policy expiration, ensuring that the reporting policy attaches to any future claim arising from the incident.