The Concept of the Coverage Trigger
In the world of Commercial General Liability (CGL) insurance, the "trigger" is the specific event or set of circumstances that activates the policy to respond to a claim. Understanding how these triggers function is essential for the insurance exam, as it determines which policy period pays for a loss. For a broader overview of liability concepts, you should consult our complete General Liability exam guide.
There are two primary coverage forms used in the industry: the Occurrence Form and the Claims-Made Form. While both provide identical types of coverage for bodily injury and property damage, they differ significantly in when they provide that coverage based on the timing of the incident and the filing of the claim.
The Occurrence Form: Timing the Incident
The Occurrence Form is the most common version of the CGL policy. Its trigger is based solely on when the bodily injury or property damage occurred. If the injury or damage happened during the policy period, that specific policy is responsible for the claim, regardless of when the claim is eventually filed—even if it is years later.
Key characteristics of the Occurrence Form include:
- Long-Tail Claims: This form is ideal for "long-tail" exposures, such as environmental damage or latent health issues, where the damage might happen today but not be discovered for a long time.
- Perpetual Coverage: As long as the policy was active on the date of the incident, the insurer is on the hook for the claim, even if the policy has since been canceled or expired.
- Simplicity: There is no need for retroactive dates or complex reporting period extensions.
Quick Comparison: Occurrence vs. Claims-Made
| Feature | Occurrence Form | Claims-Made Form |
|---|---|---|
| Trigger | Injury/Damage occurs during policy period | Claim is filed during policy period |
| Reporting Deadline | Anytime (subject to statutes of limitation) | Must be during policy or ERP |
| Retroactive Date | Not Applicable | Often used to limit past exposure |
| Tail Coverage | Built-in | Requires Extended Reporting Period (ERP) |
The Claims-Made Form: Timing the Claim
The Claims-Made Form is triggered when a claim is first made against the insured during the policy period. However, there is a secondary requirement: the injury or damage must have occurred after the Retroactive Date listed in the policy declarations.
This form is often used for professional liability or in high-risk industries where insurers want to limit their "tail" exposure. If a claim is filed after the policy expires, it is generally not covered unless an Extended Reporting Period (ERP) was purchased or provided.
To ensure you understand how these triggers are tested, practice with our practice General Liability questions.
The Retroactive Date
The Retroactive Date is a unique feature of the Claims-Made form. It acts as a "cutoff" point. If an incident happens before the retroactive date, the policy will not cover it, even if the claim is filed during the policy period. This prevents an insured from buying a policy today to cover a known mistake from years ago.
Extended Reporting Periods (ERP)
When a Claims-Made policy is canceled or not renewed, a gap in coverage can occur. To solve this, the policy provides Extended Reporting Periods (ERPs), also known as "tail coverage." These allow the insured to report claims for a certain amount of time after the policy ends, provided the incident occurred after the retroactive date but before the policy expired.
- Basic ERP: Usually included automatically. It typically consists of a "mini-tail" (60 days to report a claim) and a "midi-tail" (5 years to report a claim if the occurrence was recorded within the first 60 days).
- Supplemental ERP: An optional endorsement that provides an unlimited duration for reporting claims (the "maxi-tail"). This must be requested and paid for at the time the policy is terminated.
Claims-Made Mechanics
Frequently Asked Questions
If the retroactive date is listed as "None" or is left blank, the policy will cover claims filed during the policy period regardless of when the underlying injury or damage occurred. This provides the broadest possible coverage under a claims-made form.
No. An occurrence policy does not need an ERP because the coverage is triggered by the date of the event. As long as the event happened while the policy was active, the insurer will defend the claim even if it is brought years later.
Yes, but it creates a potential coverage gap. If an insured switches from Claims-Made to Occurrence, they must ensure they have an ERP on the old Claims-Made policy to cover incidents that happened during that period but haven't been reported as claims yet.
A claim is generally defined as a written demand for money or services received by the insured. For the trigger to work, this demand must be received during the policy period (or the ERP).