Two Co-Hosts on One Calendar: the Handover Note

Two people sharing one calendar fail at the same point: the hour between one finishing and the other starting. A written handover is cheaper than a phone call.

Last updated: October 12, 2026

Two co-hosts on one calendar don't fail across the whole week. They fail in a single hour, the one where one host stops and the other starts. That's when a late checkout goes unmentioned, a fix goes unfinished, or a guest gets told two different things. A short note written in that hour is the cheapest tool the pair owns.

Key Takeaways

• The gap is the handover, not the calendar. Most failures happen in the hour between one host stopping and the other starting.
• The note carries state, not instructions. What changed today matters more than how the flat is usually run.
• Anything still open needs a name and a time. An unowned item is the one that reaches the guest first.
• The day it changes needs one owner. On any day the plan shifts, one host owns it, and the other knows it.
• Keep each co-host's access narrow. A shared login is convenient until it isn't, and by then the damage is done.

Where shared calendars break

A shared calendar looks like the whole system. It holds the bookings, the rates and the blocks, and both hosts can see it. So it's easy to believe the coordination is handled, when the calendar only ever shows what someone took the trouble to put in.

The break shows up in the handover hour. One host finishes a turn and drives away. The other opens the app two hours later, sees an empty evening, and assumes nothing is pending. But a guest had asked to leave a bag until four, and the first host meant to pass that on and forgot. The calendar was right. The handover wasn't there.

Phone calls don't fix it either. A call happens when the first host has time and the second host has attention, and those two moments rarely line up. Whatever was said is gone the moment the call ends, so the next question starts the same conversation over.

Two co-hosts also tend to share too much access. One login is the easy answer, and it means neither host knows who changed what. When a rate moves or a date gets blocked, there's no trail and no owner, only a shared account and two people who both think the other one did it.

The calendar hides the small things, too. A guest who asked for an early check-in, a cleaner running late, a neighbour's complaint about noise. None of those live on a booking record, and all of them matter to the next shift. That's the ground the note has to cover.

The common thread is that each host starts the day from a different picture. A written note is what puts them back on the same one.

What the note has to carry

The note isn't a manual. It's a snapshot of today, written in the handover hour and read at the start of the next shift. Four things earn a place in it.

Start with the day's facts. Arrivals and departures, any late checkout, any guest who said they'd arrive early, and any booking that came in while the first host was on. These are the items a guest will act on, so they belong at the top.

Then the state of the flat. What the cleaner found, what got fixed, and what's waiting on a part or a supplier. A host walking in cold can't tell a finished fix from a half-finished one, and that's exactly the kind of thing a note settles in a line.

Then anything still open, each with a name and a time. Not "needs looking at" but "the shower head drips, I've ordered the part, you'll see it Thursday". An open item without a name is the one that reaches the guest before either host does.

Then the money side, kept plain. What was paid out today, what's owed, and what needs a receipt. Neither co-host should have to ask the other where the last charge came from.

Keep it in the same place every day. A note written in an app one day and on paper the next is a note that gets lost twice a week. Pick one channel, keep it short, and let both hosts trust that it's there.

That's the whole note. A few lines, written in the handover hour, and the next host starts the shift already knowing the day.

Who owns the day it changes

Most days run themselves. A booking comes in, a turn happens, the calendar holds. The trouble starts on a day where the plan changes, and that's when two hosts need to agree on something in advance.

Name one owner for any day that changes. If a checkout moves to a late slot, if a guest asks for a different unit, if a rate needs to move for a local event, one host owns the call and the other stands back. Two people both trying to fix the same problem create a third one, usually in front of the guest.

The rule is worth writing down, because it only applies on the odd day. Agree that whoever is on the earlier shift owns any change that lands before noon, and whoever is on the later shift owns the rest. That single sentence stops the pause where both hosts wait for the other to move.

The owner isn't the more senior host. It's whoever is closer to the guest that day, or whoever has the app open. Seniority has nothing to do with it, and deciding by rank is how a five-minute question becomes a two-hour wait.

Handover works the same way at the edges. If one host is covering a trip, write the start and end dates and what moves back afterward. A role that quietly widens over a holiday is how a favour turns into an invoice, and how a boundary that was clear in March is gone by June.

One check keeps it honest. After any day that changed, ask whether the note caught it. If a change slipped through, the next note gets a line for it. That's the whole loop, and it runs on its own once the two hosts trust it.

Keeping access narrow

The last piece is the one hosts leave until something goes wrong. Two co-hosts on one account feel efficient, right up to the day a rate moves and nobody can say who moved it.

Give each host their own way in, and give it only as wide as the job needs. A co-host who handles guest messages doesn't need to change rates. A co-host who cleans and resets the flat doesn't need the payout details. Narrow access isn't distrust. It's what lets both hosts see who did what, and it keeps a mistake small when one happens.

The same applies to guest details. A handover note doesn't need a guest's full name, phone number or ID written into a group chat. Pass on what the next shift actually needs, and keep the rest where it belongs.

That's not about keeping a partner in the dark. It's about each host seeing only what their shift needs, so a mistake stays small and a change is easy to trace. Broad access feels helpful until the day it isn't.

This is where a product setting earns its keep. LOCALSBNB shows each connected channel's own source price and status in one calendar, so both hosts read the same picture without trading screenshots. It also keeps each store's login credentials on the device, masks guest names, phone numbers and ID details, and lets you grant access by area such as bookings, finance, availability or rates. Neither host gets more than their shift needs, and any change is easy to trace. You can see how that runs on your own listing at localsbnb.com.

FAQ

Do we both need our own login?

Yes, and for the same reason you'd want separate keys. A shared login hides who did what, which is fine until a change needs explaining. Separate access with the right scope per host makes the trail visible. It also means a departing host can hand back access without changing anyone's password.

What if the note is too long to write?

Then it's too long, full stop. Four short parts, written in the handover hour, is the target. If it's growing past that, you're writing a manual, and a manual doesn't get read in the hour that matters. A note that takes ten minutes is already longer than the shift it's meant to cover.

Does the note replace the calendar?

No, it sits next to it. The calendar holds the bookings and the rates. The note carries what the calendar can't, which is the state of things today and who's holding what. You need both. One tells you what's booked; the other tells you what's actually true right now.

The handover note isn't paperwork for its own sake. It's the thing that makes the overlap hour safe, and two co-hosts who keep it accurate stop paying for the same missed message twice. Keep it short, name the owner, keep the access narrow. If you'd like both co-hosts looking at the same calendar and the same day, localsbnb.com is a fair place to begin.

---

This is general guidance for hosts, not legal, tax or insurance advice. Local rules and platform terms change, so check the current requirements of your local authority and the terms each platform applies today.