Before asking for a render, define what the visitor will do and what the organizer needs to learn. A useful interactive-event brief lets a supplier price the actual system: physical space, content, hardware, software, operations, and evidence of completion. A beautiful concept cannot answer whether a visitor can start a turn, whether the queue fits, or who restarts a failed station.
Start with one visitor task and one business purpose
Write a sentence from the visitor's point of view: “I try a short racing challenge and understand the product's role in it,” or “I explore three service options and take a relevant next step.” Then state the organizer's purpose separately: awareness, product understanding, qualified conversations, feedback, or hospitality. An experience can serve more than one purpose, but each additional purpose may add steps and reduce throughput. Decide which purpose wins if the brief becomes crowded.
The current ISO 9241-210 standard covers human-centred design activities throughout the life of computer-based interactive systems, including hardware and software. Its public abstract does not prescribe one event format or a complete project-management method. Use its human-centred scope as a reason to test the actual visitor task, not as a claim that a concept automatically conforms to a standard.
Supply the context a designer cannot infer
Provide the venue plan, event hours, expected peak periods, approach directions, lighting, sound, network reliability, power, rigging constraints, age range, languages, and whether visitors arrive alone or in groups. Name any accessibility needs already known, and arrange a separate review of the physical layout and digital controls. If the event is outdoors or beside another attraction, explain those conditions now. They change the design more than a list of preferred effects.
Crowd and queue responsibilities need an owner. The UK Health and Safety Executive advises organizers to assess movement around attractions and monitor build-up around exhibits. Its guidance does not replace the venue's own safety review or local rules. HSE, crowd-risk assessment; HSE, monitoring.
Ask for the full interaction and operating model
The proposal should show an approach state, a clear first action, the active turn, a result, an exit, and a reset. Request a throughput estimate based on the full cycle, plus a test plan for peak periods. Say whether a staff member invites, assists, supervises, or troubleshoots. Name who supplies copy, translations, rights-cleared media, devices, connectivity, and visitor-facing notices. If data is collected, specify its purpose and who will approve the collection and retention plan; do not let a default form become a surprise requirement.
Ask what happens when a camera, controller, network, or one station stops working. A reduced but coherent mode may be possible; it must be designed and rehearsed. “On-site support” should identify the hours, response owner, spare parts, and authority to pause admission. These are quote items, not details to discover during installation.
Define what approval will look like
Set checkpoints: storyboard or flow, working prototype, installed test, staff rehearsal, opening acceptance, and handover. For each, name who approves and what can be observed. The ISO 9241-11 usability standard frames evaluation around specified users, goals, and context; the public summary does not dictate a single test method. For an event, useful acceptance tasks include “a first-time visitor starts without coaching,” “the next visitor sees a cleared session,” and “staff can recover from a simulated fault.”
Archv's Formula 1 experience case documents work across a general event area and a hospitality space, including a racing-simulator concept. It does not publish measured visitor outcomes. A new brief should state which parts are concept, build, event operation, and measurement so proposals are comparable and later claims remain honest.