A hotel SOP guide. One manual, department by department.

The short answer. What a hotel SOP actually has to cover.

A hotel SOP is a written procedure for one task, built for a property where the same job gets handed between shifts, between departments and often between people who have never met. That is what separates a hotel SOP from the general method covered in our guide to how to create an SOP: a hotel runs twenty-four hours a day across several teams that depend on each other's work, so a procedure that only covers one person's task in isolation misses the point. If you are still deciding whether documentation is worth the time at all, why SOPs matter sets out the cost of skipping it. This guide assumes that case is made and gets into the hotel-specific version: which departments to document first, what each procedure has to include, and where the handoffs between them tend to break.

Kitchens are the exception worth naming up front. If the property has a food and beverage operation, those procedures need a HACCP-aligned structure of their own, covered in full in our food safety SOP guide, rather than being folded into the general operations manual described here. Front desk, housekeeping, maintenance and the handoffs between them are the focus of this guide, because that is where most hotel SOP manuals are asked to do the most work and where a generic template, written for no property in particular, tends to fall apart first.

How it works in practice. The departments to document first.

Three departments drive almost every guest-facing failure on a property, which is why they earn attention before anything else: front desk, housekeeping and maintenance. Each needs its own procedures, and each procedure needs to state what it hands to the next department, not just what the person doing the task should do themselves.

None of the three department procedures is complicated on its own. What usually goes wrong is the gap between them, which is why the fourth row in that table matters as much as the first three. A checkout that does not clearly trigger a housekeeping status change leaves a clean room marked dirty, or a dirty room marked clean, for longer than it should, and that single gap accounts for a disproportionate share of the complaints a front desk actually fields.

Cost pressure is part of why this discipline matters more now, not less. Actabl's 2025 Hotel Labor Costs and Trends Report, covering US hotels from January to September 2025, found housekeeping hours per occupied room fell 7.1 percent year on year while minutes per occupied room for room attendants improved 5.5 percent, and it put average labour cost per occupied room at 48.32 US dollars for the full year, up 12.8 percent from 42.82 US dollars in 2024. Properties are running housekeeping leaner than they were two years ago, which means a stayover clean and a checkout clean genuinely need their own documented sequence rather than one generic room-clean procedure, because there is less slack in the roster to absorb a badly sequenced shift. Typical vendor benchmarks put a standard room clean at 25 to 35 minutes and two to three rooms an hour, though this varies by room type and is a working guideline rather than a published industry standard.

Where a property is trying to work out which handoff is actually costing it the most guest complaints, mapping the flow of a booking from reservation through to checkout, the same discipline behind our process mapping work, usually finds the real bottleneck faster than documenting every department from scratch and hoping the gaps surface on their own.

Shift handover deserves its own procedure rather than a line inside each department's SOP, because it is where information about every other procedure actually crosses from one person to the next. A night-shift front desk agent needs to know which rooms are flagged for early checkout, which guests raised a complaint that evening, and which maintenance requests are still open, not buried in a diary nobody reads consistently but passed on in a fixed format at a fixed point in the shift. Properties that treat handover as a quick verbal update rather than a written one lose exactly the detail that matters most: the exception, not the routine.

What good looks like. A worked scenario on a growing property.

The scenario below is illustrative rather than a specific named engagement, but it reflects a pattern I see often enough with growing hospitality clients that it is worth setting out in full. Picture a 90-room property moving from one building to a two-building expansion, with a second front desk added for the new wing and the housekeeping team split across both. Before the expansion, status updates between front desk and housekeeping happened by walking down the corridor and asking. That stopped working the moment the two buildings were far enough apart that nobody could just look.

The judgement call worth naming is what not to fix first. The obvious move looks like buying a property management system add-on that automates the housekeeping status board immediately. I would usually hold off on that if the team has never run a shared digital board before and the expansion itself is already the bigger change the staff are absorbing. Adding new software and a new building layout in the same month tends to produce more errors than either change alone, because nobody has a stable baseline to compare a glitch against. The better sequence is to standardise the paper or whiteboard handoff format across both buildings first, same fields, same update cadence, same escalation rule when a room has been "dirty" for longer than the shift allows, and only move to a digital board once that format has run cleanly across a full occupancy cycle.

The second judgement call sits with maintenance. Housekeeping staff are usually the first to spot a fault, a dripping tap, a loose door handle, well before a guest reports it or an engineer's own inspection catches it. A hotel SOP manual that only documents maintenance as something engineering initiates misses that entire channel. Building a one-line housekeeping-to-maintenance request into the room-clean SOP itself, rather than as a separate process nobody remembers under pressure, catches faults while they are still a five-minute fix instead of a guest complaint.

Pitfalls to avoid. Where hotel SOPs fail in practice.

Most hotel SOP manuals fail quietly, months after they were written, once a system changes or a procedure gets copied to a new property without being checked against how that property actually runs. None of the five patterns below is dramatic on its own. Each one just removes a little more trust in the document until staff stop checking it at all, which is the point a manual stops being a procedure and becomes a file nobody opens.

• A checklist written where an SOP was needed. A checklist confirms a task happened. It does not tell staff what to do when the booking does not match the room type on file, or when a guest arrives four hours before check-in with nowhere to leave luggage. Properties that only have checklists have no written answer for the exception, which is exactly when staff need one most.
• No stated handoff. A front-desk checkout procedure that does not say what it triggers in housekeeping, and a housekeeping procedure that does not say what it hands back, leaves the connection between departments to memory and goodwill rather than to a written step either team can be held to.
• Written at head office, never checked on the floor. A procedure drafted centrally for a franchise or multi-property group and never walked through by the staff actually doing the work tends to assume a layout, a system, or a staffing level that does not match a specific property, and gets quietly ignored at the one point it matters.
• No version control after a system change. A new property management system, a renovated wing, or a new booking channel changes how a procedure should run, and an SOP that still describes the old system is worse than no SOP, because staff trust a document that is actively wrong.
• Maintenance treated as engineering-only. A maintenance SOP that only covers how engineering responds to a logged fault, and never covers how housekeeping or front desk should raise one in the first place, loses the earliest and cheapest point to catch a problem.

Once front desk, housekeeping and maintenance are each documented and the handoffs between them are written down rather than assumed, the next step is usually pulling everything into one structure a new hire can actually find their way around, which is exactly what our SOP manual template covers for any growing team.