Guard Policy CloudEnterprise Underwriting Intelligence
Claims & Coverage

Switching Tech E&O Carriers? How Retroactive Dates Decide Which Old Work Is Covered

Switch tech E&O carriers carelessly and a project from three years ago can end up covered by no one. Here's how retro dates, tails and run-off decide that, and what to get in writing before you sign.

By the Guard Policy Cloud editorial team · November 2026 · 9 min read

The one date that decides whether your old projects stay insured

If you're moving your technology errors and omissions cover to a new insurer, the premium and limit aren't the most important terms on the quote. The tech E&O retroactive date is. It decides whether software you shipped, systems you integrated or advice you gave before the switch is still covered once the new policy takes over.

Get it wrong and you can be uninsured for years of past work, even though you've paid premiums without a break. The failure is quiet. Nothing looks wrong until a client sues over a 2023 implementation, your old carrier says the claim arrived after its policy ended, and your new carrier says the work happened before its cover began.

Advertisement

Below: how the claims-made trigger works, the three ways a retro date can be set, two hypothetical scenarios where a gap opens, and how London-market and North American wordings handle the problem differently.

How a claims-made policy trigger actually works

Most tech E&O and professional indemnity (PI) cover worldwide is written on a claims-made basis. The claims-made policy trigger usually needs two things to be true at once:

  • The claim is first made against you, and usually reported to the insurer, during the policy period or any reporting window attached to it.
  • The wrongful act, error or breach behind the claim happened on or after the retroactive date.

Occurrence-based cover, such as most general liability, works the other way: the policy in force when the incident happened responds, whenever the claim shows up. With claims-made cover, the policy that answers is the one in force when the claim arrives. Every year's policy therefore has to reach back over your whole service history.

Tech claims tend to surface late. A data-migration error can sit unnoticed through a full audit cycle. A flaw in delivered code can be exploited two years after go-live. The gap between the work and the claim is often several years.

Full prior acts, matched retro, or inception-dated: the three settings

A new carrier will offer one of three retro positions. Know which one you're being quoted.

  • Full prior acts coverage (in London wordings, often called "unlimited retroactive cover"). Past work is covered whenever it was done, subject to the prior-knowledge exclusions discussed below. It's common in London-market PI and often available to established firms with clean histories.
  • Matched retro date. The new insurer adopts the retro date on your expiring policy, often the date you first bought E&O. This is the normal position for a well-handled switch in North America.
  • Retro date equal to inception. Only work done from the first day of the new policy is covered. A startup buying its first policy loses nothing by accepting this. For a company switching carriers, it wipes out cover for everything already delivered.

Carriers sometimes quote an inception-dated retro to a switching buyer to limit their exposure, or because the application didn't show unbroken prior cover. A matched date may cost more. For most firms with several years of client work behind them, pay it: past work usually represents more exposure than next year's new work.

Scenario one: a routine carrier switch that leaves a 2024 project uninsured

Hypothetical example. Say a 60-person SaaS implementation firm has carried tech E&O with Carrier A since March 2019, with a March 2019 retro date. In April 2026 it moves to Carrier B to save roughly 15% on premium. Carrier B's quote shows a retro date of 1 April 2026, and nobody reads that line closely.

In 2027 a client claims damages over a 2024 integration that corrupted its billing data. Carrier A's policy has expired and the claim wasn't made during its period. Carrier B's policy is in force, but the wrongful act predates its retro date. Neither policy pays.

A matched retro date can still leave a second, less obvious gap. Suppose the firm's CTO received an angry email from that client in February 2026, before the switch, and didn't pass it on. Carrier B's application asked whether anyone knew of circumstances that could lead to a claim. Its prior-knowledge exclusion removes the claim, and Carrier A was never notified while its policy was live. Same result: no cover.

The fix is procedural. Before the old policy expires, poll senior staff for known issues and send a notice of circumstances to the expiring carrier.

Scenario two: buying a development shop with years of client work behind it

Hypothetical example. A mid-size IT services group acquires a 25-person app developer that has had its own E&O since 2020. Acquisitions squeeze the retro date from two directions.

First, the target's own policy. Many North American forms include a change-in-control clause. On closing, cover typically continues only for wrongful acts committed before the deal, runs to the end of the current period, and then can't be renewed. Second, the buyer's policy. Automatic-acquisition clauses commonly add new subsidiaries below a size threshold, often defined against the buyer's revenue or assets, but they frequently set the subsidiary's retro date at the acquisition date.

The result: years of the target's past client work have no long-term home unless someone buys a tail or run-off for the target. Settle this in the sale agreement: who pays, for how many years, and whether the limit is shared with the buyer's programme. Where the deal uses warranty and indemnity insurance, remember it generally excludes matters the buyer already knew about. It doesn't replace E&O run-off.

Extended reporting periods and run-off cover: what you get and what it costs

When a claims-made policy ends with nothing replacing it, because the firm is sold, merged or closed, or because the new policy is inception-dated, protection for past work comes from a reporting extension. North American forms call this an extended reporting period (ERP), usually shortened to "tail". London-market and Commonwealth buyers usually buy run-off cover for professional indemnity instead, typically as a separate multi-year policy.

Neither adds new cover. Both extend the window for reporting claims from work done before the policy ended. In most designs the limit isn't refreshed, so one aggregate limit covers the whole tail period.

OptionTypical lengthIndicative cost (typical 2026 market ranges)
Automatic / basic ERPOften 30 to 90 daysUsually included at no charge
Optional ERP, 1 year12 monthsRoughly 75% to 100% of the expiring annual premium
Optional ERP, 3 years36 monthsRoughly 150% to 200%
Optional ERP or run-off, 6 years72 monthsRoughly 200% to 300%, or a negotiated one-off premium

Pricing varies widely with claims history, type of services, limit and region, so confirm it with your broker and carrier. Watch the election deadline: optional ERPs often must be bought within 30 to 60 days of the policy ending, and some forms withdraw the option if you've bought replacement cover elsewhere.

How London-market PI wordings and North American E&O forms differ

The core logic is the same everywhere, but the details change how you should plan a switch. Many markets across the Middle East, Southeast Asia, Africa and parts of Latin America use London-style wordings or reinsure into London, while Canada and the US mostly use carrier-specific North American forms. Admitted-insurer rules, compulsory-cover rules and limitation periods also vary by country.

FeatureLondon-market PI (typical)North American tech E&O (typical)
Default retro positionUnlimited retro is common for established firmsSpecific retro date, matched to prior cover
Protection for past work after exitStandalone run-off policy, often 6 yearsOptional ERP endorsement on the expiring policy
Known-issue protectionContinuity date and circumstance notificationPrior-knowledge exclusion and pending-litigation date
Coverage grantOften broad "civil liability" wordingDefined "wrongful act" or "professional services"
Defence costsInside or in addition to the limit; checkUsually within the limit

Run-off in London-style markets is often set at six years because many common-law limitation periods for contract claims are around six years. Limitation rules differ by jurisdiction, though, and some countries have latent-damage longstops that run longer. Ask a local lawyer how long your realistic exposure lasts.

Red flags to catch in the new quote before you bind

  • Retro date blank, "inception", or later than your first policy. Get the match in writing on the declarations page, not just in the broker's cover email.
  • A pending or prior litigation date reset to inception. This can exclude disputes already brewing, even when the retro date is matched.
  • A continuity date later than your retro date in London wordings. The insurer then won't cover circumstances you could have known about before that date.
  • Narrower definitions of professional services that leave out work you did in the past, such as managed services or hardware resale.
  • A lower limit. Past work is then insured for less than before.
  • Application warranties signed without an internal check. One undisclosed complaint can void cover for the related claim.

A switching checklist and the decision rule to apply

  1. Pull every expiring policy schedule and confirm your original retro date and continuity history.
  2. Ninety days before expiry, survey project leads and executives for client complaints, missed milestones and threatened disputes.
  3. Send a notice of circumstances to the expiring carrier for anything that turns up.
  4. Ask the new carrier for full prior acts or a matched retro date, plus a matching pending-litigation or continuity date.
  5. If a match isn't available, price an optional ERP or run-off on the expiring policy before it lapses.
  6. For acquisitions, write tail or run-off responsibility and duration into the sale agreement.

The decision rule: don't bind a replacement policy that covers less past work than the one it replaces, unless you've already bought a tail to cover the difference. If the saving from switching is smaller than the cost of a three-year tail, stay with the current carrier and renegotiate there. These terms affect your rights under the contract, so have a licensed broker or coverage lawyer review the final wording before you bind.

Frequently asked questions

Does switching carriers always reset my tech E&O retroactive date?

No. A carrier can match your existing retro date or grant full prior acts coverage. You usually have to ask, provide proof of continuous cover, and sometimes pay more. Check the declarations page, because the retro date shown there is the one that applies.

Can I buy an extended reporting period and also a new policy?

Sometimes, but many North American forms restrict or withdraw the optional ERP if you buy replacement cover. Buying both mainly makes sense when the new carrier won't match your retro date: the tail covers past work and the new policy covers future work. Confirm the election deadline and any restrictions with your broker before the old policy ends.

How long should run-off cover for professional indemnity last after selling a business?

Six years is a common choice in London-style markets because it matches many contract limitation periods. Your real exposure depends on your country's limitation rules, contract terms and the type of work. Firms with long-tail exposure, such as critical-infrastructure or financial-systems work, sometimes negotiate longer. A local lawyer can tell you how long claims could realistically arrive.

Is a matched retro date enough to guarantee my past work is covered?

Not by itself. Prior-knowledge exclusions, pending-litigation dates and continuity dates can still remove claims tied to issues you knew about before the switch. Report known circumstances to your expiring carrier before it lapses, and make sure the new policy's other dates line up with your history.

Written by the Guard Policy Cloud editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.