Property Management System / Front Desk · Documentation

User Journey

The end-to-end path through Property Management System / Front Desk, from trigger to outcome.

Live diagram — check-in emits guest.checked_in (reflected on the cockpit timeline); check-out emits guest.checked_out for #07 / #14 / #12.

1
Arrival → check-in → folio
The journey opens on the day's board, derived from every cockpit booking for the selected date. At check-in the desk assigns the suggested available room, flips the room to occupied, and opens a folio seeded with the room charge. That single action emits guest.checked_in on the spine and is reflected immediately on the booking's cockpit timeline.
2
Stay → check-out → the rest of the ecosystem
During the stay, incidental charges post to the folio (each emits folio.posted). At check-out the folio settles (simulated) and guest.checked_out is emitted. Those stay events are the hooks later clusters consume — on-property service #07, housekeeping & maintenance #14, and loyalty #12 — so a check-out here can trigger a turndown work order or a loyalty accrual without PMS knowing those apps exist.