Claims-Made vs. Occurrence Policies: What’s the Difference?

If insurance were a time machine, occurrence policies would be the kind that remembers what happened, while claims-made policies are the kind that remembers when you told it what happened. Both can protect you from expensive “uh-oh” momentslawsuits, allegations, demands, and those friendly letters that begin with “We represent…”but they do it on different timelines.

And yes, timelines matter. In liability insurance, the event and the claim often live in different zip codes of time. A client complains today about work you did two years ago. A patient sues after a long course of treatment. A data issue is discovered months after the “oops.” The policy formclaims-made or occurrencedecides which policy responds.

The Big Idea in One Sentence

Occurrence coverage is triggered by when the incident happened, while claims-made coverage is triggered by when the claim is made (and often reported). That one difference explains nearly every other detailcost, complexity, tail coverage, and why people get surprised at renewal time.

Start Here: What “Triggers” Coverage?

Insurance people love the word trigger. It sounds dramatic, like your policy is a spy gadget. In reality, it’s simply the rule that answers: Which policy year pays?

Occurrence: “Was it during my policy period?”

With an occurrence policy, coverage is tied to the date the bodily injury, property damage, or covered offense occurs during the policy period. If the incident happened while the policy was active, the policy can respondeven if the claim arrives years later.

Think of it like a concert ticket. If you were at the show on Saturday, it countseven if you post the photos on Instagram three years later when you finally remember your password.

Claims-Made: “Did the claim show up while my policy was active?”

With a claims-made policy, the claim must be made against you during the policy period. Many policies are also “claims-made and reported,” meaning the claim must be made and reported to the insurer within the policy period (or within a defined reporting window).

Think of it like a gym membership. The treadmill incident may have happened in March, but if you cancel in April and the claim arrives in July, your former membership doesn’t magically swipe you in.

A Quick Side-by-Side Comparison

The Claims-Made Twist: Retroactive Dates and Prior Acts

Here’s where claims-made policies earn their reputation for being both practical and mildly annoying. Because claims can show up late, claims-made policies often include a retroactive date. This date is the line in the sand for which past work is eligible for coverageassuming the claim is made during an active policy period.

Retroactive date, explained like you’re busy

A retroactive date says: “We’ll cover claims made today, but only if the underlying act happened on or after this date.” If you keep continuous coverage year after year, your retro date often stays the sameso your coverage “reaches back” as your career continues.

If you switch insurers, the goal is usually to keep that retroactive date (or obtain “prior acts” coverage) so you don’t create a gap. Without it, you can end up uninsured for older work, which is an exciting way to discover how expensive litigation is.

Tail Coverage: The Most Misunderstood Animal in the Insurance Zoo

The moment you hear “claims-made,” you should also hear a tiny background voice whispering: tail. Tail coverage is often called an extended reporting period (ERP). It allows you to report claims after the policy ends, for incidents that occurred after the retroactive date and before the policy termination.

In plain terms: tail coverage doesn’t “extend what happened.” It extends when you’re allowed to report it. The work (or alleged wrongdoing) still needs to fall within the eligible timeframe. The tail is about the reporting window.

How long is a tail?

It depends on the policy and carrier. Some claims-made policies include a short automatic ERP (often measured in days), and many offer optional tails that can run for yearsor even longer in certain professional settings. The key is that tails are not one-size-fits-all, and the price can be significant.

When do people actually need a tail?

• Retiring or leaving a profession (especially in malpractice-heavy fields)
• Closing a business or dissolving a practice
• Switching from claims-made to occurrence (or to a different claims-made policy without prior acts)
• Nonrenewal (voluntary or not-so-voluntary)

Where You’ll Typically See Each Policy Form

Not every type of insurance is equally likely to be claims-made or occurrence, because the form often follows the nature of the risk.

Occurrence is common in “classic” liability

Commercial general liability (CGL) is most commonly written on an occurrence basis. Many businesses like the simplicity: if the incident happened during that policy year, that year’s policy is the one to call.

Claims-made is common when claims take time to surface

Professional liability (E&O), medical malpractice, directors & officers (D&O), and employment practices liability (EPLI) are often written on a claims-made basis because allegations can arise long after the work, decision, or employment action occurred.

Cost: Why Claims-Made Can Look Cheaper (Until It Doesn’t)

Claims-made policies often start with lower premiums than occurrence policies in similar categories. One reason: the insurer’s exposure is more “contained” to claims that come in during the policy period (plus any defined reporting extensions).

That said, you have to compare apples to apples:

• Occurrence pricing bakes in the fact that claims may come laterso the policy year stays relevant for a long time.
• Claims-made pricing can be lower early on, but continuous coverage, retroactive dates, and tail options can change the long-term math.

Also, in a claims-made world, you might benefit from having your “current” policy limits respond to a claim made today, reflecting today’s settlement values and legal environmentrather than the limits you bought years ago when everything felt cheaper.

Three Timeline Examples That Make It Click

Example 1: Occurrence CGL (the “it happened then” scenario)

You’re a contractor. On June 10, 2024, a visitor trips on a loose cord at a job site and is injured. They don’t sue until September 2026.

If you had an occurrence CGL policy active in June 2024, that 2024 policy is typically the one that responds, even though the claim arrives much later.

Example 2: Claims-made E&O with a good retro date (the “tell me while it’s active” scenario)

You’re a consultant. You deliver a project on March 1, 2023. A client alleges negligence and demands damages on August 15, 2026.

If your claims-made policy is active in August 2026 and your retroactive date is on or before March 1, 2023, you’re in a much better position. The 2026 policy is the likely responder because the claim is made during that policy term.

Example 3: Claims-made without tail (the “surprise, you’re on your own” scenario)

Same consultant, same project, same alleged negligenceexcept you cancel your claims-made policy on December 31, 2025 and buy no tail coverage. The claim arrives in August 2026.

Now you’ve got a problem: the claim was made after coverage ended. Without tail/ERP (or replacement coverage with prior acts and proper continuity), the insurer may have no obligation to defend or pay.

Common Myths (and the Awkward Reality)

Myth: “Occurrence is always better.”

Occurrence can be wonderfully straightforward, but it’s not automatically “better.” Some professional lines are difficult or expensive to get on an occurrence basis, and claims-made can be the standard, practical option.

Myth: “Tail coverage extends my policy limits forever.”

Tail coverage generally extends the reporting period, not the incident period, and it doesn’t magically increase limits. In many cases, the tail uses the same limit as the expiring policy.

Myth: “If I switch carriers, I’m fine as long as I’m insured today.”

With claims-made coverage, the details of the retroactive date and prior acts coverage matter immensely. You can be “insured today” and still have a gap for yesterday’s work if the retro date resets.

How to Choose: A Practical Checklist

If you’re leaning toward occurrence, ask:

• Do I want a simpler “incident date” rule for future claims?
• Is occurrence available in my line of work at a reasonable cost?
• Am I comfortable that my limits today will still feel adequate years from now?

If you’re leaning toward claims-made, ask:

• What is my retroactive date, and will it stay the same at renewal?
• Is the policy claims-made or claims-made and reported?
• What are the reporting requirements (how fast do I need to notify the insurer)?
• What tail/ERP options exist, and when would I need one?
• If I switch carriers, will I get prior acts coverage to avoid gaps?

If you’re buying coverage for a business, also consider how your work “ages.” If your services are the kind people argue about later (design, advice, professional judgment, compliance, healthcare, finance), claims-made is common for a reason. If your exposure is more tied to physical incidents (slips, falls, property damage), occurrence is often a natural fit.

Mini-Decision Guide: Which One Fits Which Situation?

• New business on a tight budget: claims-made may be attractive, but plan for continuous coverage and understand tail options.
• Established practice with long-tail professional risk: claims-made is common; guard your retroactive date like it’s the last slice of pizza.
• General business liability exposure: occurrence is often simpler, especially for CGL-style risks.
• Planning retirement/exit: if you’re claims-made, put tail coverage on your checklist early, not the week you turn in your keys.

Field Notes: 500+ Words of Real-World Experience (What People Learn the Hard Way)

If you hang around business owners, professionals, and anyone who has ever had to fill out an insurance application longer than a streaming-service terms-and-conditions page, you’ll hear the same “I wish I’d known” stories on repeat. The funny thing is that nobody regrets buying insurance. They regret misunderstanding when it works.

One common experience: someone switches carriers to save money, feels proud for about 48 hours, and then discovers that their shiny new claims-made policy has a retroactive date that quietly resets to the new policy inception. The premium is lower, surebut now there’s a gap for prior work. When an old client resurfaces with a complaint, the professional is shocked to learn that “I have insurance now” is not the same as “I have insurance for that work.” The lesson they share later is painfully simple: always confirm that prior acts coverage (or the retro date) follows you.

Another very real scenario: a small firm closes, merges, or changes ownership. People focus on payroll, leases, vendors, and the emotional experience of turning off the lights for the last time. Then, months later, a claim arrivessometimes from a matter that was handled years earlier. If the firm had claims-made coverage and didn’t purchase tail/ERP, the mailbox becomes a horror-movie prop. It’s not that anyone tried to be reckless; they just assumed the old policy “sticks around” the way an occurrence policy does. This is where insurance jargon becomes personal. An extended reporting period isn’t a technical add-on; it’s what separates “covered” from “cash out of pocket.”

Professionals in healthcare and consulting often describe claims-made coverage as a “continuity game.” When coverage is continuous, it can feel smooth and predictablerenew, keep the retro date, keep working. But the moment you pause coverage (career break, relocation, switching jobs, leaving private practice), the timeline matters again. People who’ve been through it will tell you: if you’re stepping away, shop for tail coverage early, and read the fine print on what triggers it (retirement, disability, nonrenewal, job change). Waiting until the last day can limit options or increase cost.

Then there’s the “report it sooner than you think” lesson. Many claims-made policies have strict reporting expectations. In practice, people hesitate to report a circumstance because they don’t want to “make a big deal” or worry it will raise premiums. But experienced brokers and risk managers will tell you the opposite: if a policy requires prompt notice, delaying can jeopardize coverage. The real-world advice that gets passed around is basically: “If it feels like it might turn into a claim, don’t treat it like a diary entrytreat it like a deadline.”

Finally, one of the most relatable experiences is emotional, not technical: claims are stressful. When a claim arrives, you don’t want to also be learning vocabulary words like “retroactive date” for the first time. People who’ve lived through a dispute often describe the best insurance decision as the one that reduces surprise. Occurrence policies reduce surprise by tying coverage to the incident date. Claims-made policies reduce surprise when you understand continuity, protect the retro date, and plan for tail coverage when life changes. Either way, the “best” policy is the one that matches how your risk shows up in the real worldnot just how it looks on a quote.

Conclusion

Claims-made and occurrence policies aren’t “good vs. bad.” They’re two different ways to assign responsibility across time. Occurrence coverage is often simpler: if it happened during the policy period, that policy year is in play. Claims-made coverage can be very effectiveespecially for professional risksbut demands attention to retroactive dates, reporting rules, and tail options.

If you remember only one thing, make it this: Occurrence cares about when the incident happened. Claims-made cares about when the claim is madeand whether your coverage is continuous. If you keep that straight, you’re already ahead of most people buying insurance with one eye and a coffee in the other.