The Name Ledger: Auditing Pseudonyms and Identifying Details Before You Analyse Interviews

Why the audit belongs before analysis

Interview transcripts often arrive in a form that feels finished: the recording has been transcribed, the timestamps checked, the file saved. Yet the names within those pages may still be provisional. A participant may have been labelled with a first name in one file, a code in another, and a descriptive phrase in a supervisor’s email. If analysis begins before those labels are settled, inconsistencies can travel quietly into the findings chapter.

A short audit before coding or drafting is therefore an act of academic care. It is not a legal procedure, nor a substitute for guidance from your ethics committee or data protection officer. It is a study-skills routine: a deliberate review of how participants are represented, what surrounding details might reveal them, and whether the written record still matches what was approved. The aim is a transcript set that can be analysed with confidence and described in your methodology without avoidable uncertainty.

Start with the naming decision, not the name itself

Pseudonyms are common in UK dissertations, but they work best when the logic behind them is settled in advance. Before reading for themes, decide what kind of label your study will use. Options include a consistent pseudonym, a participant code, or a role-based descriptor such as “Participant A, second-year undergraduate”. Each has consequences for readability and for the distance it creates between the person and the printed page.

Consistency matters more than creativity. If one transcript uses “Priya” and another uses “P2”, the reader may wonder whether the difference is meaningful. A simple naming convention, recorded in a short note, prevents that ambiguity. It also makes later quote attribution easier: you can check that the same person is not appearing under two labels in different chapters.

When choosing pseudonyms, avoid names that carry unintended associations with the participant’s real identity, workplace or locality. A distinctive name may be memorable, but it can also become a clue when combined with other details. In many cases, plain and unremarkable pseudonyms serve the study better than vivid ones.

Look for the details that names alone cannot hide

Anonymisation is rarely a matter of replacing a name and stopping there. Transcripts contain context: a job title, a department, a town, a sibling’s school, a named event, a distinctive health condition, or a phrase such as “the only bakery on the high street”. Individually these details may seem harmless. Together they can narrow the field considerably.

A useful audit therefore reads each transcript for indirect identifiers as well as direct ones. Ask whether a quoted passage, placed beside a participant’s role and region, would allow someone familiar with the setting to make a confident guess. You do not need to erase every human detail; over-sanitising can strip the analysis of meaning. The task is to judge which details are necessary for the reader to understand the finding and which are simply incidental.

Where a detail is not analytically important, consider generalising it. “A market town in the Midlands” may be sufficient where “Nuneaton” is not. Where a detail is important, note why it has been retained so that your reasoning is visible later. This is especially helpful if a supervisor or ethics reviewer asks why a particular phrase remains in the transcript.

Make quote attribution a deliberate choice

Quotations are where anonymisation is most visible to the reader. A findings chapter that attributes every extract to “Sarah, 34, nurse, Leeds” may offer useful context, but it also offers a trail of identifiers. A chapter that attributes everything to “Participant 4” may protect identity but leave the reader uncertain about the basis of comparison.

A middle path is often more defensible: report the characteristics that matter for the analysis, in the aggregate or in a reduced form, and keep unnecessary personal detail out of the attribution line. If your ethics approval specifies a particular level of description, follow it. If it does not, treat the attribution line as a decision to be recorded rather than a habit to be repeated.

It is also worth checking that quotations have not been edited in ways that alter meaning. Anonymisation may require replacing a name or a place, but it should not quietly change the substance of what was said. Where a change is made, a consistent convention such as square brackets can signal it to the reader without drawing attention away from the participant’s words.

Build a simple audit trail

An audit trail does not need to be elaborate. A short table or ledger, stored with your study files, can record the decisions that would otherwise live only in memory. It might include the participant code, the pseudonym used, the date the transcript was checked, any indirect identifiers removed or generalised, and a brief note on why a retained detail was kept.

This ledger serves several purposes. It helps you spot inconsistencies across transcripts. It gives you something concrete to discuss in supervision. It also demonstrates, if needed, that anonymisation was approached as a considered process rather than a last-minute edit. In the methodology chapter, you can describe the process in plain terms without reproducing the ledger itself.

Keep the ledger separate from any document that will be shared widely, and store it in line with your institution’s guidance. The point is not to create extra bureaucracy but to leave a calm, checkable record of how the transcript set was prepared.

Align the audit with ethics and data protection expectations

UK GDPR and the Data Protection Act 2018 place obligations on how personal data are handled, and universities interpret those obligations through their own policies and ethics procedures. This article cannot substitute for that guidance. What it can do is encourage a habit of alignment: checking that the pseudonyms, retained details and quotation practices in your transcript set are consistent with what your ethics application described.

If your approval refers to “anonymised transcripts”, make sure that is a fair description of what you have produced. If you plan to retain identifiable material for a specified purpose, check that the approval and participant information allow it. When in doubt, ask early. A short query to a supervisor or research ethics contact is usually less disruptive than discovering a mismatch after analysis has begun.

A checklist to use before the first coding session

• Confirm the naming convention for every participant and apply it consistently across files.
• Read each transcript once specifically for indirect identifiers, not for themes.
• Note any detail that, in combination with other context, could re-identify a participant.
• Decide whether each such detail is analytically necessary; generalise or remove it if not.
• Check that quotation attribution lines do not reveal more than the analysis requires.
• Record decisions in a simple ledger kept with the study files.
• Compare the finished transcript set with the wording of your ethics approval.
• Ask for guidance if the approval and the practical record appear to diverge.

A calmer foundation for analysis

Anonymisation is often treated as a technical step completed before the “real” work begins. In practice, it is part of the analytical work: it shapes what can be quoted, how participants are described, and what the reader is entitled to know. A brief audit before analysis does not guarantee perfect protection, but it reduces the chance that a name, a place or an incidental detail will create avoidable worry later.

Names may change as transcripts are prepared for sharing, but the trust behind the study should remain visible. A consistent ledger, a clear naming convention and a careful reading for context clues give you a firmer footing for the chapters ahead.