Exhibition Registration Kiosk Requirements in Singapore

Start with the exhibition arrival journey

An exhibition registration kiosk should be specified around what visitors need to accomplish, not around a preferred screen or device. Begin by mapping each expected arrival path: pre-registered visitor, walk-in, invited guest, exhibitor, speaker, contractor, group arrival and anyone whose record cannot be found. State whether each person should confirm details, accept notices, select a pass, print a badge or proceed to an assisted counter.

Define the intended result for every path. For example, a valid pre-registered visitor might retrieve a record, confirm the displayed details and receive the correct badge without staff intervention. A duplicate record, changed entitlement or failed print should move to a clearly identified support process. These decisions determine the interface, data, equipment and staffing requirements.

For broader planning beyond kiosks, compare the operational scope with event registration services in Singapore. Exhibition requirements should remain specific to the venue, audience and access model.

Functional requirements to document

Guest identification and record handling

• Lookup methods: Specify whether visitors use a QR code, reference number, email address, mobile number, name search or another agreed identifier.
• Match rules: Define what happens when no record, multiple records or an already checked-in record is found.
• Editable fields: State which details visitors may correct and which changes require staff review.
• Entitlements: Document how visitor type, access level, session eligibility or badge format is determined.
• Completion state: Define when a record becomes checked in and how an accidental or interrupted transaction is handled.

Badge and confirmation output

If badges are printed, specify their dimensions, stock, orientation, required fields, branding, barcodes or QR codes, and any colour or physical distinction between access types. Confirm whether the kiosk prints directly, sends a job to a shared print station or directs visitors to collection. Badge coordination must also cover reprints, depleted stock, printer errors and records requiring approval.

Set privacy rules for information shown on screen and printed on the badge. Display only what the agreed visitor journey requires. Any collection, retention or disclosure decisions should be reviewed against the organiser’s policies and applicable obligations; operational guidance is not legal advice.

Operational and technical dependencies

A kiosk cannot be evaluated independently of its environment. Confirm venue access times, floor plan, power points, network options, loading procedures, storage, lighting, acoustics and operating hours. Record who provides each dependency and the deadline for confirmation.

• Connectivity: Define the preferred connection, fallback approach and expected behaviour during an interruption. Offline functions, if required, depend on the selected tools and agreed data rules.
• Power: Confirm socket locations, electrical loading, cable routing and whether backup power is required for critical equipment.
• Data readiness: Establish the source of guest records, import format, required fields, update cut-off and process for late registrations.
• Equipment: List screens, stands, scanners, printers, consumables, network hardware and staff devices by location.
• People: Assign responsibility for queue guidance, exception handling, technical support, stock replenishment and escalation.

If arrivals are likely to exceed the kiosk area’s practical capacity, include a separate registration-area queue management requirement. Kiosk speed alone does not resolve poor routing, insufficient space or slow exception handling.

Accessibility and inclusive use

Specify accessibility as part of the normal journey. Consider screen and control height, reach range, text size, contrast, plain-language instructions, touch-target size, glare, physical clearance and the time allowed before a session resets. Avoid making audio the only way to understand a prompt.

Provide an assisted route for visitors who cannot or prefer not to use self-service. Staff should be able to complete the same essential outcome without sending someone between several counters. Where the audience has language needs, identify required languages during scoping and test the complete translated journey, including validation messages and printed output.

Turn requirements into acceptance criteria

Each important requirement should have an observable pass condition. Avoid statements such as “fast”, “easy” or “user-friendly” unless the brief defines how they will be assessed. Useful acceptance criteria describe the starting data, user action, expected response and permitted exception.

1. A valid test QR code retrieves only its intended test record and presents the correct next step.
2. An unknown or unreadable code produces a clear recovery option without exposing another visitor’s information.
3. A completed check-in records the agreed status once, even if the visitor repeats the final action.
4. The correct badge layout and entitlement print for every configured visitor category.
5. A failed print can be identified, cleared and reissued through the agreed support process.
6. The session removes or obscures personal information before the next visitor begins.
7. Staff can identify the issue owner and escalation path for each tested failure scenario.

Performance thresholds should reflect the agreed configuration, network, equipment and test conditions. If a specific transaction time or arrival capacity matters, include the test volume, data set, measurement method and acceptable result rather than treating it as an implied guarantee.

Essential kiosk test cases

Run end-to-end tests with production-like badge stock, representative records and the intended network setup. Include successful journeys as well as malformed codes, duplicate records, missing mandatory fields, changed visitor categories, re-entry, cancelled registrations, printer disconnection, empty consumables, network loss, power recovery and an interrupted session.

Test queue behaviour too. Observe whether visitors can identify the correct kiosk, prepare their code before reaching it and find assistance without blocking the next person. A controlled preview should verify both the technology and the operating procedure. Related requirements for a larger delegate environment are covered in the conference registration system requirements guide.

Requirements checklist for procurement

• Visitor categories and permitted arrival journeys are approved.
• Lookup methods, match rules and exception routes are documented.
• Required fields, data source, import format and cut-off are confirmed.
• Badge layouts, access indicators, stock and reprint rules are approved.
• Kiosk quantity and placement are based on the arrival profile and floor plan.
• Power, connectivity, cable management and fallback responsibilities are assigned.
• Accessibility requirements and an equivalent assisted route are included.
• Privacy notices, screen exposure and data handling are reviewed appropriately.
• Staff roles, support contacts, escalation levels and spare equipment are defined.
• Acceptance criteria cover normal, exception and recovery scenarios.
• Testing uses representative records, equipment, consumables and venue conditions.
• Handover, opening checks, replenishment and end-of-day procedures are documented.

Scope the complete operation

Get Out! Events can help plan and manage RSVP, guest communications, registration operations, check-in, badge coordination, queue planning and wider event delivery. Through GO Labs, the kiosk workflow and supporting tools can be scoped against the approved brief. Feasibility, integrations, resilience and technical outcomes remain conditional on the selected platforms, venue dependencies, data quality and testing arrangements.

A useful procurement brief should therefore ask bidders to respond requirement by requirement, identify assumptions and list exclusions. This makes proposed approaches easier to compare and exposes operational gaps before installation day.