QR Codes for Events and Ticketing: Check-in, Badges and Signage

Events are the hardest environment most QR codes will ever face. Five hundred people arrive within forty minutes, the venue wifi buckles under the load, the lighting is unpredictable, and every minute spent queueing is a complaint on social media. A conference code has to work on the first attempt, on a stranger's phone, while someone is behind them in the queue.

Decide whether the code needs the internet

This is the first and most important decision, and it is usually made by accident. There are two quite different kinds of event code.

Ticket and check-in codes almost always validate against a server: the scanner looks up an identifier and marks it used. Those need connectivity on the scanning side, and no amount of clever encoding will change that.

Information codes — the agenda, the venue map, the speaker list, the feedback form — can be made to work offline if you encode the content itself rather than a URL. A plain-text or vCard QR code needs no network at all. If your venue has a phone-signal dead spot, which most basements and exhibition halls do, consider encoding critical information directly rather than linking to it. Our comparison of static and dynamic codes explains the trade-off in more detail.

Assume the venue network will fail

Plan for the worst case explicitly, because it is the normal case. Ask the venue for the real attendee wifi capacity, not the marketing figure, and test it with fifty devices, not two. If you cannot rely on it, three things help enormously:

• Pre-load the content. Send the agenda by email the night before and put the code on the printed programme as a convenience, not as the only route to the information.
• Use offline-capable codes for anything critical, encoding text or contact details directly instead of a URL.
• Give scanners a manual fallback. Every check-in desk should be able to search by name or booking reference when the code will not load. This is unglamorous and it saves the day.

Badges and lanyards: the sizing trap

Badge codes get scanned at close range by someone holding the badge, or at arm's length by a scanner leaning across a table. That argues for a reasonably large code, but a badge is small and a lanyard swings. The usual failure is a code printed too small to scan while the wearer is moving.

A practical minimum for a badge is about 25 x 25 mm on a flat, matte insert. If the badge is going to be clipped to clothing and read while worn, go larger — 30 mm and up. Avoid printing codes on curved or flexible badge surfaces, and never place one across a fold or near a lanyard clip that can cover part of the pattern.

Print the attendee's name large and scannable-by-eye as well. Staff will always fall back to reading names, and a badge that only works with a scanner slows the queue when the scanner is the problem.

Signage: distance is everything

Codes on signs fail because they were sized for a poster and installed as a banner. As a working guide, the code should be roughly one tenth of the scanning distance: for a sign people scan from two metres, print a code at least 20 cm across. For a wall at five metres, you need half a metre, which usually means the code is the sign.

Registration-desk signs are the exception — people walk right up to them, so 40–60 mm is plenty. Put the code at standing eye height, not at the bottom of an A-board, and always add a short instruction ("Scan to check in") because a bare code with no call to action gets ignored.

Our print sizing guide gives distance-based minimums for each format.

Screenshots, sharing and ticket fraud

Any code that represents an entry right can be photographed and forwarded. A static code is especially exposed: whatever it encodes is fixed, so a screenshot is as good as the original. If your code grants entry, free food, or anything of value, it should not be a static code at all — it should be a rotating or single-use credential issued per attendee.

Where you must use printed codes for anything valuable, add a human check alongside the scan: staff confirm a name, or the code is combined with a wristband. And be aware that the security conversation is wider than tickets — QR code security risks covers overlay stickers and malicious substitution, which matter at events because attackers know codes are trusted.

Where codes genuinely help at an event

• Session feedback. A code on the back of the room or at the exit, linked to a one-question form, reliably outperforms an email survey sent a week later.
• Speaker contact cards. A vCard QR code on a slide lets the room save contact details without typing anything.
• WiFi access. The single highest-use code at most events. See sharing WiFi with a QR code — and put it everywhere, because everyone asks.
• Sponsor lead capture. Works well, but tell attendees what they are opting into before they scan.
• Next-year signup. Put the early-bird code where people linger: lifts, coffee stations, the back of the printed agenda.

Test the whole flow the day before

Walk the actual route with the actual printed materials. Scan the code at the desk from where a person will stand. Scan the badge while it is being worn. Load the destination page on a congested network with fifty other people online. Print a spare set of codes, because something always gets spilled on.

The failure mode to watch for is a code that works in the office and not in the venue, which is almost always either lighting (dark exhibition halls with bright spotlights create glare) or network. Test in the venue, not in the office.

FAQ

Related guides

For network setup, sharing WiFi with a QR code is the single most useful companion piece. Badge and card codes are covered in QR codes on business cards, sizing for signage in the print sizing guide, and the trust implications in QR code security risks.