Arrival and check-in operations
Badge print proofing: what to check before the full run
The badge file looks right on screen, but nobody has yet held a printed one or scanned it.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Proof a printed sample, not the screen. Check names against the final list, test that every code scans on the devices you will use, confirm colours and category markers, and have one named person sign the proof before the full run starts.
A short proof round costs far less than reprinting on the morning of the event. Keep the sample from each round so that the signed version can be compared with what arrives.
What to proof, in order
| Check | How | Fail means |
|---|---|---|
| Names and organisations | Compare 20 random badges and the 10 longest names against the final list. | Fix the data, not the badge. |
| Code scanning | Scan the printed code on every device and app that will be at the desk. | Increase code size, contrast or quiet space. |
| Category markers | Check colours and labels at arm's length under room-like light. | Adjust colour or add a text label. |
| Physical fit | Try the holder, lanyard and clip with a printed sample. | Change stock or holder size. |
| Order of the stack | Check the sort order against the desk layout. | Re-sort before packing. |
Who signs the proof
Name one person with authority to approve the proof, usually the registration lead. A second person, such as the committee secretary, checks the names of speakers and guests of honour.
Record the date and time of approval, and what changed since the previous round.
Sequence for a proof round
- Freeze the name list and the naming rules for the round.
- Ask the printer for a physical sample on the real stock, not a PDF.
- Run the checks above and write the findings on the proof sheet.
- Send corrections once, as one list, then request a second proof if anything changed in layout or code.
- Sign, date and file the final proof, and keep one sample at the desk for comparison.
What commonly goes wrong
- Approving a screen proof that prints differently on the real stock.
- Testing codes on one phone only, when the desk uses a handheld scanner.
- Late name changes that bypass the proof.
- Delivery to the venue not planned, so the boxes arrive after the desk team.
Worked example · Fictional example
A proof round that caught a scan problem
Fictional organisation and figures, illustrative only.
A fictional trade body orders 450 badges. In the proof round, the registration lead scans ten codes with the desk's handheld scanner and two fail, because the code is printed small on glossy stock.
The printer enlarges the code and moves to matte stock. The second proof scans on every try, and the lead signs it. The delivery time to the venue is added to the arrival instructions timetable so the box is on site before the desk team.
Use this yourself
Badge proof sign-off sheet
Use one sheet per proof round and keep the signed final with the sample.
- Proof round number, date and file version:
- Name list version and naming rule version used:
- Names checked (random 20 and 10 longest), result:
- Codes scanned on each desk device, count passed and failed:
- Category colours and labels checked in room-like light:
- Holder, lanyard and stock fit confirmed:
- Stack sort order matches desk layout:
- Corrections requested, and date sent to printer:
- Approved by (name, role, date and time):
- Delivery date and time to venue, and who receives it:
Handle it in-house, or bring in help?
Your team can usually handle this when
- A single printer and a modest print run.
- One person owns the name list and the proof.
- Time for a second proof round.
Outside planning help earns its fee when
- Several badge types, vendors or print sites.
- Tight timeline between final registration and the event.
- The scanning app and the printer supplier belong to different parties and no one coordinates them.
Want someone to run the proof round?
A conference project lead can coordinate the printer, the scanning supplier and your registration lead through the proof rounds, keep the sign-off record, and plan delivery to the venue. Share your print deadline to discuss the scope.
Questions organisers ask
Is a PDF proof enough?
It checks content, not print. Ask for a physical sample on the real stock, then test scans on your devices.
How many badges should we test?
Test every code on the sample sheet, plus a random set and the longest names. Choose your own numbers and record them on the sign-off sheet.
What if a name changes after sign-off?
Treat it as a reprint request through your badge reprint workflow, not an edit to the approved file.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.