QRForge

QR codes for events

Check-in, schedules, and session feedback in one scan.

Recommended: Dynamic URL
๐Ÿ“ท Image placeholder
A conference attendee scanning another attendee's badge vCard QR at a networking event
Suggested source: Your own photo, or Wikimedia Commons search: 'conference badge QR'
Dual-QR badges turn 'what's your email' into a one-tap save. ยท Source: Your own photo, or Wikimedia Commons search: 'conference badge QR'

If you want to know whether QR codes work at scale, look at events โ€” the industry that has quietly standardized on them for fifteen years. Eventbrite built its ticketing on QR. IATA's Bar-Coded Boarding Pass (BCBP) standard, used by essentially every airline on the planet, is a QR code; your phone gets you through TSA because of a specification from 2005. Singapore's SafeEntry, at its pandemic peak, moved millions of check-ins a day through QR scans. The unglamorous reality is that QR has already won the events category โ€” the question isn't whether to use one, it's which patterns still require human attention. After running badges through a few small conferences and watching larger ones operate, I'd argue three use cases are where organizers still get it wrong. Door check-in is solved technology if you buy off-the-shelf (Eventbrite, Hopin, Swapcard, Cvent); the failure mode is operational โ€” badge design, lighting at the door, and iPad-versus-phone scanner choice. Networking via vCard QRs is genuinely useful and underused โ€” most conferences default to 'exchange LinkedIns' which works for about 40% of the room and fails for everyone else. Session feedback is the pattern most organizers promise and then underdeliver on; the form is too long, the incentive is absent, and nobody on the events team looks at the results. The thing to watch out for, specifically at smaller events: don't reinvent what Eventbrite already does. If your event has fewer than 500 attendees, their off-the-shelf flow is better than anything you'll hand-roll in two weeks. Where QR codes help independent organizers is everywhere outside the core ticketing flow โ€” venue wayfinding, session context, sponsor engagement, post-event follow-up. Those are where dynamic QR codes earn their place, because all of them change.

Pattern 1vCard

Badge QR as both ticket and business card

The badge pattern has two jobs that usually need two codes. The first is a check-in token โ€” a unique identifier your scanner turns into 'Yes, this person paid.' The second is a contact-exchange surface โ€” a vCard that saves the scanner's name, title, and email into a phone. Most conference platforms handle the first and ignore the second, which is why networking at their events feels like 2008. The pattern that works is dual QR: one small code (check-in) and one larger code (vCard) on the same badge, clearly labeled. Attendees ignore the check-in one and scan each other's vCard โ€” the scan-to-save flow is a single tap, far better than the 'what's your email again?' exchange. Big-budget conferences (SXSW, Web Summit, Collision) have used this pattern for years; mid-size conferences haven't caught up. If you run 200โ€“2,000 attendees, dual QR is the cheapest upgrade to your networking that exists.

Pattern 2Dynamic URL

Live schedule on every venue sign

Printed schedules are wrong by 10am on day one. A keynote slips, a room double-books, a speaker's flight is delayed. The printed version in the program booklet is now a liability โ€” attendees trust paper, paper is wrong, trust erodes. A dynamic QR on each wayfinding sign, pointing at a live schedule page you control, fixes this at almost zero cost. The economics only work if the live schedule is actually live; I've seen organizers point QRs at static PDFs that weren't updated any more frequently than the printed booklet, which is worse than no QR at all because now the signs are lying to you too. Pick a CMS (Airtable, a Notion database, your event platform's schedule feed) where one person on the ops team can push a change in 30 seconds, and make sure that person is sitting at the command desk with a laptop. The signs don't have to be reprinted โ€” just the web page.

Pattern 3Dynamic URL

Session feedback that someone actually reads

Session feedback is the pattern organizers over-promise and under-deliver on. A seat-back QR with a 12-question form gets roughly 3% completion; a slide-end QR with one question ('rate this session 1โ€“5, one tap to submit') gets north of 30%. The difference isn't the QR, it's the form. The other mistake: nobody looks at the results. Speakers care, organizers should, and nobody builds the loop. The pattern I recommend is slide-end QR with a single rating question and an optional comment field; results stream to a dashboard visible to the speaker that evening and the organizer at the end of each day. Use the data to decide who you invite back, not to post a 'we heard you' summary on the event blog. The value isn't the feedback โ€” it's programming decisions informed by real attendee preference.

๐Ÿ“ท A wayfinding sign in a conference venue with a live-schedule QR code
Your own photo
Source: Your own photo

Printing and placement tips

Build one now

The free generator handles every pattern above. Upgrade to Pro when you want dynamic destinations or scan analytics on top.

Further reading and sources

Related

โ† All use cases
QR codes for events ยท QRForge