The Claims-Made Nature of EPLI
In the realm of Employment Practices Liability Insurance (EPLI), the vast majority of policies are written on a claims-made basis. Unlike occurrence-based policies, which provide coverage for incidents that happen during the policy term regardless of when the claim is filed, claims-made policies require the claim to be made against the insured during the active policy period. This fundamental shift in trigger logic necessitates the use of retroactive dates to manage risk exposures from the past.
Understanding the interplay between the claim filing date and the incident date is a core competency for the practice EPLI questions on the specialty exam. Without a clear retroactive date, an insurer would theoretically be on the hook for every wrongful act in a company's history, which is an unquantifiable risk. Conversely, for the insured, a restrictive retroactive date creates a significant liability gap for past actions that have not yet resulted in a formal claim.
Defining the Retroactive Date
The Retroactive Date (often called the 'Retro Date') is the specific point in time after which a wrongful act must have occurred to be eligible for coverage under the current claims-made policy. If a supervisor engaged in harassment before this date, and the resulting claim is filed during the current policy term, the insurer will typically deny coverage because the underlying event happened 'pre-retro.'
The Retroactive Date is usually established when an organization first purchases an EPLI policy and remains consistent through successive renewals with the same carrier. Maintaining this date is essential for ensuring continuity of coverage. For a deeper dive into policy structures, see our complete EPLI exam guide.
- Incident Date: When the alleged wrongful act (e.g., discrimination, wrongful termination) happened.
- Claim Date: When the formal demand or legal notice was received by the insured.
- Retroactive Date: The temporal boundary line for the incident date.
Prior Acts Coverage vs. Retroactive Date Limitations
| Feature | Limited Retroactive Date | Full Prior Acts Coverage |
|---|---|---|
| Coverage Trigger | Acts after a specific date only | Acts occurring at any time in the past |
| Risk Level | Higher (potential gaps for old acts) | Lower (comprehensive look-back) |
| Premium Impact | Standard/Lower | Higher/Premium |
| Common Usage | Standard for new policies | Offered to established low-risk firms |
The Danger of Moving or Resetting Retroactive Dates
One of the most dangerous scenarios in employment liability is the resetting of a retroactive date. This often happens when a policyholder switches insurance carriers. If the new carrier insists on setting the retroactive date to the inception of the new policy, the insured loses coverage for all prior acts that occurred under the previous carrier but have not yet been reported as claims.
To avoid this, brokers and risk managers must negotiate for Prior Acts Coverage, which carries over the original retroactive date from the previous policy. This ensures that the 'chain' of coverage remains unbroken. If a gap occurs, the insured may be forced to purchase an Extended Reporting Period (ERP), or 'tail coverage,' from the outgoing carrier to protect against claims arising from those past incidents.
Exam Tip: The 'Knowledge' Exclusion
Even if a policy has a retroactive date that covers a prior act, the Prior Knowledge Exclusion may still apply. If the insured knew or could have reasonably foreseen that a claim would arise from an event before the policy inception, the insurer will likely deny the claim, regardless of the retroactive date. Always look for the 'reasonable person' standard in exam scenarios regarding prior knowledge.
Core Mechanics Summary
Frequently Asked Questions
Full Prior Acts coverage means the policy does not have a specific retroactive date. It covers any wrongful act that occurred before the policy period, provided the claim is made during the policy period and the insured had no prior knowledge of the potential claim.
An insurer might refuse if there has been a significant gap in coverage, if the company has a high frequency of past claims, or if the company is undergoing major structural changes like a merger or acquisition that increases the risk of unknown past liabilities.
Yes. If the underlying incident occurred before the retroactive date, the policy is not triggered, meaning the insurer has no duty to defend the claim or pay for legal expenses associated with it.
A Retroactive Date looks backward from the policy start to see if an incident is covered. An ERP looks forward after a policy has expired, allowing claims to be reported for incidents that happened during the policy period (after the retro date but before the expiration).