Who Is Liable When a Co-Host Runs the Stay

The platform contract, the insurance policy and the tenancy agreement can each name a different person. Liability lives in the gap between them.

Last updated: October 28, 2026

A co-host doesn't take on liability by running a stay. They take it on, if at all, because one of three documents already says so, and the other two say something different. Before a claim arrives, those documents are just paperwork. Afterwards, they're the only account of who was supposed to be doing what.

Key Takeaways

• Three documents, three different questions. The platform contract asks who it deals with. The policy asks who it pays. The tenancy asks who may let the unit.
• One person can be the answer to one and not the others. That's the gap, and it doesn't show up until something goes wrong.
• The co-host agreement isn't a formality. Scope, money, access, records and exit, on one page, signed and dated.
• The platform's answer to "who did this" is the account, not the person. If everything runs through one login, every action looks like one person's.
• The handover line is the only document written at the time. The other three were written in advance, and they describe intent.

Three documents, three answers

Start with the platform contract, because it's the one everybody has read and nobody has understood. It governs the account, the listing and the relationship with the guest. What it names is an account holder — the person the platform will talk to, bill, and answer to when a guest complains. It isn't a statement about who does the work.

Then the insurance policy. It names an insured party, and it describes the activity that's covered. Those two things are narrower than most hosts assume. A policy written around a homeowner letting a furnished unit is answering a different question from the one a co-host asks when they're handling check-in at eleven at night. Whether the person doing the work is a named insured, and whether the work is the activity described, are questions for the insurer — asked in writing, before the season, not after an incident.

Then the tenancy or ownership agreement. It names who has the right to let the unit at all, and on what terms. In some buildings that right is conditional. In some it's absent. A co-host who runs a stay in a unit that wasn't allowed to be let hasn't created the problem, but they're standing in it.

Read the three side by side and the gap becomes visible. The owner is the account holder. The co-host does the messaging, the check-in and the cleaner's schedule. The policy names the owner. Nothing is wrong with any of it on a normal Tuesday. It becomes a problem on the day someone asks which of those three was actually running the stay.

What a co-host agreement should name

A co-host agreement earns its keep by answering questions nobody wants to ask while the arrangement still feels friendly. Six of them, and one page is enough.

Scope. What the co-host may decide alone, and what needs a message first. Discounts, refunds, late check-out, a repair, a rebooking. If the answer is "it depends", the agreement hasn't been written yet.

Money. Who receives the payout, who pays the cleaner, who holds a deposit, and how the split is calculated on a stay that gets shortened. Ambiguity here is the most common source of the argument that ends the arrangement.

Access. Who holds keys or codes, how many copies exist, what happens when a set goes missing, and who changes the code at the end. Access is the part of the job that's hardest to reverse.

Communication. Who speaks for the listing, in what tone, and within what hours. Two people answering one guest thread is how a promise gets made twice and kept once.

Records. What the co-host has to write down and send, and how often. A daily line is enough. Silence for a week isn't a record.

Exit. Notice, handover, and what happens to the guest who's already booked. An arrangement with no exit gets ended badly instead.

Records is the item that's easiest to leave vague, so make it concrete. The smallest useful version is a confirmation attached to the action itself. On an overseas property, check-in, check-out, an extension and a room move each need a person to confirm before anything changes, and the confirmation stays with the action. localsbnb.com works that way on purpose: nothing is written silently, so "who did this, and when" has an answer that isn't a guess. It doesn't decide who's responsible. It just leaves the sequence where you can see it.

None of this decides liability. What it does is remove the argument about what was agreed, which is the argument most disputes actually are. Whether it holds up where the unit is belongs to a local lawyer, and it's worth one appointment.

Where the platform contract stops

The platform's terms govern the account and the guest relationship. They don't allocate responsibility between an owner and a co-host, and they won't read your side agreement. When a dispute is opened, the platform deals with the account, because the account is what it has.

That's the practical trap: activity inside one account looks like one person's activity. Every message, every change, every confirmation is filed under the same name, whether or not that person was in the building. Nothing improper is happening. The record simply can't tell the two of you apart.

A confirmation step narrows that gap without closing it. It tells you who confirmed an action, which is more than an account name can say. It won't tell you who was responsible for the guest's problem, and it won't interpret the agreement the two of you signed.

Which is the other half of the same point: what the platform won't do. It won't read your agreement, and it won't tell you who was on shift. If the arrangement matters, it has to be legible outside the platform as well as inside it.

The handover record that helps

Every document above was written before the stay. The handover line is written during it, and that's why it carries weight: it's the only one that describes the day as it happened rather than as it was planned.

One line per day, per unit. Who ran it. What changed. What was decided, especially anything with money attached. What's outstanding, and who's picking it up tomorrow. Three sentences is a good day. One sentence is a quiet one.

Keep it somewhere the other party can read it without asking. A shared note, a message thread, a line at the bottom of the turnover sheet — the format matters less than the habit of writing it the same day. Written on Friday about Wednesday, it records a memory.

Two rules make the line worth keeping. Don't sign a day you didn't run. And when a dispute starts, stop editing: add a dated line underneath and leave the earlier text alone. A record with a clean history is more useful than a record that's been tidied.

If a guest complaint arrives, the line tells you which of the three documents to open first. A complaint about a promise is a platform-contract question. A complaint about damage is an insurance question. A complaint about whether the unit should have been let at all is a tenancy question. Different documents, different people, different answers.

FAQ

Does a co-host take on liability just by running the stay?

Not automatically. It depends on which document is being read and what it says about the work that was actually done. That's a question for a local lawyer with the three documents in front of them, and it's a much cheaper question before an incident than after one.

Should the co-host be named on the insurance policy?

That's the insurer's call, not yours, and it's worth asking in writing. The useful version of the question is specific: this person does check-in, handles guest messages and arranges cleaning at this address — is that within the cover, and does the policy need to name them? A general question gets a general answer.

What's the one record worth keeping?

A dated handover line with a name on it. It's short, it's written the same day, and it's the only document in the set that can say who was there. Everything else describes what was supposed to happen.

Liability is decided by documents written in advance and by facts recorded at the time, and the two rarely meet unless someone puts them side by side. Start with the three names, put the arrangement on one page, and write the day down while it's still the day. localsbnb.com keeps every connected channel's bookings on one calendar, which is the boring half of the answer: the sequence exists, so the argument is about judgement rather than about what happened.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Who is liable for what is decided by the documents in force where the unit is, by the platform's current terms and by the policy you actually hold, and those differ by place. Confirm your position with a local lawyer and your insurer before you hand a listing or a set of keys to anyone else.