Writing for the People Who Gave You the Data: A Participant-Facing Summary as a Check on Interpretation

Most dissertations are written for an audience of two or three: a supervisor, an internal examiner, perhaps an external one. That audience shares your vocabulary, your methods training and your tolerance for hedged, technical prose. Participants do not. Writing a plain-English summary of your findings for them, before you draft the discussion chapter, is therefore not simply an act of good manners. It is a diagnostic exercise, and it tends to expose precisely the places where your argument needs more care.

What the note is, and what it is not

The document in question is short: ordinarily a single side of A4, occasionally two. It explains, in ordinary language, what you set out to find, who took part, what you found and what you think it means, together with an honest account of what the study cannot tell anyone. It is not a results chapter in miniature, it is not a second abstract, and it is not a vehicle for new claims that appear nowhere in your analysis.

Many UK ethics committees now expect some form of dissemination back to participants, and the UK GDPR principle of transparency supports the same instinct. Even where your approval letter is silent on the matter, the exercise earns its place on study-skills grounds alone: it forces you to translate, and translation reveals ambiguity.

Begin with the findings section as it stands

Resist the temptation to write the note from memory. Open the findings chapter, read it through once without a pen, then read it again with a single question in mind: which sentences would a thoughtful person outside my discipline need explained?

Mark every instance of shorthand. "Thematic saturation", "lived experience", "discursive framing", "purposive sample" and "thematic analysis" are all perfectly respectable terms, but each requires a plain-language gloss. Note also the placeholders and pseudonyms you have used. If you anonymised a participant as P4, your note should not undo that work by describing P4 so precisely that a colleague could identify her.

The jargon sweep: three passes, not one

A single reworking rarely produces genuinely accessible prose. Three passes are more dependable.

• First pass: replace technical terms with everyday equivalents. Where a technical term is unavoidable, define it in the same sentence, in fewer than twelve words.
• Second pass: shorten sentences. Plain English is not simplistic English; it is English that carries one idea at a time.
• Third pass: read the note aloud, or better, hand it to someone outside your field, such as a flatmate or a relative, and ask them to tell you what they think you found. If their summary differs from yours, the note needs another revision.

Checking claims against evidence

This is the heart of the exercise, and the reason it belongs in the weeks before the discussion chapter rather than after it.

Take each claim in the note and trace it back to a specific part of your data or analysis. Colour-code them if it helps: green where the evidence is direct and ample, amber where it is suggestive but thin, red where you have inferred more than the data will support. A red item is not a failure. It is information. It tells you either to soften the claim, to gather a further quotation, or to acknowledge the gap explicitly.

A useful discipline is to phrase every finding in one of three registers: the data show, the data suggest, or this raises the possibility that. Plain language has a way of making overreach visible; a sentence that reads as measured in academic prose can sound startlingly confident when rendered for a lay reader.

Confidentiality in ordinary language

Participant-facing writing creates specific confidentiality risks, because the audience is precisely the group most able to recognise itself and one another.

Avoid combining identifiers that are individually innocuous but jointly revealing, such as an occupation, a town and a family circumstance. Do not quote extensively from a single participant in a one-page note. Where a finding rests on a distinctive case, describe it in general terms or aggregate it with others. If your study involved a small, tightly defined group, such as a single department or a specialist clinic, consider whether a summary should be circulated individually rather than shared with the whole cohort.

It is also worth being explicit that quotations have been edited for clarity and that pseudonyms have been used. Participants appreciate knowing the rules of the game.

Explaining limitations without undermining the study

A lay reader does not need a rehearsal of every methodological caveat, but honesty requires that the note says what the study cannot do. Three short statements usually suffice: this is a small study and does not represent everyone; the accounts gathered reflect what people said at a particular moment; and the analysis is one interpretation, offered in good faith, rather than the only reading the data would allow.

Framed this way, limitations read as professional candour rather than apology. That is a useful lesson to carry into the discussion chapter, where students frequently either overclaim or retreat into unnecessary defensiveness.

What the note reveals about your discussion

Once the summary is written, return to your findings and read the two side by side. Three questions usually produce the most useful material.

1. Which points were easy to explain plainly, and which resisted translation? Points that resist translation often conceal an unresolved analytical step rather than a purely linguistic problem.
2. Where did you find yourself wanting to add a caveat that is not yet in the chapter? Those caveats belong in the discussion.
3. What did you want to say that your evidence would not allow? That, too, is worth recording; it may become a recommendation for further research rather than a conclusion.

This comparison frequently yields a clearer structure for the discussion chapter than any number of planning templates, because it derives from your own material rather than from an abstract model of what a discussion ought to contain.

A modest template

A workable structure runs as follows: one sentence on why the study was done; one paragraph on who took part and how; three or four short paragraphs on what was found, each with a single claim; one paragraph on what the findings suggest; one short paragraph on limitations; and a closing line thanking participants and explaining where the work goes next. Keep the whole thing under a thousand words, and prefer active verbs.

Before you send it

Check the note against your participant information sheet, confirm that it matches what you told people you would do, and run it past your supervisor if your ethics approval requires it. Send it only when you are satisfied that it is accurate, anonymous and readable.

The wider benefit is less tangible but more durable. A researcher who can explain their findings to the person sitting opposite them, without hedging or hiding, is a researcher whose discussion chapter is likely to be measured, defensible and genuinely their own.