An operations manual for a small hotel: the minimal template that works

An operations manual for a small hotel doesn't need 60 pages: it needs 9 well-chosen sections. They answer around 80% of the questions that reach the front desk on a normal shift. This is the minimal template we see working in hotels with 20 to 60 rooms.

The 9 sections

1. Arrivals and departures. Check-in and check-out times, what to do with early arrivals and late check-outs: who authorizes them, how much they cost, and how they're charged.
2. Rates and conditions. How long the non-refundable rate applies, what happens with no-shows, and who can make an exception.
3. Rooms. A sheet per room type: what fits (crib, extra bed), what doesn't, and the exact surcharges in euros.
4. Breakfast and bar. Weekday and weekend hours, the price if it's not included, and how to handle allergies and intolerances.
5. Pets. Maximum weight, which floors allow them, cleaning surcharge, and where they can't go.
6. Parking. On-site or partnered, price per 24 h, and the procedure for the voucher or the remote.
7. Technical incidents. Who to notify depending on the fault and the time of day, and when to move a guest to another room.
8. Billing. What details are needed for a company invoice and how the tourist tax is itemized.
9. External arrangements. Taxis, parking, laundry, florist: contacts, terms, and agreed prices.

Three rules when writing it

First: every fact with its exact number. “Late check-out costs €25 and is confirmed by the front-desk manager in the morning” answers the question; “check availability” doesn't. Second: one real question per paragraph, with the answer at the start. Third: a visible last-reviewed date on every section, so nobody wonders whether it's still current.

The manual isn't the end, it's the beginning

The classic mistake is thinking that writing it is enough. Nobody opens a 30-page PDF mid-shift; they ask the boss, who's faster. The second half of the job is giving it an interface: an internal assistant that answers instantly, citing the exact section, and flags any question it doesn't cover. That way the manual grows exactly where the team needs it: every gap is a real question that will never interrupt you again.