Live demo
Watch a late check-out collide with an arrival.
The front desk grants a late check-out in a room already promised to a guest arriving the same afternoon. Watch HOS notice that the room is still occupied and raise the alert. A room attendant seeing an empty room is not a check-out, so HOS keeps the alert until the PMS records the departure, and ignores an outdated plan along the way.
How to read the replay
- The updatesWhat each system sends, in the order HOS receives it. A badge says what HOS did with it: applied, ignored as a duplicate, refused, and so on.
- The arrivalWhat HOS knows about this guest's arrival after each update, and which system each piece of information comes from.
- The alertWhen HOS raises or clears an alert, it appears in the standard's own format, ready for other systems to use.
Delivered to HOS, in this order
0 / 15
Arrival-readiness projection
Waiting for facts
Deliver the first event, or play the whole scenario.
Times are local to the hotel (America/Toronto). HOS 0.1 only raises alerts: it does not move the guest, message them or change the booking. For technical readers: the projection on this page is the non-normative reference implementation, run against the published files below.
Conformance kit
Run the same scenario through your own system.
For technical teams: feed these files to your own system and check that it reaches the same result. Replay events.jsonl in file order, then compare its dispositions, readiness and situations with expected.json. All the data is made up; no guest or operational data is involved.