Event entry day checklist for wallet tickets
Animesh Bhattacharjee, Founding Engineer, RevisitUpdated 3 min read
Key takeaways
- The ticket design is done weeks before. Entry day is about staff, devices and a clear rule for problems.
- Each ticket gets in once. A repeat scan shows who scanned it and when.
- Plan for weak phone signal at the door.
The day before
- 01
Issue a test ticket
Add it to a phone and scan it from the staff device, so you know the full path works.
- 02
Charge and sign in
Staff phones fully charged, signed in to the scanner, camera permission allowed.
- 03
Brief the team
Who scans, who handles problems, and who can say yes to an exception.
- 04
Send a reminder
Tell guests to open the ticket from their wallet, not a screenshot.
At the door
The flow is simple. The guest shows the ticket from the wallet, staff scan the QR and see whether it is valid. A valid ticket is checked in and shows as "Ticket checked in" in the activity list. A second scan of the same ticket is refused, with the time it was first used and who scanned it.
- Keep the line moving: ask guests to open the ticket before they reach the scanner.
- Have two scan points for a larger crowd, and give each person one job.
- Do not wave through anyone who "has a screenshot". Scan the live ticket.
When things go wrong
| Problem | What to do |
|---|---|
| Ticket already used | Read the time and name shown. Ask the guest calmly. A friend with a forwarded link may be the cause. |
| Guest cannot find the ticket | Ask for the link or email they were sent, and look for the ticket in their wallet. |
| No signal at the door | The ticket itself opens from the phone. The staff scanner needs a connection, so bring a hotspot or a second device on another network. |
| Wrong gate or date | Send the guest to the correct gate and note it. |
| Late arrival | Decide the rule in advance and tell all scanners. |
After the event
Count the check-ins against the issued tickets. The difference is your no-shows, which is useful for next time.
What this does not cover
Revisit's ticket pass is for tickets you issue. It does not sell tickets, take payment, or control physical doors. See how digital event tickets work for how the pass is made, and Google Wallet tickets for the Google side.
Rehearse a queue with real door equipment
Give two staff members five test tickets and ask them to use the scanners, lighting and positions planned for the venue. Include a valid ticket, one for another session, one already used, one on a dim screen, and one guest who has only their order reference. Time how long it takes to detect the issue and send the guest to the right person.
Place a help desk where a guest can step out of the main line without losing sight of their group. Give it an agreed way to check orders and record exceptions. If staff need to change a guest's status, decide who is authorised to do it and what evidence they record. Review any repeated exception after the doors close. For a two-session event, also check how Google Wallet tickets show session and venue details.
Does the ticket work without internet?
Once added, the pass opens on the phone. Staff scanning needs a connection.
Can one ticket let in two people?
Not unless you design it that way. Issue one ticket per guest.
Can staff undo a check-in?
Counter actions can be undone, and the first entry stays on record.