Running housekeeping from a phone: the mobile workflow.

Why the paper board breaks down

A paper or whiteboard housekeeping list works fine at ten rooms. Past thirty, and especially with same-day turnovers, early check-ins and split shifts, it starts failing in predictable ways: the board reflects this morning's state, not right now; a supervisor has to physically walk the floor to confirm a room is actually ready rather than just marked ready; and a maintenance issue spotted by an attendant either gets forgotten by the time they reach the office, or written on a sticky note that never reaches the right person.

The fix isn't more paper discipline, it's moving the board to somewhere every attendant already has access to in real time — their own phone — and making status updates instant rather than end-of-shift.

How priority ordering works

Every morning, Sabee generates a prioritised task list per attendant based on the day's actual arrivals and departures pulled straight from the tape chart, not a manually reordered list. The default priority logic runs in this order:

• Rooms with a same-day arrival and an early check-in request — these need to be ready before anything else, since a guest waiting in the lobby is the most visible failure mode housekeeping can produce.
• Rooms flagged VIP, regardless of arrival time, so a supervisor or senior attendant handles them personally rather than whoever's next in rotation.
• Standard same-day arrivals, ordered by stated or likely check-in time where that data exists.
• Stayover rooms — occupied rooms needing a routine service rather than a full turnover — filled in around the arrival-priority rooms.
• Rooms with no same-day activity, serviced last or skipped per your property's stayover-service policy.

A supervisor can manually reorder or reassign any task — the algorithm sets a sensible default, it doesn't lock the floor into a rigid sequence when local knowledge says otherwise (a returning guest known to arrive early, for instance, even without a formal early check-in request logged).

The task card

Each room shows up on an attendant's phone as a task card containing: room number and floor/zone, current status, arrival or stayover context, any notes left by a previous attendant or the front desk, and — critically — any flags (VIP, maintenance hold, do-not-disturb reported that morning). Tapping into a card shows a simple checklist relevant to that service type — a full turnover checklist differs from a stayover checklist, and both differ again from a pre-arrival deep-clean.

The dirty → clean → inspected lifecycle

Every room in Sabee moves through a small number of defined states, and the state is what the front desk actually reads from — not a phone call to housekeeping asking "is 214 ready yet."

• Dirty. Default state after checkout, or the ongoing state for a stayover room not yet serviced that day.
• In progress. An attendant has started the room — this state exists specifically so two attendants don't both start the same room, and so a supervisor glancing at the board can see real-time coverage rather than a static list.
• Clean. The attendant has finished and marks the room complete from their phone, timestamped automatically.
• Inspected. A supervisor (or, on smaller properties, a senior attendant) does a spot or full check and marks the room inspected — only at this point does Sabee typically release the room as ready-to-sell on the front-desk tape chart, depending on how strict you want that gate to be.

The inspected gate is optional per property — some smaller operations release rooms straight from "clean" to sellable and only inspect a sample — but for properties running VIPs or a quality-sensitive brand, requiring inspection before a room shows as ready is the single control that catches the small misses (a missed amenity restock, a forgotten do-not-disturb sign left on the door) before a guest does.

VIP flags

A VIP flag can be set manually by the front desk or automatically by a rule — a guest on their third-plus stay, a guest tagged in your CRM as a repeat corporate account, or a reservation with a note attached from a previous stay. Once flagged, the room surfaces at the top of the relevant attendant's list regardless of standard priority ordering, and the task card carries forward any preference notes (a specific pillow type, a known allergy, a request logged on a prior stay) so the same information doesn't need to be re-keyed by the front desk every visit.

VIP handling is also where housekeeping and guest CRM data genuinely need to talk to each other — a flag set once in the reservation should be visible on the housekeeping task card without anyone manually copying a note across systems, which is the whole point of running housekeeping inside the same platform as your reservations rather than a bolted-on separate app.

Maintenance tickets

When an attendant spots an issue — a dripping tap, a flickering light, a broken lock — they log a maintenance ticket directly from the task card in the moment they notice it, with an optional photo attached. This does three things a sticky note never does: it timestamps the report, it routes to whoever owns maintenance without needing the attendant to track them down in person, and it can automatically place a maintenance hold on the room so it isn't accidentally sold or marked ready until the ticket is resolved.

Deep-clean rotations

Daily turnovers and stayover services cover the surface; a deep clean — mattress rotation, curtain and upholstery attention, behind-furniture cleaning, descaling — needs to happen on a schedule independent of guest turnover, or it simply never happens on busy properties. Sabee supports scheduling deep cleans as recurring tasks per room (commonly every 30, 60 or 90 days depending on room type and usage), which show up on the relevant attendant's list on their due date regardless of whether the room has a guest checking in or out that day.

A practical rotation for a mid-size property: stayover rooms on a 60-day deep-clean cycle, higher-turnover budget or dorm-style rooms on 30 days, and lower-turnover suites on 90, adjusted based on actual usage patterns you observe over the first few months rather than a rule copied from another property with a different guest mix.

Reading the board as a supervisor

The value of moving this to mobile isn't just for attendants — it's the supervisor view that changes the most. Instead of walking the floor to confirm status, a supervisor sees every room's current state, which attendant is assigned, how long a room has been "in progress," and any open maintenance tickets, all from a single dashboard updated in real time. This is what makes same-day early check-ins manageable at scale: a supervisor can see at 10am exactly which arrival-priority rooms are behind pace and reassign an attendant before it becomes a lobby-side problem, rather than finding out from a guest at 2pm.

Getting a team to trust this system rather than falling back on shouting across a floor or a paper list under the desk takes about a week of consistent use — which is exactly why staff training on the mobile workflow is built into day 7 of our onboarding sequence, covered in the first week with Sabee guide.

Handling lost-and-found from the same workflow

A guest item found during a turnover is one of the easiest things to lose track of between the room and the front desk if it relies on an attendant remembering to mention it at the end of a shift. Logging a found item directly from the task card — a short description and, where useful, a photo — creates a timestamped record tied to the room and the reservation that was in it, which makes matching an item to a guest's later enquiry considerably faster than searching through a paper logbook or asking around the team from memory.

Shift handover without a meeting

Housekeeping teams working split or overlapping shifts often lose information at the handover point — an outgoing attendant knows a room needs a follow-up but the incoming one doesn't hear about it. Because every task card carries its full history (who serviced it, when, any notes or tickets logged against it), a supervisor coming on shift can review exactly where the floor stands without needing a verbal handover meeting, and an attendant picking up a partially serviced room mid-shift sees the same history rather than starting blind.

Measuring the workflow over time

Once the mobile workflow has been running for a month or two, it's worth reviewing a small set of numbers rather than assuming it's working because nobody has complained: average time from checkout to a room reaching "clean," the proportion of rooms requiring rework after inspection, and how many maintenance tickets are logged per week against which rooms. None of these numbers mean much in isolation, but tracked over a few months they show whether staffing levels match actual turnover volume, and they surface rooms that are quietly generating more maintenance load than the rest of your inventory — the kind of pattern that's nearly invisible on a paper board but obvious once it's logged consistently in one place.