Two people meet at an event. One would like to use the other's name without leaning forward, staring or interrupting the introduction. Their badges contain plenty of information, but the names are buried under a large event logo and several lines of small print.
That is an illustrative situation, not a report from a customer event. It shows the useful starting point for a badge brief: what should the badge help somebody do in the next few seconds?
A name badge is a small piece of event communication. It can help a conversation begin, explain why somebody is there or identify a person who can help. It is not automatically improved by fitting more of the registration form onto it.
Decide which job belongs on the badge
Start with the people who will use it. At a networking event, another attendee may need a name and an organisation. At a workshop, a first name and a useful role may be enough. At an event with organisers available to help, the staff badge may need a plain word such as ORGANISER before any personal detail.
These are different jobs. They should not be combined by default. A badge designed to start a conversation does not necessarily need to function as a ticket, access pass or attendance record.
If access control is required, specify it separately with the organiser. A coloured strip or the word STAFF can communicate a role, but this guide does not turn an ordinary printed badge into a verified security system.
Write one sentence describing the main task. For example: another attendee should be able to read the person's preferred name and understand their relevant organisation. That sentence gives you a reason to prioritise the name, rather than a general instruction to make the badge look professional.
Give the useful name the strongest position
The largest element should follow the task. If the badge's purpose is helping introductions, making the sponsor logo much larger than the attendee's name works against that purpose.
Choose the name the attendee wants other people to use. Do not assume that the first field in a booking export is their preferred display name. A registration system may need a billing or formal name that is different from the name appropriate for conversation.
Below that, include the organisation or role only where it helps. A short description such as Volunteer coordinator can be clearer than an unfamiliar internal job title. Ask for the correct wording rather than shortening someone's role into a meaning they did not approve.
Keep necessary secondary information visibly secondary. A useful reading order might be name, organisation or role, then event identity. That is a design suggestion, not a universal order for every event.
The organiser's own badge may reasonably put its helping role first. The goal is not identical emphasis across every badge; it is clear emphasis for the job each badge performs.
Try the longest real name before approving the layout
A layout made around a short fictional name can be deceptively comfortable. The actual list may contain longer names, punctuation, accents, multiple surnames and longer organisation names.
Test the difficult entries before production. Check that the wording fits without reducing the important text to an unreadable size. If the name wraps, inspect where the line breaks. Avoid breaking a name in a way that changes how it is understood.
Do not remove accents or punctuation because they complicate the artwork. Confirm the correct display form with the organiser or attendee. If a particular font lacks a required character, the type choice needs attention.
There is no single font-size number that proves a badge will work. The finished size, typeface, contrast, viewing distance and the needs of the audience matter. A screen preview enlarged to fill a monitor does not settle those questions.
Use a sample at the intended physical size. View it as somebody else would encounter it, with the name in its normal position on the wearer. Ask whether the important words are clear without an awkward close inspection. Where attendees have specific access needs, discuss suitable arrangements with them rather than assuming a general sample meets every need.
A colour cue should have a word beside it
Colour can help distinguish organisers, exhibitors or participants. It should not be the only way someone learns what a colour means.
If a blue badge means an organiser can help, print ORGANISER too. A person should not have to remember a colour key before asking a question. The word also helps when the lighting, colour perception or printing makes the cue less clear.
Apply the same reasoning to symbols. An unfamiliar icon may make the badge attractive without explaining the person's role. Use a plain label where the role matters to the interaction.
Keep the number of categories manageable. A large collection of similar colours and unexplained abbreviations can create more decisions for the reader than it removes. If a distinction does not help the badge's main job, it may belong in the organiser's record instead.
The W3C's accessible-events checklist is a useful broader planning reference. It encourages organisers to consider participation and access across the whole event. It does not prescribe the badge layout above or certify any printed sample.
Separate the visible badge from the private list
A booking form may contain contact details, payment information, dietary requirements or access requests. Their presence in the organiser's system is not a reason to put them on a visible badge.
Ireland's Data Protection Commission explains principles including purpose limitation, data minimisation, accuracy and storage limitation. Its detailed guidance says the amount and nature of personal data must be assessed in relation to the processing purpose. DPC principles guidance
The practical design question is simple: does another attendee need to see this field to use the badge? For a conversation badge, a phone number is usually a different kind of information from a name. An access request is a different kind again.
Decide the display fields with the organiser and explain what will be shown. Do not silently convert a private registration export into public print. The organiser must address the appropriate lawful basis, information, permissions and handling for its event; a tidy badge template does not settle those obligations.
Keep sensitive operational information out of a casual artwork file. If authorised staff need a separate working record, give that record its own controlled purpose and handling. Do not encode private details into a QR code and assume that making them less immediately visible makes them harmless to disclose.
This is a practical application of general principles, not a complete legal-compliance guide. If the proposed badge reveals sensitive information or serves a specialist purpose, resolve the requirement with appropriate advice before production.
A fictional example: remove the information that competes with the name
Imagine a badge for a fictional attendee, Niamh Byrne, at an illustrative community workshop. The working layout contains a large event heading, an event slogan, a registration number, the full timetable and, near the bottom, Niamh's name.
None of those elements is necessarily wrong elsewhere. The problem is their competition for the space needed at the moment of introduction. A timetable can be useful on a separate programme. A registration number can be useful to an authorised organiser. Neither automatically helps the person saying hello.
A revised conversation badge gives Niamh's name the strongest position. Below it is a short approved role, Workshop volunteer. The event name remains as context. The registration number and timetable move to the places where they serve their respective tasks.
This is not evidence of a measured improvement in event engagement. It is a before-and-after reasoning exercise. You can inspect what was removed, where it went and why the remaining information is easier to prioritise.
The strongest redesign is not always the one with the fewest words. If the organisation is essential to the conversation, removing it would reduce usefulness. The aim is enough relevant information, in a useful order, rather than minimalism for its own sake.
Proof the list and the layout separately
A visually convincing sample can contain the wrong name. A correct attendee list can be placed in a layout that hides it. Treat those as two separate checks.
For the list, confirm display names, organisation wording and role categories. Identify who can approve corrections and how the final list is distinguished from an earlier export. Do not let several versions circulate under the same filename without a clear status.
For the layout, check the finished size, the longest entries, contrast, image or logo quality, and placement within the chosen badge format. If the badge will be held in a sleeve or attached in a particular way, inspect whether the important information remains visible in that arrangement.
Then check the combination. A data-merge process can repeat the first row, leave a field empty or mismatch a role with a name. Those are possibilities to inspect, not claims that a particular tool always fails. Review the actual generated output rather than assuming the sample proves every badge is correct.
For a large list, agree an appropriate checking method with the organiser. The people responsible for the list need to verify that the people and details are right. The artwork check needs to verify that those details appear correctly.
Plan for a correction without turning the desk into a redesign session
Names change, late registrations arrive and mistakes may be spotted on the day. Agree how an authorised correction will be handled before the event starts.
Keep the correction layout simple enough to preserve the same main information order. A handwritten replacement, where suitable for the event, can still make the name prominent and the role clear. Its job is to help the person participate, not to imitate every detail of the original artwork.
Decide who can approve a replacement and where it is prepared. Avoid leaving attendee lists, rejected badges or private notes accessible to everyone passing the desk. The organiser's retention and disposal arrangements should cover printed material as well as digital files.
This plan is different from promising that same-day printing will be available. Production routes, materials, quantities and timings need confirmation for the actual job. The guide does not claim a particular Time for Designs service, stock position or turnaround.
The brief you can send before asking for production
Include the event context, the badge's main job and the information that should be visible. State which fields are fixed and which vary by attendee. Provide the approved logo and the required wording for any role labels.
Add the proposed format, quantity, wearing or holder arrangement, and the required event date. If those details are undecided, mark them as questions rather than filling the gaps with assumptions. Include a few difficult entries for the layout proof, using only data you are authorised to share.
Name the person approving the display list and the person approving the artwork. They may be the same person, but the two jobs should still be clear. Explain how late changes will be collected and when the final version is expected.
Our guide to keeping changing event details and approved print separate helps with that last step. Time for Designs' printing information is a starting point for discussing the actual format and production requirements; the suitable route needs to be assessed for the job.
A good badge makes the first exchange easier
The useful badge does not ask a stranger to decode the organiser's database. It helps them find the name, understand the relevant role and begin the right conversation.
Start with that moment. Give its information room, confirm the person's wording, inspect a finished-size example and keep private operational details in their appropriate place. The result can be simple without being careless, and informative without trying to contain the whole event.
Sources and reading notes
The DPC's general principles inform the privacy discussion; the W3C resource supports considering access across event planning. The layout, proofing sequence and fictional example are Time for Designs' editorial guidance, not a standard, a legal opinion, a reported customer event or a tested conversion claim.