Why These Dates Matter
A liability claim can arrive long after the act that allegedly caused the loss. Under claims-made coverage, the date of that act is not the only date that matters: the date the claim is first made, the date it is reported, and any retroactive date can each affect whether the policy responds. If coverage ends, an extended reporting period may allow certain claims to be reported later, but it does not provide unlimited coverage for every past or future act.
This tutorial uses hypothetical policy terms to show how these dates work together. The exact contract controls. In particular, policies may define the reporting requirement differently, and an extended reporting period endorsement may have specific conditions. Assume in each example that all other coverage requirements are satisfied unless the example says otherwise. This topic is aligned with the SOA Exam FAM (Fundamentals of Actuarial Mathematics) syllabus.
The Dates in a Claims-Made Timeline
Keep four dates distinct. The act date is when the alleged injury-causing act, error, or omission occurred. The policy period is the interval when the policy is in force. The claim date is when a claim is first made against the insured, as defined by the policy. The report date is when the insured gives notice to the insurer. Those dates can be separated by months or years.
A basic claims-made trigger generally requires that a claim first be made during the policy period, subject to the policy’s terms. A claims-made-and-reported form additionally requires that the claim be reported within the specified reporting window. Some policies have other reporting language, so do not assume that the two forms impose identical requirements. A retroactive date adds a separate test: even if the claim and reporting dates qualify, an act before the retroactive date may be outside coverage.
| Question | Date or term to check | What it determines |
|---|---|---|
| When did the alleged act occur? | Act date compared with retroactive date | Whether the act falls within the permitted prior-acts period |
| When was the claim first made? | Claim date compared with policy and ERP dates | Whether the claim was made within an allowed window |
| When was the insurer notified? | Report date compared with the reporting terms | Whether notice was timely under the policy or ERP |
Worked Example: Testing a Prior Act Against the Retroactive Date
A hypothetical professional liability policy runs from January 1, 2025, through December 31, 2025, and has a retroactive date of January 1, 2022. Its terms require the claim to be first made and reported during the policy period. A client first makes a claim on August 10, 2025, and the insured reports it on August 12, 2025. The claim alleges an error made on December 20, 2021. Does the claim satisfy the timing conditions?
Method. Check the act date against the retroactive date, then check the claim and report dates against the policy period.
The act occurred on December 20, 2021, which is before January 1, 2022. It therefore fails the retroactive-date condition. The claim was first made on August 10, 2025, and reported on August 12, 2025; both dates fall within the stated policy period. Those two successful timing tests do not cure the failed act-date test.
Conclusion. The claim does not satisfy all the stated timing conditions because the alleged act predates the retroactive date. The common mistake is to see that the claim and report occurred in 2025 and stop there. A claims-made timeline must be tested against each applicable date condition.
What an Extended Reporting Period Does
An ERP can provide a limited opportunity to report claims after the policy’s ordinary expiration or termination. Under the hypothetical wording used here, a claim must first be made during the ERP and reported by its stated deadline. The ERP attaches to the expiring policy; it is not automatically a new policy period covering new acts. The act must still meet the policy’s retroactive-date condition and any other applicable terms.
The wording matters. An ERP may specify how long it lasts, which claims can be reported, and whether the claim must be both first made and reported during the ERP. It may also address claims first made before expiration but reported afterward. Do not infer answers to those questions from the phrase “tail coverage” alone. For each problem, use the stated endorsement terms.
Worked Example: Separating Claim Date from Report Date
A hypothetical policy covers January 1, 2024, through December 31, 2024, with a retroactive date of January 1, 2020. Its purchased ERP runs through February 28, 2025. The endorsement says that a claim first made during the ERP may be reported no later than February 28, 2025, and that the alleged act must have occurred during the policy period or earlier, but not before the retroactive date. A claim alleging a November 2023 act is first made on February 20, 2025, and reported on February 25, 2025. Does it meet the stated timing conditions?
Method. Treat the act-date, claim-date, and report-date tests separately. The act occurred in November 2023, which is before the policy expired on December 31, 2024, and after the January 1, 2020 retroactive date. The act-date condition is met.
The claim was first made on February 20, 2025. That is after the ordinary policy period but within the ERP through February 28, 2025. The claim was reported on February 25, 2025, also by the ERP deadline. Thus both the claim-date and report-date conditions are met under the endorsement as stated.
Conclusion. The claim satisfies the stated timing conditions. The common mistake is to compare only the report date with the ERP deadline. Here the claim also had to be first made during the ERP, and it was. This conclusion concerns only the specified timing conditions, not any other policy terms.
Why the Conditions Must Be Checked Together
The coverage test is conjunctive: meeting one date condition does not replace another. For the common hypothetical claims-made-and-reported arrangement with a retroactive date, eligibility on timing grounds requires all of the stated conditions to hold. An ERP supplies an alternative claim and reporting window only if the policy or endorsement says it does.
This follows directly from the meaning of the conditions. The retroactive date restricts the acts to which the coverage may apply. The claims-made trigger restricts when a claim must first be made. The reporting provision restricts when the insurer must receive notice. Since each condition is required by the assumed wording, failure of any one means that the timing test is not satisfied. An ERP changes only the relevant allowed claim or reporting window to the extent its terms provide; it does not erase the other requirements.
Identify when the alleged act occurred; do not substitute the date the injury was discovered or the claim arrived.
If the act predates the retroactive date, the stated prior-acts condition fails, even if a claim is made and reported on time.
Compare that date with the policy period and, if relevant, the claim window expressly provided by an ERP.
Apply the policy’s reporting rule and any applicable ERP deadline. State which wording you are using.
Worked Example: An ERP Does Not Extend the Act Period
A hypothetical policy ends on June 30, 2025, has a retroactive date of July 1, 2021, and includes an ERP through September 30, 2025. The endorsement permits claims first made and reported during the ERP for acts that occurred no later than June 30, 2025, and not before the retroactive date. A claimant first makes a claim on September 10, 2025, and the insured reports it on September 12, 2025. The alleged act occurred on July 5, 2025. Evaluate the stated timing conditions.
Method. First check the act against the retroactive date, then check whether the act is within the endorsement’s act period, and finally check the claim and report dates against the ERP.
July 5, 2025, is after the retroactive date of July 1, 2021, but it is also after the policy ended on June 30, 2025. The endorsement expressly limits eligible acts to those occurring no later than June 30, 2025, so the act-period condition fails. The claim date, September 10, and report date, September 12, are both within the ERP through September 30. These dates do not change the result.
Conclusion. The claim fails the stated timing conditions because the act occurred after the covered act period. The common mistake is to treat the ERP as if it extended the policy’s coverage for new acts. In this example, it extends the claim and reporting window, not the act period.
Common Mistakes and a Reliable Review
The most dependable approach is to write the four relevant items on a timeline before reaching a conclusion: retroactive date, policy period, claim date, and report date. If an ERP applies, mark its exact beginning and ending dates and note whether its wording applies to the claim date, the report date, or both.
- Using the injury date as the claim date. The claim date concerns when a claim is first made against the insured under the policy’s definition; it is not necessarily the date of the alleged act or injury.
- Treating an on-time report as sufficient. A timely report cannot fix a claim that was first made outside the allowed window, if the policy requires the claim to be made within that window.
- Assuming every ERP works the same way. The endorsement determines its duration, eligible claims, and reporting requirements. Read those stated terms rather than relying on the label alone.
- Assuming an ERP resets the retroactive date. An ERP does not automatically make acts before the retroactive date eligible.
- Calling a date-based conclusion a complete coverage decision. Satisfying the timing conditions does not establish that every other policy requirement is satisfied.
For a claims-made timeline, reach a conditional conclusion: state which timing tests are met, identify any failed condition, and limit the conclusion to the policy wording given. This prevents a single favorable date from obscuring a separate condition.
Check Your Understanding
For each hypothetical scenario, assess the stated timing conditions. Use the policy wording in the question; assume other requirements are satisfied.
- A policy runs January 1 through December 31, 2026, has a retroactive date of January 1, 2023, and requires claims to be made and reported during the policy period. An alleged act occurred December 15, 2022; the claim is made June 2, 2026, and reported June 4, 2026. Does it meet the stated timing conditions? (Answer: No; the act predates the retroactive date.)
- A policy runs January 1 through December 31, 2025, has a retroactive date of January 1, 2020, and requires claims to be made and reported during the policy period. An act occurred March 1, 2024; the claim is first made December 30, 2025, but reported January 3, 2026. Is the stated reporting condition met? (Answer: No; the report falls after the policy period, and no ERP is specified.)
- A policy ends September 30, 2025, has a retroactive date of January 1, 2022, and an ERP through December 31, 2025. The endorsement requires the claim to be first made and reported during the ERP and permits acts through the policy’s end date. An act occurred September 20, 2025; the claim is first made December 20, 2025, and reported December 29, 2025. Do the stated timing conditions hold? (Answer: Yes; the act is after the retroactive date and by policy end, and both claim and report fall within the ERP.)
- A policy ends March 31, 2025, has a retroactive date of April 1, 2020, and an ERP through June 30, 2025. Its endorsement requires a claim to be first made and reported during the ERP and permits acts no later than March 31, 2025. An act occurred on April 1, 2020; the claim is made June 25, 2025, and reported June 30, 2025. Does it meet the stated date conditions? (Answer: Yes; the act is on, not before, the retroactive date, and the claim and report meet the stated ERP dates.)
- A policy runs July 1, 2024, through June 30, 2025, has a retroactive date of July 1, 2020, and an ERP through August 31, 2025. The endorsement requires claims to be first made and reported during the ERP for acts no later than June 30, 2025. An act occurred June 30, 2025; the claim is first made September 1, 2025, and reported September 2, 2025. Are the stated timing conditions met? (Answer: No; both the claim and report fall after the ERP deadline.)