Category: Policy Structure & Terms
Extended Reporting Period
Also known as: ERP, tail coverage, ERP endorsement
Simply put
An Extended Reporting Period is an add-on to a claims-made insurance policy that gives the insured extra time after the policy expires to report claims. Without it, a claims-made policy generally only responds to claims reported while the policy is active. It does not create new coverage for events after the policy ends but preserves the ability to report qualifying claims that arise later.
Formal definition
An Extended Reporting Period (ERP), commonly attached by endorsement and often referred to as "tail" coverage, is a designated period following expiration or cancellation of a claims-made policy during which the insured may still report claims and obtain coverage. Subject to the specific policy wording, an ERP typically extends only the time within which a claim may be reported; it does not extend the retroactive date or cover wrongful acts occurring after the policy period. Coverage generally applies to claims arising from acts or events that took place after the applicable retroactive date and before the end of the policy period, but that are reported during the ERP. ERPs are frequently optional and may be offered on differing terms (for example, differing durations or conditions) depending on the insurer's form; whether a particular later-reported claim is covered depends on the endorsement language, the policy's exclusions and conditions, and applicable jurisdiction.
Why it matters
Cyber liability coverage is frequently written on a claims-made basis, meaning the policy generally responds only to claims that are both made against the insured and reported to the insurer while the policy is in force. This creates a structural gap: a wrongful act, privacy breach, or security failure may occur during the policy period but not surface as a claim until months or years later, after the policy has expired. An Extended Reporting Period addresses that gap by preserving the ability to report qualifying, later-emerging claims. Because notice of loss in the wrong policy period can be the difference between a defended claim and an uncovered one, the ERP is often a decisive factor in whether third-party liability exposure is actually recoverable.
Who it's relevant to
Risk managers
For organizations carrying claims-made cyber liability coverage, the ERP is a key tool for managing the transition between policies, at renewal, at cancellation, or when changing insurers. Because a claims-made policy generally will not respond to a claim reported after expiration, risk managers should evaluate whether an ERP is needed to preserve reporting rights for acts that occurred during the expiring policy but may surface later. The availability, duration, and terms of an ERP vary by insurer form and are often optional, so the specific endorsement wording should be reviewed rather than assumed.
Insurance brokers and underwriters
Brokers advising insureds on program transitions need to identify where reporting gaps could arise and whether an ERP or comparable arrangement addresses them, recognizing that ERPs may be offered on differing durations and conditions depending on the insurer's form. Underwriters set the terms on which an ERP is offered and should be clear that an ERP extends the reporting window only and does not extend the retroactive date or cover post-expiration wrongful acts. Both parties should treat coverage of any later-reported claim as conditional on the endorsement language, exclusions, and jurisdiction.
Legal and compliance professionals
When a cyber incident or privacy claim emerges after a claims-made policy has lapsed, counsel must determine whether reporting rights survive through an ERP and whether the claim falls within the covered window, that is, arising from acts after the retroactive date and before policy expiration but reported during the ERP. Because whether a particular claim is covered depends on the precise endorsement wording, conditions precedent, and applicable jurisdiction, careful review of the policy terms is essential before relying on tail coverage.
Inside ERP
Claims-Made Trigger Foundation
An extended reporting period (ERP) exists because cyber liability coverage is typically written on a claims-made basis, meaning the policy responds to claims first made against the insured and reported during the policy period. The ERP extends only the window for reporting claims, not the period during which covered wrongful acts or incidents may occur.
Reporting Window Extension
An ERP grants additional time after policy expiration or cancellation to report claims arising from wrongful acts, privacy events, or security failures that occurred before the policy ended (and after any applicable retroactive date). It does not create new coverage for events happening after expiration.
Retroactive Date Interaction
The ERP works together with the retroactive date, which typically sets the earliest point from which covered acts can originate. An ERP generally extends the reporting deadline but does not move the retroactive date, so acts occurring before that date usually remain outside coverage.
Automatic vs. Optional ERP
Many policies provide a short automatic (basic) ERP at no additional premium and offer a longer optional (supplemental) ERP that the insured may elect, usually for an additional premium and within a defined election window. The exact lengths and terms depend on the specific policy wording.
Third-Party Liability Orientation
ERPs are most commonly associated with the third-party liability sections of a cyber policy (such as privacy liability and regulatory defense). Their application to first-party coverages (such as business interruption, data restoration, or cyber extortion), which often operate on different triggers, depends on the specific policy and may be limited or absent.
Triggering Circumstances and Conditions
The availability and terms of an ERP are typically subject to conditions precedent, such as timely written election, payment of any additional premium, and the circumstances of policy termination. Wording, endorsements, exclusions, and jurisdiction all affect how an ERP operates in practice.
Common questions
Answers to the questions practitioners most commonly ask about ERP.
Does an Extended Reporting Period give me more time to experience or suffer a loss?
No. An Extended Reporting Period (ERP) generally extends only the time within which you may report claims to the insurer, not the time in which covered events may occur. In claims-made policies, the wrongful act, breach, or triggering event typically must still have taken place before the policy's expiration or a specified retroactive date. The ERP addresses the gap between when an incident happens and when a claim is actually made against you, subject to the specific policy wording.
Does purchasing an Extended Reporting Period restart or renew my coverage limits?
Not in most policies. An ERP typically operates within the limits of the expiring policy rather than providing a fresh set of limits. Claims reported during the ERP usually erode or share the same aggregate limit that applied to the underlying policy period. Whether any limits are reinstated or provided separately depends entirely on the specific wording and any negotiated endorsements.
When should I consider electing an Extended Reporting Period?
An ERP is often relevant when a claims-made policy is not being renewed or is being replaced by a new insurer, particularly where the new policy does not offer full prior-acts coverage back to the original retroactive date. Electing an ERP can help address claims arising from acts that occurred during the expired policy period but are reported after it ends. The availability, length, and cost of the option depend on the policy terms and applicable conditions.
How long does an Extended Reporting Period last, and can I choose the length?
The available duration and whether you can select among options are governed by the policy wording. Some forms offer a short automatic (basic) ERP at no additional charge and a longer supplemental ERP available for an additional premium, and durations vary across insurer forms. Because these arrangements differ significantly, review the specific policy language and any endorsements to confirm what is offered rather than assuming a standard term.
Are there deadlines or conditions I must satisfy to elect an Extended Reporting Period?
Typically yes. Many policies impose a defined election window after expiration or non-renewal and may require payment of any additional premium within a set time as a condition precedent to the ERP taking effect. Missing these deadlines can forfeit the option. Confirm the exact election period, notice requirements, and payment conditions in the specific policy, and coordinate timing with any replacement coverage.
How does an Extended Reporting Period interact with prior-acts coverage under a new policy?
An ERP and prior-acts (retroactive) coverage address overlapping gaps from different directions, and they should be evaluated together to avoid both duplication and coverage gaps. If a replacement policy grants full prior-acts coverage back to the original retroactive date, an ERP on the expiring policy may be less necessary; if it does not, an ERP may help cover claims tied to the earlier period. How these provisions align depends on the wording of both policies, and coordination is best reviewed with your broker.
Common misconceptions
An extended reporting period gives you extra coverage for incidents that happen after the policy ends.
An ERP extends only the time to report claims arising from wrongful acts or incidents that occurred before policy expiration (and after any retroactive date). It generally does not cover new events occurring after the policy period ends.
Because a policy has an ERP, there is no need to arrange continuous coverage or a new policy going forward.
An ERP is a backward-looking reporting mechanism, not a substitute for prospective coverage. It does not respond to future incidents, so continuous or replacement coverage is typically still needed to address ongoing exposure.
The automatic ERP included at no cost provides the same protection as a purchased supplemental ERP.
Automatic and optional ERPs typically differ in duration and sometimes in scope. The basic automatic period is often short, while a longer supplemental ERP usually requires timely election and additional premium, subject to the specific policy wording.
Best practices
Confirm whether your cyber policy is written on a claims-made basis and identify both the retroactive date and the ERP terms, since the ERP only helps for acts occurring within that retroactive-date-to-expiration window.
Note the election deadline and premium requirements for any optional (supplemental) ERP well before policy expiration, because the right to purchase it is typically time-limited and subject to conditions precedent.
Clarify with your broker or insurer which coverage sections the ERP applies to, distinguishing third-party liability coverages from first-party coverages that may operate on different triggers.
Do not treat an ERP as a replacement for continuous or replacement coverage; arrange forward-looking coverage to address incidents occurring after the current policy expires.
When changing insurers or non-renewing, evaluate how the new policy's retroactive date aligns with prior coverage to avoid gaps that an ERP alone may not close.
Review the specific policy wording, endorsements, and exclusions with counsel or your broker to understand how the ERP interacts with reporting obligations and whether any jurisdictional variations apply.
