Co-Host and VA Runbook for STR Turnovers (RACI + Handoffs)
In this article: how to split turnover work between host, co-host, and virtual assistant without losing the thread — RACI-style clarity and audit-friendly habits.
· Updated 2026-10-03
Key takeaways
- Ambiguous ownership creates duplicate work or dangerous gaps — especially around booking changes.
- Write down who may message guests vs who only updates internal systems.
- A shared system of record beats “everyone is in the group chat.”
In this article: how to split turnover work between host, co-host, and virtual assistant without losing the thread — RACI-style clarity and audit-friendly habits.
The useful question is not only whether co-host and va runbook for str turnovers sounds right in theory. It is whether your version still works when the calendar shifts, the cleaner is deciding, or a guest is already expecting an answer.
That is where clearer operating rules help most: they turn a one-time save into something your team can repeat without waiting for the same person to translate the situation again.
In this article
- A lightweight RACI you can paste into Notion or Google Docs
- Turnover-specific responsibilities (bookings, assignments, guest comms, payouts)
- Handoff rules that prevent silent failures
- Where tooling fits without replacing judgment
Definitions
- Responsible: does the work
- Accountable: ultimately owns the outcome (ideally one person per decision)
- Consulted: should be looped in before big changes
- Informed: should be notified after changes
Roles diagram (visual)
Turnover spine — what must stay coherent
Across most portfolios, these objects must stay aligned:
- Booking truth (dates, checkout time)
- Job / turnover record (what needs to happen, when)
- Assignee (who is confirmed)
- Guest-facing instructions (access, checkout expectations)
- Money movement rules (if payouts or guest-paid services are involved)
If any of these diverge across people, you get the classic failure: the guest thinks checkout is 11, the cleaner planned for 10, and the co-host is on a flight.
RACI template (copy/paste starter)
Adjust names to your team. The goal is single accountability per critical decision.
Booking changes and calendar hygiene
| Task | Host | Co-host | VA |
|---|---|---|---|
| Detect platform booking change | C | R/A | I |
| Update internal system of record | I | R/A | R |
| Message guest (policy/tone) | A | R | R (templated only) |
| Notify assigned cleaner / reconfirm | I | R/A | R |
Staffing and assignments
| Task | Host | Co-host | VA |
|---|---|---|---|
| Maintain primary/backup relationships | A | R | I |
| Monitor pending offers / escalations | I | R/A | R |
| Approve marketplace or exception staffing | A | R | I |
Guest experience (non-turnover)
| Task | Host | Co-host | VA |
|---|---|---|---|
| Write/update stay portal content | A | R | R |
| Emergency guest recovery | A | R | I |
Your matrix will differ — the point is to remove guessing.
Handoff rules that prevent disasters
Rule 1 — “Changed time” is an event, not a footnote
When checkout moves, your runbook should require:
- internal record updated
- assigned cleaner notified
- reconfirmation if someone was already locked in
Read: Handling booking changes.
Rule 2 — Guest messaging is a brand surface
If a VA messages guests:
- use approved templates
- define escalation triggers (access failure, damage, safety)
- log what was sent (even a simple log table helps)
Rule 3 — Money needs explicit authority
Payout approvals, refunds, and guest-paid add-ons should have a named approver. “Everyone kind of can” becomes disputes.
What a VA should not do without training
- improvising checkout policy in guest threads
- changing access codes without a documented process
- promising compensation without authority
Tooling: shared truth beats chat volume
Group chats are fine for alerts. They are weak as a database.
If your team is growing, prioritize:
- a canonical place for job status
- visibility into who is assigned
- auditability when booking truth changes
Read Next
How Oordio Fits
Oordio keeps booking times, guest requests, cleaner assignment, and payout status in one operating record so the rules from this guide are easier to repeat without extra message chasing.