Housekeeping SOPs: Turning a Binder Into Answerable Items

“Bathroom cleaned and checked to standard.”

That line is perfectly good in a binder and completely unanswerable on a phone. A housekeeping SOP written for paper is written to be agreed with — read at induction, signed, filed. An SOP that runs on a staff phone has to be answered, item by item, by a person standing in a villa with wet hands and eleven minutes. Those are different documents, and most properties own only the first one.

The gap between them is where re-dos come from. Not from carelessness: from a sentence that four people can satisfy four different ways while each believing they met the standard.

Converting one to the other is less work than it sounds, and it is not a rewrite of the binder. It is a rewrite of the ten or fifteen lines that generate arguments.

The test: what would the answer look like?

Read any line of your SOP and ask what a completed version of it looks like as data. Not as a feeling — as a mark on a record.

“Bathroom cleaned and checked to standard” has no answer shape at all. It is four or five separate actions wearing one sentence, and the only way to answer it is a single tick that means “I did the bathroom”, which is exactly what it meant before anyone wrote it down.

“Shower screen free of watermarks” has an answer: yes or no.

“Six bottles of water in the villa” has an answer: a number.

A line that cannot be answered in one gesture is not one item. It is several, and it should be split until each piece has a single answer.

Five answers, and picking the right one

In the turnover checklists we ship, every item carries exactly one of five answer types, and the phone shows a different control for each. The choice is not cosmetic — it determines what ends up on the permanent record of that job.

The SOP line	Becomes	What lands on the record
”Bathroom cleaned and checked to standard”	four separate done-items	four ticks, each timed
”Shower screen free of watermarks”	pass / fail	a pass, or a fail
”Bed made to standard”	photo	an image attached to the job
”Six bottles of water in the villa”	number, unit bottles, range 6–6	a count that flags red outside its range
”Anything the next guest will notice”	free text	a sentence attached to the job

The last row earns its place more often than people expect. A single open text item at the end of a turnover is where the useful things go — the thing that is not broken enough for a work order and not on anybody’s list.

The pass/fail row is the one to spend thought on. Pass/fail is not a stricter version of a tick; it is a different claim. A tick says I did this. A pass/fail says I looked at this and here is the state it was in, which is the only kind of item that can produce evidence when it comes back negative — and evidence is the cheapest of the three things that should ever trigger an inspection, because it costs no walking to generate.

Put the threshold in a field, never in the sentence

This is the single rule I would keep if I had to throw the rest away.

“Check there are six bottles of water” is a sentence with a number inside it. “Bottles of water”, answered as a number with a range of six to six, is a fact the system can evaluate — it can flag red on five and it can flag red on nine, which is the count that means the last guest was charged for something they did not drink.

There is a second reason, and on a multilingual team it is the more important one: the sentence is the part of an item that gets translated. A quantity living inside translated prose is a quantity that can drift in one language and not the others. Keep it in a field of its own and it is untouched in all of them.

The corollary is a small authoring discipline: any line whose meaning depends on a quantity should be a number item, not a tick with the quantity written into the label. Fridge temperature. Pool towels. Bottled water. Amenity sets. Each is a reading with a range, and each of them turns somebody’s judgment into a fact.

Write items that can be answered on a bad night

A checklist worth having gates the finish: on our boards a job with required items unanswered cannot be closed, and the phone says so. That is the right design, and it has a consequence.

An item that cannot be answered at eleven at night, in the rain, with the storeroom locked, will be answered anyway. The gate does not produce truth; it produces an answer. If the only available answer is a tick, the tick is what you get, and now the record contains something worse than a blank — it contains a confident falsehood.

So the gate is only as good as the items. Two practical rules follow. Write each item so that a truthful negative answer exists and costs nothing to give: pass/fail, so “no” is as easy to record as “yes”. And where an item genuinely cannot be answered on some nights — a check that depends on daylight, or on a department that has gone home — mark it as not required, so the incomplete answer stays available and the gate keeps its meaning.

Give the villa a line for “not free yet”

The most common thing missing from a written SOP is the guest.

An attendant arrives for a service visit and the guest is still inside. The binder has no line for this, so the decision falls to whoever is standing there, and the two available options are both bad: leave the job open indefinitely, or close it as done.

There should be a third answer, and the SOP should name it. Ours reads “Guest inside — can’t clean”.

The wording carries more than it looks. It is an answer, so the attendant can record it and move on with her round. It is specific, so it does not collapse into a general “couldn’t do it” that tells the next reader nothing. And it describes the villa, so nobody looking at the record later has to work out whether the delay belonged to the guest or to the person holding the cart. What a system then does with that answer — how the villa is painted, what happens to the deadline, who picks the job up when the guest finally leaves — is worth interrogating any vendor about closely. It is also a different question from this one.

The SOP’s question comes first and is narrower: name the situation, and say what to record when it happens. Without that line, an operational decision has been delegated to the least supported person on the property, and the answer she picks will be the one that closes the job.

A fail should leave something behind

A pass/fail item that comes back negative and does nothing is a note in a file.

On the items set up for it, a failed check writes a maintenance job in the same moment the answer is recorded — before the housekeeper has left the villa, with her photo already on it.

Which items deserve that is a genuine editorial decision, not a default to accept. Make everything raise a job and the maintenance board is noise by Thursday; make nothing raise one and the housekeeper is back to telling somebody in the corridor. The same routing question shows up on the guest side, where a message can become a work order in one action — that story is told separately.

Editing an item is an event, and someone owns it

Change the wording of an item and the template’s version moves. A change to the standard lands in every language at one moment instead of drifting outward through briefings over a fortnight.

Each item is stored once and read in fourteen of the staff app’s nineteen languages — which is a separate argument, made at length in multilingual housekeeping checklists.

The organizational consequence is the one to plan for: the person who edits items is now the person who owns the standard. At a lot of properties those are two different people today, one of whom holds the binder and one of whom holds the phone. Deciding which of them it becomes is a five-minute conversation that is much easier before rollout than after.

Settle ownership before you convert anything

One sequencing mistake is expensive and easy to make.

Converting the SOP moves the standard. Once items live in a system, the standard changes whenever somebody edits an item, which means it belongs to whoever holds that screen. At a lot of properties the binder belongs to an executive housekeeper and the system belongs to whoever configured it, and if nobody notices the handover happening, the property spends a season running two standards that agree only by coincidence — the written one in the induction pack and the real one on the phones.

So the order is: settle who owns items, then convert. That costs one conversation and it is the cheapest part of the exercise.

After that, convert three lines. Not the binder — three lines, the ones that come up in every handover, which you can name without going to look. For each, write down what a completed answer looks like as a mark on a record, split until every piece has exactly one answer, take the quantity out of the sentence, and decide whether a bad answer should leave work behind it. The rest of the SOP stays where it is, doing what it was written for.

If a second pair of eyes on the first few items would help, a walkthrough is the right format. The ownership question is the one you will have to settle in your own building, and it is worth settling before anybody opens a template.