The SOPs every hotel should have written down
Most hotels have more procedures written down than anyone can find, and fewer than they need. The gap is rarely the obvious ones — everybody has a fire plan. It is the procedures that only matter twice a year, which is exactly when nobody remembers where they are.
9 min read·
What makes an SOP useful rather than filed
A procedure earns its place if somebody can act on it under pressure without asking a question. That means four things, and a document missing any of them will be read once and then ignored.
- A threshold, not an adjective. “Respond promptly” is unenforceable; “attend within fifteen minutes” can be measured and argued about.
- A named role, not a department. “Escalate to the duty manager” tells a night porter what to do; “escalate to management” does not.
- The failure case. What to do when the first step does not work is the part people actually need at 02:00.
- A date and a version. A procedure with no date is one nobody can tell is stale.
Front office
- Reservation intake — what a booking record must contain before it counts as held.
- Identity and registration, including Form C submission for foreign nationals and the deadline for it.
- Arrival and departure timings, and what early arrival or late departure costs.
- Cancellation and no-show, leisure and corporate separately.
- Group and block bookings — release date, attrition, deposit.
- Overbooking and relocation: who gets moved, in what order, and what you pay for.
- Payment, deposits and card authorisation, including what you tell the guest a hold is.
- Complaint handling at the desk, with the waiver limit each role holds.
Housekeeping
- Departure room servicing, with the target turnaround and who signs it off.
- Occupied room servicing, including what staff do not touch.
- Privacy requests — and specifically, what happens after 24 hours of an unbroken do-not-disturb.
- Linen handling, including separation of anything stained with blood or bodily fluid.
- Lost and found: retention periods by item value, and what is never disposed of.
- Chemical handling, with the combinations that must never be used in the same room.
- Pest sighting reporting, and which rooms come out of sale on a confirmed bedbug report.
The privacy-request procedure is a welfare procedure wearing an operational hat. A sign that has not moved in a day means either a guest who wants to be left alone or a guest who cannot answer the door, and the only way to tell is to have written down when somebody goes in.
Food and beverage
- Buffet holding times and temperatures, and what happens to an item that falls out of range.
- Allergen declaration — who answers a guest's question, and the phrase staff may never use.
- Banquet event orders, including how a change inside seven days is handled.
- Banquet cancellation, as a sliding scale by notice period.
- Bar licensing hours, the legal drinking age in your state, and refusal of service.
- Food safety: delivery acceptance temperatures, batch sampling, and date labelling.
Engineering and safety
- Guest fault reporting, with response targets by severity and the rule that an unresolved fault takes the room out of sale.
- Hot water: the temperature range at the tap, and that a report at midnight is attended at midnight.
- Lift entrapment — above all, that nobody attempts a manual release without the contractor's certification.
- Hot work permits, including restoring any detection zone that was isolated.
- Fire alarm response, and that the fire service is called on every unconfirmed activation.
- Evacuation, with assembly points and an alternate for each.
- Extinguisher selection, particularly that water never goes near burning oil.
- Medical emergency, and the rule that staff administer no medication of any kind.
How to tell yours are out of date
- 1Ask three staff on different shifts the same operational question. If you get three answers, the document is not the source of truth — memory is.
- 2Look for a rate, a threshold or a supplier name that has changed since the document was written. One stale number makes a reader distrust the whole file.
- 3Check whether the escalation path names people who still work there.
- 4Count how long it takes you personally to find one specific clause. If it is more than a minute, nobody else is finding it at all.
That last test is the one that matters most, and it is not a documentation problem. The answer usually exists and is simply unreachable at the moment somebody needs it.