Hotel room status codes help teams communicate, but the same abbreviation can mean different things in different systems. Start by separating three questions: is the room occupied, what is its cleaning condition, and is it available for allocation? That distinction prevents a vacant but dirty room from being treated as ready for arrival.

Keep occupancy, condition and restrictions separate

Occupancy describes whether a guest is in the room. Cleaning condition describes the work or inspection still needed. A restriction describes whether the hotel can sell or allocate it. Store these as separate fields where your system supports them. When you use a combined code, document exactly which dimensions it represents.

  • Vacant or occupied: occupancy.
  • Dirty, cleaned or inspected: housekeeping condition.
  • Out of order or otherwise blocked: a restriction with its reason and owner.

Create a property-specific dictionary

The dictionary below is a working example, not a universal PMS specification. Some properties use VC for vacant clean; others use different codes or plain-language labels. Match your dictionary to the labels staff actually see. Include who is allowed to change each status and whether another employee must inspect a room before release.

  • Write the meaning in ordinary language.
  • Add the action triggered by the status.
  • Review the dictionary when software labels or inspection rules change.

Use a positive room-release check

After checkout, confirm the departure, complete the cleaning task and record any defect. If inspection is required, the inspecting employee releases the room only after checking the agreed standard. Front desk then confirms availability and any assignment restriction. An urgent arrival does not remove the need to resolve a reported problem.

  • Confirm that the previous guest has actually departed.
  • Record cleaning completion and any required inspection.
  • Resolve maintenance blocks through the responsible team.
  • Notify front desk through the agreed system, with a timestamp.

Investigate discrepancies rather than overwriting them

When a room appears vacant in one view and occupied in another, check the reservation, physical room condition and the last update. Possible causes include an unrecorded room move, a late departure or a delayed status update. Keep an exception log and identify the cause before changing the record. A daily discrepancy review is more useful than repeatedly resetting statuses without explanation.

  • Record the conflicting observations and time.
  • Assign one person to confirm the correct state.
  • Carry unresolved exceptions into the shift handover.

Practical worksheet

Download editable worksheet (CSV) ↓

Open the CSV in Excel, Google Sheets or another spreadsheet editor. Use fictional sample rows as examples and review the template before operational use.

Original editable planning resource. Examples are fictional; adapt and review before operational use.

Example labelDimensionMeaningRelease actionUpdate owner
VacantOccupancyNo guest currently occupying roomStill check cleaning and restrictionsFront desk
DirtyCleaning conditionCleaning requiredComplete cleaning before inspectionHousekeeping
InspectedCleaning conditionInspection recorded under property processConfirm allocation restrictionsHousekeeping supervisor
Out of orderRestrictionUnavailable because of recorded issueAuthorised resolution requiredMaintenance / duty manager

Fictional example: Room 204 is vacant after checkout and marked dirty. Housekeeping completes cleaning but reports a leaking tap. The room remains blocked until the issue is resolved, even though its occupancy is vacant and its cleaning task is complete.

Put the guide into practice

Use your property’s real labels in training and handovers. Cloudbeds’ housekeeping documentation also distinguishes room condition from vacant/occupied status; it is an example of one vendor’s terminology, not a specification for PowerOTA.

Explore housekeeping and room-status workflows, read the related practical guide, or book a demonstration to verify the workflows for your property.

Further reading

Cloudbeds documentation: housekeeping filters and inspection table. Status labels vary by system; use your property’s approved definitions.