The Foundation of Commercial General Liability Triggers
In the world of commercial insurance, the Commercial General Liability (CGL) policy is the cornerstone of protection for businesses. For students preparing for the Florida 2-20 General Lines Exam, understanding how these policies are 'triggered' is one of the most critical concepts for passing the exam and effectively advising clients in the field.
A 'trigger' refers to the event that must occur for a specific insurance policy to respond to a claim. In the CGL world, there are two primary versions of this trigger: the Occurrence Form and the Claims-Made Form. While both provide coverage for bodily injury and property damage, the timing requirements for when an incident must happen and when a claim must be reported differ significantly. Mastering these differences is essential as you navigate the complete FL 2-20 exam guide.
The Occurrence Form: The Industry Standard
The Occurrence Form is the most common version of the CGL policy. Its trigger is straightforward: the policy that is in effect at the time the injury or damage occurs is the policy that responds to the claim, regardless of when the claim is actually filed.
- Long-Term Protection: Because the trigger is the date of the incident, an occurrence policy provides 'long-tail' coverage. If a business had an occurrence policy several years ago and a claim is filed today for an injury that happened back then, that original policy still responds.
- No Retroactive Date: Occurrence forms do not utilize retroactive dates because the incident itself locks in the coverage.
- Simplicity: Policyholders do not need to worry about 'gaps' in coverage as long as they had a policy in force on the day of the accident.
The Claims-Made Form: Timing and Reporting
The Claims-Made Form is more complex and is typically used for specialized risks or in professional liability (though it exists in the CGL world). Under this form, the policy in effect when the claim is first reported is the policy that handles the loss, provided the incident occurred after a specific 'Retroactive Date'.
Key components of the Claims-Made form include:
- Retroactive Date: This is a date listed on the declarations page. For coverage to apply, the incident must happen on or after this date. Any incident occurring before this date is not covered, even if the claim is reported during the current policy period.
- Double Trigger: In essence, two things must happen: the incident must occur after the Retroactive Date, AND the claim must be made against the insured during the policy period.
- Cost Management: These forms are often used for risks where the potential for 'hidden' claims is high, allowing insurers to price the risk based on current data rather than unpredictable future liabilities.
Comparison: Occurrence vs. Claims-Made
| Feature | Occurrence Form | Claims-Made Form |
|---|---|---|
| Primary Trigger | Date of Injury/Damage | Date Claim is Reported |
| Retroactive Date | Not Applicable | Required to limit past liability |
| Reporting Window | Unlimited (any time after incident) | Must be during policy or ERP |
| Common Use | Standard Business Risks | Professional Liability / High Risk |
The Safety Nets: Extended Reporting Periods (ERP)
One of the biggest risks of a Claims-Made policy is the 'gap' that occurs if the policy is canceled or not renewed. To address this, the ISO Claims-Made CGL includes Extended Reporting Periods (ERPs), often called 'tails'.
- Basic ERP: This is automatically included at no extra cost. It consists of two parts:
- The Mini-Tail: Provides a 60-day window after the policy ends to report a claim.
- The Midi-Tail: If an occurrence is reported within that 60-day window, the insured has up to 5 years to actually have a formal claim filed against them.
- Supplemental ERP: This is an optional endorsement that must be requested and paid for within 60 days of the policy ending. It provides an unlimited duration for reporting claims, effectively turning the old claims-made coverage into something that functions like an occurrence form for that specific policy period.
Exam Tip: Retroactive Date Transitions
On the Florida 2-20 exam, pay close attention to scenarios where an insured switches from one carrier to another. If the Retroactive Date is moved forward (to a later date), it creates a 'coverage gap' for incidents that happened between the old and new dates. Always check the 'Retro Date' when reviewing practice FL 2-20 questions to ensure you catch these potential gaps.