What actually goes on a conference badge

A conference badge does three jobs: it gets somebody through a door, it tells the person opposite who they are talking to, and it survives three days on a lanyard. Most badge designs fail the second one.

The name is the badge

Print it as large as the card allows. The single most common mistake is a badge where the event logo is the biggest thing and the attendee's name is set in the same size as their institution.

The test is simple: can you read it across a handshake, without leaning in? At a conference where nobody knows anybody, that is the whole point of the object.

What goes under the name, in order

Role or ticket type. Speaker, Delegate, Faculty, Organising Committee. This is also the field most events colour-code, and the one the door uses to decide who may enter which session. It belongs where the eye lands second.

Institution. "Birat Medical College" tells somebody whether to start a conversation. A job title alone rarely does.

Job title, if there is room. Useful, but it loses to the institution when space is tight.

The QR should be the code the door scans

This is the part that causes the most avoidable pain.

Put the attendee's booking reference in the QR — the same string the door scanner reads and the same one on their emailed ticket. Not a URL, not an internal database id, not a separately generated token.

Two reasons. First, any phone camera or cheap USB scanner yields that string directly, so you are not tied to a particular app at the door. Second, if the badge encodes anything other than what the door checks, you have created two identities for one person, and eventually somebody with a perfectly valid badge gets turned away while a volunteer stares at a red cross.

Put a photo on it if you can

For anything with restricted sessions or a paid CME claim, a face on the badge is the difference between checking a badge and checking a person. It also lets the door show the volunteer the same photo, so they are comparing like with like.

Most events will not have a photo for everybody. That is fine — initials are a perfectly good fallback and better than a broken image box. But collect photos at registration if you intend to use them; asking afterwards never works.

What should not be on it

The price. Nobody needs to know what the person opposite paid, and a badge that prints a tier price turns your pricing structure into conference gossip.

A QR that points at a marketing page. The badge code has one job.

Anything you would have to reprint for. Badges get printed days in advance. Put nothing on them that changes.

Printing

Two formats cover almost every event:

• Four to an A4 sheet with cut lines. A6 tiles A4 exactly, so there is no waste and no guesswork. This is what you want for a print shop or an office printer the week before.
• One per card, on a 4×6in page, for a card printer at the registration desk. This is what you want for walk-ins and reprints on the day.

The important thing is that both come from the same template, so a badge reprinted at the desk at 9am looks identical to the four hundred printed on Tuesday. If your desk reprint looks different, delegates notice, and it reads as a counterfeit.

Print the team too

Speakers, volunteers and the organising committee need badges as much as delegates do — arguably more, because they are the people everyone else is looking for. They rarely register, so they are usually handled separately and end up with a visibly different badge. They should come off the same print run.