Event badge QR codes from a registration spreadsheet

Almost every registration platform exports to Excel, and that export is all you need to produce a scannable badge for every attendee. The payoff is at the door: a QR scan takes a second or two, while finding a name on a printed list takes fifteen to thirty. Multiply that across three hundred people arriving in the same twenty minutes and it is the difference between a smooth entrance and a queue out of the building.

Encode the ticket reference, not the attendee

Badges get dropped, photographed and left on tables. Encode a unique ticket reference and let your check-in system resolve it to the attendee record. Nothing personal then lives on the badge, and a lost badge leaks nothing.

Print the name and company on the badge in normal text — that is what other attendees read. The QR code is for the door, not for humans, so it only needs the reference.

Preparing the registration export

1. Export to .xlsx with field names in row 1 and one attendee per row.
2. Check every attendee has a unique reference. If the platform only gives you sequential IDs, generate a random reference column before uploading.
3. Deduplicate. Registration exports frequently contain the same person twice from repeat sign-ups. Two badges for one person means a confusing double check-in.
4. Trim the columns to what the badge and check-in need — reference, name, company, ticket type.

Handling ticket types

Multi-track events usually need the door to know more than "this person is valid": speaker, VIP, exhibitor and day-pass holders have different access. Two workable approaches:

• Reference only (recommended). The check-in system knows the ticket type and displays it on scan. Upgrades and corrections work right up to the moment someone arrives, because nothing about the type is printed.
• Reference plus type in JSON. Encoding {"Ticket":"TKT-8F3K9QD2","Type":"Speaker"} lets a scanner show the type offline with no lookup — but if someone's ticket is upgraded after printing, the badge is wrong and must be reprinted.

Use colour-coded lanyards or a printed band for visual identification instead of baking the type into the code. Security staff can read a colour across a room; nobody scans a badge to check it.

Preventing duplicate scans

A QR code is a static string. It cannot know whether it has been used, so duplicate prevention always lives in the scanning system. At minimum, mark each reference as checked in on first scan and have the app show a clear warning on any repeat — with the original check-in time, so staff can tell an innocent double-scan from a badge being passed back out of a window.

Plan for the venue wifi failing

This happens constantly, and it takes down cloud-based check-in exactly when the queue is longest. Before the event, load the attendee list onto each scanning device so it can validate offline and sync when connectivity returns. Also print a paper fallback list sorted by surname. It is unglamorous and it has saved a great many door teams.

Badge printing that scans first time

• Minimum 2 × 2 cm. Door lighting is often poor, and scanning happens fast.
• Matte, not gloss. Glossy laminate reflects venue spotlights straight into the camera.
• Position consistently — bottom-right of every badge, so door staff scan without hunting.
• Mind the lanyard. A badge that flips to a blank back doubles check-in time. Double-sided printing or a clip that resists rotation solves it.
• Test the whole chain a week out: print a real badge, on the real stock, and scan it with the real device under similar lighting.

On-the-day walk-ups

Some attendees always register at the door. Pre-generate a batch of blank badges with unused references, keep them at the registration desk, and assign one to each walk-up in your system as they arrive. Trying to print individual badges on the spot creates exactly the bottleneck QR check-in was meant to remove.

Frequently asked questions