Occurrence policy

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

The event date usually anchors the coverage year

The Texas Department of Insurance explains that an occurrence policy covers injury or damage that occurs during the policy period, while a claims-made policy focuses on when a claim is made and reported under its terms. The distinction sounds simple until the facts span several dates.

An allegation may involve conduct on one date, injury discovered later, a written demand later still, and insurer notice after that. The policy defines which event matters. Preserve the full timeline and avoid selecting a policy year from the complaint filing date alone.

Late claims still need timely notice

Occurrence coverage can respond to a claim reported after the policy expires when the covered injury happened during the term. This does not create unlimited reporting time. Notice, cooperation, suit-paper, record-preservation, and other conditions still apply, along with state law.

Build a reporting route that remains usable after staff leave or the practice changes systems. Keep policy numbers, carrier contacts, broker contacts, forms, endorsements, and notice instructions available for every historical year.

Completed operations can matter after service ends

Some policies separate premises and ongoing operations from products-completed-operations exposure. Confirm when the form treats work as completed, which aggregate applies, and whether a professional-services exclusion changes the analysis.

ABA services involve professional judgment, documentation, supervision, and work in varied settings. A general liability occurrence form may cover a premises event while excluding a claim arising from professional services. Professional liability, abuse coverage, auto, cyber, employment, and workers' compensation each need their own map.

One incident can cross policy periods

Repeated exposure, progressive injury, multiple locations, or related allegations can create allocation questions. Definitions of occurrence, related events, batch, or series can determine whether facts produce one event or several and which limits or deductibles apply.

Do not merge events simply because they involve the same client or workflow. Preserve service dates, locations, people, alleged injuries, discovery dates, demands, notices, and corrections. Broker and counsel can then evaluate the actual language.

Occurrence and claims-made require different continuity checks

An occurrence policy generally protects qualifying events during its term. A claims-made form can require a claim to be first made and reported during the term, often subject to a retroactive date. Tail coverage usually concerns an extended reporting period for claims-made coverage; it does not extend the dates when services occurred.

Switching forms can create gaps or overlaps. Before moving from claims-made to occurrence, review prior acts, tail options, known circumstances, pending claims, and any gap between the retroactive date and new occurrence term. Before the reverse switch, confirm the new retroactive date reaches back far enough.

Limits belong to the historical policy

A late claim typically draws on the limits, deductible, aggregate, exclusions, and endorsements of the applicable past policy, subject to the governing terms. Increasing today's limit does not automatically increase an older year's protection.

Store complete policies rather than declarations alone. Endorsements may change insureds, services, locations, exclusions, aggregates, notice, or defense. A certificate is not a substitute for that package.

Create an annual coverage index with the insurer, policy number, exact effective dates, named entities, trigger, retroactive date if any, notice channel, and storage location. A later reviewer should be able to find the operative form without reconstructing the practice's history from invoices or certificates.

A fictional timeline review

Fernway ABA reviews nine facts after receiving a demand involving an incident allegedly occurring three years earlier. Eight are verified: service date, location, named entity, policy term, endorsement set, occurrence description, notice address, and applicable limit. The precise first-injury date remains unclear.

Timeline readiness is 8 of 9 facts, or 88.9%. The unresolved date stays visible and the practice promptly sends the demand through counsel and the broker under the required notice route. It does not wait for perfect certainty before preserving rights.

This measure describes evidence completeness. It says nothing about coverage, negligence, liability, defense acceptance, or payment.

Records support long-tail reporting

Retain policies, applications, binders, endorsements, audits, certificates, contracts, incident files, claim correspondence, and closure evidence according to legal and business requirements. Clinical records follow their own retention, access, privacy, and correction rules.

The NAIC small-business guide recommends annual policy review. Reassess new locations, services, ownership, contractors, vehicles, events, and contract requirements before renewal. Ask the broker to show any change in trigger, exclusions, limits, or notice terms.

After renewal, archive the full expiring and issued forms under immutable policy-year labels and test retrieval. Assign a long-tail notice owner and backup contact. A historical policy remains operationally useful only when a future reviewer can locate it, identify the correct entity, and follow the stated reporting route promptly.