# QR codes for conference organisers

> Conference organisers should treat QR codes as a batch job: badge codes from the registration CSV, one feedback code per session, all generated in bulk and every one verified to decode before print. Collect feedback at the room door, not in the follow-up email.

Source: https://useqr.app/qr-codes-for/conferences · Last reviewed 2026-08-21 · UseQR is free forever, MIT licensed, no signup.

---

## This is a pipeline, not a poster

Attendee-facing advice — badge design, both-sides printing, the last-slide code — is on
the [events](/qr-codes-for/events) page. The organiser's problem is different: hundreds of
codes, generated from data, printed once, unfixable after the badges ship.

## Badges from the CSV

The payload decision scales with you. Per the
[badge payload trade-offs](/qr-codes-for/events), a short opaque ID or profile URL beats a
full vCard at any size — and at 2,000 badges it is also the difference between coarse
codes that scan through [badge pouches](/qr-codes-on/name-badges) and dense ones that do
not. The pipeline:

1. Export the registration CSV.
2. Generate one code per row [in bulk](/docs/how-to/how-to-make-qr-codes-in-bulk) — the
   UseQR batch endpoint takes up to **1,000 items per call**.
3. **Verify every code decodes** before the print run. A
   [render-then-decode check](/docs/developers/why-verify-that-your-qr-code-decodes) is
   one API call per badge; a badge misprint is discovered by a sponsor at the door.

## One feedback code per session

Emailed post-event surveys arrive after opinions have evaporated. A
[feedback code](/feedback-qr-code) on the door of each room, unique to each session —
generated in bulk with the session ID in the URL — captures reactions in the corridor
minute, and tells you *which talk* the rating belongs to without asking. One question per
form; response rates halve with every added field.

## Sponsor scanning has economics

Sponsors pay for lead capture, which is attendees' data — so the badge code must carry an
opaque ID that only your lead-capture system resolves, and scanning must map to a consent
the attendee actually gave at registration. Spell out in the programme what a badge scan
shares. An attendee who learns a scan handed over their phone number is a complaint;
five hundred of them are a story.

## The hub code

One short URL — agenda, maps, WiFi details, changes — printed on the badge back, the
lanyard card and every room sign. When the schedule slips 20 minutes, the hub is the only
thing that needs updating.

## FAQ

### How do you generate hundreds of conference badge QR codes?

From the registration CSV, in bulk: one code per attendee ID or profile URL. UseQR's
batch API accepts up to 1,000 items per call, and a bulk tool maps a spreadsheet column
straight to codes. Verify each decodes before sending badges to print.

### What should session feedback QR codes link to?

A one-question form with the session ID in the URL, one code per session per room. Door
placement catches attendees while the talk is fresh; identifying the session in the URL
means nobody has to type which talk they attended.

### What data does a badge scan give a sponsor?

Whatever your lead-capture consent says — which is why the badge should carry only an
opaque ID. The sponsor's scanner resolves it through your system, which releases exactly
the fields the attendee consented to share at registration, and nothing more.

## Try it

- https://useqr.app/vcard
- https://useqr.app/url
- https://useqr.app/feedback
- https://useqr.app/bulk