Events
Event QR codes that survive a schedule change on the day
Print signage and badges with dynamic codes so that when a session moves rooms an hour before doors open, you edit one destination instead of reprinting anything. Separate codes for schedule, map, check-in and feedback keep each one simple and fast to load.
The four codes most events actually need
| Code | Points to | Where it goes |
|---|---|---|
| Schedule | Session list or agenda page | Entrance signage, printed program, badge back |
| Venue map | Floor plan or wayfinding page | Entrance, near stairwells, program |
| Check-in / ticket | Registration or ticket scan page | Confirmation email, not usually printed signage |
| Feedback | Post-session or post-event survey | Exit signage, badge lanyard card, follow-up email |
Handling a session that moves rooms
This is the case that makes a dynamic code worth it at an event. If the printed schedule code points at a live web page rather than a static image or printed timetable, you update that page the moment a room changes and the same signage in the hallway is now correct.
Announce the change through whatever live channel you have — app notification, stage announcement, volunteer word of mouth — because not everyone re-scans a code they already used once. The code fixes the printed material problem, not the awareness problem.
Badge and signage placement
- Badge back is a reliable spot for a schedule or wifi-details link, since attendees glance at their own badge more than they check hallway signage.
- Freestanding signage at entrances and room doors needs a larger code than a badge — people are reading it from a few steps away, not holding it in their hand.
- Avoid putting a code on something that gets folded, clipped, or worn against fabric all day. Lanyard cards and printed badges take wear; check a sample after a few hours of handling.
- Don't put the feedback code next to the schedule code. People scan schedules constantly through the day and feedback only once at the end; keeping them visually distinct avoids wrong scans.
Check-in and ticket pages
A code on a ticket confirmation typically points at a page confirming the ticket or showing an entry pass, not a schedule. Keep this separate from marketing codes: a ticket-holder scanning at the door needs a fast, simple confirmation, not a landing page with an agenda and sponsor logos.
For multi-day events, consider whether the check-in code needs to be scanned once or every day, and make sure the linked page makes that obvious rather than assuming attendees remember from the day before.
Venue wifi reality
Conference center and hotel wifi is frequently congested at exactly the moments a lot of people scan at once — right after a keynote, at the doors before a session starts. A code that depends on a redirect and then a heavy page load will feel broken in that moment even though nothing is actually wrong.
Keep the destination page light: fewer large images, no autoplaying video, text-first schedule information. If you expect genuinely unreliable connectivity, consider printing a basic paper schedule as backup for anything time-critical, the same logic as keeping paper menus in a restaurant.
Post-event feedback and follow-up
- Put the feedback code where people naturally pause at the end: near the exit, on the last page of a printed program, on a table by the coffee.
- A single post-event code is usually enough; per-session feedback codes work for multi-track conferences but add scanning fatigue if every single talk asks for a separate scan.
- Re-point the code the day after the event to a thank-you page or the recording archive, so the same signage and badge cards keep being useful rather than dead-ending on a closed survey.
When not to rely on a QR code
Emergency information, accessibility details and anything safety-critical should be printed directly, not gated behind a scan and a working phone. Use QR codes for convenience — schedules, maps, extras — not for anything someone needs when their phone is dead or the network is down.
Common questions
- Can I change a session room on a printed schedule code after signage is up?
- Yes, if the code points at a live schedule page rather than a static PDF snapshot. Edit the page and the same signage shows the correct room on the next scan.
- Should check-in and schedule share one QR code?
- No. Check-in needs a fast, simple confirmation page; a schedule needs a browsable agenda. Keeping them separate avoids confusing either audience.
- Where should the feedback code go?
- Somewhere people naturally pause at the end of the event — exits, the last page of a program, or a table near the coffee station — not next to a code people scan repeatedly through the day.
- What if venue wifi is unreliable?
- Keep destination pages light and text-first, and print backup information for anything time-critical. A slow or failed load right after a keynote is a capacity problem, not a QR code problem.
- How big should a QR code be on entrance signage?
- Larger than a badge code, since people read it from a few steps away rather than holding it in their hand. See our size guide for the distance-to-size ratio.
Keep reading
- QR code size and scan distanceThe 10:1 rule, minimum print sizes and quiet-zone requirements.
- Dynamic QR codesHow editable QR codes work and why they beat static codes in print.
- QR code analyticsSee when, where and on what device your printed material gets scanned.
- Marketing campaignsAttribute offline campaigns with one code per placement.
Print once. Change the destination anytime.
Create a free account, generate your code and edit where it points whenever you need to.