It’s a conversation no one ever wants to have. How does insurance respond to something as horrific as a mass shooting? It feels almost cold to talk about policies and deductibles in the face of such profound tragedy. But for the victims, the families, and the institutions left to pick up the pieces, these details are incredibly important.
And recently, a federal court case stemming from the Parkland, Florida shooting forced a really tough, and frankly, very technical question: When a tragedy unfolds over several minutes, is it one single "occurrence," or is it many?
You might be thinking, "Of course it's one event!" But from an insurer's perspective, the answer to that question could mean the difference between paying out one policy limit or many, many times over. This case put that very idea under a microscope, and the court’s decision sent a clear message to the entire industry.
The Heart of the Matter: One Event or Dozens?
Let's get right to the core of the dispute. The Broward County School Board had a liability policy with Zurich American Insurance Co. The policy provided coverage of $1 million for each "occurrence."
After the devastating shooting at Marjory Stoneman Douglas High School, the school district faced numerous lawsuits from the victims' families. When they turned to their insurance, a major disagreement came to light.
The school board argued that the entire shooting was one tragic, continuous event. Therefore, it was a single "occurrence," and the $1 million policy limit should apply once to the collective claims.
Zurich, the insurer, saw it differently. They argued that each individual shot fired by the gunman that resulted in injury or death was its own, separate "occurrence." If the court agreed with them, it would mean the insurer’s liability would be capped at the $1 million limit, but it would be subject to a separate deductible for each and every claim. This would drastically reduce the total amount the insurer would have to pay out.
Think of it like this: Imagine a hailstorm damages 20 cars in a parking lot. Is the storm one "occurrence," or is each car being hit by a piece of hail a separate "occurrence"? The answer changes everything about how the policy pays.
What Did the Policy Actually Say?
Here’s where it gets really interesting, and it’s a lesson for all of us in the insurance world. The entire case hinged on the definition of one word: "occurrence."
So, what did the policy say? Surprisingly, not much.
The policy defined an "occurrence" in a pretty standard way, as an "accident, including continuous or repeated exposure to substantially the same general harmful conditions."
You can probably see the problem right away. That language is broad. It’s ambiguous. Does a shooting spree count as "repeated exposure to substantially the same general harmful conditions"? You could argue it either way, and that’s exactly what the lawyers did.
Zurich’s legal team pointed to the gunman’s actions—pausing, reloading, moving through the school. They claimed these breaks in the action created distinct, separate events. The school board’s team argued the opposite, stating it was a single, uninterrupted attack with one cause and one goal.
The Court Steps In: The "Unfortunate Event" Test
When policy language is vague, it’s up to the courts to interpret it. The 11th U.S. Circuit Court of Appeals took up the case and ultimately sided with the school district.
They didn't get there by accident. The court applied something called the "cause theory" or, as it's sometimes known, the "unfortunate event" test.
Here’s a simple way to think about it:
- You look for the root cause. The court asked, what was the underlying cause of all the injuries and deaths?
- Was there one proximate cause? In this case, the court determined that the single, proximate cause of all the harm was the shooter's rampage. Even though he fired multiple shots, it was all part of one continuous, tragic event.
The court essentially said that you can't just slice up a single, horrifying event into tiny little pieces to limit your liability. The judges stated that unless the policy language is crystal clear and unambiguously defines each injury as a separate occurrence, the default interpretation should be that the entire event is one occurrence.
They pointed out that if the insurer wanted to treat each injury from each bullet as a separate occurrence, they should have written it explicitly into the policy. They didn't, so the ambiguity was interpreted in favor of the policyholder.
Why This Ruling Sends a Big Message to the Insurance World
Okay, so why are we talking about this? Because this wasn't just a ruling about one case. It sets a powerful precedent for how insurance policies will be interpreted in the face of mass casualty events, which are tragically becoming more common.
For insurers, the message is loud and clear: Clarity is king. If you want to limit your exposure by defining "occurrence" in a very specific way, you had better spell it out in plain, unmistakable English. Vague, boilerplate language isn't going to cut it anymore when a court is looking at it. We're likely going to see underwriters get much, much more specific in their policy wordings for general liability, especially for public entities like schools.
For policyholders and the brokers who advise them, this is a moment to pay extremely close attention to definitions. When you're reviewing a policy, don't just look at the limits and the premium. Dig into the definitions section. Understand exactly how an "occurrence" is defined. If it's vague, that could be a good thing in a claims scenario, as this case shows, but it also creates uncertainty.
At the end of the day, this ruling brings a bit of common sense to a terribly uncommon situation. It affirms that a single, nightmarish event should be treated as just that—one event. And it puts the responsibility squarely on insurers to be upfront and clear in their contracts, which is something we can all agree is a good thing for everyone.
