Skip to content

Systems and records

Hotel room status reconciliation: clean, inspected or available?

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Hotel room status reconciliation works when clean, inspected and available are kept as three facts: housekeeping condition, occupancy and inventory or block status. When systems disagree, an agent should hold the room, read the newest evidence for each fact, let the front desk resolve sleeps, skips and occupant mismatches through the reservation, map out of order and out of service by inventory effect, and log every step as a replayable case.

System export

Hotel room status

This page covers hotel room status reconciliation: clean, inspected or available.Illustrative

Key takeaways

  • Clean or inspected, vacant or occupied, and sellable or blocked are separate facts with separate owners; store them as separate events.
  • A mismatch between housekeeping and the front desk is a discrepancy case that the front desk closes through the reservation, not a status to overwrite.
  • Out of order and out of service have different inventory effects in different systems, so normalize by effect before applying any rule.
  • Linked reservations, day use and late departures can make a correct single-room change wrong for the booking as a whole.
  • A usable dataset keeps events, cases and the status mapping, with roles instead of names and no guest identifiers.

Why clean, inspected and available are three different facts

They are three separate facts held by different owners, so a reconciliation rule has to keep them apart. Clean or inspected describes the physical condition housekeeping last recorded. Vacant or occupied describes whether a guest is in the room. Available describes whether the room can be sold or assigned for a date, which depends on inventory blocks and reservations rather than on cleaning.

Property management systems encode the split differently. Oracle's published OPERA Cloud housekeeping API lists room status values of Clean, Dirty, Pickup, Inspected, OutOfOrder and OutOfService, and keeps a separate front office status of Vacant or Occupied. Mews's connector API documentation gives a resource state (Dirty, Clean, Inspected, OutOfService, OutOfOrder) and a separate occupancy state that includes Vacant, Reserved, ReservedLocked, InternalUse and OutOfOrder.

The practical consequence: a dashboard tile that says a room is available is a derived answer. An agent or analyst who treats it as a single field loses the reason a room was or was not offered, and that reason is exactly what a reconciliation dataset needs to keep.

Why clean, inspected and available are three different facts
FactWho records itOPERA Cloud API valuesMews API valuesQuestion it answers
Housekeeping conditionRoom attendant or supervisorClean, Dirty, Pickup, InspectedDirty, Clean, InspectedIs the room physically ready?
OccupancyFront desk, from check-in and check-outFront office status Vacant or OccupiedOccupancy state such as Vacant, Reserved or InternalUseIs a guest in the room right now?
Housekeeping observation of occupancyRoom attendant on the floorHousekeeping status Vacant or OccupiedNot a separate field in the connector APIDoes the floor agree with the desk?
Inventory blockEngineering or rooms division managerOutOfOrder or OutOfService with a date rangeOut of order or internal use resource blocks with start and end timesCan this room be sold or assigned for these dates?
Reservation linkReservations and front deskReservation status such as Arrival, DueOut, StayOver, DayUseReservation assigned to the resourceWhich booking depends on this room?

Which record wins when housekeeping and the front desk disagree?

Neither record wins automatically: a mismatch between the floor and the desk is a discrepancy to resolve, not a value to overwrite. OPERA Cloud's documentation names three kinds. A sleep is a room the front office shows as vacant but housekeeping reports as occupied. A skip is a room checked in at the front office that housekeeping finds vacant. A person discrepancy is a conflict in the number of occupants.

Oracle's guidance is that front office resolves these by checking in or checking out the reservation for the room, after housekeeping has recorded what it saw. That ordering is the rule worth copying into any automated process. The housekeeping observation is evidence; the reservation action is the authorized change; the person who takes it is recorded.

For a dataset, this means each discrepancy becomes a small case with an opening observation, the evidence gathered, the action taken, the actor and the time it closed. A history that only stores the final room status hides every one of those steps, and an agent trained on it would learn to flip statuses rather than resolve them.

Out of order versus out of service: the word that changes meaning between systems

The same label can carry a different inventory effect from one system to the next, so map each status by what it does, not by its name. In OPERA Cloud, out of order rooms are removed from room inventory and cannot be assigned to reservations, while out of service rooms stay in inventory and can still be sold. Mews's help center describes out of order as a space needing major repair and out of service as one needing minor repair, and says out of service does not reduce availability while out of order does.

Blocks also end in different ways. Mews says the space status changes to Dirty automatically at the end time of an out of order block. OPERA Cloud returns an out of order room to inventory during end of day processing. A reconciliation rule that assumes a room comes back clean after maintenance will be wrong in both systems, and a dataset that merges properties on different platforms needs a mapping table before any rule is applied.

Record the mapping as data, not as code comments: source system, source value, normalized condition, whether it removes the room from sellable inventory, whether it can be assigned, and what status the room takes when the block ends.

Resolution rules: what an agent may change and what it must hand back

An agent may propose or apply a change only when the evidence for that one fact is newer than the conflicting value and the change sits inside its granted permissions; anything that alters a reservation goes to a person. OPERA Cloud's arrival guidance allows check-in when the room is vacant and its housekeeping status is clean or inspected, and offers a queue when it is not. Whether a property also requires inspection before arrival is a property setting, so the rule must read it rather than assume it.

The table below is a starting rule set. Each row names the conflict, the evidence to read first, the action an agent can take on its own and the point where it stops.

Resolution rules: what an agent may change and what it must hand back
ConflictEvidence to read firstAction an agent may takeHand back to
Desk says vacant, floor says occupied (sleep)Last check-out time, key or lock activity if the property records it, attendant noteHold the room from assignment and open a discrepancy caseFront desk, which checks the reservation out or corrects it
Desk says occupied, floor says vacant (skip)Check-in record, payment authorization, attendant noteFlag the reservation and stop status changes on the roomFront desk, which decides whether the guest left
Room clean, property requires inspected before arrivalProperty setting for inspection, supervisor scheduleQueue the arrival and request inspectionHousekeeping supervisor
Room inspected, then a maintenance ticket opensTicket open time against inspection timeDowngrade readiness pending ticket outcomeEngineering, then housekeeping for re-inspection
Out of order block ended, status still shows the pre-block valueBlock end time, system rule for end of block statusSet the system's documented post-block status and request cleaningHousekeeping
Arrival assigned to an out of service roomBlock reason and date range, guest arrival timePropose an equivalent room of the same typeFront desk for any room move or upgrade
Occupant count differs (person discrepancy)Reservation adults and children, attendant countRecord both counts and open a caseFront desk, which corrects the reservation
Two systems report different conditions at the same timeEvent timestamps from each source and the interface logKeep both values and mark the room unresolvedSystems owner for the interface

The room state reconciliation dataset specification

The specification is an event table, a case table and a mapping table, so every resolution can be replayed from raw observations to the final decision. Field names below are suggestions; the types and rules are what matter. Version the specification and date it, because status vocabularies and property settings change.

  • Validation rule 1: every case must reference at least two events with conflicting values for the same fact or for linked facts.
  • Validation rule 2: a resolution that changes a reservation must carry a front desk or supervisor role, never the agent role alone.
  • Validation rule 3: no event may be timestamped after the case close unless it is the verifying event.
  • Validation rule 4: the mapping table version in force at event time is stored with each normalized value.
  • Grade each case A (all events and verification present), B (verification missing) or C (one side of the conflict inferred); export A by default.
The room state reconciliation dataset specification
FieldTableType or allowed valuesRule
room_keyAllHashed room identifier plus property codeStable across exports; never a guest identifier
event_time_utc and source_systemEventISO 8601 timestamp; PMS, housekeeping app, maintenance, interfaceRequired; reject events without a source
fact_typeEventcondition, occupancy_desk, occupancy_floor, block, reservation_linkOne fact per event, never a combined status
source_value and normalized_valueEventRaw label and value from the mapping tableKeep the raw label so mappings can be revised
actor_roleEvent and caseAttendant, supervisor, front desk, engineering, agent, interfaceRole only; no names or employee IDs
block_type, block_start, block_endEventOut of order, out of service, internal use with UTC timesStore the documented status the room takes at block end
reservation_stateEventArrival, due out, stay over, day use, departed, not reservedTaken from the PMS at event time, not backfilled
discrepancy_typeCaseSleep, skip, person, cross-system, block conflictRequired when a case opens
resolution_action and resolved_by_roleCaseCheck-in, check-out, status correction, room move, no changeMust match a permitted action for that role
opened_at, closed_at, outcome_verifiedCaseTimestamps and a yes or no flag with the verifying eventClose only when a later event confirms the outcome

How shared reservations, day use and late departures change the valid action

Linked bookings turn a single-room correction into a group decision, so the case must carry every reservation that shares or depends on the room. OPERA Cloud's housekeeping API exposes reservation status values such as Arrival, DueOut, StayOver and DayUse against the room; a day use room can be occupied and dirty in the afternoon and ready again by evening, and a due out room that is still occupied is not a sleep until the departure time has passed.

The dependencies that most often change the valid action are shared reservations on one room, connecting rooms booked together, group blocks with a single arrival time, late check-out approvals and early arrival promises noted on the booking. For each, store the dependency type and the rule that ties the rooms together, for example that two rooms must be released together or not at all.

Authorization belongs in the same record. A room move, an upgrade or a released block changes what the guest paid for or was promised, so it needs the role that is allowed to approve it at that property, and the record should say who approved it and when.

Illustrative case: a connecting-room arrival with one room in dispute

This case is illustrative and uses invented timings. A family holds two connecting rooms with an early arrival noted on both reservations. At 11:40 the first room is inspected. The second room shows clean in the PMS, but at 11:55 the attendant marks it occupied because luggage is still inside, which is a sleep: the desk had checked the previous guest out at 10:20.

The agent reads the events in order. The desk occupancy (vacant, 10:20) and the floor occupancy (occupied, 11:55) conflict, and the floor observation is newer. The agent holds the second room from assignment, opens a sleep case and notifies the front desk. Because the two rooms must be released together, it does not release the inspected room alone, and it queues the arrival rather than proposing a different pair.

At 12:25 the desk confirms the previous guest left a bag for collection, the bag is moved to storage, and the attendant marks the room vacant and clean at 12:40. A supervisor inspects it at 12:50, and the family checks in at 13:05. The case closes with resolution action no change to the reservation, verified by the check-in event.

The exception: had engineering opened a ticket on the connecting door at 12:45, the inspected status of both rooms would be stale. The correct action then is to downgrade readiness for the pair and ask the front desk whether to offer a different pair, because a room move for a family booking is a guest-facing decision the agent should not take.

Limits of the specification and who should review it

The specification describes record structure and decision order; it does not set a property's policies. Stop and get a hotel operations lead to confirm the rules when a property uses inspection selectively, when the PMS and a separate housekeeping app both write status, or when brand standards govern what may be sold. Ask the systems owner to confirm which interface events are authoritative before any automated change is switched on.

Room state histories sit next to guest data. Drop guest names, contact details, loyalty numbers and free-text notes that mention guests before any export, keep room numbers hashed per property, and ask a privacy reviewer to look at retention and any location or lock data. Attendant identities are personnel data; keep roles, not names.

Check the documentation version for each system, because Oracle's pages differ by release and Mews notes several version-dependent behaviors. Treat the precedence rules here as a draft that a property signs off, not as a standard.

Turning reconciled room histories into a licensable dataset

Reconciled status histories are useful training and evaluation material for operations agents because each case shows conflicting evidence, a permitted action and a verified outcome. Whether a hotel group can license them depends on its PMS agreements, brand agreements and privacy obligations, which are separate questions from whether the data is clean.

A hotel group that wants to explore this can have SourceX handle rights review, contracting, preparation and delivery of the selected room histories. Several years of consistent status events in one PMS, ideally tens of thousands of cases, is the usual starting point, though a rarer workflow can qualify on less. The group approves scope and terms and signs before anything leaves, large exports can stay on its own storage, and qualification starts with a short assessment that needs no upload.

Frequently asked questions

What does inspected mean in a hotel PMS?

Inspected means a supervisor has checked a room that was already cleaned. In OPERA Cloud it is an optional status that appears only when the property turns on the Inspected Status control, so some properties never use it. A rule that requires inspection must read the property setting first.

What is the difference between a sleep room and a skip room?

A sleep is a room the front office shows as vacant while housekeeping finds it occupied. A skip is the reverse: the room is checked in, but housekeeping finds it vacant. Both are resolved by the front desk through the reservation, not by changing the housekeeping status alone.

Can a guest be checked into a room that is clean but not inspected?

In OPERA Cloud, check-in is allowed when the room is vacant and clean or inspected, and the reservation can be queued if it is not ready. Whether a clean but uninspected room is acceptable is a property decision. Record which rule applied so the case can be audited later.

Does out of service remove a room from inventory?

It depends on the system. OPERA Cloud keeps out of service rooms in inventory and removes out of order rooms. Mews says out of service does not reduce availability while out of order does. Map each label by its inventory effect before comparing properties.

What should a room status event log keep for later analysis?

Keep one fact per event with its source system, timestamp, raw label, normalized value and actor role, plus the reservation state at that moment. Store block start and end times and the status a room takes when a block ends. Leave out guest identifiers and attendant names.

Sources

  • Oracle's OPERA Cloud housekeeping API lists room status values Clean, Dirty, Pickup, Inspected, OutOfOrder and OutOfService, a front office status of Vacant or Occupied, discrepancy types Sleep, Skip and PersonDiscrepancy, and reservation statuses such as Arrival, DueOut, StayOver and DayUse. Source
  • Mews's connector API gives resource states Dirty, Clean, Inspected, OutOfService and OutOfOrder and occupancy states including Vacant, Reserved, ReservedLocked, InternalUse and OutOfOrder. Source
  • Mews resource blocks are out of order or internal use blocks with start and end times in UTC. Source
  • OPERA Cloud defines sleep, skip and person discrepancies between front office and housekeeping, and front office resolves them by checking a reservation in or out. Source
  • In OPERA Cloud, out of order rooms are removed from room inventory, cannot be assigned, and return to inventory during end of day processing. Source
  • In OPERA Cloud, out of service rooms are unavailable for occupancy but remain part of inventory and can be sold. Source
  • OPERA Cloud allows check-in when the room is vacant and clean or inspected, and offers a queue when it is not ready. Source
  • OPERA Cloud describes Inspected as an optional status for a clean room checked by a supervisor, available when the Inspected Status control is active. Source
  • Mews describes out of order as major repair and out of service as minor repair, says out of service does not reduce availability while out of order does, and changes a space to Dirty when an out of order block ends. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies