Category: Policy Structure & Terms

Occurrence Policy

Also known as: Occurrence Form, Occurrence-Based Coverage, Occurrence Coverage

Simply put

An occurrence policy covers losses caused by an event that takes place during the period the policy is active, even if the claim for that loss is filed much later. This means that if an incident happens while the policy is in force, coverage can still respond years afterward, even after the policy has expired or been canceled. The timing that matters is when the event occurred, not when someone reports it.

Formal definition

An occurrence policy is a coverage trigger structure under which the insurer responds to claims arising from injury, damage, or a covered event that took place during the policy period, regardless of when the claim is subsequently made or reported. The operative trigger is the date of the occurrence itself, so a policy in force at the time of the incident remains obligated to respond even after expiration or cancellation, subject to the specific policy wording, applicable limits, exclusions, and conditions. This contrasts with a claims-made structure, in which the trigger is when the claim is first made (and typically reported) during the policy period. The distinction described here concerns the temporal coverage trigger only; whether any particular loss is covered still depends on the policy's insuring agreement, endorsements, exclusions, and jurisdiction.

Why it matters

The distinction between occurrence and claims-made triggers determines whether a policy responds to a loss at all, which makes it one of the most consequential structural choices in a coverage program. Under an occurrence structure, the policy in force at the time the event took place remains obligated to respond even after it has expired or been canceled, so an insured can be protected years later for something that happened while coverage was active. This matters most for losses that surface long after the triggering event, where the gap between when an incident occurs and when a claim is filed can be substantial.

Because the operative trigger is the date of the occurrence rather than the date the claim is made, occurrence coverage can protect an organization from legal action for years to come, regardless of when a claim is filed. This has practical implications for how insureds think about historical exposure: coverage decisions made in past policy periods continue to matter, and the terms, limits, and exclusions of an expired occurrence policy may still govern how a late-emerging claim is handled. It also affects how buyers evaluate the two structures against one another, since claims-made coverage instead responds only when the claim is first made during the policy period, creating different continuity considerations.

Who it's relevant to

Risk managers

Risk managers need to know which policy period will respond to a given loss, particularly for exposures that may surface long after the triggering event. Understanding that an occurrence policy responds based on when the event happened, not when the claim is filed, helps in evaluating historical coverage and in comparing occurrence and claims-made options during placement.

Insurance brokers and underwriters

Brokers and underwriters structure and price coverage around the trigger. The occurrence structure creates a long tail of potential future claims tied to a given policy period, which affects how coverage is compared against claims-made alternatives and how continuity across renewals is addressed. Underwriters must account for the possibility that a policy remains obligated to respond years after it expires.

Legal and compliance professionals

Legal and compliance teams assessing potential liability for past acts benefit from knowing that occurrence coverage can respond to claims filed years after the underlying event, provided that event occurred while the policy was in force. Whether a specific claim is ultimately covered still turns on the policy's insuring agreement, exclusions, conditions, and the applicable jurisdiction.

Inside Occurrence Policy

Occurrence Trigger

The defining feature of an occurrence-based policy: coverage responds to events (the injury, damage, or wrongful act) that take place during the policy period, regardless of when the resulting claim is actually made or reported. This contrasts with a claims-made trigger, which responds based on when the claim is first asserted against the insured.

Policy Period Anchoring

The point of reference for coverage is when the loss-causing event happened, not when it was discovered or reported. A policy in force at the time of the occurrence may be called upon to respond even years later, subject to the specific wording and any applicable time limitations.

Long-Tail Exposure

Because claims can surface long after the policy period ends, occurrence forms create extended, sometimes open-ended, liability tails for insurers. This is a defining structural characteristic that influences pricing, reserving, and availability, and is one reason occurrence forms are less common in fast-evolving cyber lines.

Application in Cyber and Liability Lines

In cyber and related liability insurance the claims-made form predominates, in part because of the difficulty of pinpointing when a cyber event 'occurred' versus when it was discovered. Where occurrence language appears, the definition of what constitutes an 'occurrence' and when it is deemed to take place is critical and varies by form.

Relationship to Exclusions and Conditions

As with any form, whether a loss tied to a covered occurrence is ultimately paid depends on exclusions, conditions precedent, endorsements, sublimits, retentions, and jurisdiction. The occurrence trigger governs timing of coverage attachment, not the full question of whether a given loss is covered.

Common questions

Answers to the questions practitioners most commonly ask about Occurrence Policy.

Does an occurrence policy cover claims based on when I actually file them?

No. This is a common misconception. An occurrence policy responds based on when the triggering event or injury occurred during the policy period, not when the claim is made or reported. A claim reported years after the policy expired may still be covered if the underlying occurrence took place while that policy was in force, subject to the specific wording. This is the opposite of a claims-made policy, which typically responds based on when the claim is first made against the insured.

Are cyber insurance policies usually written on an occurrence basis?

In many markets, cyber insurance is predominantly written on a claims-made basis rather than an occurrence basis. Occurrence structures are less common in cyber lines, in part because it can be difficult to pinpoint when a cyber event 'occurred', for example, when an intrusion began versus when data was exfiltrated or damage manifested. Do not assume any particular cyber policy is occurrence-based; the trigger structure depends on the specific form and should be confirmed in the wording.

How do I determine which policy year responds when the triggering event is spread over time?

Under an occurrence form, the policy in force when the injury, damage, or triggering event took place is generally the one that responds, subject to the specific wording. When an event unfolds across multiple policy periods, identifying the applicable trigger point can be contested, and different policy definitions of 'occurrence' may allocate the loss differently. Review how the form defines the occurrence and its timing, and be aware that allocation across years may require careful analysis or, in disputed cases, involve the insurer's claims and legal teams.

Do I need to purchase tail coverage when I switch away from an occurrence policy?

Typically no. Because an occurrence policy continues to respond to events that took place during its period regardless of when the claim is reported, the need for extended reporting (tail) coverage is generally associated with claims-made policies rather than occurrence ones. If you move from an occurrence form to a claims-made form, the tail considerations attach to the claims-made structure. Confirm the specifics against each policy's wording rather than assuming.

What records should I retain to support a future claim under an occurrence policy?

Because a claim may be reported long after the policy period ends, it is prudent to retain the policy documents, endorsements, and evidence of the timing and nature of events that occurred during each policy period. Documentation that helps establish when a triggering event took place can be important, since coverage under an occurrence form turns on that timing. Retention practices should be aligned with your jurisdiction's limitation periods and record-keeping obligations.

How does an occurrence structure affect how I manage exclusions and coverage gaps over time?

Whether a given loss is covered still depends on the exclusions, conditions, sublimits, and retentions in the policy that was in force when the event occurred, not the terms of your current policy. This means older occurrence policies may carry different exclusions or limits than your present program, so a claim tied to a past event is evaluated against that period's wording. When reviewing your program, consider how successive policies' terms interact so that changes in exclusions or limits over time do not create unexpected gaps.

Common misconceptions

An occurrence policy covers me for any claim made while the policy is in force.

That describes a claims-made structure. An occurrence policy responds based on when the underlying event took place, not when the claim is made or reported. A claim made during the current period for an event that happened before coverage incepted would generally look to the policy in force at the time of the occurrence, subject to the specific wording.

Occurrence and claims-made forms are largely interchangeable ways of writing the same coverage.

The two forms differ fundamentally in their trigger and in how liability tails behave. Occurrence forms can be called upon long after the period ends, creating long-tail exposure, while claims-made forms rely on the timing of the claim and often involve retroactive dates and extended reporting provisions. The choice materially affects pricing, availability, and how gaps arise at renewal or when switching insurers.

Cyber insurance is typically written on an occurrence basis.

Cyber and related liability lines are predominantly written on a claims-made basis, partly because of the difficulty of establishing when a cyber event actually occurred as opposed to when it was discovered. Assuming an occurrence trigger in cyber coverage without confirming the form is a common and consequential error.

Best practices

Confirm the trigger of every liability policy in your program by reading the actual form, and do not assume the trigger based on the line of business, since cyber and related lines are predominantly claims-made.

Where an occurrence form is used, scrutinize how the policy defines an 'occurrence' and when the event is deemed to take place, because that definition governs which policy period responds.

Map how occurrence and claims-made forms interact across your renewals and prior programs to identify potential gaps or overlaps in coverage when switching insurers or forms.

Account for long-tail exposure when evaluating an occurrence form: recognize that a policy may be called upon years after the period ends, subject to any applicable time limitations in the wording.

Remember that the trigger determines only when coverage attaches; separately assess exclusions, conditions precedent, endorsements, sublimits, retentions, and jurisdiction to understand whether a specific loss would actually be paid.

Engage your broker and coverage counsel to document, in writing, how each form responds to events that span or predate policy periods, rather than relying on general assumptions about occurrence coverage.