Event badge templates

How event badges get generated

Badge day before a conference is the canonical batch job. Four hundred attendees, each needing a badge with their name, their company, their ticket tier and a QR code tied to their attendee ID for check-in scanning. Done by hand it is an all-hands afternoon and there are always three typos. Done from the attendee CSV it is one upload and a ZIP. The tier field is worth binding even when it only takes three values, because badge colour or a lozenge usually keys off it and hard-coding that means three templates to maintain instead of one. Print-ready PDF is the usual export, since these go to a print shop rather than a screen.

In practice: One CSV export from the ticketing platform, one batch, print-ready PDF to the printer.

Fields you'd usually bind

{{attendee_name}}

The large line — auto-fit matters, names vary a lot in length.

{{company}}

Organisation, shown smaller beneath the name.

{{ticket_tier}}

Speaker, VIP, staff, general — often drives a colour or lozenge.

{{attendee_id}}

Bound to the QR code for check-in scanning.

Any text, image, QR code or barcode on the canvas can become a variable — these are just the ones this category tends to use.