Breachvaultops • Updated November 2026
📝 Claims & Coverage • 7 min read

Claims-Made or Occurrence? How Your Liability Policy Decides Which Year Pays

A coding error in 2024, a client complaint in 2025, a lawsuit in 2026: which policy pays? A timeline of how the trigger works, and what to do when you cancel, switch carriers or sell.

SPONSORED CONTEXTUAL PLACEMENT
💼
Evaluating Enterprise Deployments in 2026?

Request our confidential total cost of ownership matrix and vendor RFP templates.

Launch Calculator →

The trigger decides which policy year pays

Every liability policy has a trigger: the event that decides which policy year has to respond. Get it wrong and a claim can fall into a gap between two policies, even though you paid premium every year without a break. That's why the claims-made vs occurrence policy choice matters well beyond the wording.

An occurrence policy responds when the injury or damage happens, whenever the claim is made. A policy you held in 2019 can pay a claim filed in 2027, provided the damage happened during 2019. A claims-made policy responds when the claim is first made against you, and usually only if you report it during that policy period or a short window after it. The year you bought the policy matters far less than the year the demand arrives.

Advertisement

Tech E&O, professional indemnity (PI) and D&O are written almost entirely on a claims-made basis worldwide. Occurrence wording remains common for general and product liability in many markets, but you'll rarely be offered it for professional risks. So for most buyers the real question isn't which trigger to pick. It's how to run a claims-made program so no year is left uncovered.

RECOMMENDED SOLUTION

Looking to streamline vendor RFP selection?

Access pre-negotiated tier discounts through our independent institutional network.

Compare Pricing →

One mistake, three dates: a worked timeline

Take a hypothetical 60-person software firm. In March 2024 it ships a faulty integration to a logistics client. In September 2025 the client emails to say shipments have been mis-routed and it is "reviewing its position." In May 2026 the client's lawyers serve a formal demand for USD 1.2 million. The firm's policies renew every 1 January.

DateEventOccurrence policyClaims-made policy
March 2024Error made2024 policy if damage begins in 2024Nothing yet; the error only needs to fall after the retroactive date
September 2025Complaint, no demandNo changeProbably not a "claim" yet, but a circumstance. Notify it and the 2025 policy is locked in
May 2026Written demand for moneyStill the policy in force when the damage occurredIf the firm didn't notify in 2025, the 2026 policy is the one in play, subject to its exclusions

The September 2025 email is the moment that matters. If the firm sends a notice of circumstances to its 2025 insurer, that policy should respond to the eventual lawsuit, under the 2025 limits and wording. If the firm stays quiet and changes carrier in January 2026, the new insurer will probably exclude the matter as a known circumstance, and the old insurer can argue the claim came after its policy expired. That's the classic claims-made gap.

Retroactive and continuity dates: how far back the cover reaches

Two dates on a claims-made schedule decide how far back your cover reaches.

The retroactive date ("retro date") is the earliest date a wrongful act can occur and still be covered. Ideally it's "full prior acts" or the date you first bought cover. If a new insurer sets it to the inception of its own policy, everything you did before that day is uninsured, even if the claim arrives mid-term.

The continuity date is separate. It's common in D&O and some PI wordings, and it anchors the prior-and-pending litigation and prior-knowledge exclusions. Matters known or pending before that date are excluded. When you move carriers, ask the new insurer to keep your original continuity date. Otherwise anything you knew about before the switch can drop out of cover.

Treat both dates as negotiable, not boilerplate. A broker who can't tell you where each sits on your current schedule hasn't read it.

Notice of circumstances: tying a future claim to this year's policy

Most claims-made wordings let you notify circumstances that could reasonably give rise to a claim. Once accepted, a later claim arising from those facts is generally treated as made in the year you gave notice. It's the most useful tool a professional liability buyer has, and it's under-used.

Insurers expect specifics. A useful notice includes:

  • The client or third party involved and the contract or engagement
  • What went wrong, when, and who was involved
  • The potential loss or the nature of the allegation
  • Why a claim is possible, such as a complaint, a missed deadline or an outage report

A vague "we might get sued someday" notice is usually rejected. Rules differ by jurisdiction. Some legal systems, Australia's for example, have statutory protection for facts notified during the policy period. Many North American forms are "claims-made and reported," with strict reporting windows. UK, EU and Asian wordings vary by insurer. Check the clause in your own policy, and when in doubt, notify before renewal.

RECOMMENDED SOLUTION

Looking to streamline vendor RFP selection?

Access pre-negotiated tier discounts through our independent institutional network.

Compare Pricing →

Switching carriers without leaving a gap

A carrier switch is where most gaps open. Before you sign with a new insurer, work through these steps in order:

  1. Sweep for circumstances. Ask delivery, account and legal leads to list complaints, disputes and incidents. Notify all credible ones to the outgoing insurer before it expires.
  2. Match the retro date. The new policy should carry your existing retroactive date, not a fresh one.
  3. Preserve the continuity date on D&O and any PI wording that uses one.
  4. Answer the proposal form carefully. In most markets, failing to disclose a known circumstance gives the new insurer grounds to decline a claim or, in some places, avoid the policy.

If the new carrier insists on a new retro date, compare its price with the cost of an extended reporting period from the old insurer. The cheaper premium often turns out to be the more expensive option.

Cancellation or shutting down: pricing an extended reporting period

When a claims-made policy ends and you don't replace it, later claims have nowhere to go. An extended reporting period (ERP, also called "tail" or "run-off" cover) lets you report claims for wrongful acts committed before the policy ended. It does not cover new work.

Many policies include a short automatic ERP, often 30 to 90 days. Longer optional ERPs usually must be bought within a set window after expiry, sometimes only 30 days. Typical 2026 market ranges, which vary by insurer, claims history and contract, are below. Confirm with your broker.

ERP lengthIndicative one-time cost (% of last annual premium)
1 yearRoughly 75%–125%
3 yearsRoughly 125%–225%
6 yearsRoughly 175%–300%

Choose the length by how long you could realistically be sued, which depends on local limitation periods and your contracts. Six years is a common benchmark in the UK and much of the Commonwealth, and some regulated professions must hold run-off for a set period. Elsewhere, statutes and contract terms can push exposure shorter or longer. Check with a broker and a local lawyer.

Selling the company: run-off for D&O and Tech E&O

In an acquisition, the target's claims-made policies usually end on a change of control or convert automatically into run-off. Former directors still face claims over pre-sale decisions, and the business still faces claims over work delivered before the deal.

Six-year D&O run-off, paid at closing, is a common negotiating outcome. Who funds Tech E&O run-off, or whether the acquirer's program picks up prior acts, is usually agreed separately. Settle it in the purchase agreement, not after signing. Where warranty and indemnity (W&I or R&W) insurance is involved, check that its exclusions line up with what the run-off actually covers.

Red flags and a rule for every renewal

Look for these on any claims-made quote:

  • A retroactive date equal to inception when you've had continuous cover
  • No optional ERP, or one the insurer can refuse to offer
  • A broad definition of "claim" that includes informal complaints, pulling matters into years you may not have notified
  • Strict reporting conditions with no grace period
  • Prior-knowledge exclusions tied to the new policy's inception rather than your continuity date

The rule: at every renewal, carrier switch, cancellation or sale, run a circumstance sweep, notify everything credible to the policy that's ending, and don't bind new cover until the retro and continuity dates match your history. Have a licensed broker or coverage lawyer review the wording before you sign.

Frequently Asked Questions

Can I buy an occurrence policy for Tech E&O or professional indemnity? +
What happens if a claim arrives after my policy lapses and I didn't buy an ERP? +
Is a client complaint a claim or a circumstance? +
Does an extended reporting period restore my policy limits? +
Who pays for run-off cover when a company is sold? +
BR
Breachvaultops Editorial Team
Independent research desk
Guides on Breachvaultops are produced by our editorial team. Pricing, features and regulations change often - confirm details with the vendor or a licensed professional before making decisions.
SPONSORED 2026 Vendor Pricing Benchmarks: Model exact seat pricing, setup fees, and ROI across our verified database.
Launch Calculator →