Direct answer
Test one chain: reservation status, payment condition, room assignment, housekeeping release, access credential, arrival message and staff response. Give every handoff a source, trigger, expected delay, responsible person, failure signal and manual recovery step.
Run six exceptions before signing: early arrival, room move, failed cleaning inspection, dead lock battery, lost connectivity and after-hours lockout. The goal is one operating state that both the guest and staff can understand.
Operating state
Define ready before choosing software.
A reservation is not ready for arrival merely because payment succeeded. The assigned unit must be cleaned and released, the correct access credential must work during the intended window, and staff must see any exception that blocks check-in.
Write the states used by reservations, rooms and credentials. Distinguish a completed cleaning task from an inspected, ready unit. Identify the source of truth and the event that permits each transition. Use the reservation number, guest, unit and stay dates to trace every message, code and task to the same stay.
This is narrower than the full operating-stack map. It is an acceptance test for arrival and turnover, where several systems must agree that one unit is ready for one guest.
Access handoff
Make the credential depend on an explicit status.
Ask what creates a code, when it becomes valid, which door or gate receives it and what revokes it. Move the guest after the original code exists. The old and new credential status should remain visible, and the guest should receive one accurate instruction.
Simulate a dead battery, disconnected lock, failed sync and late lockout. Name who can verify identity, issue an approved temporary credential and record the override. Keep emergency access and physical-key procedures separate from a promise of contactless arrival.
Give staff only the permissions needed for assigned work. NIST defines least privilege as limiting resources and authorizations to what the task requires. CISA recommends logging user and administrator activity so unusual changes can be reviewed. Those principles frame the questions; they do not certify a vendor.
Messages and rooms
Separate the guest instruction from the staff alert.
The guest needs accurate arrival time, parking, access and help instructions. Staff need a visible alert when the condition behind that message fails: unpaid balance, room not released, missing code, delivery failure or reply awaiting action.
List each outbound message with its trigger, owner and stop condition. A cancellation should stop future arrival instructions. A room move should replace the earlier assignment. Two-way replies need a monitored queue, after-hours escalation and a named owner.
The turnover begins with the real departure record. If inspection is separate from cleaning, access should wait for the inspected or ready state. A maintenance defect must be able to block the unit and create owned follow-up rather than disappear in a free-form note.
Exception test
Break the happy path before the first guest does.
- Early arrival: change the approved time without bypassing room release.
- Room move: trace both credentials, tasks and the revised guest message.
- Failed inspection: return the unit to rework and keep access blocked.
- Dead lock battery: follow the alert, dispatch, temporary access and replacement record.
- Lost connectivity: identify offline visibility, queued changes and conflict resolution.
- After-hours lockout: test escalation, identity verification, authority and the incident record.
Score each case pass, conditional or fail. A conditional result needs a trained owner, named manual action and acceptable response window. Use vendor-approved test data, never a real guest’s personal or payment information.
Evidence and support
Put the handoff into the commercial file.
Staylist describes integrations across messaging, access, housekeeping and maintenance. RMS documents assigned housekeeping tasks, statuses, privileges, linen records and staff messaging. These first-party pages supply concrete demo questions. They do not prove plan availability, implementation effort or fit.
Record which company supports each interface, the escalation path, support hours, log access and responsibility when an integration fails. Require current plan-specific documentation, acceptance tests, training and a usable export in the proposed scope.
The PMS shortlist provides the broader demo method. The opening-readiness guide carries the selected workflow into training and commissioning.
Sources
Named sources and limitations.
The official event page is the exact discovery source. Vendor documentation is first-party evidence of described features, not independent proof of package availability, security, uptime, support quality, price or property-specific fit.
FAQ
Questions owners ask before committing.
Should a door code be sent as soon as a reservation is confirmed?
Not automatically. The property should define the required payment, unit assignment, room-release and timing conditions, then test how the selected systems enforce them.
Does one platform need to control messaging, locks and housekeeping?
No. Separate tools can work when each record has one owner and every integration has a defined trigger, delay, failure signal and recovery procedure.
What should happen when a guest changes units?
Handle the original credential according to policy, issue the new credential for the correct window, move housekeeping and maintenance work, send one accurate guest instruction and retain the change history.
Can a small glamping property manage this manually?
Yes, when the manual process has named owners, controlled credentials, visible room status, a response schedule and retained records.
Does the UNIKOST calculator choose an operations platform?
No. It identifies project workstreams and coordination pressure. It does not select software, test integrations, certify security, set staffing levels or predict operating results.
Next step
Bring the unresolved handoffs into project review.
Map the unit count, arrival pattern, staffing and support constraints first. The calculator identifies coordination pressure; it does not select software or certify an operating workflow.
Sources checked September 30, 2026. No attendance, partnership, endorsement, guest result, staffing reduction, occupancy, revenue, ROI, approval or opening date is claimed. Security, privacy, messaging and access procedures require review for the actual systems, contracts, property and jurisdictions.