Resort operations glossary
The words resort operations teams use every day, defined plainly — and where they differ from what the same word means in a city hotel. No jargon defended for its own sake.
Housekeeping and villa turnover
The vocabulary of getting a room from a departure to an arrival.
-
Turnover
- The full cycle of work that takes a room or villa from a guest departing to it being ready for the next arrival — stripping, cleaning, restocking, checking. On villa properties a turnover is a journey as much as a job: the distance between two villas can exceed the time spent inside either.
-
Room status
- The coded state of a room in the property's system — commonly vacant dirty, vacant clean, inspected, occupied, and out of order. Worth remembering that a status is a claim made by a person at a moment, not a live reading of the room.
-
Room readiness
- Whether a room can actually be given to a guest right now. Distinct from "clean": a spotless villa with a failed air-conditioning unit is clean and not ready. Properties that conflate the two end up verifying readiness by phone.
-
Stayover service
- The daily service of a room that is still occupied, as opposed to a departure clean. Lighter work, but far more of it on a full house, and it competes for the same staff at the same hours as turnovers.
-
Blocker
- A specific, named reason a room is not lettable — a failed fitting, a missing part, an odor, a pending repair. A system that cannot express a blocker forces staff to encode it by withholding a status, which makes the whole board ambiguous.
-
Inspection
- A supervisor's verification of completed housekeeping work. On corridor properties inspection is cheap and near-universal; on villa properties it can cost more walking than cleaning, so it becomes selective whether or not the process admits it.
-
Checklist template
- The reusable definition of what a job involves, item by item, from which individual jobs are generated. Storing the standard once — rather than in a laminated sheet per role — is what lets it be updated, translated, and audited.
-
Out of order vs. out of service
- Out of order means the room cannot be sold because something is broken; out of service means it is deliberately held back — a deep clean, a project, a buffer. Most SOPs blur the two, and the board then cannot tell a revenue problem from a planning decision.
-
Make-up room (rush room)
- A room pulled forward in the queue because an arrival is waiting on it. On a villa property a rush is expensive in a way it is not in a corridor hotel: it costs a walk out of sequence, not a detour of thirty seconds.
-
Arrival and departure lists
- The two lists that drive a housekeeping morning. Only the departure list is usually planned against, which is how properties end up sized to the smaller half of the day — occupancy, not departures, drives the stayover workload.
-
Rooms per attendant
- The planning ratio almost every property uses, and the one with no term for distance in it. It is portable between buildings and not between layouts: fourteen rooms down a corridor and fourteen villas along a beach are not the same shift.
-
Deep clean
- Periodic intensive work — mattresses, vents, behind furniture — on a longer cycle than a turnover. It competes for exactly the same people as daily work, which is why it slips first in a full season and why it needs a protected slot rather than good intentions.
-
SOP (standard operating procedure)
- The written definition of how a job is done. A standard is only executable when each line has exactly one answer shape — done, not done, or blocked for a named reason. A line that invites a paragraph is a line that will be skipped.
-
Par level
- The stock of linen or amenities a property holds to keep circulation going. Included here because it is standard vocabulary a housekeeper will look up.
-
Hard turn
- A checkout with a same-day arrival into the same room. There is no slack in it, which is why it is worth inspecting every time even on a property that samples the rest.
-
Failed item
- A checklist item a member of staff marked as not passing — a bulb out, a fitting broken. Valuable precisely because the judgment has already been made by a person in the room, which makes it a safe trigger for follow-up work.
Work orders and task management
How a problem becomes tracked work, and what keeps it from getting lost.
-
Work order
- A tracked, assignable unit of maintenance or repair work with a status and an owner. The defining property is that it belongs to the property rather than to the person who happened to hear about it.
-
Task source
- What caused a task to exist — a checkout, a failed checklist item, a recurring schedule, an inspection falling due, or a staff member raising one from a guest conversation. Knowing the source is how you tell whether your workload is reactive or planned.
-
Reactive vs. preventive work
- Reactive work responds to something that has already broken; preventive work happens on a schedule to stop it breaking. Reactive work has a complainant and always wins triage, which is why preventive work needs a forcing function to survive a busy season.
-
Recurring task
- Work generated automatically on a schedule rather than created by a person. The point is not automation for its own sake — it is that the work appears in the queue people already read, instead of in a spreadsheet they do not open in August.
-
Retyping gap
- The step where a problem reported in one system has to be manually re-entered into another. Where work orders are most often lost, degraded, or delayed, because it happens at the busiest moment of the day. Closing the retyping gap →
-
Offline outbox
- A queue on a staff device holding work completed without a signal, delivered when connectivity returns. On properties where staff walk between buildings, this is the normal case rather than an error state — and it must deliver exactly once, or the board shows work done twice.
-
Single writer
- The rule that exactly one system is authoritative for a given piece of state — a villa's readiness, say. Where two systems can both write, they diverge, and the divergence surfaces at the worst hour of the busiest day.
-
Blocked
- A job that cannot proceed for a named reason outside the assignee's control — a guest still in the room, a part on a boat. Distinct from late. A board that merges the two teaches everyone to read the overdue count as weather.
-
Pool vs. assignment
- Whether a job goes to a named person or to a queue anyone qualified can claim. The workable default is pool by default, route by exception — naming an owner up front is a guess about who is free, made by someone who is not there.
-
Escalation rule
- A written condition under which a job changes priority or ownership without a person deciding to raise it. Its value is social as much as operational: nobody has to be the one who made a fuss.
-
CMMS
- A computerized maintenance management system — maintenance software organized around assets rather than jobs, with service histories, meter readings and parts. It carries a staffing prerequisite that is usually discovered in year two: somebody has to own the register, or it decays into fiction.
-
Asset register
- The equipment list a CMMS is built on. True on the day it is entered and decaying from then on at a rate set by staff turnover.
-
Resolution vs. closure
- Resolution is the work being done. Closure is the guest knowing it was done. They are separate events, and the second one is the one nearly every process forgets — a closed ticket the guest never heard about produces a guest who still thinks they were ignored.
-
Priority
- The relative urgency of a task, typically low through urgent. Useful only if the scale is used sparingly; a queue where most items are urgent has no priority scheme at all.
Guest messaging
The channel between a guest and the people who can help them.
-
Guest messaging
- Text-based communication between guests and property staff during a stay. Distinct from a shared inbox in that the useful versions attach a conversation to a guest and a stay, rather than to a channel and a handset. Compare the four options →
-
Reply time vs. resolution time
- Reply time measures how fast the first response goes out; resolution time measures how long until the thing the guest asked for actually happened. They come apart constantly, and only the second one predicts a review.
-
Shift handover
- The moment an outgoing shift hands responsibility to an incoming one. The single most common point at which a guest request dies, because a request that was read and answered looks closed even when nothing has happened.
-
Service recovery
- Putting right a guest experience that has gone wrong. Most usefully understood as beginning before the complaint — in the window between a problem occurring and the guest concluding the property does not care.
-
App-free access
- Reaching a guest-facing service through a browser — typically a QR code or saved link — with nothing to install and no account to create. The practical alternative to an app nobody downloads on holiday data. Villa QR cards →
-
Pre-arrival window
- The period between booking and arrival, when guests volunteer the logistics information a property is later judged on — flight times, dietary needs, who is travelling — and when almost none of it reaches the people who will act on it.
-
Fallback thread owner
- The rule that a guest who writes without an assigned staff member is picked up by a named default — usually reception — so no guest message is ever unowned. Distinct from thread ownership, which is about the thread belonging to the guest rather than to a handset.
-
Thread ownership
- Whether a conversation belongs to the guest or to a device. A thread owned by the guest can be picked up by any authorized staff member across shifts and departments; a thread owned by a handset ends when that handset does.
Translation and multilingual operations
Language as an operational constraint, on both sides of the property.
-
On-server translation
- Translation performed on infrastructure the property controls, rather than sent to a third-party service. Matters because guest messages routinely contain names, room numbers, health details, and complaints.
-
Cloud fallback
- A third-party translation service used when the primary one is unavailable.
-
Pacing vs. failing
- How a translation queue behaves under load. Pacing slows down and still delivers everything; failing drops individual messages. Almost every property would choose pacing, and the naive implementation does the other one.
-
Original-alongside
- Showing a guest's message in the language they wrote it, next to the translation rather than replaced by it. Lets a colleague who shares the language catch an error, and stops a garbled room number being acted on.
-
Staff-side translation
- Job instructions and checklists rendered in each staff member's own language, as opposed to translating only guest-facing text. The less-discussed half, and arguably the one with more operational leverage.
-
Language tiering
- The unplanned pattern where response time depends on the guest's language — messages in the desk's languages answered at once, others waiting for the right person. Usually mistaken for cultural differences in expectation.
Where these show up in the product
Most of the vocabulary above maps to something on a screen: turnover boards, checklists and work orders, guest messaging with translation, venue and activity requests, and the card printed once per villa that guests scan to reach any of it.
See the vocabulary on a real board.
A 20-minute walkthrough on your own property's layout — turnover, work orders, and the guest thread.