CYDON GAMES — Interactive game software scope brief Country / city: ______ Venue type / project stage / opening target: ______ Selected games / hardware models: ______ For every item: requirement; included / optional / unconfirmed; version/provider; demonstration evidence; responsible party. 1. Record the games, modes and versions For each selected room, list the hardware model, game modes, software version, interface languages and licence scope. For the illustrated GRID floor, the handbook shows safe green tiles, blue targets and red hazards. Use the proposed mode to demonstrate how a session begins, registers a target, ends and resets. Ask which controls are available to staff; do not infer them from the floor photograph. Project requirement / agreed status: ______ 2. Demonstrate operation and connectivity Use a witnessed demo to define session start, stop and reset, staff permissions, displayed scores and any session records included in the quotation. Agree how each selected function behaves when the venue network or internet is unavailable and how it recovers. Record the test result and any function that requires connectivity. This checklist does not establish offline operation, shared control across rooms or a guaranteed recovery time. Project requirement / agreed status: ______ 3. Separate booking, payment and data responsibilities The handbook describes booking, payment and session-related records. For your destination, ask which functions and providers are supported in the proposed version, who performs any integration and who is responsible for accounts, refunds and fault handling. Request a sample using demonstration data, plus the proposed storage, access, retention and export scope. Do not assume a third-party payment service, customer database or bespoke analytics is included. Project requirement / agreed status: ______ 4. Agree on updates, licensing and support Request the delivered content list, licence duration and permitted use, update responsibilities, release procedure and any recurring charges or renewal conditions. Where branded content is proposed, ask for the relevant authorisation. Confirm how staff report faults, what remote access is permitted and which training and documentation are included. Neither a stated update practice nor a product photo establishes free future content, ownership of source code, an AI feature or a fixed support response time. Project requirement / agreed status: ______ 5. Make acceptance observable Give each requested function a status: demonstrated and included; optional and separately scoped; or not confirmed. Attach the selected mode/version and the witnessed test result to the proposal. Specify who confirms unresolved items before ordering and which tests are repeated at handover. A useful acceptance record names the actual configuration and responsibility; it does not substitute for the local safety or installation review. Project requirement / agreed status: ______ This is a planning worksheet, not a supplied feature list, contract, price or approved technical design. Do not include sensitive personal, payment or player data.