An Airbnb co-host handover checklist should let another person handle the next reservation without guessing who owns each task. It needs the property's current facts, access arrangements, open issues, and a clear route for decisions.
A guest welcome book is part of that handover, but it cannot replace the private operating notes. Guests need instructions for their stay. A co-host also needs suppliers, responsibilities, outstanding work, and the limits of their authority.
Assign each recurring task
| Task | Owner | Backup | When to escalate |
|---|---|---|---|
| Guest messages | [person] | [person] | [coverage or decision limit] |
| Turnover confirmation | [person] | [person] | [readiness risk] |
| Access failure | [person] | [local contact] | [backup needed] |
| Maintenance | [person] | [supplier] | [approval threshold] |
| Guide updates | [person] | [person] | [changed guest information] |
Replace “we handle it” with a named owner. Confirm that every backup has agreed to the role and can respond during the relevant hours. A number in a spreadsheet is not a coverage arrangement.
Prepare the property facts
- The exact guest entrance and walking route from parking.
- The normal check-in and checkout times.
- The current supply locations and advertised amenities.
- Equipment notes that guests regularly ask about.
- The cleaning contact and confirmation process.
- Verified local help contacts, with their actual availability.
- The latest guest guide and its revision date.
Use the same source of truth for facts that appear in the listing, messages, and guide. A co-host should not discover three different checkout times across three documents.
Hand over access securely
Use the platform's supported co-host access and permission controls as appropriate, and verify the current settings in the account. Do not share an owner's password as a substitute for an individual access arrangement.
Keep lock administration, permanent codes, and private supplier details separate from guest-facing material. Test the authorised workflow together: can the co-host find a reservation, identify its access arrangement, and contact the agreed local backup?
Include the next reservation, not just the normal routine
Next-stay handover
Reservation reference: [internal reference].
Arrival and departure: [dates and confirmed times].
Approved exceptions: [early arrival, late departure, or other agreement].
Readiness owner: [person and confirmation time].
Open issues affecting the stay: [facts and next action].
Guest communication still due: [message and owner].
Backup if the plan fails: [agreed contact/process].
Share only the guest information needed for the job. Keep booking details inside the appropriate private systems rather than copying them into a publicly shared guide.
Record decisions the co-host can make
Agree who can approve a changed arrival time, arrange a contractor, replace an essential item, or discuss a proposed remedy. Separate routine spending from decisions needing the owner's approval. Platform permissions and your operating agreement should support the responsibilities you assign.
If someone cannot authorise the next step, give them an escalation contact and realistic response window. Avoid leaving a guest waiting while several people assume another person is deciding.
Run a scenario before the first solo shift
Try an access failure, a missing essential, and an appliance fault. The co-host should be able to locate the correct instructions and identify the responsible person. Use our issue-response guide for guest updates and the maintenance checklist for tracking work.
Update both sides of the handover
When an appliance or supply location changes, update the private operations notes and the guest instructions. Record who made the change and check the printed copy too.
Give the co-host a current guest-facing resource. The Check-in Guide brings verified home instructions and local information into a downloadable welcome book.