A QR check-in flow lives or dies in the first 15 minutes of an event. Below is the readiness checklist we walk every NGO partner through before doors open. Tick off all seven and the entrance becomes a non-event — exactly what you want.
1. Ticket design with a high-contrast QR
Print or render the QR with strong contrast and at least a 2cm margin. Avoid placing it over photos, gradients, or dark backgrounds. Include a human-readable backup code underneath so volunteers can key it in if a scan fails. Test print one ticket and scan it under venue lighting before sending the batch.
2. Volunteer device prep
Decide whether volunteers use their own phones or pre-issued tablets, and lock the choice 48 hours before. Pre-install the scanner app, log everyone in, run a connectivity test, and put each device at 100% battery with a power bank assigned. Brief volunteers on the one thing they should NOT do — usually “don’t manually mark a guest checked-in unless I say so.”
3. Offline fallback plan
Assume venue Wi-Fi will fail. Have an offline-capable scanner mode, or a printed guest list sorted by last name plus QR code prefix at every station. Define exactly when volunteers should switch to fallback (e.g. “two scans fail in a row”) and who they should ping.
4. Station signage
A simple A3 sign at each station with “Check in here — have your QR ready” cuts the most common cause of slowdown: confused arrivals. If you have multiple ticket types (member, guest, VIP, press), give each its own lane and colour.
5. Redemption logic for meals and gifts
If guests redeem a meal voucher, swag bag, or door gift, the system should mark the redemption against their record, not just check them in. Decide whether double-redemption is blocked outright or just warned, and document the manual override process for edge cases.
6. Live attendance dashboard
The organiser needs a live count by ticket type, by entrance, and by minute. This is what tells you to open a second lane, send a runner with extra lanyards, or start the programme on time. Put the dashboard on a tablet at the ops table — not buried in someone’s laptop.
7. Post-event report
Decide before the event what the report needs to show: total attendance, no-show rate, peak arrival minute, redemption counts, and any flagged exceptions. Have the export ready within 24 hours while the event is still fresh.
Running an NGO event soon? Talk to PHB Solution about our event check-in platform, used by community organisations across Hong Kong.