Occurrence vs. Claims-Made Coverage Triggers
Imagine a roofing contractor finishes a major commercial installation in 2022. The work appears flawless—until a hidden structural defect gives way in 2026, causing the roof to collapse onto a warehouse of expensive electronics. When the multimillion-dollar lawsuit arrives, an immediate and profound question arises: which insurance policy responds? The policy active when the hammer swung in 2022, or the policy active when the lawsuit was served in 2026?
The answer depends entirely on the coverage trigger. The underlying machinery of casualty insurance is dictated by time. Understanding how an insurance contract measures time is the difference between constructing an impenetrable safety net for your client and inadvertently leaving them exposed to ruinous financial liability. As an insurance producer, you are not merely selling pieces of paper; you are engineering temporal defenses. To do this, we must master two distinct mechanisms that govern when a policy activates: the occurrence trigger and the claims-made trigger.
For decades, the standard mechanism for triggering liability coverage was the occurrence form. It is highly intuitive because it aligns with our basic understanding of cause and effect.
An occurrence coverage trigger is based on the date the injury or property damage takes place. Under this framework, an occurrence policy covers claims for incidents that happen during the active policy period. If the roof was built defectively in 2022 and collapsed in 2022, the 2022 policy pays.
But the true power of the occurrence form is its permanence. Under an occurrence policy, the filing date of the claim does not affect coverage eligibility. Because the trigger is tied strictly to the moment of injury or damage, an occurrence policy will pay a covered claim even if the policy has expired by the time the injured party files the claim.
The Concept of the "Long Tail" Think of an occurrence policy as a time capsule. If an incident occurs between January 1 and December 31 of the policy year, that specific policy is sealed in the capsule alongside the event. Whether the lawsuit is filed three weeks later or thirty years later, you dig up that specific time capsule.
This creates a scenario known as a "long tail" of liability for insurance companies. An insurer might collect a $5,000 premium in 2005, only to pay out a $1,000,000 settlement in 2025 for an asbestos exposure or environmental leak that occurred during the 2005 policy period.
To combat the unpredictability of long-tail claims—and to price premiums more accurately based on current economic realities—the insurance industry developed a fundamentally different mechanism.
A claims-made coverage trigger is based on the date the claim is first filed against the insured. Rather than looking backward to see when the injury happened, a claims-made policy covers claims that are filed during the active policy period. If a client is sued today, today's active policy is the one that responds, regardless of when the original work was performed.
However, insurers cannot simply take on the liability for every past mistake a business has ever made the moment they underwrite a new claims-made policy. They require a boundary. Therefore, a claims-made policy requires the underlying injury or damage to occur on or after the policy retroactive date.
The Retroactive Date: The Line in the Sand
The retroactive date is the most critical component of a claims-made policy. A retroactive date is a specific date entered on the declarations page of a claims-made policy.
What does this date actually do? The retroactive date establishes the earliest date an incident can happen for a claims-made policy to provide coverage. If an event happens before this line in the sand, the current policy will not touch it. Incidents occurring before the retroactive date are explicitly excluded from coverage under a claims-made policy.
As a producer, managing this date upon policy renewal is one of your highest professional responsibilities. Let us look at two distinct renewal strategies:
- The Dangerous Route: Advancing a retroactive date upon policy renewal creates a gap in coverage for past incidents. If your client had a retroactive date of 2020, and upon renewal in 2026 you move the retroactive date up to 2026 to save them a few dollars in premium, you have just erased coverage for anything they did between 2020 and 2025. If a lawsuit arrives for work done in 2023, they will have no coverage.
- The Professional Standard: Keeping the exact same retroactive date during policy renewal provides continuous coverage for past incidents. As long as you maintain that original inception date on the declarations page year after year, your client maintains their historical safety net.
| Feature | Occurrence Policy | Claims-Made Policy |
|---|---|---|
| Trigger Mechanism | Date the injury/damage occurs | Date the claim is filed |
| Role of Filing Date | Irrelevant to coverage eligibility | Must fall within active policy period |
| Historical Boundary | N/A (Policy year is self-contained) | Governed strictly by the Retroactive Date |
| Insurer Predictability | Low (Vulnerable to long-tail claims) | High (Current pricing matches current risks) |
The primary vulnerability of a claims-made policy arises when the policy ends. What happens when a business closes, a professional retires, or a client simply decides to switch carriers?
If a claims-made policy requires the claim to be filed during the active policy period, canceling the policy immediately terminates the client's ability to report lawsuits—even for perfectly valid incidents that happened after the retroactive date.
To solve this, the industry utilizes an extended reporting period (ERP). An extended reporting period extends the time allowed to file a claim after a claims-made policy expires or is canceled.
Because we are dealing with complex insurance contracts, clarity is paramount. An extended reporting period does not provide coverage for incidents that happen after the policy expiration date. It is not an extension of active liability coverage; it is merely an extension of the mailbox—it keeps the window open to receive lawsuits for things that already happened.
Industry Terminology: Tail Coverage In the daily vernacular of producers, underwriters, and claims adjusters, an extended reporting period is commonly referred to in the insurance industry as tail coverage. You are "buying a tail" to attach to the end of the expired policy.
The Basic Extended Reporting Period
The creators of the Commercial General Liability (CGL) form recognized how easily a client could accidentally expose themselves to ruin if a claims-made policy lapsed. Therefore, a basic extended reporting period is automatically included in a standard claims-made Commercial General Liability policy without extra premium.
This built-in feature operates under two very specific temporal rules:
- The 60-Day Window (Unknown Incidents): A basic extended reporting period covers claims first made against the insured within 60 days after the claims-made policy expires. If the policy ends on December 31, and a completely unexpected lawsuit arrives on February 15 of the next year, the basic ERP absorbs it.
- The 5-Year Window (Known Incidents): What if your client slips on a wet floor on December 30, right before the policy expires? A lawsuit won't materialize for months or years. The policy accounts for this: A basic extended reporting period extends the claim filing window to five years if the underlying incident is reported to the insurer within 60 days of policy expiration.
Think of this as planting a flag. If your client notifies the insurer of the incident before the 60-day clock runs out, they buy themselves a five-year runway for the actual claim (lawsuit) to manifest.
The Supplemental Extended Reporting Period
While the basic ERP is a helpful default, a 60-day window for unknown claims and a 5-year window for known incidents is rarely sufficient for long-tail liabilities like construction defects or professional malpractice.
This is where you, as a producer, must act. A supplemental extended reporting period is an optional endorsement added to a claims-made policy for an additional premium. Often costing up to 200% of the annual premium, this endorsement is a substantial but vital investment.
Why is it worth the cost? Because a supplemental extended reporting period provides an unlimited duration for filing claims related to covered incidents that occurred before policy expiration. It effectively converts the expired claims-made policy into a permanent time capsule, matching the lifelong protection of an occurrence policy for all past acts.
As a licensed producer, you will frequently restructure your clients' insurance portfolios. Moving a client from one policy to another requires immense precision to avoid opening a temporal gap where claims fall through the cracks.
There are two primary scenarios where purchasing tail coverage (a supplemental ERP) is absolutely necessary to protect your client:
1. Transitioning to an Occurrence Policy Tail coverage is necessary when replacing a claims-made policy with an occurrence policy to prevent a coverage gap.
- The Mechanics: The new occurrence policy will only cover incidents that happen after its inception date. The old claims-made policy will no longer accept claims because it has expired. Therefore, any incident that happened in the past, but results in a lawsuit tomorrow, has no home. The tail coverage bridges this gap, allowing the old claims-made policy to absorb lawsuits for past mistakes, while the new occurrence policy takes over for all future mistakes.
2. Transitioning to a Claims-Made Policy with a New Boundary Tail coverage is necessary when replacing a claims-made policy with a new claims-made policy that features a later retroactive date.
- The Mechanics: If you move a client to a new carrier, and the new carrier refuses to honor the original retroactive date (perhaps due to a change in underwriting appetite), they will advance the retroactive date to the present day. Just like the scenario above, this severs the client from their historical coverage. Purchasing tail coverage on the expiring policy ensures that the client's history remains protected while the new policy begins building a new track record.
Mastering these triggers is not just an academic exercise for your licensing exam; it is the fundamental architecture of casualty insurance. By understanding precisely how an occurrence policy traps time, how a claims-made policy leverages the retroactive date, and how extended reporting periods bridge the gaps between them, you elevate yourself from a salesperson to a trusted risk architect.
