Event badge reprint workflow
A delegate is at the desk with a misspelt name or a lost badge, and the queue behind them is growing.
The short answer
A reprint workflow answers four questions before the event opens: who can request a reprint, what is verified first, where the new badge is printed, and what happens to the old badge.
Written down and given to desk staff, it turns every reprint into the same two-minute routine instead of a negotiation.
Why reprints need their own workflow
Reprints are exceptions, and exceptions slow the whole queue. If every desk volunteer decides for themselves, the same delegate can end up holding two valid badges.
A short workflow also protects the delegate list. The old badge, especially one with a QR code, should stop working once a new one is issued.
Reasons for a reprint and who decides
Sort requests into a few types so staff know whether they can act alone or must call the desk lead.
| Reason | Who can approve | What to check first |
|---|---|---|
| Spelling or title error caused by the organiser | Desk staff | Registration record shows the correct spelling |
| Spelling or title error entered by the delegate | Desk staff | Registration record; correct the record before printing |
| Lost or damaged badge | Desk lead | Identity matched to the registration record; old badge marked void |
| Category change (for example delegate to speaker) | Desk lead, with the programme owner informed | Written confirmation from the person who owns the category list |
| Late registration or walk-in | Follow the walk-in approval process | Approval already recorded |
The workflow in order
- Staff member finds the delegate in the registration list and states the reason for the reprint.
- Staff member applies the approval rule from the table, or calls the desk lead.
- Correct the record first. Print only from the corrected record, never from a hand-typed label.
- Print the new badge at the agreed print point and compare it with the record before handing it over.
- Collect the old badge if the delegate still has it, or mark it void in the system if it was lost.
- Write one line in the reprint log.
Decisions to settle before the event
- Where reprints are printed: at the desk, at a separate point, or by a supplier runner. Confirm the equipment and power arrangement with the registration supplier.
- Spare stock: how many blank badges, holders and lanyards are held back for reprints, agreed with the supplier.
- Whether a reprint costs the delegate anything. Most organisers do not charge, but a charge needs a named approver.
- Who watches the reprint count. A sudden rise usually points to a data problem upstream, such as a name field that was never cleaned.
Effect on queue time
Each reprint adds service time at a desk. When you test your desk numbers in the check-in throughput estimator, treat reprints as longer service times for a share of guests, and keep the result as an illustration to confirm with the venue and registration supplier.
Worked example · Fictional example
Reprint rules for a 300-delegate member conference
Fictional organisation and figures. The numbers are illustrative, not benchmarks.
Persatuan Fiktif Juruaudit Selangor expects about 300 delegates. Its secretariat assumes that around 10 delegates may ask for a reprint on the morning, mostly spelling corrections and a few lost badges.
One desk lead is named as approver for lost badges and category changes. The registration supplier agrees to hold 20 spare blanks and one reprint printer at the side of the desk, away from the main queue. After the morning peak, the desk lead reviews the log and finds six of eight reprints came from one membership class whose names were stored in capital letters, so the badge naming rule is corrected for the afternoon session.
Use this yourself
Badge reprint log and rules
Copy this into a shared sheet. One row per reprint, completed by the desk staff member.
- Rule: record is corrected before printing, never print from a hand-typed label.
- Rule: lost or category-change reprints need desk lead approval.
- Rule: old badge is collected or marked void on the same row.
- Review: desk lead reads the log after the first peak and after the event.
| Time | Delegate (as in record) | Reason | Approved by | Old badge: collected / void | Printed by | Notes |
|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- Your registration platform prints from the record and your team has handled badge corrections before.
- The delegate list is small and one person owns the desk.
- A supplier already provides printing and a spare-stock plan.
Outside planning help earns its fee when
- Several desks, several categories and a registration supplier all need one shared set of reprint rules.
- Previous events had duplicate badges or disputes over who could reissue.
- The event needs the reprint log reconciled against attendance afterwards.
Want reprint rules agreed with your registration supplier?
A conference project lead can agree the reprint rules with your secretariat, brief the registration supplier on spare stock and print points, and review the reprint log with you after the first peak. The decisions on who may reissue a badge stay with your organisation.
Questions organisers ask
Should delegates be allowed to reprint their own badge at a kiosk?
It can work when the platform prints only from the registration record and logs each print. Ask the registration supplier how a kiosk reprint retires the old badge before you allow it.
How many spare badges should we hold?
There is no standard number. Use your own past reprint rate if you have one, add a margin for category changes, and agree the figure with the registration supplier.
What if the delegate wants the name written differently from their registration?
Correct the record first, then print. That keeps the attendee list, certificates and follow-up emails consistent with the badge.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.