5C Insurance
Switching Claims-Made Insurance: A California Business Checklist
How an advanced retroactive date, prior-acts coverage, and an extended reporting period affect a claims-made switch — and what to confirm in writing before the old policy expires.
By 5C Insurance · Published November 16, 2026 · Updated November 16, 2026
Note: Sources reviewed November 16, 2026. This guide is general information; actual coverage, retroactive dates, and reporting terms depend on the policy and underwriting. Confirm any deadline against your actual policy and the insurer's instructions.
Why switching a claims-made policy is different
A claims-made policy covers claims first made — reported to the insurer — during the policy period, subject to its terms. When you replace one claims-made policy with another, the switch is not a seamless continuation: the new policy's retroactive date, the expiring policy's reporting rules, and any extended reporting period (tail) each determine whether a claim from earlier work is covered, and by which policy. Treat the switch as a handoff to be confirmed in writing, not an automatic transfer. The wrong date or a missed reporting deadline can leave a claim without a responding policy — even when the work itself was covered at the time.
Professional liability, Tech E&O, and cyber: a California business checklist →
An advanced retroactive date can leave earlier work outside the new policy
The retroactive date limits which acts the policy will consider. If the replacement policy's retroactive date is later (more recent) than the expiring policy's, work performed before the new date may fall outside the replacement's coverage. That is why prior-acts coverage — extending the replacement policy's retroactive date back to or earlier than the expiring policy's — is usually the key term in a switch. A date that is not aligned can create a gap for earlier professional services. Ask for the actual retroactive date in writing and confirm it covers the period you need.
A hypothetical date example
Suppose a firm's expiring claims-made policy carried a retroactive date of January 1, 2020, and it expires December 31, 2026. The firm replaces it with a new policy effective January 1, 2027. If the replacement policy's retroactive date is set at January 1, 2020 — matching or predating the expiring policy's date — work performed from 2020 forward can generally be considered by the new policy, subject to its terms. If the replacement's retroactive date is instead set at the new policy's inception (January 1, 2027), work performed from 2020 through 2026 may fall outside the replacement's coverage. This example illustrates how dates drive coverage; it does not describe your actual policy or guarantee any outcome.
An extended reporting period on the expiring policy
An extended reporting period (ERP), sometimes called a tail, is purchased on the expiring policy and generally extends the time to report qualifying claims arising from acts that occurred before the policy expired. An ERP extends the reporting window for eligible earlier claims; it does not extend the policy period for new work performed after the policy ends, and it does not create new coverage where none existed. If you purchase a tail on the expiring policy, confirm in writing how long the reporting window lasts, what claims it covers, and what it excludes. If you rely on the replacement policy's prior-acts coverage instead, confirm that the retroactive date fills the gap the expiring policy leaves behind.
Reporting timing varies by form
Claims-made reporting deadlines — how quickly a claim must be reported once made, and what counts as 'made' — vary by form and by state. A deadline that applied under the expiring policy may not be the same under the replacement. Ask how each form treats a claim first made during its policy period, whether notice must be in writing, and what the reporting deadline is. Do not assume the two policies share the same reporting rules.
Known claims and circumstances
Both the expiring and replacement policies may exclude or limit claims or circumstances already known at the time coverage attaches. Before the expiring policy expires, discuss any known claims or circumstances with your broker and ask how the actual policy requires them to be reported. A circumstance reported under the expiring policy may not transfer to the replacement automatically, and a known claim reported late can be denied under either. Address known matters before the expiration date rather than assuming the new policy picks them up.
A switching checklist
Use this to compare the expiring and replacement claims-made policies on the same terms before the old policy expires. Confirm the actual dates and reporting rules in writing from each insurer's authorized representative.
- Compare declarations and endorsements — insureds, defined services, limits, retentions, and exclusions across both policies
- Confirm the replacement policy's inception date and retroactive date in writing — verify it predates or matches the expiring policy's retroactive date if you need continuous prior-acts coverage
- Ask about changes in terms, conditions, and reporting deadlines between the two forms
- If a tail is available on the expiring policy, ask for the election deadline in writing and what the ERP covers and excludes
- Discuss any known claims or circumstances with your broker before expiration and confirm how the actual policy requires them to be reported
- Confirm which policy responds to a claim first made during the switch and how the two policies coordinate to avoid a gap
- Keep copies of the written confirmations and the actual declarations and endorsement pages from both policies
Sources reviewed
Frequently asked questions
Next step
Pull the declarations and endorsement pages from both policies and request a quote or coverage review — we'll walk through the retroactive date, reporting terms, and any tail election before the switch.
Put this into action
Request a quote or ask a coverage question — we'll help you apply this to your business.
