Every STR host eventually deals with a broken lamp, a stained rug, or a hot tub that "wasn't like that when we checked in." The question isn't whether damage happens — it's whether your protection setup actually pays out when it does. Most hosts default to whatever their booking platform offers by default and never revisit it. That's a mistake, because deposits, host guarantee programs, and third-party damage waivers protect you in very different ways, with very different odds of collecting.
Here's how the three main approaches actually work, where each one fails, and how to combine them so you're not the one eating the cost of a guest's mistake.
The Three Ways to Cover Damage
Refundable Security Deposits
A deposit held on the guest's card (or collected via the platform) and released after checkout if nothing's wrong. On paper this looks like the cleanest option: you saw the damage, you charge against the deposit, done.
In practice, deposits are weak. Airbnb doesn't support a true pre-authorized deposit anymore for most hosts — instead, damage claims go through AirCover or a request-money flow after the fact, which means you're asking the guest to agree to the charge or escalating to platform support. On Vrbo and direct-booking sites where you control the payment processor, a real deposit hold is more enforceable, but guests dispute charges, card holds expire, and you're often arguing over "normal wear" versus "damage" with no independent judge.
Platform Host Guarantee Programs
Airbnb's AirCover and Vrbo's equivalent process are marketed as free protection, and they're worth using, but treat them as a backstop, not a plan. Coverage typically excludes normal wear and tear, has valuation and depreciation rules that lowball older furniture, requires photo documentation within a tight window after checkout, and can take weeks to resolve. Payouts are not guaranteed — they're adjudicated, and the platform is incentivized to keep both host and guest happy, not to maximize your reimbursement.
If you're relying on a host guarantee as your only protection, document obsessively: pre-stay photos of every room, timestamped, stored somewhere you control (not just the platform's messaging thread). Without that evidence, most claims stall.
Third-Party Damage Waiver Fees
A growing number of hosts charge guests a small non-refundable fee at booking (sometimes bundled through a dedicated damage-protection provider) in exchange for a set coverage amount if something breaks. This shifts the model from "hope I can prove damage and collect" to "file a claim against a policy with defined terms."
The advantage is clarity: coverage limits, exclusions, and claim windows are spelled out in a contract instead of a platform's discretionary process. The tradeoff is cost — you're either absorbing the fee or passing it to guests, and coverage caps mean a guest who causes five figures of damage (a kitchen fire, a flooded unit) will still exceed the policy. That's a separate exposure landlord and STR-specific insurance policies are meant to cover, not damage waivers.
Where Each One Fits
These aren't competing options — they cover different layers of risk:
- Small stuff (broken glassware, a stained comforter, a missing remote): Absorb it as a cost of doing business or use the platform's resolution process. Not worth the friction of a formal claim.
- Mid-range damage (furniture, appliances, minor property damage): This is where a damage waiver or a documented deposit process earns its keep. Defined coverage and a claims process beat arguing with platform support.
- Major loss (fire, flooding, structural damage, a guest injury): None of the above will fully cover this. That's what your STR-specific liability and property insurance is for — and if you're operating an arbitrage unit, your landlord's policy almost certainly doesn't cover guest-caused damage or the increased liability of short-term occupancy at all.
Building a Protection Stack That Actually Pays Out
Instead of picking one option, layer them:
- Document before every stay. Timestamped photos of every room, stored off-platform, are the single biggest factor in whether any claim — platform guarantee, damage waiver, or insurance — actually pays.
- Use a damage waiver or deposit for predictable, mid-range risk. Pick whichever gives you an actual contract with claim terms, not just a discretionary review.
- Keep the platform host guarantee as a fallback, not your primary plan, and know its exclusions before you need it.
- Carry STR-appropriate insurance for the losses that exceed deposit and waiver limits — and if you're subletting or arbitraging, confirm your lease and your insurer both explicitly permit short-term guest occupancy, or a major claim can get denied on a technicality that has nothing to do with the damage itself.
The mistake most hosts make isn't skipping protection entirely — it's assuming whatever came pre-enabled on their booking platform is sufficient. It usually isn't, and you find out at the worst possible time: mid-claim, with a guest who's already checked out and stopped responding.
If you're still underwriting whether a given property is worth the operational overhead of running an STR at all — deposits, insurance, and damage risk included — AirLoom's underwriting pulls the compliance and demand signals together so you're not evaluating that risk on gut feel.