Branding and visual collateral
Event name card verification before printing
The registration list is nearly final and the printer is waiting for a file with 400 names on it.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Verify name cards in three passes: check the data against what each person supplied, check the layout on a printed sample, then check a small batch against the real delegate list before the full run.
A written freeze date matters most. After it, changes go to a reprint list, not to the master file.
What a name card has to get right
A name card is read at arm's length by strangers, so the errors that matter are the ones people notice: a misspelt name, the wrong title, an organisation that has been renamed or a category that sends someone to the wrong room.
Decide first which fields appear at all. Every extra field is another thing to check and, for personal data, another thing to justify.
Fields to verify, and against what
Use this table to give each field a source of truth and a person who checks it.
| Field | Check against | Checked by |
|---|---|---|
| Full name and spelling | Registration entry or the person's own confirmation | Registration lead |
| Title or honorific | What the person supplied; ask if unsure | Registration lead |
| Organisation name | Registration entry, then the organisation's current name | Secretariat |
| Category (delegate, speaker, sponsor, press, staff) | Master category list approved by the event owner | Event owner |
| Access marks (sessions, meals, zones) | Programme and catering plan | Project lead or operations |
| Language and script | Exactly as the person supplied it; never converted by the team | Registration lead |
Names are not yours to correct
Malaysian names can include honorifics, patronymics such as bin or binti, initials, mixed-script names and Chinese characters with a separate romanised form. A tidy-up that looks like a correction can be wrong.
Print what the person supplied. If the entry looks inconsistent, ask the person and record the answer in the registration file.
The three-pass sequence
- Set a freeze date for the registration data and tell the secretariat that later changes go to the reprint list.
- Check the full export against the table above, with a second person checking a random sample.
- Print 15 to 20 sample cards on the real stock and check size, legibility from arm's length, lanyard hole position and colour of the category bands.
- Print the full run only after the event owner signs the sample against the print specification in print specification sign-off.
- Prepare blank cards, a label printer or a handwriting station, and one named person to run a reprint desk on the day.
Keep the data on the card to what is needed
Mobile numbers, dietary notes and membership numbers rarely belong on a badge that is visible to everyone. If a code is needed for scanning, discuss with your data protection contact what it may reveal.
The registration form field minimiser helps you decide which fields are collected at all, so the card inherits only what the form really needed.
Worked example · Fictional example
A fictional logistics association's 410-name run
Fictional organisation and figures, illustrative only.
Persatuan Fiktif Pengurus Logistik froze its list at seven days before the event with 410 names. A second checker reviewed 40 random entries and found three with titles entered in the wrong order, so the secretariat emailed those three people instead of editing the titles itself.
The 18-card sample showed the category band colours were hard to tell apart under the ballroom lights, so the owner changed two colours before printing. Nine late changes arrived after the freeze and were printed at the reprint desk.
Use this yourself
Name card verification checklist
Copy this into your event file and tick each line with the date and the initials of the checker.
- Fields on the card agreed with the event owner (name, organisation, category only, unless a reason is written):
- Freeze date set and communicated to the secretariat:
- Full export checked against registration entries; second checker sampled at least 10 percent:
- Queries raised with the person, not corrected by the team; answers logged:
- Category list and colours approved; colour difference checked under venue lighting:
- Sample cards printed on real stock and signed by the event owner:
- Reprint list, blank cards and a named reprint desk operator ready:
- Version and date of the file sent to the printer recorded:
Handle it in-house, or bring in help?
Your team can usually handle this when
- Under about 150 names and one person owns the registration data.
- The categories are the same as last year.
- There is time for a sample print.
Outside planning help earns its fee when
- Several organisations supply registration data in different formats.
- Names arrive in several scripts or with many honorifics and the team is unsure how to check them.
- Late changes keep arriving close to the print deadline and nobody owns the decision to reprint.
Need someone to run the name card freeze?
A conference project lead can hold the freeze date, run the second-person check, chase queries with delegates and agree the reprint desk arrangement with the event owner. Send the registration export format and your print deadline.
Questions organisers ask
How many sample cards should we print?
Enough to cover every category and the longest names, usually 15 to 20. Check them at arm's length, not on a screen.
What if a delegate asks for a change after the freeze?
Add it to the reprint list with the date and the name of the person who approved it, and print it at the reprint desk or before doors open.
Should the badge show a barcode or QR code?
Only if the check-in or session scanning plan needs it. Ask your data protection contact what the code reveals when scanned and whether a plain reference number is enough.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.