Academic writing

Your Lay Summary Reads Like a Proposal. That's Why the Panel Skipped It.

A lay summary isn't your proposal in smaller font. It's a different argument structure — problem-first, not method-first.

You spent three months on a 2,000-word proposal. Your supervisor said "solid." Then you sat down to write the 250-word lay summary for your fellowship application — and you froze. Not because you have nothing to say. Because nobody ever taught you to say it differently. A GRFP panel, a SSHRC reviewer, a departmental fellowship committee — they are not your advisor. They don't owe you patience. If your structure still opens with methodology, they've moved to the next application before you finish the first sentence.

Here's the misconception that kills more lay summaries than any vocabulary level: "non-specialist audience" doesn't mean "dumber." It means zero context. Your job isn't to simplify. It's to re-anchor. Academic writing defaults to method-first, significance-later. Fellowship reviewers need the opposite: start with the human problem, explain why current approaches fail, then show your method as the natural next move. You're not dumbing down. You're redrawing the map. A lay summary isn't a smaller volume of the same signal. It's a different signal entirely.

Look at an opening that fails and one that works. ❌ "This project employs a mixed-methods approach combining computational text analysis with semi-structured interviews to investigate epistemic injustice in clinical decision-making environments." Your advisor would nod. A panel reviewer reads it and thinks: what is this person actually doing? ❌ The structure is method-first. There's no problem, no stakes, no image. ✅ "When a doctor dismisses a patient's symptoms as 'just anxiety,' something is broken — and we can't measure how often it happens or why. This project examines how clinical environments silence patients, using patient narratives alongside analysis of hospital records." Same research. The second one has a face, a feeling, a reason to care. The first has a method.

The methods paragraph is where I can tell whether someone understands lay communication or just swapped synonyms. ❌ "Data will be collected through ethnographic observation (12 months fieldwork) and analyzed using NVivo software with iterative coding protocols following Braun and Clarke's six-phase framework." No one on that panel has read Braun and Clarke. You're spending one of your 250 words on a citation that buys you nothing. ❌ You're writing for a hypothetical peer reviewer. ✅ "I will spend a year inside hospital consultation rooms, watching how conversations between doctors and patients actually unfold — not what policy documents say they should. I'll pair this with interviews of patients who felt unheard, to understand the gap between institutional intent and lived experience." Serious methodology, human logic chain. The panel follows because the reasoning is visible.

The significance paragraph decides whether you get funded. ❌ "This research contributes to the growing literature on epistemic injustice in medical settings and offers implications for institutional policy reform." In academia this reads as safe. In a fellowship context, it reads as hollow. A reviewer asks: what will actually change in the world because you did this? ❌ "Offer implications" is academic for "I don't know." ✅ "Findings will directly inform training modules we are developing with three NHS trusts, aimed at reducing diagnostic dismissal. The patient narratives collected will be made available through a public-facing archive — a record that currently does not exist." You named partners. You named outputs. You named what's missing from the world right now. That's significance.

By now you've probably drafted two or three versions and you're not sure which one is "clear enough." That's the moment to run it through easydue — not for tone, but for a clarity check: if an English-speaking reader with zero domain knowledge can't restate what you're doing after one read, you're still writing for your supervisor. The tool flags where your logic chain breaks silently. Use your saved time to sharpen the image — make the reviewer see what you see.

One last thing. Stop treating the lay summary as a degraded version of your proposal. It's harder. In a proposal you can lean on shared knowledge, jargon, citations. In a lay summary every choice — what to lead with, what to cut, which example to use — is a decision made in front of a stranger with 46 other applications and no obligation to understand you. This isn't a lesser skill. Explaining your work so someone outside your field genuinely gets it is the highest-order thing a researcher can do. Treat it that way.