Agenda, venue map, speaker list and feedback form — all reachable from the badge, and all editable after the badges are printed.
A room change is an edit, not a reprint of 800 badges.
Per-stand codes give exhibitors scan counts instead of anecdotes.
A code on the seat back collects reactions before the attendee leaves the room.
Badge stock is ordered weeks ahead and the agenda keeps moving until the morning of the event. That mismatch is exactly what a dynamic code solves: the badge carries a code that never changes, pointing at an agenda page you edit as rooms swap and speakers drop out. The alternative — reprinting eight hundred badges because a keynote moved rooms — is the situation this is worth setting up to avoid.
A calendar-event code on session signage lets attendees save the slot to their phone diary with the title, time and room already filled in. A venue-map code at each entrance answers the most repeated question of the day. A feedback code on the seat back collects reactions before people stand up, which is when responses are both honest and likely. A per-stand code gives each exhibitor a scan count instead of an anecdote about footfall.
Scan data by hour is the closest thing to an attention map an event produces. It shows when the room actually filled rather than when the schedule said it would, which sessions pulled people away from lunch, and which stands were busy at times the organiser assumed were quiet. That is the material for next year’s floor plan and running order, and it exists only if the codes were separated before the event rather than after.
Yes. The event type encodes the title, time and location so the phone offers to save it.
Dynamic codes, yes — repoint them at the new agenda. Static codes carry this year’s details permanently.
Not yet. These codes carry links and data; scanning for entry control needs a ticketing system.
Build the agenda, map and feedback codes in one session.