Prepare one complete station first
Build and test a reference station before repeating the configuration across the fleet. Use the intended tablet model, operating system, application, enclosure, charger and peripherals. Registration, a sales demonstration and a self-guided catalogue have different failure points; give each role its own test.
Write down the approved application and content version. Identify who owns the devices, who can change their settings and who will restore them after the event. A borrowed office tablet may contain personal notifications, saved logins or files that should never become part of a public demonstration.
Match setup to the role
| Role | Essential check | Fallback to agree |
|---|---|---|
| Staff registration | Find the correct attendee, complete check-in and handle an uncertain result | Staff escalation when the record cannot be confirmed |
| Self-service form | Keyboard, validation, confirmation and clearing the previous visitor's entries | Assisted completion without exposing another person's data |
| Product demonstration | All media and languages open on the actual device | Approved local presentation or another prepared device |
| Mobile sales tool | Battery, connection changes and resuming an interrupted conversation | Charging handover and a defined way to recover saved work |
Control the public session and keep recovery possible
Choose the restriction method with whoever manages the devices. Apple's App Lock documentation describes a managed configuration that keeps a selected app open and returns to it after restart. Supported enrollment and settings matter; the label “kiosk mode” alone does not describe a finished setup.
Keep administrative recovery instructions with authorised staff, away from the public interface. Test what happens when someone presses available hardware buttons, follows an external link or leaves a session unfinished. Confirm that restrictions do not accidentally remove an accessibility feature required by a visitor.
Schedule software updates early enough to repeat the workflow test afterwards. Keep a record of the tested versions and agree how urgent changes will be approved. An update performed on arrival may change permissions, sign-in screens or application behaviour at the moment the team has the least time to investigate.
Plan power through the whole day
Test charging with the final enclosure and cable arrangement while the real application runs. Check that connectors remain accessible and the support does not press on them. Label chargers and devices so staff can identify the right replacement without dismantling the desk.
Apple's battery guidance explains that temperature and battery condition affect operation. Do not base an event shift on an advertised runtime measured under different conditions. Observe the prepared device at the intended brightness and workload, then choose continuous power or an organised swap plan with the technical team.
Worked example: four desks and one prepared spare
Imagine a hypothetical registration area with four active tablets and one agreed spare. Before opening, each active desk completes a test registration in a test dataset. The spare carries the same approved app version and is ready for its assigned role; a sealed tablet requiring account setup is not an immediate replacement.
During the rehearsal, desk three loses its connection after submission. Staff first check whether the record arrived before trying again. If they switch devices, they follow the agreed record-recovery procedure and identify the affected desk. The exercise reveals whether the problem is a single tablet or the shared network.
The spare count here is an example, not a recommended ratio. Decide it from the consequence of a failed station, available support and measured replacement time. Additional devices do little when they share the same untested configuration problem.
Opening and closing checks
Open the approved app, check the content version and verify the correct event or dataset.
Test touch, keyboard, camera or scanner where required, power and the actual network.
Complete one test workflow and confirm its result in the receiving system.
Check reset, idle behaviour, restart and the staff help route.
At closing, reconcile pending records, secure the devices and assign responsibility for charging and the next opening.
Common mistakes include testing only the first screen, confusing Wi-Fi connection with application availability, leaving the previous visitor's information visible and storing the spare without preparing it. Device return also needs an agreed process for data export, account removal and clearing event data.
Provide the workflow, device ownership, event hours and application access requirements when discussing event applications. For fixed stations, include the display and kiosk equipment requirements so software and physical setup are reviewed together.