A QR code on a ticket is not a decoration. It is the thing that lets a volunteer with a phone decide, in a second, whether this person paid and whether they already walked in. If your “ticket” is a WhatsApp screenshot of a UPI payment, you do not have check-in. You have a queue and an argument.
This is the organizer’s guide: what to set up before the doors open, how the scan should behave, and what to do when the network at the gate is bad.
One person, one code
Each guest gets their own ticket after they register or pay. The code encodes that ticket, not the event poster.
That gives you three facts at the door:
- This ticket belongs to this event.
- It has not been scanned yet.
- You can count entries without a clicker.
Sharing one code in a group chat is the failure mode. A proper scan marks the ticket used, so the second phone that shows the same code is rejected. Tell guests this on the event page so the person who “just forwarded it” is not shocked at the gate.
What to set up the day before
- A test ticket. Buy or register one with your own number. Scan it. Scan it again and confirm the second scan fails.
- The phones. Two at a minimum for a fest gate, charged, with the check-in screen already logged in. One phone is a single point of failure.
- A role split. One person scans. Another looks at bags or answers questions. The person scanning does not also solve sponsorship arguments.
- A help desk two metres away from the scan line, for name mismatches and genuine payment problems. If help happens in the scan line, the line stops.
- A printed guest list only as a fallback if you have no signal at all. It goes stale the moment someone buys a ticket at the door. Prefer the live list.
The sale that creates the ticket is covered in how to sell tickets online in India.
How a good scan feels
The volunteer should not interpret a code. The screen should say one of:
- In. Name, ticket type. Wave them through.
- Already used. Stop. Point them to the help desk, do not rescan five times.
- Not for this event, or not found. Stop. Same desk.
Speed matters more than a speech. At a college fest gate, a scan that takes ten seconds of tapping will not survive the rush before a pro night.
If you are checking in teams — a hackathon, a BGMI squad — scan the captain and match the roster to the form before they sit down. That flow is in how to host a BGMI or Valorant tournament.
When the network is bad
Campus basements and grounds are where check-in goes to die.
- Test the exact spot the table will stand, at the time of day you will use it.
- Have a second network (a phone hotspot) ready. Write the password on the inside of the table, not in the group chat an hour later.
- Do not switch on a brand-new phone ten minutes before gates. Log in the night before.
If you must pause scanning, pause the gate. Letting people through “and we’ll note names” creates a list nobody reconciles.
What the count is for
The number of successful scans is the footfall you can say out loud to a sponsor. Registrations are intent. Check-ins are people who showed up.
Put that number in the post-event report. The sponsorship side of that report is in how to get sponsors for a college fest.
Also use it the same night: if a session is full, stop scanning into it. If a session is empty, you still know, instead of guessing from the doorway.
Door rules worth writing on the table
- A screenshot of someone else’s ticket is a used or invalid scan. It does not become valid because they travelled.
- Name on the ticket should match an ID if you said it would. Do not invent that rule at the gate.
- Volunteers and artists are on a list or they have a ticket. “They know me” is not a ticket type.
- Cash at the door, if you allow it, still becomes a ticket in the system before they walk in. Otherwise your count and your cash box will disagree.
Ready to scan?
Create the event, issue a QR ticket with each registration, and run one test scan before you print the volunteer briefing.