Skip to content
bagevent.io

What should be on a conference badge, and when should you print it?

By Updated 24 September 20264 min read

Short answer

A badge needs a name readable from two metres, the organisation, any role the room needs to see, and a scannable code that holds an opaque token rather than personal details. Print it on arrival, as a name label on a pre-cut badge: searching a rack of pre-printed badges at the desk is slow and gets messy at any real volume. Keep blank stock at the enquiry desk either way.

A badge does three jobs at once: it gets someone through a door, it tells a stranger whether to start a conversation, and it is visible to everyone in the building all day. Most badge problems come from optimising one of those and forgetting the other two.

This is a field guide to the decisions, not to any particular badge designer. It applies whatever you print with, ours included.

What a badge is for

Entry, recognition, and privacy — in that order of urgency and the reverse order of how often they are considered.

  • Entry. Staff have to confirm at a glance that this person belongs here, and at some events which areas they may enter.
  • Recognition. Someone standing two metres away decides whether to start a conversation from what they can read.
  • Privacy. Whatever is printed is visible to every other attendee, every supplier, and every photograph taken that day.

The third one is why a badge is not simply a print of the registration record.

The four things worth printing

WhatWhy it earns the spaceThe trap
Name, largeIt is read from two metres away, standing up, in bad lightSized to fit the longest name in the file rather than to be read — set a size and truncate deliberately instead
OrganisationIt is the single most useful thing for deciding whether to say helloFree-text company names arrive in six spellings; normalise before printing
Role or ticket typeSpeaker, exhibitor, staff, press — the badge is how the room knowsPrinting a job title instead, which is long, self-described, and not what the room needs
A scannable codeSession access, lead capture, and re-entry all run off itPutting readable personal data next to it, which defeats the point of the token

Everything else — dietary marks, pronouns, first-time attendee, membership grade — is a deliberate addition with a reason, not a default. Each one is also a disclosure to the whole room.

The code should carry a token, nothing else

A badge is photographed, left on tables, and posted to social media. Anything encoded in the QR is effectively public, so the code should contain an opaque identifier that means nothing outside your own system — not a name, not an email, not a ticket reference that resolves to a person anywhere else.

Scanned by your own scanner, the token resolves to the attendee. Scanned by any other app, it is a meaningless string. That property is worth protecting, because it is the difference between a lost badge and a data incident.

On-demand or pre-printed

This is the decision that shapes the desk. They fail differently — and in practice one of them fails much more often.

Printed on arrivalPrinted in advance
Late changesHandled — name corrections and last-minute registrations print correctlyBecome a manual pile: reprints, handwriting, or a second desk
Queue behaviourEach person waits for a printer; throughput is bounded by the slowest printerFast if the badge is found quickly, slow if someone is searching an alphabetical rack
Failure modeA printer jam stops that lane entirelyA missing badge sends someone to the exceptions desk
Good forEvents with heavy walk-ups, corrections, or several ticket typesSmall, invited audiences where the list stopped changing days ago

Running events on BagEvent, the recommendation for conferences is to print on arrival. Finding a pre-printed badge at the desk looks fast on paper and is slow in practice: volunteers search, badges get misfiled, and the rack turns into a second queue. A label printer within arm's reach of each lane, printing a name onto a pre-cut badge, is faster and survives late changes.

Whichever you choose, keep the other available for a handful of people. Blank stock and a marker at the enquiry desk has saved more mornings than any amount of planning.

Sizing, and the part everyone gets wrong

Names vary far more than layouts allow for. Decide these three before the first proof:

The printed name
Ask for it separately at registration. Legal name and the name someone wants on a badge are routinely different, and the difference is otherwise discovered at the desk.
The longest name you will accept
Set a character limit, show it on the form, and decide in advance whether longer names shrink or truncate. Do not let the layout decide silently.
Orientation
Portrait badges flip in lanyards and show a blank back. Either print both sides or use landscape; the room will not fix it for you.

Before you approve the proof

  • Print one and read it from two metres, standing, in the lighting the venue actually has.
  • Print the longest name in your list and the shortest, on the same layout.
  • Scan the code with a phone camera and confirm it reveals nothing about the person.
  • Hang one in a lanyard and look at the back.
  • Ask what happens when the printer jams at 08:50 — and make sure the answer is a procedure rather than a person.

Frequently asked questions

Name in a size readable from two metres, organisation, a role or ticket type the room needs to see, and a scannable code. Everything beyond that — job title, dietary marks, pronouns, membership grade — should be a deliberate choice, because a badge is visible to every other attendee, supplier and camera in the building all day.