'Occurrence': One Storm, Three Leaks — How Many Deductibles and How Many Limits?

A hurricane damages the roof on Monday, water enters again in Thursday's rain, and a weakened tree falls the following week. Is that one claim or three? The answer lives in a word most policyholders never read: occurrence. How a loss is grouped controls how many deductibles are subtracted, which limits apply, and sometimes whether a claim was reported on time. Carriers and policyholders argue the grouping in whichever direction the money points — and the policy's definition, plus the facts of causation, are supposed to decide it.

What 'occurrence' means in a property policy

In liability insurance, 'occurrence' is a defined term at the center of the policy. In homeowners property forms, the concept often works more quietly: deductibles are typically expressed as applying per occurrence, loss settlement and limits are applied per loss event, and endorsements (hurricane deductible windows are the classic example) define the period within which damage counts as a single event. The practical definition is built from causation and time: damage arising from one continuous cause or event is generally grouped as one occurrence; damage from separate, independent causes is grouped as several.

Grouping cuts both ways. One occurrence means one deductible — favorable when a single storm causes widespread damage. But one occurrence also means one set of limits and sublimits — unfavorable when a mold sublimit or a water-backup cap is consumed by what might otherwise be two events. Neither side's preference is principled; both are arithmetic.

How it appears in your policy language

Because standard property forms may not carry a single bolded definition, the occurrence concept must be assembled from several places. The deductible condition typically states the deductible applies once per occurrence. Special deductible endorsements (hurricane, named storm, wind/hail) commonly define a window — for example, the period beginning when a watch or warning is issued and ending a stated number of hours after it expires — within which all wind damage counts as one event for deductible purposes. Other-insurance and limit provisions and additional-coverage terms (loss assessment, mold, backup) apply their sublimits per occurrence as the endorsements state. In liability sections, by contrast, 'occurrence' is expressly defined, usually around an accident or continuous exposure to conditions.

When grouping is disputed, the first move is always textual: collect every place the form and endorsements attach consequences to a single event, and read them together.

How disputes typically arise

Repeat water intrusion after a storm. The roof is damaged Monday; rain enters again Thursday through the same opening before repairs. One occurrence (the storm) or two (two intrusions)? Tarping and mitigation facts matter to the answer.
The weakened tree. A tree damaged by a covered storm falls weeks later onto a fence. Grouped with the storm claim by one side; treated as a new, possibly differently-covered event by the other.
Two storms, one season. Successive hurricanes or hail events weeks apart damage the same roof. Carriers may separate them (two deductibles); policyholders separating them may instead seek two sets of sublimits — the argument flips with the numbers.
Long-running leaks. A single continuous plumbing failure producing damage over months is usually grouped as one occurrence — which also means one deductible, but one visit to every applicable cap.

What you can do

Report each distinct event when it happens and keep separate documentation per event: dated photos, weather records, and distinct contractor findings. Clean per-event files make any grouping argument possible; one blended file makes only confusion possible.
If a second intrusion follows an unrepaired first loss, document your mitigation — tarps, temporary repairs, contractor scheduling — because the grouping discussion and the mitigation discussion will arrive together.
Ask in writing how the carrier is grouping the losses and under what policy language, and request the deductible and sublimit consequences of that grouping in numbers.
When two groupings are arguable, work out both sets of arithmetic before choosing a position: one deductible but one cap, or two deductibles but two caps. The better grouping depends on where your damage dollars sit.

Occurrence vs. claim: a useful distinction

A claim is an administrative file you open; an occurrence is a policy concept about causation. You can open one claim that contains two occurrences, or report two events that the carrier groups as one occurrence. Confusing the two produces bad assumptions: filing twice does not create two deductibles' worth of coverage, and filing once does not guarantee a single deductible. When you communicate about a loss, describe events and causes factually — dates, weather, failure points — and let the grouping be argued on those facts with the policy text in hand, rather than conceding a grouping in the first phone call's vocabulary.

When grouping helps you and when it hurts

Run the numbers both ways before taking any position. Grouping into one occurrence helps when the damage is spread across many items under generous main limits: one deductible absorbs it all. Grouping hurts when the loss concentrates in capped categories — mold, water backup, loss assessment, scheduled items — because one occurrence means one trip to each sublimit, and a severe loss can exhaust a cap that a second occurrence would have refreshed.

Carriers run the same arithmetic from the other side, which is why initial grouping decisions in a denial or settlement letter should never be accepted as neutral bookkeeping. Ask for the grouping, the language behind it, and its dollar consequences in writing; then compare against the alternative grouping the facts also support. The definition does not change — but which causation story the facts are organized under often decides which grouping the definition produces, and that story is built from your documentation.

The denial you'd never lose

"Insufficient documentation" is the most reversible denial reason there is — and the one you can eliminate before it ever happens. Photos with timestamps, receipts, serial numbers, a room-by-room record — assembled once, in an afternoon. That's exactly what the ClaimReady Vault ($39/yr) is built to hold, somewhere a fire or flood can't reach.

Get the Vault — $39/yr

Common questions

One storm damaged my roof, fence, and shed. How many deductibles?

Typically one — damage from a single occurrence is generally subject to one deductible, even across Coverage A and Coverage B items, as the deductible condition provides. Verify on the settlement statement that it was subtracted only once.

Two separate storms hit a month apart. One claim or two?

Ordinarily two occurrences: separate causes at separate times, each with its own deductible and its own application of sublimits. Documenting each storm separately — dates, weather records, photos — is what keeps the two events distinct.

Rain came through my storm-damaged roof twice before repairs. New deductible for the second entry?

Often argued as one occurrence, because the second entry traces to the same covered cause — the unrepaired storm opening. Your mitigation efforts (tarping, temporary patching) support the single-occurrence, single-deductible reading and answer the separate failure-to-mitigate argument.

Does grouping affect my mold or water-backup limits?

Yes. Sublimits stated per occurrence reset with a genuinely separate occurrence and do not reset within one. That is why grouping is sometimes worth more in sublimits than it costs in deductibles — run both calculations.

Keep reading

Insurance rules change — verify current requirements with the NAIC or your state’s insurance department.

Educational content, not legal advice. Deadlines, rules, and coverage vary by state, carrier, and policy — read your policy and consult a licensed professional for your situation.