Occurrence vs Claims-Made

How occurrence and claims-made policies work

Both options are common in commercial insurance, but they respond to different timing rules. The key question is not only when the incident happened, but also when the claim is reported.

Occurrence coverage applies to bodily injury, property damage, or other covered events that happen during the policy period, even if the claim is filed later. If the loss occurred while the policy was active, the policy can still respond after the policy has ended, subject to the policy terms.

Claims-made coverage generally applies only when the claim is first made against the insured during the policy period, and often requires that the incident also be reported promptly while the policy is active. Some claims-made policies also include a retroactive date, which limits coverage for incidents that happened before that date.

• Occurrence = trigger is the date of the event.
• Claims-made = trigger is usually the date the claim is made and reported.
• Claims-made policies may involve retroactive dates and extended reporting options.

Key differences that matter in real life

For many business owners, the biggest difference is long-tail exposure. If a customer alleges harm years after a job was completed, an occurrence policy may still respond if the event happened during the policy term. That is why occurrence forms are often easier to understand and can be simpler to manage when a business changes carriers.

Claims-made coverage can be a good fit for risks that are more likely to be identified and reported quickly, but it requires more attention to dates. If a business switches insurers, cancels coverage, or forgets to maintain continuous protection, a gap in reporting can leave a claim without coverage even if the wrongful act happened while a policy was in place.

• Occurrence policies are often easier for long-tail claims.
• Claims-made policies require close attention to renewals, reporting deadlines, and retroactive dates.
• When switching carriers, claims-made policies may need tail coverage or prior acts protection, depending on the policy.

Who should consider each type

There is no one-size-fits-all answer. Occurrence coverage is often preferred by businesses that want simpler claim handling and more certainty for incidents that could surface later, such as contractors, property-related operations, and many general liability buyers.

Claims-made coverage is common in professional liability lines, such as errors and omissions, medical professional liability, and some directors and officers policies. Businesses that generate advice, design work, consulting, or other services may find claims-made coverage standard in their industry.

• Choose occurrence if you want the simplest fit for long-tail claims.
• Choose claims-made if your line of business commonly uses it and you can manage reporting and renewal timing carefully.
• Review whether prior acts, retro dates, or extended reporting periods are available.

Georgia-specific notes and common mistakes to avoid

Georgia generally follows standard U.S. commercial insurance practice on these policy forms. There is no Georgia rule that makes one of these coverage types mandatory for all businesses, but some contracts, lenders, landlords, or professional boards may require specific liability wording. Georgia businesses should also remember that workers’ compensation is required once a business has three or more employees, but that is separate from the occurrence vs. claims-made choice.

Common mistakes include assuming a claims-made policy covers old incidents automatically, letting a policy lapse without understanding tail coverage, or switching insurers without confirming how prior acts will be handled. Another frequent error is comparing only premium and not the reporting terms, retroactive date, and extended reporting options.

• Do not assume past work is covered under a new claims-made policy without checking the retroactive date.
• Do not cancel claims-made coverage before asking about tail or extended reporting protection.
• Do not compare price alone; compare trigger dates, exclusions, and reporting requirements.