By a working hotelier · Includes a complete free SOP at the end
Most hotel SOPs die in a binder. They were written once for a quality audit, they describe a hotel that doesn't quite exist, and the night shift has never read them. The difference between that binder and an SOP a receptionist actually opens at 23:00 is not writing talent — it's five structural decisions.
A check-in SOP that describes a calm lobby is decoration. The SOP earns its place when three guests arrive at once, one reservation is missing, and the card machine is offline. Start every procedure by asking: what goes wrong here, and what does the least-experienced person on shift need at that exact moment? That's why our no-show procedure covers the guest who shows up the next morning claiming a late check-in — because they do.
"Respond promptly" is not an instruction. "Call back within 10 minutes; if unresolved after 30, escalate to the duty manager" is. Every threshold in an SOP should be a number someone can be right or wrong against: float amounts, minutes per room, OTA no-show reporting windows (usually 24–48 hours — miss it and you pay commission on a stay that never happened), compensation ceilings a receptionist may offer without asking.
The full SOP is for training week. What lives at the desk is a one-page quick reference: numbered steps, thresholds, phone numbers, nothing else. If a procedure can't be compressed to one page, it's two procedures. Every SOP we sell ships with its one-pager for exactly this reason.
"Maria checks the float" fails the day Maria leaves. Every step belongs to a role — receptionist, shift leader, duty manager, night auditor. In a small property one person holds three roles before breakfast; the SOP still names the role, so the procedure survives every staffing change.
Date every revision, keep one owner per document, and before publishing, have someone read it aloud while another person mimes the steps. Anything that makes the room laugh gets rewritten. This ten-minute ritual catches more nonsense than any review cycle.
The excerpt on our home page shows the no-show handling SOP built with this method — purpose, timed procedure, OTA reporting windows, KPIs, and the morning-after script. Use its structure for your own documents, or skip the writing entirely:
27 SOPs, checklists and script libraries, already written this way.
Front office, housekeeping, and guest communication — editable, with one-page references.