Manual for event day
Give the entrance team a clear process before the first guest arrives.
Fast entry depends more on preparation and clear decisions than on scanning speed alone. Entriza separates tickets, tables, guest-list entries and rewards so staff can use the correct mode and understand the result. This manual covers preparation, live scanning, exceptions, privacy and the handover after the doors close.
Assign roles, stations and escalation before opening
Decide who supervises entry, who scans tickets, who handles guest lists or tables and who can resolve an exception. Give each person their own account and the narrowest role required for that event and station. Do not share an organizer password across devices. Every staff member should know the event manager, the refund contact and the point at which a queue issue must be escalated instead of improvised.
What to do
- Confirm the event, station and scan mode on every device.
- Record the event manager's contact and exception authority.
- Remove unrelated events and administrative functions from entrance access.
Prepare devices and the physical queue
Use charged phones with working cameras, reliable data access and a screen that staff can read outdoors or in low light. Open the scanner and sign in before guests arrive. Place the scanning point where staff can stop a duplicate or blocked credential without holding up everyone behind it. A manual code is a fallback for camera problems, not a shortcut for lists of codes copied into chat.
What to do
- Charge devices, carry approved power banks and verify connectivity.
- Check the camera, screen brightness and scanner permissions.
- Create a separate place for manual review and keep the main line moving.
Scan once and follow the result
Select Ticket mode for ticket QR credentials and use the dedicated modes for tables, guest-list entries or rewards. The first valid ticket scan records admission atomically. A later scan should show that the code was already used rather than admitting another person. Read the plain-language result before waving anyone through. Avoid repeated rapid scans because they make the interaction harder for both staff and guests without changing the credential state.
What to do
- Frame one QR code and wait for the result on screen.
- Confirm the guest only after a valid response.
- Move blocked, revoked, refunded or already-used results to the exception point.
Handle guest lists, tables and rewards separately
A guest-list name is not a paid ticket, a table package can cover several people and a reward QR is not an entrance credential. Use the matching scanner mode and confirm the scope shown on screen. Reward staff should check validity, station, age and any ticket requirement before redemption. Once redeemed, a reward cannot be treated as unused simply because the guest still has a screenshot.
What to do
- Check quantity and package details before completing a table admission.
- Use the guest-list workflow for named entries rather than searching ticket orders.
- Redeem rewards only at the assigned station and offer the stated non-alcoholic alternative where required.
Use the exception and emergency path carefully
When a credential is unclear, verify the selected event and scan mode first. Ask the event manager to review the order or guest record through the authorized dashboard. Do not accept a bank notification, social message or editable PDF as a replacement for a valid credential. If connectivity fails, use only the audited emergency process activated by the responsible manager, record exceptional decisions and return to the live scanner as soon as service is restored.
What to do
- Keep the guest out of the admitted flow while the record is reviewed.
- Escalate identity, payment and refund conflicts to the named manager.
- Never photograph IDs, payment cards or QR codes on a personal phone.
Protect guest data and close the operation
Entrance staff should see only the information needed to decide admission. Avoid printed exports, shared spreadsheets and screenshots of guest records unless an approved emergency process specifically requires them. After the final entry period, compare scanner and operational counts, document unresolved exceptions and sign out shared or temporary devices. Remove event access that is no longer needed and send remaining customer cases through structured support.
What to do
- Reconcile admitted tickets, tables and guest-list counts with the event manager.
- Record unresolved cases without copying unnecessary personal data.
- Sign out devices and close temporary staff access after the shift.
Thirty minutes before doors open
0 of 5 completed
The checklist remembers your progress in this browser.
Manual for event day
Common entrance questions
The scanner says the ticket was already used. Should we scan again?
No. Move the guest to manual review and let the authorized event manager inspect the admission and order record. Repeated scans do not restore the credential and should not replace an accountable decision.
The internet connection has failed. Can we admit everyone from screenshots?
No. The responsible manager must activate the approved emergency process. Screenshots alone cannot show whether a credential was refunded, transferred, revoked or already consumed.
A guest has a reward QR but no ticket. Is the reward valid?
Read the reward result and campaign rule. Some campaigns require a valid event ticket and others may have an age or station restriction. A reward credential must never be scanned as an entrance ticket.