Understanding Policy Triggers in Liability Insurance

In the world of commercial insurance, the Commercial General Liability (CGL) policy is the bedrock of protection for businesses. For an adjuster, one of the most critical concepts to master is the "trigger of coverage." A trigger is the specific event or condition that must occur for a liability policy to respond to a claim.

CGL policies are written on one of two primary forms: the Occurrence Form or the Claims-Made Form. While the coverage for bodily injury and property damage remains largely the same between the two, the timing requirements for when a loss happens and when it is reported differ significantly. Understanding these nuances is essential for passing your exam and accurately processing claims in the field. For a broader overview of exam topics, visit our complete Claims Adjuster exam guide.

The Occurrence Form: Timing of the Event

The Occurrence Form is the most common version of the CGL policy. Its trigger is straightforward: the policy that was in effect when the bodily injury or property damage occurred is the policy that must pay the claim, regardless of when the claim is actually filed.

This form is particularly beneficial for businesses because it provides "long-tail" coverage. If an accident happens during the policy period, but the injured party does not file a lawsuit until several years later, the original policy still responds. This is true even if the policy has long since expired or been replaced by another carrier.

  • Key Advantage: No gaps in coverage for events that happened during the active policy term.
  • Adjuster Focus: When investigating an occurrence claim, the adjuster's primary goal is to determine the exact date the damage or injury took place to identify which policy year applies.

The Claims-Made Form: Timing of the Report

The Claims-Made Form was developed to handle risks that are difficult to predict or that may result in claims many years after an event. Under this form, the trigger is dual-natured: the claim must be made against the insured during the policy period, and the occurrence must have happened after a specific date known as the Retroactive Date.

Because the insurer only pays for claims actually reported during the policy year, this form allows for more predictable underwriting. However, it requires careful management of dates to ensure the insured does not lose coverage when switching carriers.

  • Retroactive Date: A date listed on the declarations page. The policy will not cover any occurrences that happened before this date, even if the claim is filed during the policy period.
  • The Trigger: The claim must be received and recorded by the insured or the insurer during the policy term.

Comparison: Occurrence vs. Claims-Made

FeatureOccurrence FormClaims-Made Form
Primary TriggerDate of the injury/damageDate the claim is filed
Retroactive DateNot UsedRequired
Reporting WindowUnlimited (as long as event was in term)Limited to policy period (unless ERP exists)
Tail CoverageBuilt-inRequires ERP endorsement

Extended Reporting Periods (ERP)

When a Claims-Made policy is cancelled or not renewed, a "gap" can occur where the insured is no longer covered for past events that haven't resulted in a claim yet. To solve this, insurers offer Extended Reporting Periods (ERPs), often called "tail coverage."

There are two main types of ERPs adjusters must know for the exam:

  • Basic ERP: Automatically included in the policy. It usually provides a five-year window to report claims for occurrences that were reported to the insurer within 60 days of the policy expiration (often called the "midi-tail"), and a 60-day window for claims where the occurrence was not previously reported (the "mini-tail").
  • Supplemental ERP: An optional endorsement the insured can purchase. This provides an unlimited duration for reporting claims. It effectively turns the claims-made protection into something resembling occurrence protection for that specific period.

To practice identifying these triggers in scenario-based questions, visit our practice Claims Adjuster questions.

ℹ️

Adjuster Exam Tip: The Retroactive Date

On the exam, watch for questions where an event happens before the Retroactive Date but the claim is filed during the policy period. In a Claims-Made form, there is no coverage in this scenario. The Retroactive Date acts as a hard barrier.

Frequently Asked Questions

This is an endorsement sometimes used in Claims-Made policies to specifically exclude coverage for certain accidents, products, or locations that would otherwise be covered. It 'beams' out a specific risk.
No. Occurrence policies do not use retroactive dates because they only care about when the event happened. If it happened while the policy was active, it is covered, regardless of how far in the past that was.
This creates a 'coverage gap.' Any events that happened between the original retroactive date and the new one will no longer be covered. This is generally avoided in professional insurance placement.
Yes, the Basic ERP is typically included in the Claims-Made form at no extra premium, whereas the Supplemental ERP requires an additional premium charge.