Do not turn one age label into four promises
When planning an interactive venue, avoid treating suitable for families as a complete operating rule. Write four separate answers: who the operator admits, what remains to be confirmed about the selected activities, what accompanying adults must do, and what a guardian needs to complete before arrival. A ticket or a booking answers none of these automatically.
This is a proposed buyer-planning framework. The public operator examples below show why the questions differ; they are not recommended CYDON age limits, customer installations, legal advice or evidence of equipment equivalence. The operator and appropriate project reviewers must establish the actual local policy and selected-configuration requirements.
Check admission and challenge level separately
Activate's public FAQ gives a minimum participation age of six, but separately describes its games as adult-designed and potentially difficult for children below ten. That is a useful example of an admission threshold not being the same statement as expected challenge level. It does not establish a universal age rule or prove that a particular child can use a particular activity.
In a supplier brief, name the intended participant groups and the selected activities. Ask what the exact configuration requires and what remains unconfirmed about the proposed audience. Keep a product description, an operator's admission policy and the evidence from a configuration-specific demonstration in separate fields. Do not translate another venue's threshold into your own published promise.
Define where adults stay and whether they play
Playplex's FAQ differentiates its arrangements for younger players. For ages six to eight, it calls for an accompanying adult who stays on-site and attentive throughout; for ages nine to thirteen, it requires an adult at the facility without requiring that adult to participate. Activate's FAQ states that players aged six to thirteen need an adult present in the facility for the session. These are each operator's stated conditions, not interchangeable supervision standards.
Your own brief should answer location and participation separately. An adult waiting at reception, an adult accompanying a group and an adult joining the game are different planned roles. Identify the applicable operator rule, who explains it and who checks that it is met. Do not assume the presence of venue staff removes an accompanying-adult duty, or invent a staff-to-player ratio from these examples.
Treat pre-arrival guardian action as its own task
For players aged fourteen to seventeen, Playplex's public FAQ permits attendance without an adult while still requiring an advance parent or legal-guardian waiver. Permission to arrive alone therefore does not mean there is nothing to complete before the visit. This is an attributed policy example, not a model waiver or a conclusion about enforceability in your jurisdiction.
If your operator requires a guardian action, record its approved route, the responsible role and the deadline. Decide who handles an incomplete, unclear or outdated record before announcing that a booking is ready. Do not copy another operator's waiver language or send real children's information to a supplier as demonstration data. Use a blank or fictional case when discussing the workflow.
Create a participant admission-readiness matrix
Use one blank row per intended participant group. Include the operator's admission rule and dated source; selected activity and unresolved fit question; adult-presence location; whether the adult participates; guardian action before arrival; decision owner; and review trigger. End with either a confirmed next step or a plainly unresolved status, not an assumed approval.
Consider a fictional mixed-age group whose planned session includes children and teenagers. An operator may have an admission rule but still need to confirm a selected game's requirements, clarify where adults remain and check whether any guardian action is complete. Those open fields should remain visible. The example supplies no recommended ages, approved configuration, participant capacity or successful customer result.
The matrix is different from a commercial access record. A party-package inclusion or hotel activity entitlement says what has been offered; this record asks what participation conditions the operator has actually resolved. Neither document should silently stand in for the other.
Run three independent buyer checklists
Admission and activity fit: identify the participant groups, record the operator's actual admission rule, list the exact proposed activities and assign each unresolved configuration question to a reviewer. Do not mark every activity suitable merely because a group meets the venue's entry threshold.
Adult responsibilities: state where adults must remain, whether participation is required, who communicates the rule and how staff handle a group that arrives without the required adult arrangement. Keep that decision separate from staffing estimates, ticket inclusions and spectator counts.
Pre-arrival readiness: identify any operator-approved guardian action, the deadline, the role checking completion and the communication for an unresolved case. Keep personal data out of the equipment brief. Any alternative activity, changed booking or rescheduling option remains subject to the operator's actual confirmation.
Use the record before advertising an all-ages offer
Before publishing guest-facing wording, compare it with the completed matrix. Check whether a phrase such as all ages implies access the operator has not approved. Keep the scope specific to the activity and configuration under discussion; do not infer medical suitability, accessibility compliance or safety certification from an age label or a successful demonstration.
For a CYDON GAMES project enquiry, provide the proposed location, intended participant groups, selected game formats and unresolved operating questions. Ask which requirements can be demonstrated and which remain the operator's or another qualified reviewer's decision. Age verification, waiver collection, booking rules and automated access controls are separate technical requirements to confirm, not capabilities established by this article.
Our planning perspective
The useful planning unit is a participant group with four separately owned decisions, rather than a venue-wide age badge. Admission establishes only the operator's entry condition. Selected-activity fit remains a configuration question, adult presence and participation are distinct roles, and guardian action may still be required even when a young visitor can arrive alone. Recording unresolved fields and their owners prevents a commercial inclusion or marketing phrase from becoming an unsupported participation promise. The matrix is a proposed planning aid, not a safety standard, legal policy, universal age recommendation or claim that CYDON already automates these decisions.
Buyer decision checklist
- Admission: record the operator's actual participant rule and dated policy source for each intended group.
- Activity fit: identify the exact proposed configuration and name the reviewer for every unresolved requirement.
- Adult presence: distinguish where accompanying adults remain from whether they must join the activity.
- Guardian action: identify the approved pre-arrival task, deadline and completion-checking role where applicable.
- Open cases: keep unresolved requirements visible and confirm any alternative with the operator.
- Public wording: check that family-friendly or all-ages language does not promise unapproved participation or technical functions.
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.