Skip to content
Two investors reviewing resources on a laptop

Get industry-leading resources — for free

Unlock resources for every investing strategy and stage with a free account.

By continuing, you agree to BiggerPockets LLC's Terms of Use and Privacy Policy

Posted 10 days ago

Direct Bookings and the Coverage Gap Most Hosts Miss

Contain 800x800

I was talking with a host last fall who was proud of his numbers. He'd moved about 40 percent of his reservations off Airbnb and onto his own booking site. No platform fees, more repeat guests, better margins. He'd done everything the direct-booking crowd tells you to do, and he'd done it well.

Then I asked him what happens if one of those direct guests gets hurt on the property. He looked at me like I'd asked a trick question. "I have insurance," he said. And he did. The problem was that he assumed his coverage and his booking channel had nothing to do with each other. For most of his policy, that's true. For one important piece, it isn't.

This is the gap I run into most with hosts who are doing well enough to start going direct. It's something they never thought about.  They only recognize it when something happens, and by then it's too late.

So let's talk about what actually changes when a guest stops booking through a platform.

What direct booking really changes

When a guest books through Airbnb or Vrbo, two things happen at the same time. You get a reservation, and you get a layer of platform protection that rides along with it. AirCover, the host guarantee, whatever the platform is calling it that year.

People argue about how good that protection really is. I'm one of the people arguing it's thinner than the marketing suggests. But thin is not the same as nothing.

When the guest books direct, that layer is gone. Not reduce - gone. The platform was never part of the transaction, so none of its protections apply. The damage guarantee doesn't apply. The liability backstop doesn't apply. The payment dispute process, the screening, the after-the-fact support, none of it exists for that stay.

Most hosts know this in theory. Where it catches them is the next assumption: that their own policy will fill the coverage the platform used to occupy. Sometimes it does. Sometimes it doesn't. And the difference between those two outcomes is usually buried in how the policy was written, not in how the host operates.

Why your own policy might not follow the booking

Here's the part that surprises people. A lot of STR policies were quoted with platform activity in mind. The agent asked how you rent the place. You said Airbnb. The policy got built around that picture, sometimes with assumptions baked into the underwriting that nobody walked you through.

Then your operation changed and the policy didn't.

I'm not saying every STR policy has a problem with direct bookings. A properly written commercial STR liability policy generally doesn't care how the guest found you. It covers the business activity of renting the property, period. That's what you want.

The trouble is that plenty of hosts aren't on that kind of policy. They're on a homeowner's policy with a short-term rental endorsement, or a landlord policy they were told would "cover the Airbnb," or a converted personal policy that was never really designed for paying guests at all. Those policies often have exclusions that don't care whether the booking was direct or not, but they care very much that you're running a business out of the property. The platform protection was the thing that had been silently covering for that gap. Take the platform out, and the gap is just sitting there in the open.

What happened to a host who found out the hard way

A host I know in a mountain market had a setup a lot of people would envy. Strong direct-booking site, loyal repeat guests, a property that performed in every season.

One of his direct guests was a family with two kids. One of the kids took a bad fall on an exterior staircase that had a loose railing. Nothing dramatic at first. A trip to urgent care, then a follow-up, then a specialist. A few weeks later he got a letter from an attorney. The family was claiming the railing was a known maintenance issue and seeking damages for the injury and ongoing treatment. The demand came in around $185,000.

His first instinct was the same as that other host's. He had insurance. He had also, in the back of his mind, been treating Airbnb's million-dollar liability coverage as his real safety net. Except this stay never touched Airbnb. So there was no platform liability to call on. Zero.

That left his own policy. And his own policy was a landlord policy that excluded the kind of commercial guest operation he was actually running. The carrier didn't deny him out of spite. They denied him because the activity that produced the claim was outside what the policy was built to cover. The deductible didn't matter. The policy limits didn't matter. The coverage simply wasn't there for that loss.

He ended up settling for far less than the demand, but he paid for his own attorney and a meaningful chunk of the settlement out of pocket. Mid five figures, gone, plus a year of stress. The hard part  wasn't just the money. It was that he'd been one honest conversation away from knowing this in advance, and the conversation never happened because nothing had forced it.

The booking channel was what finally forced it. The injury could have happened to an Airbnb guest just as easily. But the platform coverage had been quietly masking the hole in his real policy, and direct booking pulled the mask off.

The way to think about it

I find it helps to separate two things that hosts tend to blur together.

One is your booking channel. That's a business decision about fees, control, and guest relationships. Going direct is often a smart move.

The other is your liability and property coverage. That should respond to a loss regardless of how the guest got there. If your coverage depends on the platform being involved, you don't really have coverage. You have a coincidence that's been working out so far.

The goal isn't to scare anyone away from direct bookings. The goal is to make sure your real policy is doing the job you've been assuming the platform was doing for free. When those two things are aligned, direct booking is exactly the upgrade people say it is. When they're not, you're running a more exposed operation than you were before you started keeping the platform fees.

What to actually do this week

Call your agent and ask one direct question: does my policy cover guest claims and property losses the same way whether the booking came through a platform or directly from me? Don't accept "you're fine." Ask them to point to the language. If they can't, that's your answer.

Pull your declarations page and find out what kind of policy you're actually on. Homeowner's with an endorsement, landlord, or a true commercial STR policy. If you've been operating direct bookings on anything other than a real STR policy, treat that as a flag worth resolving, not a maybe.

Stop counting platform liability protection as part of your coverage stack. Look at what your own policy would pay if a guest were injured tomorrow on a stay the platform never saw. If that number makes you squirm you've found the thing to fix before the next direct guest checks in.

None of this requires panic. It requires one discussion and a few minutes with your own paperwork. The hosts who get burned aren't the ones who run direct bookings. They're the ones who change how they operate and never update the coverage underneath it.



Comments