Hotel SOPs Your Team Will Follow: Write, Roll Out, Maintain

A hotel SOP that lives in a binder is not a procedure. Nobody opens it on a busy shift, so everyone does the job the way the last person showed them. The fix is smaller documents, written with the people who do the work, taught on the floor and reviewed on a calendar. This guide covers which ones to write first, how to format them, a sample, and how to keep them current.

Pick the first ten by cost of failure, not by department

Writing procedures for every task is how binders get built and never used. Start with the tasks where a miss costs the most, and sort them into three groups.

1. Procedures that protect people and are expected of you. These are the ones an inspector, insurer or plaintiff's lawyer will ask for. Examples:

• Water safety. CDC guidance for hotel owners and managers says water management programs are now an industry standard for most hotels and tourist accommodations in the United States. Your engineer's flushing, temperature and monitoring routines belong in writing. They should include the protective equipment to wear and a pointer to the manufacturer's instructions and the safety data sheet for any disinfectant used.
• Chemicals. Under OSHA's hazard communication rule, employers must train employees on hazardous chemicals in their work area at the time of initial assignment, and whenever a new chemical hazard is introduced (see 29 CFR 1910.1200). Your housekeeping chemical procedure is the document that training points to.
• Equipment isolation. If your engineers service equipment that can start unexpectedly, OSHA's lockout/tagout standard requires an inspection of the energy control procedure at least annually, performed by an authorized employee other than the one using it (29 CFR 1910.147). Check which federal, state and local rules apply to your property.

2. Procedures where a miss becomes a guest complaint. Think no cooling in an occupied room, a room not ready at arrival, a noise complaint at 1 a.m., a guest who reports a missing item, or a request that has sat for an hour. If your last ten bad reviews cluster around two or three of these, those are your first SOPs. Start where errors or complaints cluster, not with the easiest procedure.

3. Procedures at handoffs. Most failures happen when work changes hands: shift change, a key issued to a contractor, a room released from maintenance back to housekeeping. These are short and have a high payoff.

Existing Insights pieces cover several of these in detail: the cleaning sequence, lost and found, escalation timing and the preventive maintenance checklist. Don't duplicate them. Link to them from your SOP.

Write it on one page, from the floor up

Each SOP should fit on one screen of a phone or one side of a sheet. If it doesn't, split it. Use the same layout every time so staff know where to look:

• Title and owner. One named role, such as chief engineer or front office manager.
• Trigger. What starts this procedure.
• Steps. Numbered, one action each, starting with a verb.
• Stop point. When to stop and escalate, and to whom.
• Done means. What the finished job looks like and who is told.
• Last reviewed. A date and a name.

Write the steps by watching, not by sitting at a desk. Talk to employees and observe how the task is done today. Document what your best attendant, night auditor or engineer already does. If your best attendant does the bathroom last because it keeps the floor dry for the vacuum, that sequence is the standard.

Two rules keep the writing honest. First, put numbers where numbers matter, such as response times, temperatures or counts, and set them from your own property's history. Second, test the draft on your newest hire. For any procedure that involves energy isolation, opening equipment or hazardous chemicals, do that test as a verbal walk-through only. Rewrite whichever step stalls them.

A sample: guest reports no cooling in an occupied room

Fill in the bracketed targets from your own response data.

1. Trigger: A guest reports a room that is too warm, by phone, at the desk or to any associate.
2. Whoever takes the report: Record room number, guest name and what the guest sees (thermostat reading, fan running or not, any noise or water). Apologize once and give the guest the time you will check back.
3. Log it as a job at once, not as a note, with the room number and priority set to guest-impacting.
4. Assigned technician: Reach the room within [X minutes]. Check thermostat mode, setpoint, batteries, and that windows and balcony doors are shut. Check the filter and vents for obvious blockage, but only where you can see them without removing a panel or cover.
5. Safety: Only an authorized employee may open the unit. Isolate the power at the disconnect, apply your lockout/tagout procedure, verify zero energy, and follow the manufacturer's instructions before opening anything. Wear the right protection for the task. Refrigerant, gas and electrical repairs go to a licensed technician, not a house engineer.
6. Stop point: If the room is not cooling after [X minutes] of basic checks, notify the duty manager. The manager decides between a portable unit, a room move or a vendor call.
7. If a move is needed: The desk offers the next available comparable room before the guest asks. Housekeeping prioritizes the new room.
8. Done means: The guest has been called back, the room is out of service or restored, and the job is closed with the cause noted.
9. Same day: The engineer adds the room to the preventive maintenance list if the cause was a filter, drain or coil.

Notice what's missing: no script about warm greetings, and no policy essays. It tells each person what to do, what to stop doing, and when to hand off.

Roll it out by training, not by posting

Emailing a PDF is not rollout. Use a four-step sequence for each SOP:

• Walk it through at a shift huddle, once per shift, including nights and weekends. If your night auditor misses it, it doesn't exist.
• Demonstrate it in the real place, such as a guestroom or the boiler room.
• Have each person do it back to you. Watch one run-through, and fix the step that stumbles.
• Record who was trained and when. It is good practice, and it shows the hazard communication training actually happened. OSHA's hazard communication guidance summarized by a state regulator says training should be in a manner and language employees understand.

For procedures involving energy isolation, opening equipment or hazardous chemicals, only authorized, trained employees do the hands-on demonstrations and do-backs. Equipment is safely isolated first, and chemical work follows the safety data sheet with the right protection worn. Everyone else walks through the steps verbally.

Put the SOP where the work happens: on the task card in the linen room, taped inside the engineer's cart, or on the phone staff already carry. Remove outdated paper copies when you replace one, because two versions in circulation is worse than none.

Add each SOP to new-hire week one. Most procedures are forgotten because nobody asked the new person to use them.

Review on a calendar, not when something breaks

An SOP is wrong the day a vendor, system, room layout or staffing pattern changes. Build the review into routines you already run.

• Every SOP gets a named owner and a review date, usually twelve months out. Treat safety-related procedures as the minimum annual case, as the lockout/tagout rule does.
• Quarterly, spot-check two. Pick any two and have someone who didn't write them walk through the steps with a staff member on shift. Fix the gaps the same week. For hazardous procedures, the spot-check stays verbal unless both people are authorized and trained and the equipment is safely isolated. Lockout/tagout periodic inspections must be performed by an authorized employee (29 CFR 1910.147).
• Event-driven reviews. Any incident, near miss, guest complaint tied to a procedure, new equipment or a new hire who couldn't follow it triggers a review of that SOP, not a general memo.
• Retire what nobody uses. If a procedure hasn't been touched in a year and nobody can say why, merge or delete it. The exception is safety and legally required procedures (energy control, chemical hazard communication, water management, life-safety). Those are reviewed and kept, never deleted for disuse.

Keep a single list of all SOPs with owner, last-reviewed date and next-due date. A one-page list checked at the monthly department-head meeting is enough.

Where software helps

A procedure is easiest to follow when it arrives with the job. In Altoreva Ops, an action code can link to an inspection checklist or a preventive maintenance checklist, so the call shows a button to inspect or run PM on its room, and finishing that closes the call. If your SOP's steps already exist as a checklist, the person who gets the call has them in hand. A manager can also author an action code or inspection task in each language, which helps when your team doesn't share one. The preventive maintenance worklist is the one part that works offline. Altoreva doesn't replace the owner, the training or the review date.

This article is general guidance for hotel operators, not legal, engineering or safety advice. Codes and regulations vary by jurisdiction and by edition, so confirm what applies to your property with your local authority and a qualified professional. Spot something wrong or out of date? Tell us and we'll correct it.
Last reviewed: 12 October 2026