QR codes for events and conferences

Events run on last-minute changes, and print deadlines do not care. QR codes — especially dynamic ones — let the printed signage stay fixed while everything behind it stays current: the schedule, the room assignments, the feedback form that goes live at 4pm.

Where codes do real work at an event

Registration and check-in. A code on the pre-event flyer or lobby banner opens the registration or check-in page — attendees start the process in line rather than at the desk.
The live schedule. The single highest-value code at any conference. Rooms change, talks slip, speakers cancel; a code on every sign pointing at a living agenda page beats reprinting the program, every time.
Session feedback. A code on the podium sign or final slide, straight to a short form. Response rates collapse within minutes of a talk ending — catch people before they stand up.
Speaker bios and slides. Outside each room, one code per track to bios, abstracts, and post-talk slide decks.
Venue WiFi. A WiFi code beside the schedule code gets attendees online without a help desk queue.
Badges. A vCard code per badge turns contact exchange into one scan — no badge-scanner hardware rental.
Sponsor placements. Codes on sponsor signage with per-sponsor scan counts give sponsors a number instead of a vibe when you report back — a genuinely stronger sponsorship story.

Why dynamic codes are the event default

Signage goes to the printer days or weeks before doors open, and the one certainty is that something will change afterward. A dynamic code separates the two timelines: ink freezes at the print deadline, destinations stay editable through the closing keynote. Concretely: print “scan for today’s schedule” on everything, and if Friday’s room swap breaks your agenda URL, you fix it in the dashboard in thirty seconds instead of running new signs. After the event, repoint every code at the photo gallery or next year’s save-the-date — the deployed signage keeps working for you until it comes down. Static codes still make sense for things that cannot change, like a badge vCard.

Producing badge codes at scale

For a few hundred attendees, badge codes come from the registration export and the CSV batch workflow: one row per attendee, the data column pointing at their contact info or profile URL, the filename column set to their registration ID so the badge-printing merge can match files to names automatically. Generate, download the ZIP, hand it to whoever runs the badge template. A 300-badge batch generates in about a minute, in the browser, with the attendee list never leaving your machine — worth noting when the list is personal data you would rather not upload to a third-party tool.

Signage sizing: the 10:1 rule, applied to venues

Placement	Typical scan distance	Minimum code size
Podium sign / table card	0.5 m	5 cm
Room-door sign	0.5–1 m	5–10 cm
Lobby poster / easel	1–2 m	10–20 cm
Stage backdrop / projected slide	3–10 m	30–100 cm

Code width of at least one-tenth the scanning distance, and when a sign serves both the front row and the back, size for the back. Projected codes deserve a special note: put the code on its own slide, large, for a full minute — a small code in a slide corner shown for eight seconds mostly generates blurry photos of your slide.

Placement craft from real venues

Caption everything. “Scan for schedule” / “Scan to leave feedback” — a code without a promise gets skipped by busy people between sessions.
Chest height beats eye height for scanning comfort, and never behind glass at an angle to the lighting rig.
Matte lamination. Convention-hall lighting is glare-hostile; gloss signage fails where matte scans clean.
One code per sign. A sign with four codes converts worse than four signs with one purpose each. Prioritize per location: schedule near rooms, WiFi near seating, feedback near exits.
Contrast check under venue light — brand-colored codes that pass in daylight can fail under warm stage lighting. Dark on white is the safe answer for anything mission-critical; see the branding guide for how far you can push it.

Reading the analytics during and after

Per-code scan counts turn the event into data while it is still running: the schedule code’s spikes map your real break behavior (useful for timing announcements), room-door codes show which tracks pull walk-up interest, and a dead sponsor placement can be moved to a better wall between sessions rather than after the retro. Afterwards, the same numbers write the wrap-up report — “the schedule was opened 1,400 times, feedback conversion doubled when we moved the code to the final slide” — and give next year’s signage plan an evidence base. The scans-over-time view in the analytics dashboard is the one you will screenshot.

Pre-event checklist

Every code test-scanned from final printed signage, at realistic distance, under venue lighting — not from your monitor.
Destination pages checked on a phone over cellular, since venue WiFi will be saturated by 10am.
Dynamic codes named clearly in your collection (“Lobby easel — schedule”), so mid-event edits under pressure hit the right code.
A fallback short URL printed under the most critical codes for the no-smartphone case.
Feedback form set to go live before the first session ends, not after lunch.

A production timeline that survives contact with print deadlines

Four weeks out: list every code the event needs — schedule, registration, feedback, per-track, WiFi, sponsors — and create the dynamic ones now, even though half the destinations do not exist yet. Point placeholders at the event homepage; the printed pattern is what the deadline needs, and it is already final.
Three weeks out: signage files go to the printer with codes placed at the sizes from the table above. Because every code is dynamic, nothing about a late agenda change can invalidate the print order — this is the deadline decoupling doing its work.
One week out: destinations go live and every code gets repointed from placeholder to real page. Test each from the printed proofs, not screens.
Day before: walk the venue with the signage plan, scan every hung sign from visitor distance under actual lighting, and fix mounting angles while there is still tape and time.
During: one person owns the collection dashboard. Room swap? Repoint the track code. Feedback form ready early? Flip it live. Every fix is seconds, and no one touches a printer.
After: repoint everything to the thank-you/photos page, export the scan story for the wrap-up report, and archive the code names for next year — the same physical banner stock can even be reused if the design is date-free.

Recurring events compound the value

For a monthly meetup or an annual conference, the code inventory becomes infrastructure. Date-free signage — “Scan for tonight’s agenda” — gets reused every edition with only the destination changing, which quietly eliminates the largest recurring print cost. Year-over-year scan data also answers planning questions with numbers: whether the lobby easel outperforms the elevator poster, whether feedback conversion improved after moving the code to the final slide, which sponsor placements are genuinely premium inventory (and can be priced accordingly). Series organizers who name their codes carefully — lobby-schedule, roomA-track, badge-vcard — are effectively building a small, reusable measurement system for free alongside the event itself.

Common questions

Can I change where a code points mid-event?: Yes — that is the core dynamic-code feature. Edits take effect on the next scan, within seconds.
How many dynamic codes does a typical event need?: A small conference runs well on 5–10: schedule, registration, feedback, a couple of track codes, WiFi (static), and sponsor placements. The Personal plan covers a simple event; Pro covers a multi-track program with per-sponsor codes.
Do attendees need an app?: No — native cameras handle URL, WiFi, and vCard codes on any phone from the last several years.
What about ticket-scanning at the door?: Different problem — admission control needs a ticketing platform with validation. These codes cover information flow and engagement around the event, not entry security.
Projected codes: do they work?: Well, if you give them a dedicated slide, real size, and a full minute. Screens have perfect contrast; time on screen is the constraint.
Can sponsors get their scan numbers?: Yes — give each sponsor placement its own dynamic code and read counts per code. It is the difference between “great visibility” and “217 scans over two days” in the post-event report.
What about hybrid or virtual attendees?: Codes shown on stream slides work exactly like projected ones — remote viewers scan their own screen. Give the stream its own dynamic code so online engagement is counted separately from the room.
Paper programs: still worth printing?: A one-page program with the schedule code on it is the sweet spot — cheap to print, never out of date, and it hands every attendee the code in their pocket instead of relying on wall signage alone.

Make your event codes →