Why we threw out our spreadsheets in six weeks.
This operator didn't have a software problem. They had a truth problem: at any given moment, nobody knew which rooms were actually clean. Here are the six weeks that followed.
The spreadsheet was never the problem
Eighty-four rooms, three buildings, a shared Excel whose "Cleaning, day X" tab was copied each morning into a WhatsApp group. The spreadsheet wasn't the culprit: it did exactly what it was asked to. The problem was that the truth lived in the head of the head housekeeper, and nowhere else.
On her day off, the information left with her. A room marked "OK" at 11 a.m. could be re-soiled by a late checkout with nobody the wiser until the next check-in. The cost wasn't in the sheet — it was in the fifteen daily phone calls spent rebuilding a state the system should have held on its own.
Weeks 1–2 — map what's real, not what's ideal
We automated nothing for the first fortnight. We imported the rooms, the floors, the actual skills of each agent (who does linen, who handles a minibar, who covers which building) and let the team log their interventions by hand, from their phones.
The goal was modest: make a room's state stop being a rumour. The moment an intervention closed on mobile, the rack updated for everyone at once. No syncing, no re-keying. The head housekeeper could take her day off again without taking the whole operation with her.
Weeks 3–4 — assignment stops being manual
Once skills and floors were known to the system, the morning assignment became a derivation, not a decision. Hostik splits cleanings by skill, by floor and by load: the agent already covering the 2nd floor no longer crosses the building for one stray room, and nobody ends up with four simultaneous checkouts while a colleague has zero.
It wasn't the algorithm that saved time — it was the disappearance of the fifteen-minute meeting where rooms were divided out loud. The plan was ready before the first agent arrived.
Weeks 5–6 — proof replaces trust
The last lock was the dispute: a guest who swears the room was dirty, a platform asking for proof, and nothing to show. We turned on signed photo proof. Every end-of-intervention photo is sealed (SHA-256 hash, Ed25519 signature, timestamp) at capture — not editable after the fact.
The effect wasn't legal first, it was cultural. When an agent knows their work is recorded verifiably, remote inspection becomes possible and corrections happen on facts, not blame. The supervisor stopped physically re-checking every room.
What changed, in numbers
Average turnover: 54 → 42 minutes. The gain doesn't come from faster agents; it comes from dead time removed — waiting for the assignment, the second inspection pass, the phone call to find out whether 214 is ready.
The lesson we keep: don't migrate a spreadsheet, replace what it never knew how to do. A spreadsheet holds a list. It holds neither a shared real-time state, nor an assignment, nor a proof. That exact trio was costing the twelve minutes.