Conference check-in with QR codes and digital passes
A practical guide to getting attendees from registration to their first session.
Conference check-in connects a confirmed registration to a person arriving at the venue. A useful workflow gives each attendee a unique pass, lets staff validate it at the door, and provides a clear way to handle exceptions. This guide explains how to plan that workflow with PassEngine, from pass creation to multi-day entry.
1. Separate registration from arrival
Start with the system that collects registrations or sells tickets. Decide when a registration is confirmed and who is responsible for issuing the attendee pass. For a paid conference, issue access only after your registration system confirms payment.
PassEngine handles digital passes and QR validation. Keep your registration form, payment workflow, agenda, and badge-printing process alongside it. If you automate issuance through the API, store the returned pass reference with the registration so a repeated request does not accidentally lead to multiple passes.
2. Create a conference pass for each attendee
Create a branded template with the conference name and prepare one pass per attendee. Set the validity window to cover arrival through the end of permitted access, checking the times against the venue’s local time. Use a test attendee before issuing the real passes.
Add the information staff need to recognize the registration, such as attendee name and ticket category. Keep internal notes private. A visible “VIP” or “Workshop” field is a label: it does not by itself enforce room-level access. Define how staff will verify those permissions or use a separate pass for an independently controlled workshop.
3. Send the pass before conference day
Share the attendee’s pass link in your confirmation or pre-event message. Include the venue entrance, opening time, and contact details for registration support. Ask attendees to open their pass before travelling, so problems can be resolved away from the entrance queue.
Attendees can use the pass page or add the supported pass to Apple Wallet or Google Wallet from that page. Wallet storage gives them another way to find the pass at arrival. Include the original link in reminders and keep a help desk available for people with a flat battery or a missing email.
4. Choose single entry or conference re-entry
A single-use pass fits an event where one successful scan completes admission. After it is used, it cannot support normal re-entry. If delegates need to leave for lunch and return, plan a multi-use pass instead and set any usage limit to match the access you actually intend to allow.
For a two-day conference, a validity window spanning both days and a suitable multi-use configuration can support repeated entry. A total usage limit is not the same as one entry per day. Test your selected settings with the actual arrival and re-entry scenarios before sending passes.
5. Run a rehearsal at the registration desk
Invite the check-in team with the access they need and open the built-in scanner on the devices they will use. Test camera permission, lighting, and internet connectivity at the entrance. Scan an active test pass, then try a used single-use pass, an expired pass, and a revoked pass so staff recognize each outcome.
Ask staff to act on the validation result, not just the appearance of the QR code. A copied QR code is still a copy of the same credential, not proof of the holder’s identity. If your admission policy requires an identity check, explain that policy before attendees arrive.
Keep a separate queue for missing passes and registration changes. Agree on a manual fallback for connectivity problems, record any manual admissions, and reconcile them afterward. A saved wallet pass does not make server-side validation available offline.
6. Review attendance without double-counting
After the conference, review scan history against your registration records. Count distinct attendee passes when estimating attendance: a delegate who re-enters several times creates more scans without becoming several attendees.
Entry scans show that a pass was validated at the entrance. They do not establish time spent at the conference or attendance at individual talks. If those measures matter, define a separate session check-in workflow before the event and explain it to attendees.
Conference check-in checklist
- Confirm how registrations become attendee passes.
- Check dates, ticket categories, and re-entry settings.
- Send a test pass and open it on the devices your audience uses.
- Rehearse successful and rejected scans with the check-in team.
- Prepare a help desk, backup connectivity, and a manual admission log.
- Compare unique checked-in passes with confirmed registrations.
Conference check-in questions
Do attendees need to install a conference app?
No separate conference app is needed to open a PassEngine pass link in a browser. Attendees can also add a supported pass to Apple Wallet or Google Wallet.
Can one QR pass cover a multi-day conference?
A multi-use pass can cover repeated entry within its validity window. Choose usage limits carefully and test the planned re-entry flow. Separate workshop admission may need a separate pass or a staff check.
Does a digital conference pass replace a printed badge?
It can serve as the entry credential, while a printed badge can still help people recognize names and organizations. Decide separately whether your conference needs physical networking badges.
Can we use our existing registration system?
You can share passes after confirming registrations in your existing system. For automated issuance, review the PassEngine API and your plan’s integration features, and test the workflow before launch.