LinkForge

Aug 10, 2026

QR Codes for Events: Signage, Badges and Feedback

Events are the environment QR codes were made for: physical, temporary, and full of people holding phones. They're also the environment where the failure modes are worst, because you cannot reprint a banner at 9am on the day.

The four placements worth doing

Entrance and directional signage. Scanned from distance, often by a moving person. These need to be large — the ten-to-one rule means a code read from three metres wants around 30cm. Point it at a schedule or a map, not a homepage.

Table, booth and stand codes. Scanned at arm's length, so about 6cm. This is where the code should lead to something specific: your catalogue, a booking form, a chat link. Not your homepage, where the visitor has to navigate again.

Badges and lanyards. Small, scanned close, and personal. Point them at a contact card or profile. Keep these codes simple — a short destination means fewer modules, which matters at badge size.

Feedback and follow-up. The most commonly skipped and the highest value. A code at the exit pointing at a two-question form gets responses that an email the next day never will.

Plan for the venue, not your desk

Wifi will be bad. Crowded halls are the worst mobile environment there is — hundreds of devices on the same cells. Your destination must be light: minimal images, no video autoplay, no heavy fonts. If the page needs three seconds on good wifi, it will fail in the room.

Lighting is unpredictable. Spotlights on glossy laminate wipe out codes completely. Print matte for anything that will sit under a light.

People are in front of things. A code at knee height behind a table gets scanned by nobody. Eye level, unobstructed, on the side people actually approach from.

Make every code dynamic

This is non-negotiable at an event, for one reason: the schedule will change. Sessions move, rooms swap, speakers cancel.

A dynamic code — one that encodes a short link — means you repoint the destination and every printed sign is instantly correct. A static code encoding the URL directly means reprinting, which at an event means not fixing it.

It also means the signage keeps working after the event. Repoint the entrance code at the recordings, the slides, or next year's registration. Printed material that would otherwise be waste becomes a channel for months.

Measure what the signage did

Give each placement its own link. Entrance, each booth, badge, feedback. Then you learn things no other method tells you:

  • Which signage positions actually got used, which decides where you put them next time
  • When the room filled, from scan timing
  • Whether the feedback code was seen at all, as opposed to seen and ignored

Scan counts by hour are a genuinely good proxy for attendance flow, and you get it for free.

The day-before checklist

  • Print one of each at final size and scan it in the actual venue if you can get in
  • Test on the oldest phone available, in the room's lighting
  • Confirm the destination loads on a throttled connection
  • Check the destination is mobile-first — event scans are essentially 100% phone
  • Have a short typed URL beside each code as a fallback
  • Confirm every code is dynamic and you can log in to repoint it from your phone on the day

That last one is the one people forget: make sure the person on site has access to change destinations, not just the person who made the codes.

After the event

Don't let the links die. Repoint them at recordings, a thank-you page, or next year's signup. Every badge and flyer that walked out of the venue is still in someone's bag, and some of them will get scanned weeks later.

Generate event QR codes — SVG for print, and pair them with repointable short links so the schedule can change without a reprint.

Track every click, free

Unlimited short links with real-time analytics.

Create free account