Letters at the Lapel: Name Badges, Pronunciation and Belonging in the Manchester 2013 Archive

Name badges are among the least dramatic objects in any conference archive. They are small, disposable and usually printed in haste. Yet the badge is also the first document many delegates receive and the one they wear closest to their face. In the Manchester 2013 record, the badge survives as a quiet index of registration practice: what the form asked for, what the printer produced, what a delegate added by hand, and what the front desk could or could not correct. Read closely, these lapel cards are not merely wayfinding tools. They are records of how a scholarly gathering managed identity, attribution and belonging.

The Badge as an Access Document

A conference badge appears to answer a simple question: who is this person? In practice it answers several at once. It signals institutional affiliation, status within the programme, and the name by which a delegate expects to be addressed. The Manchester 2013 badges, like most congress ephemera, were generated from registration data. That data was shaped by fields that may have assumed a legal name, a single surname convention or an academic title. Where those assumptions did not fit, the badge became a site of negotiation.

For 2026 conveners, the lesson is not that the 2013 process was uniquely flawed. It is that badge design is an access decision made long before the printer is switched on. Names are personal data under UK GDPR, but they are also intellectual data: the name under which a paper is cited, a contribution is attributed and a career is recognised. A badge that misstates a name can misdirect a citation as surely as it can embarrass a delegate at a coffee urn. The Equality Act 2010 does not use the word ‘badge’, but its concern with reasonable adjustments and dignified participation reaches the registration desk quite directly.

Pronunciation Notes and the Limits of the Record

The Manchester 2013 archive does not preserve every spoken introduction, and it should not be asked to. What it does preserve are traces: a preferred name written in place of a formal one, a phonetic spelling added by hand, a marginal note that a surname is pronounced differently from its appearance. These marks are uneven. Some delegates annotated their badges; most did not. The absence of a pronunciation note is not evidence that pronunciation was unimportant. It may simply mean that a delegate had learned to endure correction, or that the registration form offered no space in which to volunteer the information.

This is where archival reading requires restraint. A badge can tell us that a name was printed in a particular form. It cannot tell us whether the bearer was addressed correctly in the session, whether a chair stumbled over a syllable, or whether a delegate chose silence rather than repeat a correction for the fourth time. The badge is a starting point, not a verdict. Used alongside the programme, the abstract book and the correspondence of the organising committee, however, it helps reconstruct the ordinary labour of being named at a large international congress.

From Lapel to Front Desk: A 2026 Checklist

The Manchester 2013 record suggests a practical agenda for conveners preparing for 2026. The following checklist treats names as both personal and scholarly data, and it can be adapted to conferences of any size.

• Ask for preferred names explicitly. Registration forms should distinguish between a legal or administrative name, a name for the badge and a name for the programme. Make clear which will be public and which will be used only for invoices or travel documents.
• Offer pronunciation as an optional field. Do not force phonetic spelling on delegates. Some prefer IPA, some prefer a simple respelling, and some prefer to explain in person. The form should allow any of these, or none.
• Design badges for correction. Leave space, or provide a small annotation area, so that a delegate can adjust a name without feeling that they are defacing official material. A pencil at the registration desk is a modest inclusion measure.
• Brief front-of-house staff on names. The person handing over a badge is often the first person to read it aloud. A short script – ‘I have your badge as … is that how you would like to be addressed?’ – costs little and prevents much.
• Use name tents and session chairs as allies. Chairs should be able to check preferred names before introducing speakers. A brief note in the chair’s pack is more effective than an assumption that everyone will remember.
• Build in a correction route. If a badge is wrong, the delegate should know where to go and should not be charged for a reprint. The same applies to programme entries and online profiles.
• Retain data with care. Pronunciation notes and preferred names are personal data. They should be held only as long as needed, shared only with those who require them, and never treated as a decorative quirk of registration.

A Teaching Resource in Disguise

The badge also has a teaching afterlife. In research methods seminars, it can be used to discuss how institutions record identity, how forms encode assumptions and how apparently minor administrative choices shape who feels entitled to speak. Students can compare a badge template with an abstract form, or trace the difference between a printed name and a preferred name. The exercise is small, but it trains attention on the ethics of description – a central anthropological concern.

Manchester 2013 is now part of the historical record, and its badges are unlikely to be remembered as its most important documents. That is precisely why they are useful. They show that inclusion is often decided in the unglamorous infrastructure of a conference: the field on a form, the font on a card, the sentence a steward is trained to say. Getting names right is not housekeeping. It is a form of scholarly recognition, and 2026 conveners can begin it at the lapel.