Claims-made E&O looks ordinary on the declarations page, which is exactly why it catches firms off guard. The limit and the premium are easy to read. The parts that actually decide whether your past work stays covered, the retro date, unbroken continuity, and a tail at the end, are not the parts most owners look at. When continuity breaks, the claim that follows is rarely about the quality of your work. It is about a hole in the timeline. If you want the foundation first, what is claims-made coverage and the retro date explains how the structure works.
Why claims-made is different
Most E&O is written on a claims-made basis. That means the policy in force when a claim is made is generally the one that responds, not the policy from the year the work was actually done. That single rule changes everything about how you have to think about coverage. With an occurrence policy, the year of the work locks in its own protection and you can move on. With claims-made, protection for old work lives inside your current policy, and it only stays there as long as the chain from year to year holds together. Continuity is not a nice to have. It is the mechanism.
The retro date, and how it slips
The retroactive date generally sets how far back your covered work reaches. Work done before it is typically outside the coverage, even under a current policy. In a stable program the retro date sits far in the past and quietly protects everything you have done since. The danger is that it can move without anyone deciding it should. Switch carriers carelessly and the new policy may write a fresh retro date at today. Reinstate after a lapse and the same thing can happen. In a moment the years behind that new date stop being covered, and nobody notices until a claim on old work has nowhere to land.
The lapse that opens a hole
A lapse is the most common way continuity breaks. Coverage gets missed during a busy stretch, a renewal slips, a payment is late, and there is a gap in the timeline. When the firm reinstates, the new policy may carry a later retro date, and the work done before it can fall out of coverage. The uncomfortable part is that the lapse does not have to be long to matter. A short gap can still reset the timeline, and a claim that surfaces later on earlier work may find no continuity behind it. The firm did the work. The structure is what failed.
The tail at the end
Continuity also matters at the finish. Because claims-made responds based on when a claim is made, ending a policy can leave a window where old work is exposed and no current policy exists to answer. Tail coverage, also called an extended reporting period, generally lets you report claims after a policy ends for work done while it was in force. It is most important when you close the firm, retire, merge, or switch in a way that does not carry your retro date forward. Skipping the tail to save the premium is how a clean exit turns into an uncovered claim months later.
Keeping the chain intact
The through line is simple even if the mechanics are not. Know your retro date, keep coverage continuous, and plan for a tail whenever a policy ends or a change is coming. None of that shows up in the limit, which is why price and limit shopping misses it entirely. The firms that get surprised are almost never the ones with bad work. They are the ones whose timeline had a break they never saw.
Questions to ask your advisor
- What is my retro date, and has it carried forward through every past renewal?
- If my coverage lapsed even briefly, what happens to work done before the gap?
- When I renew or switch, how do we preserve the existing retro date?
- If I close or sell the firm, do I need a tail, and for how long?
- Which of my past engagements would still be covered if a claim surfaced today?
Claims-made coverage protects your history only as long as the chain holds. A firm that confirms its retro date, guards continuity, and plans the tail is protecting the work it already did, not just the work ahead.
Want guidance first? Compare your coverage. Already know what you need? Get a quote.