Minnesota Appeals Court Issues Decision on One-Occurrence Argumen

What Happened: The Life Time vs. Zurich Dispute in Plain English

Life Time operates health and fitness clubs across the U.S. When COVID-era governmental authorities ordered gyms to close in 2020, Life Time sustained losses and sought coverage under a Zurich commercial property policy endorsement providing “Interruption by Communicable Disease” coverage.

Here’s the twist that made lawyers everywhere reach for a fresh highlighter: the parties weren’t fighting over whether there was coverage in the abstract. The coverage grant existed and the case was teed up on how many “occurrences” the shutdowns counted as, because each occurrence carried a $1 million sublimit.

The Policy Language That Started the Food Fight

The endorsement hinged on a very specific trigger: coverage applied when a suspension of business activities was caused by an order of an authorized governmental agency enforcing laws or ordinances regulating communicable diseases. Meanwhile, the policy defined an “occurrence” as all loss or damage attributable directly or indirectly to one cause or a series of similar or related causes.

In real-life terms, this is the difference between “COVID existed” (a broad backdrop) and “a government order shut this location down” (a discrete event that flips the policy’s coverage switch).

The “One-Occurrence” Argument (and Why It’s So Popular at Insurer Parties)

A one-occurrence argument is basically insurance’s version of “group project credit.” Lots of separate bad things happen, but the insurer argues they all roll up into one “cause,” so only one per-occurrence limit applies. It’s clean, tidy, andif you’re writing the checkbeautiful.

Policyholders, on the other hand, see it like ordering 29 pizzas and being told the restaurant’s “one-delivery” policy means you only get one slice. Technically food arrived. Practically, chaos.

Why Courts Get Dragged into This

“Occurrence” disputes pop up everywhere: mass torts, product claims, cyber incidents, serial theft, construction defects, and (yes) pandemic losses. The outcome changes available limits, deductibles/self-insured retentions, and sometimes whether excess layers even wake up and return your calls.

What the Minnesota Court of Appeals Decided

The appellate court reversed the trial court and drew a sharp line between background conditions and the policy’s operative cause. The key holdings can be summarized like this:

• Government shutdown orders were the “causes” of Life Time’s covered losses for determining the number of occurrencesnot the COVID-19 pandemic itself.
• Orders issued by different jurisdictions were not a single “series,” so they shouldn’t be mashed into one occurrence.
• Orders issued within the same jurisdiction were a “series,” so multiple closure periods within one state could still be grouped as one occurrence.
• Applying that framework, the court landed on 29 occurrences (not 41, and definitely not 1).

That 29-number matters because it can expand a $1 million per-occurrence limit into a potential $29 million conversation (subject, of course, to the policy’s other limits, terms, and whatever happens on remand).

How the Court Got There: Reading the Trigger Like It Actually Triggers Things

Step 1: Start with the Coverage Grant (Not the Vibes)

The court focused on the endorsement’s plain structure: coverage applies if the suspension is caused by a government order. If no order exists, there’s no communicable disease interruption coverage under that endorsement. That makes the order more than a supporting actorit’s the lead.

Step 2: Minnesota Doesn’t Automatically Use the “Cause Test” Like Many States

Many jurisdictions apply a traditional “cause test” for counting occurrencesasking whether there was one proximate, uninterrupted, continuing cause. Minnesota’s supreme court, however, has emphasized a more pragmatic approach that begins with the policy language. That matters because “occurrence” isn’t physics; it’s contract interpretation.

Step 3: “Series of Similar or Related Causes” Has Teeth

Zurich didn’t lose every aggregation argument. The court still allowed grouping orders within a jurisdiction as a “series.” The court’s logic: separate states issued orders independently, often on the same day, with no meaningful relationship. But within one state, an initial closure and a later closure (after reopening) are events in succession tied to a common governmental authority.

Why 29 Occurrences (Not 41 and Not 1)

Life Time pointed to 41 distinct shutdown periods across 29 jurisdictions. The insurer said: “One pandemic, one occurrence.” The court said: “Orders are the causes,” but then added: “Within a jurisdiction, multiple orders can be a series.”

Think of it like a playlist:

• Different jurisdictions = different DJs, different rooms, different playlists. Not a single “series.”
• Same jurisdiction = one DJ changing tracks through the night. Still one “series.”

The result: 29 occurrencesone per jurisdiction that independently ordered closures affecting Life Time locations.

Is This a COVID Case or a Policy Drafting Case?

It’s both, but the enduring value is drafting. COVID will (eventually) stop being the headline. “Occurrence” fights will not. The court’s reasoning is a reminder that specialized endorsements can have narrow triggersand those triggers can control the occurrence analysis even when the broader world event feels like “the real cause.”

In other words: the policy didn’t say, “We pay when a pandemic happens.” It said, “We pay when a government order causes a suspension.” Words matter. Every. Single. One.

Practical Implications for Businesses, Insurers, and Brokers

For Multi-Location Businesses

If you operate across states (or even across counties with separate authorities), your available limits may depend on how your policy defines an occurrence and what the coverage trigger is. Endorsements for communicable disease, civil authority, ingress/egress, and similar provisions can change the math dramatically.

• Claims strategy: Document shutdown orders by jurisdiction and time period.
• Policy review: Look for “series,” “related causes,” and how location/premises are defined.
• Expect pushback: One-occurrence arguments are the insurer’s cardio. They do it daily.

For Insurers

This decision is a caution sign: if an endorsement’s trigger is a governmental order, courts may treat those orders as the operative cause for occurrence counting. If the intent is to aggregate broadly, wording needs to be explicit and internally consistent.

For Brokers and Risk Managers

When negotiating sublimits and endorsements, “occurrence” language is not boilerplate. It’s a lever. And like any lever, it can move a lot more weight than you expectespecially when a rare event makes everyone read the fine print for the first time.

How This Fits the National “Number of Occurrences” Puzzle

Nationally, courts often split based on (1) which “test” they apply, and (2) the exact endorsement language. Some decisions treat the virus or pandemic as the single underlying cause; others treat governmental orders as the operative event when policy language makes orders the trigger.

The Minnesota decision aligns with a growing theme in insurance coverage litigation: when a policy is written to pay upon specific government action, courts are less willing to let the insurer reframe the “cause” as a broader societal condition. The outcome may differ in states that strictly apply a cause-based test or under policies drafted differently.

What Happened After the Decision

After the Court of Appeals ruled on August 11, 2025, Zurich sought further review. But by late October 2025, the Minnesota Supreme Court denied Zurich’s petition for review. That left the Court of Appeals decision standing, and the case headed back to the district court for further proceedings, including the damages phase.

Translation: the “how many occurrences?” fight largely ended at 29, and the next chapters became about proving losses, applying deductibles, and navigating whatever other policy conditions show up to the party.

A Practical Checklist: If You Ever Have to Fight a One-Occurrence Argument

1. Start with the coverage grant: Identify the exact trigger. If the policy says “caused by order,” treat the order as a central fact.
2. Map the causes: Build a jurisdiction-by-jurisdiction timeline. Courts like facts that can be pinned to a calendar.
3. Read the “series” language like a detective: “Similar” and “related” are not magic words; courts still ask “related how?”
4. Don’t ignore how your state counts occurrences: Some states default to a cause test; others (like Minnesota) lean heavily on policy text.
5. Assume the insurer will aggregate: Be ready with a contract-based explanation for why separate events are separate occurrences.

Conclusion

The Minnesota Court of Appeals’ decision is a reminder that insurance coverage often turns less on what feels like the “real-world cause” and more on what the policy says causes coverage. In Life Time v. Zurich, the court treated government shutdown orders as the operative causes, refused to lump independent jurisdictions into a single “series,” and landed on 29 occurrencesdramatically reshaping what the per-occurrence sublimit could mean for a multi-state business.

If your takeaway is “I should probably reread our endorsements,” congratulationsyou are now the most popular person in the risk management meeting.

From the Field: of Real-World “Occurrence” Lessons

If you’ve never lived through a “number of occurrences” dispute, it sounds simple: count the bad things, multiply by the limit, cash the check, buy celebratory donuts. In practice, it’s more like assembling IKEA furniture while everyone argues about whether “one screw” counts as “a series of related screws.”

One recurring lesson: the first story people tell is usually the wrong story. In a crisis, the natural narrative is broad“the pandemic shut us down,” “the hacker hit us,” “the product defect happened,” “the storm did it.” But insurance outcomes tend to depend on narrower building blocks: the specific order, the specific intrusion, the specific shipment, the specific decision point that actually triggered the policy language. The Minnesota case is a textbook example: COVID is the backdrop, but the endorsement’s trigger made the governmental orders the star.

Another lesson: aggregation language is a personality test. Policies that define an occurrence as loss attributable to “one cause” invite big-picture arguments. Add “a series of similar or related causes,” and now everyone fights over what “series” means. Is it temporal succession? Common decision-maker? A shared mechanism? A shared motive? Courts often want something more than “it feels connected.” That’s why Minnesota’s approachtreating separate jurisdictions as independent, but grouping orders within a single jurisdictionmakes intuitive sense: it demanded an actual relationship, not just a shared era of misery.

Third: timelines beat adjectives. “Widespread,” “unprecedented,” and “unavoidable” are great words for press releases and terrible tools for counting occurrences. If you can show a clean timelinewho issued what order, when it took effect, when it lifted, and whether a later order restarted restrictionsyou replace argument with structure. Courts (and adjusters) respond well to structure because it looks like reality instead of advocacy.

Fourth: the number you claim matters strategically. In Life Time, the policyholder argued for 41 occurrences and the court landed at 29. That’s not a loss; that’s the normal friction of “series” language. In many disputes, an all-or-nothing posture invites an all-or-nothing ruling. A well-framed alternative“here’s why it’s multiple; here’s the cleanest way to group them if you think grouping is appropriate”often keeps you in the game.

Finally: occurrence disputes are rarely isolated. They affect deductibles, waiting periods, aggregation across coverage parts, and whether excess policies attach. A “win” on multiple occurrences can still be blunted if each occurrence carries a separate deductible, or if the policy has aggregate caps you forgot existed. The best outcomes come from treating occurrence counting as one piece of a larger coverage puzzlebecause your opponent definitely will.

Bottom line: the Minnesota decision is fun legal reading (as fun as insurance law gets, which is still less fun than puppies), but it’s also a practical reminder: policy language doesn’t just describe riskit measures it. And measurement is where the money lives.