What a Lay Summary Is (and What It Is Not)
A lay summary is a short, accessible explanation of your research, written for someone with no specialist knowledge of your field. It answers the questions a curious, intelligent non-expert would ask: What problem were you solving? What did you find? Why does it matter?
It is not a simplified abstract. Simplifying your abstract produces a text that is marginally less dense, but still clearly written for researchers. It is not a press release (which has different structural requirements). And it is not a blog post, it is typically 200–400 words, structured around the reader's questions rather than the paper's methodology.
Lay summaries are now required by many journals (including all PLOS journals), most major funders (including NIHR, Wellcome, UKRI, and the Gates Foundation), and all REF impact case study submissions. Writing them well is no longer optional, it is a career skill.
The Core Problem: Who Are You Actually Writing For?
Before writing a word, answer this question: Who specifically needs this research?
Not "the general public", that is too vague. Be specific:
- A GP who needs to know how this changes clinical guidelines
- A secondary school teacher working with students with the profile you studied
- A housing policy officer who needs to understand the urban planning implications
- A patient or carer who is living with the condition you researched
- A journalist writing about AI governance who needs the specific technical finding explained
Your lay summary should be written for that specific person. If you are writing for multiple audiences, write multiple summaries, a 200-word version for practitioners, a 300-word version for general public engagement.
The Structure That Works
Opening sentence: the problem, not the paper
Don't write: "This paper investigated the relationship between sleep deprivation and cognitive function in adolescents."
Write: "Teenagers who sleep fewer than seven hours per night perform significantly worse on tasks requiring concentration, with consequences for both learning outcomes and mental health."
The second version starts with the world the reader lives in, not with the paper. It creates immediate relevance.
The method: one sentence, no jargon
One sentence is sufficient. Use plain language for the study design: "We surveyed 1,400 teenagers across eight schools in the UK over two academic years." The reader needs to trust that this is rigorous research, they do not need the methodological detail that belongs in the paper.
If your method involves a term that requires explanation (randomised controlled trial, systematic review, meta-analysis), use the plain language equivalent: "We tested the intervention by randomly assigning participants to treatment and control groups" rather than "We used a randomised controlled trial."
The finding: specific, concrete, consequential
This is the most important section, and the most commonly written too vaguely. Vague: "We found that sleep matters for teenage learning." Specific: "Students sleeping fewer than 7 hours were 43% more likely to score in the bottom quartile of attention tasks. This effect was consistent across all demographic groups we studied."
The specific finding creates both credibility and relevance. A reader can do something with a specific number. They cannot do anything with "sleep matters."
The implication: what should change?
This is where researchers often add excessive nuance, qualifications, and caveats, defaulting to academic caution. This is the wrong instinct for a lay summary.
The reader needs to know: given this finding, what should I do differently, think differently, or advocate for differently?
"Schools that start before 8:30am may be structuring the day in ways that systematically disadvantage their students." This is a claim a reader can take back to a school board meeting, a policy consultation, or a clinical practice decision.
Ending: Where can I learn more?
Provide a link to the full paper (ideally an Open Access version). If you are willing to be contacted by practitioners or journalists, say so and provide a professional contact route.
Common Lay Summary Mistakes
Starting with "This paper...", The paper is not the subject. The problem is.
Using field-specific acronyms without defining them, Every acronym you use without defining it excludes a category of reader. Write it out the first time, every time.
Writing passively, "It was found that..." creates distance. "We found..." or "The study found..." creates a human presence.
Hedging every finding to death, "There may be some suggestion that, under certain conditions, this could potentially influence..." This is appropriate in the paper. In the lay summary, it communicates nothing. Acknowledge uncertainty once, briefly, then state the finding.
Making it too long, 400 words is a generous limit. 250 words, written with precision, will be read and shared. 600 words, however accurate, will not.
When You Need Help
Research communication is a skill, and like all skills, it improves with practice and feedback. If you are writing your first lay summaries, try reading them aloud to a non-researcher friend or family member. If they ask questions you can answer in conversation but couldn't in the summary, those answers belong in the text.
For researchers who produce large volumes of outputs, or whose work is crossing into policy or public discourse, professional research communication support makes the difference between findings that sit in journals and findings that change practice.
Your research findings deserve to reach the people who need them. The Researchvy Media division creates professional lay summaries, policy briefs, and knowledge translation content for researchers across every discipline, written to reach the specific audiences your work is meant to serve. See how research communication fits into the full visibility framework by reading our guide on visual abstracts, or explore the Researchvy ecosystem to understand every dimension of scholarly visibility.
