Start with three decisions, not one guest label
For a proposed hotel activity room, write three separate answers: may this visitor enter the property, may this visitor use this particular activity, and what session or start time has actually been confirmed? A yes at one gate should not silently answer the next. The record can be a simple worksheet; it does not require a new access-control system.
This is our proposed procurement framework, not a rule shared by all hotels. Official operator policies illustrate different choices. They are useful comparisons when drafting your own brief, not evidence that those operators use CYDON equipment or that their policies suit your property.
Gate one: establish permission to enter the property
Tangalooma's published visitor policy requires official-guest registration before arrival. It also describes a timeshare-member casual-visit route that permits entry without extending further timeshare entitlements. The useful distinction is between being admitted and what that admission includes, not a universal overnight-guests-only rule.
For your property, list the visitor categories you intend to support: for example, staying guests, approved day visitors or invited event attendees. These are planning examples, not categories your hotel must accept. Give each category an admission decision owner and describe the minimum proof staff need to check. Do not put real guest lists or identity-document copies into a supplier brief.
Gate two: name the activity and its exclusions
Warner's Day Experience page permits non-resident daytime visits, while its terms exclude other facilities or experiences unless the confirmation includes them. A welcome to the property is therefore not a useful substitute for a written list of activity inclusions.
RISONARE Kohamajima labels its Activity Counter reservation link as requiring login and being for hotel guests. The same contact page places its after-check-in reservation restriction in the separate RYUKYU SPA section. Do not transfer that spa-specific rule to every activity, and do not assume that another hotel's guest-login label defines the software your project needs.
For each visitor category, name the proposed activity rather than writing all facilities. Mark the entitlement as included, separately bookable, excluded or unconfirmed. Record any locally decided supervision or participation conditions separately; a commercial entitlement is not evidence that a person is ready or permitted to take part under the activity's own requirements.
Gate three: state what booking confirmation means
A reservation request, a confirmed session window and an assigned exact start are different promises. Warner states that, for an experience including a spa treatment, the treatment and precise time are confirmed on arrival within the booked session. This is a specific spa example, not a prescription for an interactive room; it demonstrates why the confirmation level should be explicit.
For your activity room, decide which state the guest-facing message can truthfully show: requested, confirmed window, exact start assigned, unavailable or awaiting staff decision. Name the role that moves a request between states. If the guest is eligible but no session is confirmed, explain that status instead of treating the eligibility check as a reservation.
Do not infer real availability from a catalogue, a readable booking page or a sample screen. Ask how a changed activity, expired entitlement or unavailable session is communicated. Keep any alternative offer subject to staff confirmation rather than promising an automatic replacement.
Build one access decision record per visitor category
Use a blank record with these fields: visitor category; property-admission rule and proof; named activity entitlement and exclusions; booking-confirmation state; verification role; exception approver; expiry or change trigger; unresolved decision and owner. Complete the policy fields first. Only then ask whether a proposed technical configuration can support them.
Consider an invented event-attendee example. An organiser's invitation might support property admission, while use of the activity room remains unconfirmed and no session has been allocated. The record should retain those two open decisions. It should not turn the invitation into an activity ticket, or assume the front desk can approve an exception merely because it checked the visitor in. This is a planning example, not a customer result.
Use three separate buyer checklists
Eligibility and proof: list the permitted visitor categories, separate property admission from activity entitlement, name the verification role and describe the minimum necessary proof. Use demonstration records rather than personal guest data when discussing a possible system.
Exceptions and responsibility: name who may authorise an exception, specify which gate it changes and state the activity and validity window covered. Record the decision owner for a denied, expired or unclear request. An exception to property admission need not change activity eligibility or allocate a session.
Booking and communication: identify the correct booking route, distinguish a request from the promised confirmation level, and decide who explains unavailability or a change. Align the public wording with the actual decision state before announcing access to guests or outside visitors.
Turn the policy into questions for a technology proposal
Take the completed record to the hotel team and the proposed equipment or software supplier. Ask which decisions remain manual, which staff permissions are needed and what evidence a demonstration should show. Room-key, property-management, booking, payment or guest-login connections are separate requirements to confirm; none is established by this framework or by an operator's public policy.
Keep an unknown field open until its owner resolves it. A useful first brief can describe the country and property, visitor categories, intended activity, decision owners and unresolved confirmation rules without claiming a capacity, revenue outcome or integration that has not been demonstrated. Review equipment and software scope only against the decisions the property has actually made.
Our planning perspective
The practical unit is a visitor-category decision record, not a single guest flag. Separate property admission, a named activity entitlement and the level of booking confirmation, then assign a verifier and a limited exception owner to each. This prevents one piece of evidence, such as an invitation or room key, from implying a different permission or a reserved time. It also exposes which questions are policy decisions and which are technical requirements. The framework is a proposed planning aid; it does not establish a live access-control function, hotel customer relationship or default integration.
Buyer decision checklist
- Eligibility: write the property-admission and named-activity rules separately for every intended visitor category.
- Proof: assign a verification role and use only the minimum necessary evidence, not personal guest records in a supplier brief.
- Exceptions: name the approver, the specific gate being changed and the exception's activity and validity window.
- Confirmation: distinguish a booking request, a confirmed session window and an assigned exact start in guest-facing wording.
- Changes: decide who handles denied, expired, unavailable or unresolved requests without promising an unconfirmed alternative.
- Technology: keep room-key, property-management, booking and payment integrations unconfirmed until the exact project scope is demonstrated.
Sources and scope
Source material supports the stated facts, not a guarantee of capacity, revenue, safety certification or project outcomes. Final equipment and software scope require a project review.