A useful guest list starts with correct tickets
Distinguish the order buyer from the people attending with the tickets. Check names and types where required without collecting unnecessary data. The fictional list demonstrates search and check-in; it is not a production account or import tool. In the actual app, permissions determine which events and guests are accessible.
Agree how to help visitors without an identifiable ticket.
Give the door team two clear views
Recent arrivals help verify a just-completed check. Guests not yet checked in help locate someone at the entrance. Select the correct event and entrance before opening. A long list is less useful when nobody understands its current status. This demo stores changes only locally and offers a reset button.
Use individual scanner permissions rather than shared administrator credentials.
Make manual check-in deliberate
Tapping a name should not immediately register admission. Review the guest, ticket and instructions before confirming. Already-used admission must not be treated as unused again. The demo therefore provides a separate confirmation panel with Back and Confirm demo check-in. In operation, rely on current records rather than an old downloaded list alone.
Route payment and identity questions to the designated staff member.
Treat the list as operational information
Give access only to staff who need it for their role. Do not share the full list through public links or group chats. Plan connectivity and devices at the venue. Attendance differs from ticket revenue and order count. Retain and remove personal data under appropriate arrangements; a marketing demo does not replace your event privacy policy.
Before opening, test search, scanning and duplicate-scan feedback.