A System for Perfecting Daily Turnover

Daily room turnover is the departure clean: the production line that takes a vacant, dirty room and turns it back into a vacant, clean, inspected, sellable one. It runs many times a day, on every occupied floor, and it touches more of your building than its name suggests — housekeeping plans and executes it, maintenance catches the issues it surfaces, and the front desk, reservations, and revenue management all live on its output. It is also nearly invisible. Nobody stands and watches a room get turned. You only notice the process at all when something visible breaks: a guest waiting in the lobby, the average turnover time creeping up, a fault that nobody ever logged.

That invisibility is the trap. The work can be done perfectly and the day can still fall apart, because turnover is less about the cleaning than about the handoffs around it — and those are the parts no SOP writes down. By the end of this post you'll have a copy-pasteable spec for the whole turn: every step, every owner, every handoff, plus two portable principles you can run by hand tomorrow. The problem is a room that's spotless upstairs and dirty in the system. The solution is knowing exactly which handoff let "done" and "ready" come apart.

When the Turn Goes Wrong

It's a heavy checkout Tuesday. James takes his board — fifteen departures across the twelfth floor — and starts where he always starts, at the near end of the corridor. Somewhere on the printed sheet, in a column he scanned past in the morning rush, room 1208 is flagged: early arrival, VIP, wanted by noon. He'll get to it; in floor order it's fourth in his run.

He turns the first three rooms well. By 1208 he's in rhythm. He strips the bed, and at the sink he notices the faucet won't stop dripping and the safe won't take a new code. He makes a note to tell Denise, his supervisor, and pencils "faucet" in the margin of his board. Then he cleans the room properly — every surface, fresh terry, bed to standard — and at 11:40 he marks 1208 clean and moves to the next door. The only record that the room is done is a clipboard on the twelfth floor.

Denise is two floors down, buried. Clean rooms are stacking up behind her waiting to be inspected, and the desk has no idea any of them exist yet — in the system, 1208 still reads vacant dirty. At 11:55 the VIP arrives early at the front desk. The agent checks: not ready. The guest is asked to wait, and waits.

Denise finally walks 1208 at 12:35, passes it, flips it ready. The room has been sellable for nearly an hour that nobody could see. The desk assigns it. And the penciled "faucet" never made it off the board — somewhere in the back-and-forth of inspection it simply evaporated. So the VIP rides up to a clean, correct, beautifully made room, and the faucet drips, and the safe won't lock.

At 2:45 the manager notices the average turnover time creeping up and starts asking why. At 4:00 the guest complaint lands at the desk. The work had been done since 11:40.

The Same Turn, Done Right

Same Tuesday, same Fifteen Rooms, Same 1208.

This time the priority is the first thing James sees, so 1208 is the first room he turns. At the sink he catches the same dripping faucet — a couple of taps, a photo, a severity — and it's out of his hands. He finishes the room and marks it clean, and the moment he does, it's no longer a secret on a clipboard: the desk sees it move. Maintenance has already picked up the faucet; the room steps out for the ten minutes that takes and steps back in. Denise inspects it, it passes, and it reads ready downstairs before the guest is anywhere near the lobby. The signal that closes the loop also asks the desk to confirm the room is theirs to sell — a last glance, in case anything looks off. And for the newer attendants on the floor, the same handheld walks them through the clean step by step, a worked example in their hand, so the property standard travels with the device instead of living in one supervisor's head.

Then nothing happens. The VIP arrives, checks in, rides up to a quiet, correct room. No one had to ask twice.

How?

The Broken Run, as a Picture

Start with the broken run as a picture. Watch where the arrows go dotted.

1. Front desk / PMS → housekeeping. Checkout posts the room as vacant dirty, and the day's room assignments — priority flags and all — go to the housekeeping board.
2. Supervisor → attendant. The board is split into sections and handed out on paper. The priority flag is in there somewhere.
3. Attendant → maintenance. The faucet gets penciled in a margin and mentioned in passing. Nothing structured leaves the floor.
4. Attendant → supervisor. The room is marked clean on the clipboard and joins the inspection queue.
5. Supervisor → front desk / PMS. Eventually the room is inspected and flipped — but the "ready" signal crawls back to the desk by word of mouth and manual entry, long after the work was finished.

Three things broke in that run, and not one of them was the cleaning.

The priority never surfaced. The flag on 1208 was on the board, but the board doesn't do anything with it. With nothing to lift the priority room to the top of the run, it sits fourth, and "ready by noon" gets decided by where the room happens to fall in a corridor.

Nobody owned the return leg. Look at arrow 5. The work finished at 11:40; the desk learned about it after 12:35. That gap — physically ready, invisible in the system — is the single most expensive thing in this whole process, and it costs nothing in labor to close. You can't manage a clock nobody is watching, so the room was sellable for an hour that nobody could sell.

The work order had no home. Arrow 3 never really happened. A handoff that depends on someone remembering to mention something, on a busy floor, isn't a handoff — it's a hope. The fault the attendant did catch never reached the person who could fix it, so the guest caught it instead.

The same run, with the gaps closed

Here is the same turn with those gaps closed:

1. Front desk / PMS → Lush. Checkout posts the room into the system — vacant dirty, with its priority flag.
2. Supervisor → Lush. The housekeeper still builds the board: assigning attendants and sections, setting the priority order — now inside the system instead of on a printout.
3. Lush → attendant. The priority room is sequenced to the top of the run on the handheld — and for newer attendants, the same handheld walks them through the clean with a worked example, so the property standard travels with the device.
4. Attendant → Lush → maintenance. The faucet is captured right at the sink — room, symptom, severity, photo — and routed straight to maintenance, who acknowledge it. The handoff can't be forgotten, because nobody had to remember it.
5. Attendant → Lush. The attendant marks the room clean; the status writes itself the instant the tap lands.
6. Lush ↔ supervisor. The room surfaces for inspection; on a pass, its status flips to vacant ready.
7. Lush → front desk / PMS Ready status and a sellable-inventory update broadcast in real time, the priority-ready trigger fires for the desk.

Put the two pictures side by side and the difference is almost embarrassing. Same rooms, same people, same work — the cleaning didn't change at all. What changed is that the desk got told the moment the room was ready instead of an hour later, the priority room got lifted to the front of the line, and the boring, easy-to-drop relay work — capturing the fault, routing it, flipping the status, confirming it back — was handled by something that doesn't get busy and doesn't forget. The work simply stopped having places to fall through. Nothing heroic happened. The gaps just closed.

The Whole Turn, Yours to Keep

You may not always be able to wave a magic wand and put a system under all of this — and we'd rather hand you something useful than a sales pitch. So here is the whole turn as a spec you can lift straight into your SOPs and run by hand, no software required. Read it as See, Plan, Act: see the room and what it carries in, plan the handoff out, act on it — and at every row, know the one number that tells you whether that step worked.

Step	Owner	Input	Output	Success metric	Direction
Plan the day & own the board	Housekeeping supervisor	Room assignment: room, status, checkout time, priority flag, prep flags	Room assignment (adds attendant, section)	Room coverage accuracy (every room accounted for), Total Cleaning Minutes / Total Staff Minutes	↑, →
Dispatch the board	Housekeeping supervisor	Room assignment (adds attendant, section)	Room assignment (delivered to room attendant)	Board Distribution Time	↓
Travel to the room	Room attendant	Room assignment	Room assignment (attendant on site)	Dispatch time (assignment to room)	↓
Clean the room	Room attendant	Room assignment	Room assignment (status → vacant clean, awaiting inspection)	Room cleaning time, Cleanliness Score	↓, ↑
Assess & log faults	Room attendant	Room assignment	Maintenence Issue: room, location, symptom, severity, photo → maintenance	Guest Issues Reported	↓
Status update	Room attendant / system	Serviced room	Room status: clean/ready, timestamp	Room status latency	↓ lower better
Travel to the room to inspect	Housekeeping supervisor	Room assignment (awaiting inspection)	Room assignment (supervisor on site)	Inspection dispatch time (assignment to room)	↓
Inspect the room	Housekeeping supervisor	Room assignment (awaiting inspection)	Room assignment (adds inspection result)	Inspection time, Cleanliness Score	↓, ↑
Pass or send back	Housekeeping supervisor	Room assignment (inspection result)	Room assignment (status → vacant ready) — or returned to attendant	First-try inspection pass rate	↑
Status update	Housekeeping supervisor / system	Room assignment (vacant ready)	Inventory update: room, sellable, ready time (adds priority-ready trigger) → front desk	Room turnover time (checkout → vacant ready)	↓

Room turnover time is the headline — the clock that runs across the timed steps above (attendant dispatch + cleaning + inspection dispatch + inspection), pausing for any maintenance hold, which belongs to its own process. Targets are left out on purpose — set your own; the arrow already tells you which way good runs.

Two ideas worth stealing

Before you go, two ideas are worth pulling out of this one process, because they hold true for every process in your hotel.

Pick one number that matters. Every process should have a single number that tells you if it worked. For the turn, it's room turnover time — how long a room takes to go from checkout to vacant ready, on average (the maintenance clock runs its own process, so it doesn't count against you here). That's the score. Cleaning time, the two dispatch times, inspection time, pass rate, coverage: those are the clues for why the score moved, not the score itself. Chase a dozen numbers at once and you're chasing none of them. Pick the one. Let the rest explain it.

Watch the handoffs, not the departments. Work almost never fails inside a team. It fails in the gap between two of them. Look back at the bad run: the cleaning was perfect — the day broke in the space between "I'm done" and "the desk knows." So check every handoff with three plain questions: who owns it, what gets passed, and how would you know if it dropped?

The Full Playbook

You've felt the morning where the work was done and the day still slipped, you've seen how quiet it gets when the seams hold, and you've got the full spec for the turn — free, above, yours to keep.

Every process in this series is free to read, right here on the blog; none of the frameworks are locked away. If you'd rather not collect them one post at a time, we've assembled the whole operation end to end — check-in through the stay to checkout and everything after, every process in one guide. Drop a name and an email and it's yours.

And if running this many connected processes by hand is starting to feel like the real problem — we can run all of it for you.