Writing hotel SOPs that staff actually follow

A hotel SOP (standard operating procedure) is a one-page instruction for one repeatable task: the trigger that starts it, the steps in order, the record it leaves, and the role that approves exceptions. Staff follow it when it is written in their own words, tested on a new hire, and dated and reviewed.

The binder sits on the shelf behind reception, forty pages, dated three years ago. The new seasonal hire learns check-in from the person standing beside them, and that person leaves in September. After reading this guide you will be able to write a procedure a first-week employee can follow without asking a question, train it properly, and know which five procedures to write first.

Why do hotel SOP binders go unread?#

Because they are written for an auditor or a chain head office, not for the person doing the task at two in the morning. Length, generic wording, translation drift and the absence of an owner each make a page unusable on its own.

Length is the first problem. A forty-page department manual is a reference book, and nobody opens page thirty-one during a shift, so the page that mattered is never found. Generic wording is the second: "ensure high standards of cleanliness" names no action, so the doer still has to invent the step, and every doer invents a different one.

Translation drift is common in Türkiye. A chain template translated line by line describes a building the hotel does not have, with different room types, a different breakfast format and a different front desk system. Two structural faults finish the job: pages with no trigger ("the receptionist should...") never say when the task starts, so it starts when someone remembers; and a page with no named owner decays quietly, because the person who knows the work is rarely the person who wrote it.

The real cost is not paper. Staff learn from the colleague beside them, and that works until the colleague leaves, and then the knowledge leaves with them.

What is a hotel SOP, and what does it contain?#

A standard operating procedure is a short written instruction for one repeatable task: when it starts, the steps in order, the record it leaves, and who decides when the normal path does not fit.

Hotels usually merge four documents that should stay separate. A policy is a rule, for example "no room is sold without guest identity notification". A procedure is how one task is done. A checklist is the ticks made while doing it. A job description says who is accountable. Merging them is what produces the binder.

The trigger is the event that starts the task, written in the first line: a guest arrives with a reservation the system does not show; a room status changes to departed. The steps are numbered, one action each, in the order they happen, with decision points written as plain if/then lines.

The record is what remains after the task: a note on the reservation, a room status change with a time, a maintenance ticket, a signature. This is the part hotels forget, and it is the only way to tell later whether the procedure was followed. Exceptions come next, because the normal path will not always fit, so the page names the role that decides: duty manager, housekeeping supervisor, food and beverage manager. "Management" is not a role.

Finally, owner and date: one named role responsible for the page being true, and a review date in the footer. A page without both is a rumour with formatting.

How do you write a procedure that fits on one page?#

Split the work until one page holds one task with one trigger and one record. If a draft needs two triggers, it is two procedures, and the second one gets its own page.

Title it as a verb phrase: "Checking in a guest whose room is not ready", not "Front office procedures". The title should tell a new hire whether this is their page. Open with the trigger, then the prerequisites: what must be in hand before step one, such as the reservation record, a key card or the current room status.

Write each step as one imperative action in the present tense. Decision points become explicit lines: if the room will be ready within the hour, offer luggage storage; if not, offer the alternative. Name system steps in plain words: "open the reservation and check the room status" is enough, and screen names and internal codes belong in training, not on the page.

Put limits only where they change behaviour, and mark them as hotel practice rather than law. "Acknowledge the guest before anything else" is a practice the hotel chooses. Keep prices, legal detail and rate rules out of the page; point to the current rate sheet or to the colleague who owns that decision.

Then test it on the newest person in the department. Every question they ask is a missing line, and every step they skip is a step that is in the wrong order.

Worked example: a front desk procedure for a room that is not ready#

The page covers one arrival situation, from the moment the guest reaches the desk to the note that lets the next shift pick it up. It is illustrative, not a template to copy word for word.

The trigger: a guest with a reservation arrives and the assigned room is not ready for sale. The steps: greet and acknowledge first, check the live room status, give a realistic time rather than a hopeful one, offer the practical alternatives the hotel has chosen in advance (luggage storage, breakfast, a seat in the lobby), notify housekeeping that the room is now a priority, and write the note before the guest walks away.

The record is a dated note on the reservation saying what was promised and by when, plus one line in the shift handover, so the promise survives the shift change. If you want to go deeper on that handover moment, see our front desk shift handover checklist.

An upgrade or any paid gesture needs the duty manager, and the page names that role rather than "management". The rate itself stays on the current rate sheet, not on the procedure. Legal steps stay general on the page: in Türkiye, every stay involves a payment, a fiscal document (an invoice or e-document), a guest identity notification (KBS) and personal data (KVKK). The procedure says who does each step and where the record sits; the hotel confirms the detail with its accountant and legal adviser.

Keep the page to one screen of paper. If the arrival situation needs three variants, write three pages with the same shape. For how this moment fits the whole business day, see how one hotel business day fits together.

Worked example: a housekeeping procedure for a departure room#

The page turns one room from departed to sellable in a fixed order, and it makes the status change and the maintenance ticket part of the task rather than an afterthought. It is illustrative.

The trigger: the room status shows departed, or the front desk marks the room as left. The steps run in a fixed order: knock and announce, confirm the room is empty, strip and count linen, clean from dry to wet and from top to bottom, restock, then inspect against a short list before reporting the room.

Define the hotel's own room status codes on the page. Codes such as vacant clean, vacant dirty or out of order are common practice and differ between systems, so the page states what this hotel means by each one. Any fault becomes a maintenance ticket in the same step, not a spoken message in the corridor, and the room does not return to sale until the supervisor changes the status.

The record is the status change with its time and the maintenance ticket number, so a later question about a room has an answer. A room that cannot be brought to standard goes out of order, and the housekeeping supervisor decides that, not the room attendant. The page also says what is counted (linen, minibar, amenities) and where the count is written, so the same number reaches the same place every day.

How is a procedure trained, signed off and reviewed?#

Train it in four moves (read together, watch a demonstration, do it while watched, do it alone), record a dated sign-off against the version that was trained, and review on a fixed cycle plus after anything goes wrong.

The sign-off record carries three things: the person's name, the date, and the version number of the page they were trained on. When the page changes, the sign-off expires and the training is repeated. Version control means version and date in the footer of every page, one master copy, and printed copies removed from the back office the day they are replaced. Two versions in circulation means no version.

Review yearly for stable tasks, sooner after a guest complaint, an incident, a system change or a new room type. The reviewer is the person who does the task plus the department head, and the named owner signs the new version. Keep a short change log: what changed, why, who approved it. It answers the question "why is this different from last season" without an argument.

With high seasonal turnover, week one is the procedure's real test. If a new hire cannot follow the page in their first week, rewrite the page, not the hire.

Which procedures should a hotel write first?#

Start where money, legal records, guest safety or a shift change meet a task done many times a day. Those pages pay back in the first month; the rest can wait.

Rank by frequency multiplied by consequence, then lift safety and legal records above the ranking regardless of frequency. Write the shift-change procedures early: handovers lose more information than any other moment in the day, because the promise made at 16:00 has to survive until 08:00.

Money first: cash and card handling at the front desk, then the night audit close, because both leave a financial record that must reconcile. Legal records next: guest identity notification at check-in and the handling of personal data, written in general terms with the detail confirmed by the hotel's accountant and legal adviser. Then the physical operation: key control, incident and accident reporting, departure-room cleaning, maintenance reporting.

Do not write sixty pages in a month. Write five, train them, watch them for two weeks, fix what the new hires stumble on, then continue. And retire pages nobody uses: a binder with dead pages teaches staff that the live ones can be ignored too.

For the close itself, our night audit checklist covers the order of operations; for the end of the season, see closing a seasonal hotel for winter.

What to do next#

Pick one task this week, write it as a single page with a trigger, numbered steps, a record, a named approver and a review date, then hand it to the newest person in the department and rewrite whatever makes them pause. The binder fails because it is a library; a procedure works because it is one page that is trained, dated and owned, and five of those beat forty pages nobody opens.