Somewhere in nearly every liability policy, platform protection program, and incident report you'll ever encounter as an STR operator, the word "negligence" appears. A guest slips on a wet deck because the host didn't add a non-slip surface — negligence. A guest falls down stairs because a railing was loose — negligence. A property catches fire because a space heater the host provided didn't meet current safety standards — negligence.
What rarely gets explained is that "negligence" isn't one thing. It's a spectrum, and at a certain point along that spectrum, the legal and insurance treatment of a claim changes substantially. On one end is ordinary negligence — a failure to exercise the care a reasonably careful person would have exercised, usually unintentional, often an oversight. On the other end is gross negligence — a conscious disregard of a known risk, where the person knew or should have known about a serious hazard and chose not to address it.
Almost every standard liability policy is built around covering the first category. Almost every policy excludes, or treats very differently, the second. And the exclusion language used by platform protection programs — particularly the phrase "host negligence" — sits in a place that creates real confusion about which category it's actually describing.
This article is about that distinction: what it means, why it matters more than most operators realize, and what separates an incident that stays in "ordinary negligence, covered" territory from one that drifts toward "gross negligence, probably not."
Ordinary Negligence: The Failure to Be Careful Enough
Ordinary negligence, in the way courts and insurance policies generally use the term, describes a failure to exercise the degree of care that a reasonably prudent person would exercise under similar circumstances. It does not require intent. It does not require that the person knew something bad would happen. It describes an oversight — a failure to notice, to maintain, to inspect, or to correct something that a careful property owner should have caught.
In the STR context, ordinary negligence is the category that covers the overwhelming majority of premises liability claims. A deck board that's developed a soft spot from seasonal wear, and nobody walked the deck recently enough to notice before a guest's foot went through it. A pool gate latch that's gradually loosened over a season of use, and nobody tested it before the next booking. A handrail that was secure last year but has worked loose from normal use and hasn't been checked since.
None of these scenarios involve a host who knew about the problem and ignored it. They involve a host who, in hindsight, should have caught something through reasonable maintenance and didn't. That's ordinary negligence. It's the most common basis for a premises liability claim, and — this is the important part — it's also the thing standard liability insurance is specifically designed to respond to.
Gross Negligence: Knowing About It and Choosing Not to Act
Gross negligence describes something categorically different: a conscious and voluntary disregard of the need to use reasonable care, in circumstances where the failure to act is likely to cause serious, foreseeable harm. The defining feature isn't just that something bad happened because of a maintenance failure — it's that the person responsible knew, or had been specifically warned, about a serious hazard, and chose not to address it anyway.
The difference often comes down to a timeline. A deck railing that fails because it quietly loosened over a season, with no prior indication of a problem, points toward ordinary negligence. A deck railing that a previous guest reported as wobbly, that the host acknowledged and said they'd "get to," and that then fails on the next guest before anyone addressed it — that same physical failure, with that history attached, starts to look like something else. The hazard was known. It was specifically flagged. And it was left in place anyway, with a foreseeable and serious outcome.
This is also where the regulatory non-compliance pattern that's appeared repeatedly in Threshold STR's incident report series becomes relevant. A pool that doesn't meet a state's published safety code, or a property in a designated fire hazard zone that hasn't maintained the legally required defensible space, isn't a case of an unknown hazard. The standard is published, the requirement is public, and the operator's obligation to comply is established by law rather than by happenstance. When an incident occurs under those conditions, the gap between "I didn't know" and "I was supposed to know, because it's the law, and I didn't comply" is exactly the gap between ordinary and gross negligence — even though, in many of these cases, carriers handle it as a partial coverage dispute rather than a full denial, attributing only the portion of the loss connected to the non-compliant condition.
Why This Distinction Exists in Insurance at All
It might seem like insurance should simply cover "negligence" without needing to subdivide it. The reason it doesn't gets at something fundamental about what insurance is for.
Insurance exists to spread the financial cost of unintentional, unpredictable losses across a large pool of policyholders. A claim arising from ordinary negligence — an oversight, a maintenance gap, something that could happen to any reasonably careful operator on a given day — fits this model. It's the kind of risk that's genuinely uncertain in advance and genuinely insurable.
A claim arising from gross negligence is different in kind. By definition, it involves a known risk that the policyholder chose not to address. Insuring against the consequences of knowingly ignoring a serious hazard would mean insuring against the policyholder's own choices in a way that undermines the incentive to actually maintain the property safely. This is why gross negligence, willful misconduct, and intentional acts sit outside what most liability policies are designed to cover — not as an arbitrary technicality, but as a reflection of what insurance is structurally meant to do.
The practical upshot: ordinary negligence coverage isn't a loophole or a generous add-on. It's the core product. A liability policy that didn't cover ordinary negligence claims wouldn't cover almost anything, because almost every premises liability claim is, at its foundation, an allegation of ordinary negligence.
The AirCover Paradox
This is where the language used by platform protection programs becomes genuinely important to understand — and where a lot of operators get a misleading impression of what they're actually protected against.
AirCover's host liability protection, like similar programs from other platforms, contains exclusionary language for claims arising from the host's negligence — sometimes framed as a maintenance failure exclusion, sometimes as a broader negligence exclusion. Read in isolation, this sounds like a narrow, reasonable carve-out: if the host did something wrong, the program won't bail them out.
But here's the paradox. If "host negligence" is read broadly — to include ordinary negligence, the failure to catch a maintenance issue through reasonable inspection — then the exclusion potentially covers the majority of claims that would otherwise be eligible. A guest slips on a wet deck because there's no non-slip surface: that's a maintenance condition the host could arguably have addressed. A guest falls because of a loose railing: same thing. Read broadly enough, "host negligence" describes nearly every premises liability scenario, because nearly every premises liability scenario involves some allegation that the host should have done something differently.
Incident Report №001 in Threshold STR's case file series documented exactly this dynamic. A guest slipped on a wet surface near a hot tub. AirCover's review attributed the incident to host maintenance negligence — the absence of slip-resistant surfacing — and the claim was excluded on that basis. The host's actual STR liability policy, by contrast, was specifically designed to respond to exactly this kind of claim, because ordinary negligence arising from a maintenance condition is the central thing that policy exists to cover.
The lesson isn't that platform protection programs are acting in bad faith, or that their negligence exclusions are unusually aggressive compared to industry norms. It's that platform protection programs are not built to be an operator's primary liability coverage, and the negligence exclusion is one of the clearest reasons why. A standalone STR liability policy treats ordinary negligence as the claim it's there to pay. A program with a host negligence exclusion treats the same fact pattern as potentially outside its scope. Those are two very different starting points, and an operator relying on the platform program as their primary protection is relying on the one that starts from "probably excluded" for the most common type of claim.
Punitive Damages: The Other Place This Distinction Shows Up
The ordinary-versus-gross-negligence line matters for a second reason that's easy to miss until it's relevant: punitive damages.
Compensatory damages — the category that covers medical expenses, lost income, and pain and suffering tied directly to the injury — are what most liability coverage is built to pay. Punitive damages are different. They're not compensation for the plaintiff's losses; they're a financial penalty intended to punish the defendant and deter similar conduct, and courts generally reserve them for conduct that rises above ordinary negligence — gross negligence, recklessness, or willful misconduct.
Punitive damages are treated very differently in the insurance world than compensatory damages. Some states prohibit insurance coverage for punitive damages as a matter of public policy — the reasoning being similar to the reasoning behind excluding gross negligence generally: if punitive damages exist to punish and deter, allowing insurance to absorb them defeats the purpose. Other states permit it, but many liability policies exclude punitive damages regardless, through specific policy language.
This is where the regulatory non-compliance incidents in Threshold STR's case file series connect back to this topic directly. Incident Report №004 — the pool near-drowning — involved documented violations of a state's pool safety code: a gate that wasn't self-latching, missing depth markers, absent safety equipment. The plaintiff's demand letter explicitly raised the prospect of punitive damages if the case proceeded to litigation, specifically because the documented code violations supported an argument that the operator's conduct went beyond ordinary negligence. That threat was part of what drove the settlement pressure in that case. Whether or not punitive damages would ultimately have been awarded, the mere fact that the regulatory violations opened the door to that argument changed the negotiating dynamic — and punitive damages, had they been awarded, would very likely have fallen outside whatever liability coverage was in place, regardless of the limit.
The Documentation Dividing Line
If the distinction between ordinary and gross negligence often comes down to what the operator knew and when, then documentation — or its absence — is one of the most direct ways an operator's actual practices translate into where an incident falls on that spectrum.
Consider two versions of the same physical failure: a deck railing gives way and a guest is injured.
In the first version, the operator has a maintenance log showing the deck was inspected at the start of the season, the railing was checked and found secure, and nothing in the guest communication history before the incident flagged any concern with it. The railing failure, on this record, looks like exactly what ordinary negligence describes — a condition that developed in a way reasonable maintenance practices didn't catch in time. This is the scenario a standard liability policy is built to cover, and the documentation supports that characterization.
In the second version, a guest messaged the host two weeks earlier saying the railing felt loose. The host replied that they'd look at it. No inspection happened. No work order was created. The next guest leaned on the same railing and it failed. The physical event is identical to the first version. The record is not. This version has a known hazard, a specific warning, and a documented choice not to act before a foreseeable and serious outcome occurred — the elements that define gross negligence.
The maintenance log isn't paperwork for its own sake. It's the evidence that determines which of these two stories an insurance investigation, and potentially a court, will conclude actually happened. An operator with consistent documentation of inspections, guest-reported issues, and how those issues were resolved is building a record that keeps incidents in ordinary-negligence territory — the territory where coverage is designed to respond. An operator without that record is leaving the characterization of any incident more open to interpretation, in a direction that doesn't favor them.
What This Means in Practice
None of this changes what operators should already be doing — inspecting amenities regularly, addressing guest-reported issues promptly, maintaining the property to the standards a reasonably careful operator would maintain it. What it changes is the understanding of why those practices matter beyond simple risk reduction.
A property maintained to a reasonable standard, with documentation showing that standard was met, is a property where incidents — when they happen, because they sometimes will regardless of how careful an operator is — fall into the category of risk that liability insurance is specifically designed to absorb. That's not a small thing. It's the difference between an incident being a covered claim, handled by the insurer, within a process the operator has already paid for, and an incident becoming a direct financial exposure with the operator negotiating alone.
It's also worth revisiting, specifically, what "host negligence" exclusions in platform protection programs actually mean for an operator's coverage strategy. If a meaningful share of realistic claim scenarios — a slip near a wet surface, a fall related to a maintenance condition, an injury connected to an amenity that wasn't perfectly maintained — could plausibly be characterized as "host negligence" under a broad reading of that exclusion, then a platform protection program is not a substitute for a liability policy that's specifically designed to treat those same scenarios as the claims it exists to pay. This isn't a reason to be alarmed about platform protection programs; it's a reason to understand what role they're actually suited to play, and to make sure the primary liability coverage — the STR policy itself — is the layer doing the work for the most common category of claim.
Operational Lessons
Understand which category of negligence your coverage is built around. A standard STR liability policy is designed to cover ordinary negligence — the most common basis for premises liability claims. Platform protection programs with "host negligence" exclusions occupy a different position, and a broad reading of that language can encompass much of what a liability policy would otherwise pay. Don't treat platform protection as a substitute for liability coverage; treat it as a supplementary program with meaningfully narrower scope for negligence-based claims.
Known hazards need documented resolution, not just acknowledgment. If a guest reports a problem, "noted, we'll look at it" is not the end of the process from a risk standpoint. The gap between an unaddressed known hazard and a documented inspection-and-repair record is, in many cases, the gap between ordinary and gross negligence. Close that gap with a record, not just a reply.
Regulatory compliance isn't a separate issue from negligence — it's evidence of it. When a published safety standard exists — pool codes, defensible space requirements, fire safety regulations — non-compliance with that standard is one of the clearest ways an incident moves from "unfortunate oversight" toward "known, defined obligation that wasn't met." This is also where punitive damages most commonly enter the conversation, and punitive damages sit outside most liability coverage regardless of limit.
Maintenance documentation is the record that tells your side of the story. An inspection log, a record of guest-reported issues and how they were resolved, and dated photos of conditions before and after maintenance work are not bureaucratic overhead. They're the evidence that an incident, when it happens, reflects an oversight rather than a known and ignored risk — which is the difference between a claim your insurance is built to pay and one it's built to question.
The Bottom Line
"Negligence" is not a single legal category, and the difference between its two main forms — ordinary and gross — runs through almost every coverage decision an STR operator will face. Ordinary negligence, the everyday oversight that any careful operator could experience, is what standard liability insurance is built to cover. It is the product, not an exception to it. Gross negligence — a known hazard, specifically flagged, left unaddressed until it caused serious harm — sits outside what most coverage responds to, and it's also where punitive damages, themselves largely uninsurable, become a real possibility.
The practices that keep an operator on the right side of that line are the same practices that make for a well-run property: regular inspection, prompt resolution of reported issues, compliance with published safety standards, and a documentation habit that turns "we take care of this place" from a claim into a record. Those practices don't just reduce the chance of an incident. They determine, when an incident happens anyway, which kind of negligence it looks like — and which kind of negligence your policy is actually there for.
Schedule a full audit with Threshold STR to review how your current coverage responds to ordinary negligence claims, or take the free five-minute Risk Score to see where your coverage stands.
This article is prepared by Threshold STR for educational and operational guidance purposes. Definitions of ordinary negligence, gross negligence, and the treatment of punitive damages vary by state. It does not constitute legal or insurance advice. Before making coverage decisions or assessing a specific claim, consult with a licensed insurance professional or attorney in your state.