Handing Over to a Remote Co-Host: The Document Pack That Prevents Chaos

A handover fails on the eleventh question, not the first. The pack exists to answer it before it is asked.

Last updated: September 21, 2026

Every handover starts well. You spend an hour on the phone, you share the lockbox code and the cleaner's number, and for the first fortnight nothing goes wrong because nothing much happens. Then a guest arrives to find the wrong linen, the boiler makes a noise nobody has heard before, and a rate decision is needed by Thursday — and each of those arrives as a message at an hour when you are not awake. The first question is never the problem. It is the eleventh, three weeks in, that tells you whether you handed over work or only handed over a code. This guide sets out what a co-host needs on day one, in week one and in month one, the five documents that absorb most of the questions, which access to grant and which to keep, and how to rehearse the whole thing before it matters.

Key Takeaways

• Hand over decisions, not just keys. A code lets somebody in; a rule lets them act.
• Day one, week one, month one. Three different sets of needs, three different deliveries.
• Five documents absorb most of it. Facts, standard, contacts, money, calendar.
• Grant access by domain. Room status and orders usually yes; rates and payout details usually no.
• Rehearse before you need it. One real weekend tells you more than a month of theory.

What they need on day one, in week one, in month one

A handover delivered all at once is a handover nobody reads. Split it by when the need actually arrives.

	What they need	What happens if they do not have it
Day one	How to get in, who to call, what an emergency is, and what they may spend without asking	First incident becomes a phone call to you at the worst possible hour
Week one	The standard the unit is turned to, the stock levels, and how to report a problem	Standards drift to whatever they think is reasonable
Month one	What they own completely, what needs a yes from you, and how the money works	Every decision routes back to you, which is the failure you were trying to fix

The month-one column is the one that decides whether the arrangement survives. A co-host who still needs you for routine decisions is not a co-host; they are a deputy with a key. The purpose of the pack is to move decisions across, and that only happens when ownership is written down rather than assumed.

Written ownership also changes what you do with the tools. Availability and rates for Airbnb, Booking.com, Agoda and Trip.com sit on one grid at localsbnb.com, and deciding who is allowed to move which part of that grid is a better use of an hour than agreeing a rate over the phone every week.

Five documents that absorb most of the questions

Five is enough. Each one exists to answer a specific question that otherwise becomes a message.

Document	The question it answers	What breaks without it
Unit fact sheet, one page per unit	Where is the thing, and how does it work	"Where is the stopcock" at eleven at night
The standard, with photographs	What does ready look like in this unit	A standard that lives in your head and drifts
Contacts and escalation ladder	Who do I call, and when do I call you	Either silence, or you being called for everything
The money rules	What can I spend, and what needs a receipt	Small problems waiting for approval until they are big
The calendar rules	Who moves rates, who blocks nights, what needs asking	Two people editing the same week for different reasons

The escalation ladder deserves more attention than it usually gets. It needs three rungs and a number on each: what they decide alone, what they decide and tell you later, and what stops and waits. Without the middle rung, everything either escalates or is handled silently, and both are worse than the alternative.

Keep the fact sheet to one page, and put in it only what a person standing in the unit needs: the stopcock, the consumer unit, the spare key, the bin day, the building contact, and the one appliance that behaves oddly. Everything else belongs in a folder they can open, not in a document they have to scan.

Money and access: what to grant, and what to keep

Access is the part people get wrong in both directions — too little, and nothing gets done; too much, and you find out about it on a bank statement.

Area	Grant	Why
Room status and the calendar	Usually yes	Turning a unit and blocking a night are the job
Orders and guest messages	Yes, where the channel allows it	Answering a guest is the job; the alternative is a delay
Rates and pricing	Only with a stated range	Rate decisions compound, so bound them rather than forbid them
Finance and payout details	No	Nothing in the day job requires it

Grant by domain rather than by trust. That is the whole rule: give the areas the role needs, and not the areas it does not, rather than deciding how much you like the person. Access that is scoped to a domain can be reviewed and withdrawn; access granted as a favour cannot be, because nobody remembers what was included.

Two things about data belong next to that table. Credentials stay on your own machine and out of the shared pack — a handover document is the wrong place for anything that opens the business. And guest names, phone numbers and identity details are masked in the system rather than shown in full, so the pack should never become a second, unprotected copy of them. Whatever you write, assume it will be forwarded.

Rehearse the pack before you need it

A pack that has never been used is a hypothesis. One weekend of real operation turns it into something you can rely on.

Step	What you do	What you are testing
Pick a weekend with real arrivals	Hand it over completely, and do not answer	Whether the fact sheet covers what actually came up
Log every question	Have them write down what they had to ask	Which document has the gap
Withhold one answer	Let one genuine question go unanswered until Monday	Whether the escalation ladder works
Review on the Monday	Fix the pack, not the person	Whether the same question can ever be asked again

The third row is the uncomfortable one and the most useful. A pack only proves itself when you are genuinely unavailable, and the questions that surface then are exactly the ones the next version has to absorb.

Then run it twice a year. Standards drift, staff change, and a pack written for the person you hired in March will not fit the person covering in November.

Two habits keep it alive. Version the documents with a date, so nobody works from a saved copy. And fix the pack rather than the person — if a question was asked twice, the answer belongs in a document, not in a message.

FAQ

Should a co-host have their own login rather than mine?

Yes, always. A shared login makes every action unattributable, and it cannot be withdrawn without changing the password for everyone.

How much spending authority is right?

Enough to solve the problems that arrive on a Sunday, and not enough to commit you to anything structural. Set it in the currency you think in and review it yearly.

What if the arrangement ends?

Withdraw the access domain by domain, take the code back, and keep the pack. The next handover starts from a document instead of from a phone call.

The measure of a handover is not how well the first week went; it is how few questions reach you in the fourth. Write the five documents, grant the two domains the job actually needs, and keep Airbnb, Booking.com, Agoda and Trip.com on one calendar at localsbnb.com so that neither of you is guessing what the other changed.

---

This is operational guidance drawn from common practice, not a legal standard. Access arrangements, payment authority and data handling obligations differ by market and by contract; check the terms you agree with your co-host and the rules that apply where your units are.