damage waiver

The guest pays a modest fee at booking, typically presented as damage protection. That fee buys cover for accidental damage up to a limit stated by the provider. When damage happens, the host claims against the waiver rather than asking the guest for money, which keeps the relationship intact and speeds up recovery.

The important word is accidental. Waivers are generally written to cover mishaps rather than deliberate destruction, theft or breaches of the rules, so a party wrecking a property is usually outside the cover and back in ordinary claim territory.

A refundable damage deposit holds the guest's own money and returns it after checkout: strong protection, real booking friction, and a release process to manage. A waiver removes the friction and the admin, but caps recovery at the provider's limit and excludes intentional damage. Deposit-free relies on the platform programme alone.

The three models are compared directly in damage waiver versus security deposit versus deposit-free, including which one suits a direct-booking operation and which suits a platform-only one.

On platform bookings, host damage protection already sits behind the stay, so a waiver is mostly redundant there. Waivers earn their place on direct bookings and partner-platform stays, where nothing from the platform reaches you at all.

That is the same gap covered in direct-booking damage with no AirCover and collecting a damage deposit for direct bookings. If most of your nights come through your own site, this is the decision to get right.

It does not remove the need to document. Waiver providers ask for the same evidence a platform does: proof of condition before the stay, dated evidence of the damage, and a third-party cost. A claim with no before-record fails with a waiver provider for exactly the reasons it fails elsewhere.

It also does not remove liability exposure, which is a different risk entirely, covered in host liability insurance, and it does not replace a property policy for your building and contents.