9.3 Extended Reporting Periods (ERPs): Basic vs Supplemental

9.3 Extended Reporting Periods (ERPs): Basic vs Supplemental

Quick Summary: In claims-made casualty insurance, an Extended Reporting Period (ERP)—widely referred to as "tail coverage"—protects an insured against claims that are filed after a policy has expired, cancelled, or renewed with an advanced retroactive date. An ERP does not extend the policy term or insure new accidents; it simply provides an extended reporting window for occurrences that took place between the retroactive date and policy expiration. The standard ISO CG 00 02 policy provides an automatic, cost-free Basic Extended Reporting Period (BERP) with 60-day and 5-year provisions, while offering an optional Supplemental Extended Reporting Period (SERP) that provides an unlimited reporting window and fully reinstates aggregate limits.

The Fundamental Rule of Extended Reporting Periods

Insurance practitioners must master the core operating principle that governs all Extended Reporting Periods under the ISO CG 00 02 Claims-Made form:

The Golden Rule of Tail Coverage: An Extended Reporting Period extends the reporting window for claims; it never extends the policy period. An ERP does NOT cover any bodily injury, property damage, or offense that occurs after the date of policy cancellation or expiration.

For an ERP to apply, the underlying incident must satisfy two immutable criteria:

1. The bodily injury or property damage must have taken place on or after the retroactive date; and
2. The bodily injury or property damage must have taken place prior to the end of the policy period.

If a commercial contractor's claims-made policy expires on June 30, and the contractor causes a fire on a job site on July 5, an ERP provides zero coverage, even if the contractor purchased an unlimited tail. The fire occurred after the policy period expired.

When Does an ERP Become Available?

Under Section V of the CG 00 02, an ERP is triggered and made available to the insured only when any of the following specific events occur:

• The claims-made policy is cancelled or not renewed by either the insurer or the insured;
• The insurer renews or replaces the policy with a claims-made form having a retroactive date that is later than the date shown in the expiring policy (an advanced retroactive date);
• The insurer renews or replaces the policy with a standard occurrence policy (CG 00 01).

If a policy renews normally with the identical retroactive date maintained, an ERP is neither needed nor activated.

---

The Basic Extended Reporting Period (BERP)

The Basic Extended Reporting Period (BERP) is built directly into Section V of the ISO CG 00 02 policy contract. It requires no policy endorsement, incurs no additional premium charge, and takes effect automatically upon policy termination.

The BERP operates through two distinct, synchronized temporal mechanisms: the mini-tail and the midi-tail.

                     THE BASIC EXTENDED REPORTING PERIOD (BERP)
                     
  [ Policy Period: Inception ──────────► Expiration ]
                                           │
                                           ├─────── 60-Day "Mini-Tail" ───────► (Day 60)
                                           │        Any claim first made against
                                           │        insured is covered.
                                           │
                                           └─────── 5-Year "Midi-Tail" ─────────────────────────► (Year 5)
                                                    Claims covered ONLY IF the underlying occurrence
                                                    was reported to the insurer within 60 days!

1. The 60-Day "Mini-Tail"

• Scope: Provides a 60-day reporting window immediately following the policy expiration date.
• Application: Applies to any claim first made against the insured during those 60 days, arising from an occurrence that took place between the retroactive date and policy expiration.
• No Prior Notice Required: The insured does not need to have known about or reported the underlying incident prior to receiving the claim. As long as the claimant brings the demand within 60 days of policy expiration, the BERP responds.

2. The 5-Year "Midi-Tail"

• Scope: Provides a 5-year reporting window running from the policy expiration date.
• The Strict Notice Requirement: The midi-tail applies only to claims arising from an occurrence that was reported to the insurer, as the Duties condition requires, not later than 60 days after the end of the policy period.
• How It Functions in Practice: Suppose a machine manufacturer's policy expires on December 31. On January 15 (within the 60-day window), an industrial customer alerts the manufacturer that an assembly press overheated and leaked fluid, threatening equipment damage. The manufacturer promptly sends written notice of this occurrence to its insurer. If the customer does not file a formal lawsuit until three years later, the midi-tail triggers and provides coverage, because the underlying occurrence was reported in writing within the first 60 days.
• The Trap: If the manufacturer knew about the press failure in January but neglected to notify the insurer within the 60-day window, any claim first made after day 60 is barred.
• Subsequent Insurance Rule: The Basic ERP does not apply to claims covered under any subsequent insurance the insured buys, or that would be covered but for exhaustion of that insurance's limits.

The Major BERP Limitation: No Aggregate Reinstatement

The most critical vulnerability of the Basic ERP is that it does not reinstate the policy aggregate limits.

Any claim paid under the 60-day mini-tail or 5-year midi-tail erodes whatever remains of the General Aggregate Limit and Products-Completed Operations Aggregate Limit from the expired policy year. If the policy carried a $2,000,000 General Aggregate, and the insurer paid $1,900,000 in settlements during the policy term, only $100,000 remains available to pay claims under the BERP. Once exhausted, the insurer's defense and indemnification obligations terminate completely.

---

The Supplemental Extended Reporting Period (SERP / Maxi-Tail)

To overcome the time limitations and aggregate exhaustion risks of the Basic ERP, ISO provides the Supplemental Extended Reporting Period (SERP) endorsement (ISO form CG 27 10). Commonly known in the industry as the "maxi-tail," the SERP provides comprehensive, permanent reporting security.

Key Provisions and Operational Terms of the SERP

1. Unlimited Reporting Duration: The SERP is indefinite and begins when the Basic ERP ends. A claim arising from an occurrence between the retroactive date and policy expiration can be reported ten, twenty, or fifty years later.
2. The 60-Day Request Deadline: The first named insured must request the SERP in writing within 60 days after the policy period ends. If the 60-day deadline passes without a formal written request, the right to purchase the SERP is permanently extinguished.
3. Premium Cost Limitation: The insurer may charge an additional premium for the SERP, but the CG 00 02 form caps this charge at 200 percent of the annual premium for the expiring claims-made coverage. Once in effect, an extended reporting period may not be canceled.
4. Prompt Payment Condition: The insured must pay the supplemental premium promptly when due. If it is not paid, the SERP does not take effect.
5. Excess Coverage Status: The SERP policy language explicitly states that the supplemental tail is excess over any other valid and collectible insurance available under policies in force after the SERP starts.

Reinstatement of Aggregate Limits

The crowning advantage of the SERP is the contractual reinstatement of aggregate limits.

Upon attachment of the SERP endorsement, the policy provides a brand-new, separate General Aggregate Limit and Products-Completed Operations Aggregate Limit equal in dollar value to the original limits displayed in the Declarations:

• Prior claims that depleted the original annual aggregate limits have zero impact on the SERP limits.
• If the original policy had a $1,000,000 Each Occurrence limit and a $2,000,000 General Aggregate limit, the SERP provides a fresh $2,000,000 aggregate pool dedicated exclusively to claims first reported during the SERP.

---

Comparative Matrix: Basic ERP vs. Supplemental ERP

---

Practical Claim Scenarios: ERPs in Commercial Practice

To see how the BERP and SERP function in real-world commercial accounts, consider the following claims scenarios for Apex Machinery Corp, whose claims-made policy expired on December 31, 2024 (Retroactive Date: January 1, 2019; Aggregate Limit: $2,000,000):

Scenario 1: The Fast-Filing Claimant (Mini-Tail)

On December 12, 2024 (before the policy expired), an industrial worker is injured by a conveyor built by Apex in 2022. Apex never reports the incident. The worker's lawyer sends a demand letter that Apex receives on February 20, 2025 (51 days post-expiration). Apex had not purchased a SERP.

• Coverage Result: Covered under the 60-day mini-tail. The bodily injury occurred after the retroactive date and before the policy expired, and the claim was first made within 60 days after the end of the policy period. Had the injury happened on February 10, 2025, no extended reporting period would help, because the injury would have occurred after the policy period.

Scenario 2: The Late Lawsuit with Proper Notice (Midi-Tail)

On January 25, 2025 (within 60 days post-expiration), a manufacturing client notifies Apex that a gearbox installed in 2023 cracked and caused property damage. Apex immediately sends written notice of the occurrence to its insurer. The client engages in settlement discussions but finally files a lawsuit in October 2028 (nearly four years later).

• Coverage Result: Covered under the 5-year midi-tail. Because Apex provided written notice of the occurrence within 60 days of policy expiration, the resulting claim is covered for up to 5 full years.

Scenario 3: The Unreported Latent Damage (The SERP Solution)

In 2021, Apex installed a coolant-dosing pump in a customer's food plant. Throughout 2023, a hairline crack let the pump leach coolant into stored product, contaminating inventory that no one tested at the time. In 2029, a lab audit traces the contamination to Apex's pump, and the customer makes a claim. No notice of occurrence had ever been given because no one knew the damage existed.

• Under the BERP: Zero coverage. The claim arrived long after the 60-day window, and the 5-year window applies only to occurrences reported within 60 days after expiration.
• Under the SERP: Covered. The property damage occurred in 2023, after the retroactive date and before the policy ended, and the SERP's unlimited reporting period accepts the 2029 claim, provided Apex requested the endorsement in writing within 60 days after the December 31, 2024 expiration and paid the premium. By contrast, if the pump had first failed and caused damage in 2029, no tail would respond, because that damage occurred after the policy period.