Somewhere in the twelve-point pre-season property checklist of almost every STR operator is an item about smoke detectors. Test them, replace batteries if needed, check that they're all still there. Most operators do this, or mean to.
What almost none of them have is a clear picture of how much a functioning detector, versus an absent one, versus one that's present but past its service life, actually changes what happens in a claim. Not the safety outcome, though that obviously matters. The claims outcome: whether a liability policy responds, what the claim's settlement value is, and whether the regulatory non-compliance pattern that's threaded through Threshold STR's incident report series shows up here too.
It does. And the mechanism is worth understanding, because "I have smoke detectors" and "I have a detector program that would hold up in a claims investigation" are not the same statement.
How Detectors Appear in a Claim
When a fire or CO incident occurs at an STR property, the claims investigation doesn't begin and end with who was at fault for the ignition source. It also asks what warning systems were in place and whether they functioned as required, because the answer to that question directly shapes how the negligence analysis is framed.
A claim arising from a fire where guests were warned and evacuated because a functioning detector activated looks quite different, from a liability standpoint, than a claim arising from a fire where guests were harmed and no detector alerted them. In the first scenario, the detector is evidence of reasonable care, the host identified the hazard, installed the appropriate warning system, and it worked. In the second, the absence or failure of the detector becomes evidence of exactly the kind of foreseeable risk that the host was obligated to address and didn't.
This is the same mechanism documented in Threshold STR's incident reports involving pool safety codes (Incident №004), defensible space requirements (Incident №009), and exterior egress lighting (Incident №011). In each of those cases, a published regulatory standard existed, the property was non-compliant, and that non-compliance became the evidentiary basis for a claim's escalation beyond what ordinary negligence alone would have produced. Smoke and CO detector requirements follow exactly the same pattern: they're published standards, generally mandated by state or local law, and their absence at the time of an incident is not a fact that quietly disappears. It goes into the investigation file.
In Incident Report №007, the space heater fire, the smoke detector worked. The guests were alerted, evacuated, and neither was injured. The claim that followed was about property damage and contents coverage, not about guest harm from a fire that went undetected during a sleeping stay. That's the best version of how a fire claim resolves at an STR property, and the functioning detector is a significant reason why.
The Regulatory Baseline, and Why CO Is the One Most Hosts Are Behind On
Smoke detectors in residential properties have been required nationwide for long enough that most hosts have them without giving it much thought. The regulatory situation with carbon monoxide detectors is different: requirements have expanded dramatically over the past decade, vary meaningfully by state and local jurisdiction, and a significant number of operators are still running properties that don't meet current requirements, not because they decided not to comply, but because the requirements are newer and less universally understood.
The general trigger conditions for CO detector requirements, which exist in most current state and local codes covering rental properties, are: gas appliances (furnace, water heater, range, dryer), an attached garage, and fuel-burning heating systems of any type (oil, propane, natural gas). A property with any of these features typically needs a functioning CO detector in the current regulatory environment, and the specific placement and quantity requirements depend on the jurisdiction.
Carbon monoxide is the specific hazard that makes the "I didn't know it was leaking" scenario uniquely dangerous: it's colorless, odorless, and produces symptoms, headache, dizziness, confusion, fatigue, that guests in an unfamiliar place may not immediately recognize as poisoning rather than illness. By the time guests understand what's happening, the situation may have progressed significantly. This is the hazard that CO detectors exist to interrupt, and it's the one where the absence of a required detector in a claim investigation carries the most significant implications, because the foreseeability of serious harm without adequate warning is well-established.
Present Isn't Enough: The Three Ways a Detector Can Fail a Claims Test
The more operationally specific point, and the one that separates a genuine detector program from a box-checking exercise, is that having a detector present isn't the same as having a detector that would function in an incident and hold up in the investigation that follows. Three failure modes are worth understanding.
Age. Smoke detectors have a manufacturer-recommended service life, typically ten years from the manufacture date, not the installation date. CO detectors vary by type but typically run five to seven years. These aren't suggestions; they reflect the actual operational reliability of the sensing elements over time. A detector that's past its service life is present but may not function reliably, and a claims investigation that discovers an expired manufacturer date on a detector that didn't alert during an incident will treat that expired detector as a maintenance failure, not as a properly functioning safety device.
This matters specifically because the manufacture date is printed on the detector itself and is trivially discoverable by an investigator. An operator who replaces detectors on a documented cycle is in a fundamentally different position than one whose basement-level smoke detector has a 2011 manufacture date.
Battery status. Battery-powered detectors are the most common type in vacation rental properties, and they're adequate in most jurisdictions provided they're maintained. A dead or dying battery renders the detector non-functional regardless of whether the device itself is in-date. The "low battery" chirp is a warning that guests sometimes remove the battery to stop the noise rather than replace it, particularly if they're staying for a weekend and the sound is disruptive at 2 AM. A protocol that confirms battery status before every booking, rather than just at the start of each season, addresses this in a way that seasonal testing doesn't.
Placement. Having detectors and having detectors in the right places are different statements. Most codes require smoke detectors on each level of the property, in or near each sleeping area, and in specific locations relative to sleeping rooms and common areas. CO detector placement requirements often specify proximity to sleeping areas and, in some codes, floor level (CO is slightly lighter than air but detectably concentrated near floor level in accumulation scenarios). A single detector in the main hallway of a two-story, four-bedroom property is unlikely to meet current placement requirements, and an investigator assessing why a detector in the wrong location didn't alert a guest in a specific room will find the placement non-compliant.
The Combination Detector Question
Smoke/CO combination detectors, single units that detect both hazards, are widely available and frequently used as an efficient way to meet both requirements with fewer devices. They're appropriate in many circumstances, but the efficiency logic breaks down if the two sets of placement requirements point to different locations.
Smoke detectors need to be on the ceiling or high on walls, near sleeping areas, on each floor. CO detector placement requirements, depending on the jurisdiction, may specify proximity to sleeping areas but also sometimes address floor-level placement where CO concentrations are measurable. In a property where the optimal placement for smoke detection and the appropriate placement for CO detection aren't the same location, a single combination unit placed to meet one requirement may not adequately meet the other.
The practical answer for most properties is a combination unit for each sleeping area and each floor, rather than a single combination unit per floor on the theory that it covers both requirements in one device. This is slightly more hardware than the minimal approach, but it addresses both placement dimensions for both hazards simultaneously and produces the cleanest claims record: every sleeping area, every level, fully covered for both smoke and CO, with no ambiguity about whether a single hallway unit met the placement requirement for bedrooms.
Interconnected Alarms and Larger Properties
Some jurisdictions require that when any detector activates, all detectors activate, a configuration called interconnected or whole-house alarming. For large STR properties with multiple sleeping areas across multiple floors, interconnection is worth understanding regardless of whether it's locally required, because the alternative, a fire that starts in a lower-level common area, with a detector that activates, but guests asleep on the upper level who don't hear it, is exactly the scenario that interconnection is designed to prevent.
Wireless interconnected systems have become widely available and much more practical to retrofit into existing construction than the hardwired interconnection that older code editions required. For properties above a certain size, confirming the interconnection question specifically, either because local code requires it, or because the property profile warrants it regardless, is the kind of due diligence that distinguishes a detector program built for a claims investigation from one built to pass a pre-season checklist.
What Documentation Actually Looks Like
The documentation practice that transforms a routine safety task into a defensible record is simpler than it sounds: photograph the detectors, including the manufacture date labels, at the start of each season and before each major booking period. Note battery replacement dates. Keep a log that shows the testing schedule and outcome. This is the difference between being able to say "we maintain our detectors" and being able to show it, to an adjuster, to a defense attorney, to an underwriter at renewal.
If a guest ever complains about a chirping detector or removes a battery during a stay, that complaint or that access-log entry is a moment that should generate an action item, the same way a review mentioning a safety condition (as documented in Incident №011) should generate a work order. The standard isn't perfection; it's documented reasonable care, consistently applied.
The CO Scenario Specific to STR Properties
There's a CO exposure scenario specific to how STR properties are typically operated that's worth naming directly: a gas appliance malfunction or flue blockage that develops between a guest's departure and the next guest's arrival, during a period when nobody is monitoring the property. Guests arrive, spend their first night, and the accumulated CO makes them ill overnight before any detector alert reaches a threshold, if there's no functioning detector in the sleeping area, or if the detector is present but not maintained.
This is the CO version of the "slow leak nobody noticed" scenario from Incident №005 (mold and water damage). The hazard accumulates in an unmonitored property. The first people to encounter it are the next guests. And the question of whether there was a functioning CO detector in the sleeping area on the night of exposure becomes the central fact in the liability investigation.
A functioning CO detector in that scenario doesn't necessarily prevent the exposure, it interrupts it before it becomes serious and gives guests the information to evacuate. That distinction, between a detected early-stage exposure and an undetected one that progresses overnight, is the difference between a claim that involves medical monitoring costs and one that involves something significantly worse.
Operational Lessons
Confirm your current detector inventory against your jurisdiction's specific requirements. Not the general standard, the specific current requirement for your state and locality, for a rental property with your specific appliance configuration. The CO detector regulatory environment has moved significantly in recent years, and "I have a smoke detector in the hallway" may not reflect what's actually required in your market.
Check the manufacture date on every detector in the property and replace anything past its service life. The date is on the back of the unit. Ten years is the general smoke detector standard; consult the manufacturer label on CO detectors, which varies by type. An expired detector is not a functioning safety device, and it's not a defensible one.
Confirm battery status before each booking, not just at the start of each season. The guest who removes a battery at 2 AM and doesn't tell anyone has created a gap in your safety program that your seasonal test didn't catch.
Photograph the detectors, including manufacture date labels, and document the testing schedule. This is the difference between "we maintain our detectors" and "here's the record showing we do." One of those is useful in a claims investigation.
For large or multi-story properties, confirm whether interconnection is required and whether the property meets that standard. The scenario where a guest on the third floor doesn't hear the first-floor detector isn't abstract.
The Bottom Line
A functioning smoke and CO detector program isn't a safety feature that sits separately from the insurance conversation. It's one of the most direct ways a host's maintenance practices translate into claims outcomes, specifically, into whether an incident involves evidence of reasonable care or evidence of a documented regulatory failure that was left unaddressed.
The difference between those two outcomes isn't whether a host had good intentions about safety. It's whether the detectors were present, in code-compliant locations, within their service life, with functioning power sources, documented as maintained, and whether, in the incident that followed, they did what they were installed to do.
Schedule a full audit with Threshold STR to walk through your property's safety device program alongside your coverage review, or take the free five-minute Risk Score to see where your current setup stands.
This article is prepared by Threshold STR for educational and operational guidance purposes. Smoke and CO detector requirements vary by state, locality, and property type and have changed frequently in recent years. It does not constitute legal or insurance advice. Confirm current requirements with your local jurisdiction and a licensed insurance professional before making decisions about your detector program.