COI Policy Limits: Per-Occurrence vs. Aggregate Explained for Operations Teams

When reviewing vendor certificates of insurance (COIs), operations teams frequently encounter two types of policy limits that can make or break your coverage protection: per-occurrence limits and aggregate limits. Understanding these limits is critical for setting appropriate vendor requirements, with common guidelines requiring minimum general liability policy limits of $1 million per occurrence and $2 million aggregate.

The difference between these limits isn't just insurance jargon—it directly impacts how much protection your organization has when multiple claims arise from vendor work. Getting this wrong can leave you exposed to significant liability gaps.

What Are Per-Occurrence Limits?

Per-occurrence limits represent the maximum amount an insurance policy will pay for any single incident or claim. Think of it as a "per accident" cap. A commonly recommended minimum limit for general liability coverage is $1,000,000 per occurrence.

For example, if a contractor causes a fire that damages your facility and injures three people, the per-occurrence limit is the total amount available to cover all damages from that single incident—property repair costs, medical bills for all injured parties, and legal fees combined.

Key characteristics of per-occurrence limits:

• Apply to each separate incident or event
• Reset for each new occurrence
• Cover all damages and costs from one incident
• Provide predictable coverage per event

What Are Aggregate Limits?

Aggregate limits cap the total amount an insurance policy will pay during the entire policy period, regardless of how many separate incidents occur. Industry standards often require $2,000,000 aggregate limits to provide sufficient overall protection.

Using the same contractor example: if they cause three separate incidents during the policy year, the aggregate limit is the maximum the policy will pay for all three incidents combined. Once this limit is exhausted, no further claims will be paid until the policy renews.

Key characteristics of aggregate limits:

• Apply to the entire policy period (usually one year)
• Shared across all claims during that period
• Do not reset until policy renewal
• Can be depleted by multiple smaller claims

Why Both Limits Matter for Vendor Requirements

Vendor insurance requirements vary drastically by industry because different contractors face completely different liability scenarios. Operations teams need both limits working together to ensure adequate protection:

Protection Against Large Single Events

Per-occurrence limits protect against catastrophic single incidents. A contractor's equipment malfunction that causes extensive property damage needs sufficient per-occurrence coverage to handle the full scope of damages.

Protection Against Multiple Claims

Aggregate limits protect against claim frequency. A maintenance contractor working across multiple properties might face several smaller liability claims throughout the year. Without adequate aggregate limits, early claims could exhaust coverage and leave later incidents unprotected.

Common Limit Combinations by Risk Level

Low-Risk Vendors (office services, consulting):

• $1M per-occurrence / $2M aggregate
• Sufficient for most professional services

Medium-Risk Vendors (maintenance, light construction):

• $2M per-occurrence / $4M aggregate
• Accounts for increased exposure from hands-on work

High-Risk Vendors (major construction, hazardous materials):

• $5M+ per-occurrence / $10M+ aggregate
• Umbrella/Excess Liability insurance may be advisable as a safety net of additional protection for instances with catastrophic loss potential

Red Flags to Watch For

Operations teams should be alert to these problematic limit structures:

Inadequate Aggregate Relative to Per-Occurrence: A policy showing $2M per-occurrence but only $2M aggregate provides just one claim's worth of total coverage.

Shared Aggregates: Some policies share aggregate limits across all the contractor's jobs. Your project might compete with their other work for available coverage.

Products-Completed Operations Separate Limits: Homeowners should confirm that the policy includes "products and completed operations" coverage, which protects against defects or damage that appear after the job is finished.

Practical Steps for Operations Teams

1. Set Clear Requirements: Specify both per-occurrence AND aggregate minimums in your vendor agreements

2. Verify Current Limits: When reviewing certificates, confirm coverage limits are appropriate for the scope and risk of the work being performed

3. Track Aggregate Depletion: For ongoing vendors, monitor whether previous claims have reduced available aggregate coverage

4. Document Requirements: Create standardized limit requirements by vendor category to ensure consistency

5. Review Annually: Templates should be reviewed by your risk management team or insurance broker annually and updated when market conditions, project requirements, or regulatory changes warrant adjustment

How Can I Verify That Vendors Meet Our Limit Requirements?

Request certificates of insurance (COIs) that clearly show both per-occurrence and aggregate limits. Proof of insurance coverage should always come directly from the insurer, never from the vendor, as every insurance company has processes in place to send you the documentation you'll need.

What Happens If Aggregate Limits Are Exhausted Mid-Project?

Once aggregate limits are depleted, the policy provides no further coverage until renewal. This is why monitoring aggregate usage and requiring adequate limits relative to project duration and risk is critical.

Should We Require Umbrella Coverage on Top of Primary Limits?

For higher-risk projects or valuable properties, umbrella policies provide additional layers of protection above primary limits. Umbrella or excess liability coverage ($5M–$25M+) is required on larger construction projects, public infrastructure work, and contracts with major corporations.

Understanding per-occurrence vs. aggregate limits empowers operations teams to set appropriate vendor insurance requirements and avoid costly coverage gaps. The right combination of both limits, tailored to your specific risks, creates a robust foundation for vendor insurance compliance. Consider implementing unifi.ai to automate the verification of these critical limits and streamline your COI compliance process. See our pricing options to get started.

Check Your COI Compliance Instantly

Try unifi.ai free — no signup required.