Occurrence Reporting Requirements Under Liability Policies

Occurrence reporting requirements define the procedural obligations a policyholder must satisfy when an incident, accident, or event takes place that may give rise to a liability claim. These requirements appear in virtually every commercial and personal liability policy as a condition of coverage, and failing to meet them can void an insurer's duty to defend or indemnify. Understanding the specific triggers, timelines, and documentation standards embedded in these requirements is essential for any organization managing liability exposure across types of liability insurance.

Definition and scope

An occurrence reporting requirement is a contractual condition embedded in a liability insurance policy that obligates the insured to notify the insurer—within a specified time and in a specified manner—when an occurrence takes place that may result in a claim. Under standard Insurance Services Office (ISO) Commercial General Liability (CGL) forms, the relevant condition is typically titled "Duties in the Event of Occurrence, Offense, Claim or Suit" and appears in Section IV of the policy.

The ISO CGL form (ISO Form CG 00 01) defines an "occurrence" as an accident, including continuous or repeated exposure to substantially the same general harmful conditions (ISO, CG 00 01). Scope extends beyond a single traumatic event to cover gradual processes such as environmental contamination or cumulative bodily injury.

The reporting duty applies across a wide spectrum of coverage lines:

The scope of the requirement also interacts directly with policy form type. Occurrence-based policies require reporting of the triggering event itself; claims-made policies impose a separate (and often stricter) obligation tied to when a claim is first made. That distinction is detailed in occurrence vs. claims-made policies.

How it works

The reporting obligation is typically structured in three discrete phases:

  1. Notice of occurrence — The insured must notify the insurer or its authorized representative "as soon as practicable" after the occurrence. Most ISO-based forms do not specify a fixed number of days but courts in states including California, New York, and Texas have interpreted "as soon as practicable" to mean within a reasonable time given the circumstances. Some manuscript policies impose hard deadlines of 30, 60, or 90 days.

  2. Notice of claim or suit — If a third party presents a demand or files a lawsuit, the insured must immediately forward every demand, notice, summons, or legal paper received. This is a separate trigger from the initial occurrence notice and carries independent consequences for non-compliance.

  3. Cooperation and documentation — The insured must cooperate in the investigation, provide written statements, submit to examination under oath, and assist in securing and giving evidence. The National Association of Insurance Commissioners (NAIC) Model Acts governing claims settlement practices (NAIC Model #900) frame insurer investigation rights and policyholder cooperation obligations in parallel.

Notice must typically be delivered to the insurer's designated representative in writing. Oral notice to a local agent may not satisfy the condition unless the policy explicitly names the agent as an authorized recipient. The liability insurance claims process page covers downstream procedural steps once formal notice has been accepted.

Prejudice standards govern the consequences of late notice. Under the traditional New York rule (pre-2009), late notice was an absolute defense regardless of prejudice. New York's 2009 amendment to Insurance Law § 3420 shifted the state to a prejudice standard for policies issued after January 17, 2009 (New York State Legislature, Insurance Law § 3420), meaning an insurer must demonstrate actual prejudice before denying coverage on late-notice grounds alone. California applies a similar prejudice standard under California Insurance Code § 554. Many states follow the majority prejudice approach, while a minority of states retain notice-as-condition precedent rules.

Common scenarios

Slip-and-fall on commercial premises — A visitor sustains an injury. The property owner may not immediately recognize that the event is serious, creating a gap between the occurrence and notification. Under premises liability insurance, the reporting clock starts at the moment of the accident, not when a formal demand arrives.

Construction defect discovered post-completion — A contractor finishes a project; structural defects manifest 18 months later. The completed operations liability coverage obligation to report is triggered when the insured first becomes aware of facts that would cause a reasonable person to believe a claim is possible—not when litigation begins.

Gradual environmental release — A facility discharges a pollutant over an extended period. Courts in multiple states have ruled that the occurrence date for notice purposes is the date the continuous release began, not the date of regulatory detection. Pollution liability insurance policies often include specific environmental incident reporting timelines that supersede general notice conditions.

Cyber incident — A network intrusion exposes third-party data. Cyber liability insurance policies frequently impose hard deadlines—commonly 72 hours—mirroring incident notification windows established under the FTC's Safeguards Rule (FTC, 16 CFR Part 314) and state breach notification statutes.

Employment practices event — A harassment complaint is filed internally. Employment practices liability insurance policies may require reporting of any "wrongful act" the insured becomes aware of, even before a formal charge is filed with the Equal Employment Opportunity Commission (EEOC).

Decision boundaries

Four variables determine whether a reporting obligation has been properly satisfied:

Variable Key Distinction
Policy form type Occurrence vs. claims-made (see occurrence vs. claims-made policies)
Notice trigger Accident date vs. knowledge date vs. claim receipt date
Prejudice standard Notice-as-condition-precedent states vs. prejudice-required states
Recipient specification Named insurer vs. authorized agent vs. surplus lines broker

Occurrence-based policies require notice of the underlying event. The insured's subjective belief that no claim will result does not suspend the obligation. Courts in Ohio, Pennsylvania, and Florida have held that once a reasonable person in the insured's position would recognize a potential for a claim, the notice obligation is active.

Claims-made policies require notice of the claim itself, but many include a supplemental condition requiring the insured to report known circumstances that may give rise to a future claim before the policy period expires. Failure to report known circumstances can eliminate coverage under a successor policy, making this one of the most consequential reporting distinctions in commercial insurance. The mechanics of extended reporting are addressed in tail coverage and extended reporting periods.

Surplus lines carriers operate outside state-admitted markets and may impose non-standard notice conditions that differ materially from ISO baseline language. The admitted vs. non-admitted liability carriers comparison explains how regulatory oversight diverges between these market segments and why notice conditions in surplus lines policies warrant closer scrutiny.

Government contractor policies are subject to Federal Acquisition Regulation (FAR) reporting requirements that may run parallel to and independent of commercial policy conditions. FAR 28.306 and FAR 28.307 establish minimum insurance and reporting standards for contractors working on federal projects (FAR, Title 48 CFR Part 28), creating a dual-track obligation that neither the insurer nor the government agency waives on behalf of the other.

References

📜 2 regulatory citations referenced  ·  🔍 Monitored by ANA Regulatory Watch  ·  View update log

Explore This Site

Regulations & Safety Regulatory References Tools & Calculators Compound Interest Calculator