Skip to content
allanninal.dev/build
Collaborate

Part 2 of 7 · Housekeeping dispatcher series ~5 min read

How rooms get prioritised

The instinct is to prioritise by how much cleaning a room needs, and the right answer is to prioritise by when somebody needs it, which produces a substantially different list.

Key takeaways

  • Urgency comes from arrival time, not from how dirty the room is.
  • A checkout with no arrival today can wait until tomorrow.
  • Stayovers are shorter work and slot around the checkouts.
  • Do-not-disturb removes a room from dispatch entirely, with no override.
  • Rooms with a specific request attached need their own flag.

What makes a room urgent

How a room's cleaning priority is determinedA vertical chain of five steps entered by a box labelled A room needs attention, whether checkout or stayover. Step one asks whether do not disturb is set, checked first always; if so it exits to Removed from dispatch, re-offered later. Step two asks whether a guest is arriving today and at what time; if not it exits to Low priority, do it when convenient. Step three asks whether the arrival is before three o'clock, an early arrival; if not it exits to Standard, ready by check-in. Step four notes any special request such as a cot, accessibility or an allergy. Step five produces a priority with a time rather than a rank. A note says the first gate runs before everything else and its exit has no path back in.AWS ACCOUNTA room needs attentioncheckout or stayoverDo not disturb?checked first, alwaysRemoved from dispatchre-offered lateryesArriving guest today?and at what timeLow prioritydo it when convenientnoBefore 15:00?early arrivalStandardready by check-innoAny special request?cot, accessibility, allergyPriority, with a timenot a rankThe first gate runs before everything else, and its exit has no path back in.
Fig 1. How a room’s urgency is determined. Do-not-disturb is checked before anything else so it can never be traded against a priority.
  • Compute
  • App integration
  • Machine learning
  • Security & identity
  • Management
  • Analytics
  • Front-end & mobile

A time, not a rank

Ranking rooms one to thirty-four produces a list that is meaningless the moment anything changes. A required-by time is stable, survives reallocation, and lets a housekeeper make a sensible local decision: this room is needed by one o’clock and it is eleven, so there is time to do the two next door first.

It also degrades gracefully when the day goes wrong. A list of times makes it obvious which rooms are now at risk; a rank ordering does not.

The room nobody is waiting for

A checkout with no arrival for three days is genuinely not urgent, and treating it as urgent because it is dirty consumes the morning that the six early arrivals needed.

Those rooms are still on the list, at low priority, and they act as the buffer: when a day runs short they are the ones that move to tomorrow, deliberately and visibly, rather than something being dropped at random.

Stayovers are different work

Median measured cleaning times for four kinds of room workA bar chart with four bars showing median measured minutes. Checkout, standard: thirty-two. Checkout, family: forty-eight. Stayover: fourteen. Refresh only: seven. A note says these are measured rather than assumed, and most rotas are built on one figure for every room.020406080~32Checkout, standard~48Checkout, family~14Stayover~7Refresh onlyMeasured minutes, medianMeasured, not assumed. Most rotas are built on one figure for every room.
Fig 2. Four kinds of room work with their measured durations. Planning a day on a single average figure produces a list that is impossible on some days and light on others.

The gap between fourteen and forty-eight minutes is the reason a day allocated by room count is unfair and frequently impossible. Eighteen checkouts is a very different day from eighteen stayovers, and a rota built on rooms per person cannot express that.

Measuring is straightforward: the housekeeper marks start and finish, which they are already doing to report a room as cleaned. A few weeks of that produces medians per room type and eventually per room.

Do not disturb

Why there is no override

  • The sign means what it says. Somebody is asleep, unwell, working, or wants privacy.
  • An override would be used. Not maliciously, but on a busy day with a supervisor under pressure, which is exactly when it should not be.
  • The room is deferred, re-offered at a stated time, and deferred again if still set.
  • After a policy threshold — often a stated number of hours, or a welfare check — a person makes contact.
  • That is a human process, written down by the hotel, and the system’s job is to flag it and record what happened.
  • Recording matters: a room not entered for two days is a welfare question, and the system should be able to say so.

The last line is the one worth building for. A room with do-not-disturb set continuously is occasionally a serious situation, and the count of hours since anybody has been in the room is a number the system can produce and a person can act on.

Special requests

A cot to be set up, an accessible room to be checked, a guest with an allergy who has asked for a particular cleaning product. These are not priority in the timing sense; they are additional work that has to reach the right room.

They travel with the room rather than with the priority, and they should appear on the housekeeper’s list for that room rather than in a separate briefing that may not reach the person who actually cleans it.

Next: the walking.

All posts