The hotel operations playbook
Housekeeping, maintenance, stock, staff and reporting — the five things that quietly determine whether a property runs itself or runs its owner.
Operations is everything that happens between a booking being confirmed and a guest leaving a good review — and at a small property, it usually runs on habit and memory rather than a written system, which works fine until the day it doesn't. This guide walks through the five areas that make the most difference: housekeeping, maintenance, stock, staff, and reporting.
As with the revenue guide, this page is the map. Every section links to the feature or article that covers the specifics — a live worked example, a real schema, or a full checklist.
Housekeeping: the room board and the step most tools skip
A room passes through five real states — dirty, being cleaned, clean, inspected, occupied — and most budget tools collapse that to two: clean and dirty. The missing state is inspected, and it's the one that actually matters: a second person confirming, after the fact, that a room marked clean is genuinely ready to sell. On a busy turnover day, that one extra step is the difference between a smooth check-in and a guest finding yesterday's towels.
Maintenance: from reactive to preventive
Small properties rarely lose money on the big repair — they lose it on the small one nobody owned. A work-order board with a priority, a trade category and an average-days-to-close figure turns 'someone should look at that' into a ticket with an owner and a date. Layered on top of that, a preventive schedule — checked on a recurring basis rather than waited on — catches the failure before a guest does, which matters more at a coastal property where salt air and humidity break things faster than anywhere else.
Stock: the ledger that catches what a count alone can't
A monthly count tells you what's left. It doesn't tell you what should be left, and without that second number, shrinkage and ordinary consumption look identical — a bottle poured into a paying guest's drink and a bottle that quietly disappeared are both just gone by the time anyone checks. A movement-by-movement ledger — purchases, usage, waste, counts, each its own entry — is what makes a discrepancy checkable instead of just a bad feeling about the numbers.
PAR levels handle the other half of the same problem: the floor you never want to drop below, set once per item, so the item tells you when it's crossed rather than everyone finding out at the worst possible moment.
Staff: scheduling, access, and training that actually sticks
A visible weekly rota with a coverage minimum catches a short-staffed day before it happens rather than during it — especially useful for a mixed team of full-time and part-time staff, where a shortage is easy to miss until the shift is already understaffed. Access is the other half: most owners keep the only login because handing one out means handing out everything, which is a software problem more than a trust problem — scoped roles fix it by giving each job exactly the screens it touches and nothing else.
None of it works if the team doesn't actually use it. For a Tagalog-first team, rollout starts with the interface language, not with a training manual translated after the fact.
Reporting: the record that replaces a memory
A shift report filed at the end of every shift — hours, rooms handled, tasks done out of assigned, issues flagged — is what turns 'how did the evening go' from a question answered by memory into a specific, comparable record. Approved by a manager rather than just collected, it becomes a queue instead of a pile of paper nobody reads. Rolled up over a season, it's also the fairest performance record a small team can have.
The night audit — reconciling the day's charges while the day is still fresh — matters even at ten rooms, for the same reason a Z-reading matters at a restaurant till: catching a discrepancy the same day beats discovering it a month later with no way to trace it back.
Managing all of it from a distance
An owner who doesn't live at the property, or who lives in a different country entirely, has to trust the same operational record described above without being able to walk the floor and check it by eye. That's a real constraint, and it's handled by the same reports, the same approval queues, and the same audit trail — read on a ten-minute Monday routine rather than relayed secondhand from a manager.
Where these five actually connect
None of the five areas above are as separate as this guide's structure makes them look. A housekeeping SOP that keeps rooms turning smoothly on a busy weekend depends on the staffing behind it being adequate in the first place — the same coverage gap that causes a room-board bottleneck usually shows up as a thin rota, not a housekeeping problem to solve on its own. A maintenance board with a rising urgent-ticket count is often a preventive-schedule gap, not a sign the team is careless. And a shift report's task-completion figure is only meaningful once the tasks themselves are actually written down properly in the first place.
The properties that get the most out of operations software treat these as one connected system worth reviewing together — a slow week is a good time to check all five at once, rather than only reacting to whichever one broke most recently.
See it on your own property
Thirty minutes with the IslandLink team, your rooms and your rates. No card, nothing to sign.
Book a demo