A turnover can look organised on the calendar and still fail at the front door. The cleaner arrives, but the access code is wrong. The job is finished, but the linen delivery never came. Everyone has done their part, yet nobody can confirm the property is ready.
A useful operations playbook makes those handovers explicit. It tells the team what must be true before work starts, who makes decisions when something changes, and what evidence closes the job. Start with one property and refine the process before applying it across the portfolio.
Build a service brief for each property
Keep the property brief short enough to use on a phone. Include the address, parking, access instructions, bed configuration, supply location and cleaning scope. Separate permanent details from booking-specific notes so a late checkout does not become a permanent instruction.
Assign an owner to maintain the brief. When a lockbox moves or the linen arrangement changes, update the shared record before the next job. A correct brief in one place is more useful than several almost-correct versions scattered through messages.
- Confirmed checkout and next check-in, with the property's local time zone.
- Expected service duration and a buffer for review or rework.
- Named cleaner, backup contact and escalation owner.
- Current access details, linen stock and property-specific checklist.
- Required completion photos and the person who approves guest readiness.
Plan backwards from guest arrival
Set the latest acceptable finish before choosing a start time. Allow room for inspection, restocking and a small correction. Then subtract the expected cleaning duration. This gives you a latest viable start, which is more useful than treating every checkout as an identical slot.
Travel belongs in the schedule too. Two jobs that fit separately may not fit on the same cleaner's route. Check the whole day's commitments, including breaks and any linen collection, before confirming an assignment.
Resolve competing jobs before confirming the route
On a busy day, sort turnovers by their latest viable start rather than by the order in which bookings arrived. Flag jobs with an early check-in, a long service, difficult access or no nearby backup. Those are the jobs that can make an otherwise plausible schedule fail.
If two assignments overlap, compare the whole route: finish time at the first property, travel and parking, the next property's access window and the time needed to approve both handovers. Moving the second job to another cleaner may be safer than shortening either clean. Record who approved the new plan and notify both cleaners before they travel.
- Identify every property with a same-day guest arrival.
- Check each cleaner's route against the latest viable start for every job.
- Reserve review time at properties with unresolved issues or recent rework.
- Confirm the revised assignment and access details with the people affected.
Make every handover visible
Choose statuses that describe an observable event. A message sent to a cleaner is an offer, not a confirmed assignment. A submitted checklist is evidence of completion, not a decision that every reported issue has been resolved.
| Stage | Evidence needed | Accountable role |
|---|---|---|
| Confirmed | Cleaner has accepted the scope and time window | Coordinator |
| In progress | Cleaner has arrived and can access the property | Cleaner |
| Ready for review | Checklist, photos and exceptions submitted | Cleaner |
| Guest-ready | Required checks passed; blockers resolved | Property manager |
Agree on an exception path
Write down what happens when a cleaner declines, cannot gain entry or discovers damage. The instruction should identify the next action, the person responsible and the point at which the situation becomes urgent. A general request to keep everyone informed does not assign responsibility.
Give the coordinator authority to arrange cover within agreed limits. Keep guest communication with the property manager, so an operational delay does not produce conflicting promises. If the deadline is no longer realistic, communicate that fact early instead of leaving the job marked as on track.
Treat a reported issue according to its effect on arrival. A missing spare roll may be restocked during review; no clean linen or a failed lock needs immediate ownership. Record the issue, the person resolving it and the time of the next check. A job should not become guest-ready just because the cleaning checklist was submitted.
Review the next day before closing this one
Run a short check of tomorrow's turnovers: unaccepted jobs, overlapping assignments, missing supplies and narrow arrival windows. Resolve the dependencies while there is still time to act. Recheck when a booking changes; yesterday's confirmed schedule may no longer be feasible.
After service, review late starts, rework and time spent finding replacements. Look for patterns by property and route, not just by individual cleaner. Repeated overruns at one home may point to an unrealistic duration or an incomplete brief.
Once a week, compare the jobs that needed intervention with the assumptions in their briefs. Were the service times too short, were bookings updated late, or was the backup pool too small? Change one part of the process at a time and watch the next few comparable turnovers. That makes the playbook an operating routine rather than a document nobody revisits.
Put the playbook into practice
Trial the process on a small group of properties with different layouts. Ask both a regular cleaner and a backup to use the same brief. Record where either person needs clarification, then improve the brief or the handover rather than adding another message thread.
The first useful outcome is straightforward: at any point in the day, someone can identify who owns the next action and whether the property is on course to be ready. Once that is reliable, software can help carry the same process across more bookings.
