What Is a Lay Summary and Why Does It Matter?
A lay summary is a short, plain-language explanation of your research project. It’s written for people who are not experts in your field. Think of it as the elevator pitch for your grant application - clear enough for your neighbour, your bank manager, or a high-school teacher to understand.
This is not a simplified technical abstract. A technical abstract assumes your reader knows your discipline’s vocabulary, methods, and assumptions. A lay summary assumes nothing. It stands alone and answers four questions: Why does this matter? What will you do? Who benefits and how? Why can your team deliver?
Why does this distinction matter? Because over 90% of major UK and EU funders - UKRI, NIHR, Horizon Europe, Wellcome Trust - now require a lay summary as a mandatory part of your application. And here’s the critical point: many of your assessors will be non-scientists. Innovate UK panels, for example, include industry practitioners, commercial experts, and business leaders - people who care about market readiness and return on investment, not algorithm novelty.
These non-expert reviewers often spend three minutes or less on initial review. Your lay summary is frequently the only section they read to form a first judgment. If your language is dense with jargon, or if you hide your impact behind technical detail, you risk losing them. A study of unsuccessful NIH applications found that over 65% attracted reviewer comments like “unclear significance” - a problem rooted in weak lay summaries, not weak science.
In short: your lay summary is the gateway to your entire proposal. Write it poorly, and the rest of your hard work may never get read. Write it well, and you give your project its best chance to be understood, valued, and funded.
The Four Essential Questions Your Lay Summary Must Answer
Your lay summary needs to answer four specific questions. Miss one, and you risk losing non-expert assessors before they ever reach your technical sections.
Why does this matter? Start with the real-world problem - not your gap in the literature. Paint a picture that makes the urgency obvious. Example: Instead of “there is a need for improved immunotherapy targeting,” say “every year, 10,000 people in the UK are diagnosed with pancreatic cancer, and fewer than 7 in 100 survive beyond five years. Current treatments stop working after six months because tumours develop resistance.” That lands. That’s human.
What will you do? Describe the action, not the methodology. Leave out “we will employ a randomised controlled trial using double-blinded placebo controls.” Say “we will test a new blood test against the current standard in 500 patients to see which catches cancer earlier.” You are clarifying what happens, not how you will do it.
Who benefits - and how? Be specific about who gets the outcome. Patients? Clinicians? Manufacturers? Communities? Example: The Australian irrigation grant that won replaced technical hydrology with logistics - it showed which farmers would get water, when planting windows opened, and how three contractors would install the system. That made the benefit concrete for non-engineer assessors.
Why can your team deliver it? Do not list CV highlights. Instead, anchor credibility in logistics: who does what, when, and with which resources. “We already hold the water license for the site and have quotes from three certified installers” beats “our PI has 20 years’ experience.” Feasibility, not seniority, is what non-specialists trust.
Common Mistakes That Undermine Non-Expert Assessors’ Trust
Even the strongest research can sink a grant application if your lay summary makes the wrong impression. Here are the most common mistakes researchers make - and how to avoid them.
Mistake 1: Treating jargon as a sign of expertise
It’s tempting to think that using technical terms shows you know your field. But non-scientist assessors don’t read jargon as credibility - they read it as confusion. When you write “employing convolutional neural networks for image segmentation,” they hear “something complicated I don’t understand and can’t evaluate.”
That erodes trust. If the reviewer can’t grasp what you’re actually doing, they can’t judge if you’ll deliver. And they’ll assume the worst.
The fix: Replace every acronym and technical term with plain language. Test each sentence: “Would my uncle understand this?” If not, rewrite it. For example, instead of “deep learning model for tumour detection,” say “a computer system trained to spot cancer cells in medical scans - like a second set of eyes for radiologists.”
Mistake 2: Promising big outcomes with no roadmap
“This research will revolutionise stroke recovery.” That sounds impressive. But to a non-expert panel, it sounds like hot air - unless you show how.
Over 50% of rejected proposals fail because of poor communication of implementation, not weak ideas. When assessors see vague promises without specifics, they mark you down for “unclear significance.” They don’t trust you to deliver.
The fix: Ground every benefit in concrete logistics. Show the who, when, where, and with what resources. The Australian irrigation grant that won didn’t talk about hydrology theory - it listed water license status, installation windows, and contractor quotes. That’s what built credibility.
Mistake 3: Writing a mini technical abstract
Some researchers try to cram their entire methodology into 300 words. Big mistake. A lay summary is not a condensed version of your technical sections. It needs to stand alone and answer different questions - the four questions we covered earlier.
The fix: Start with the real-world problem, not the literature gap. Use the inverted triangle: big-picture problem → your specific gap → your solution → the benefit. Save the methodological details for later sections.
Mistake 4: Skipping the reality check
The single best test? Let a non-scientist read your summary aloud. If they pause, frown, or ask “what does that mean?”, revise. One researcher’s draft scored at grade 14 reading level (graduate). After a citizen reviewer helped, it dropped to grade 8 - accessible to most adults.
Bottom line: Assessors don’t need to be impressed by your vocabulary. They need to be convinced you can deliver. Clarity is credibility.
A Simple Step-by-Step Framework for Writing Your First Lay Summary
Now let’s turn those principles into action. Here’s a step-by-step framework you can apply to your next lay summary - no matter how technical your research.
1. Start with the inverted triangle
Open big, then zoom in. Begin with the broad problem that matters to society - climate change, antibiotic resistance, declining literacy rates. Then narrow to the specific gap your project addresses. Then present your solution. End with the real-world benefit.
Example: Instead of “We will investigate the role of prion-like propagation of tau protein in neurodegenerative disease,” try: “Memory loss affects millions of families worldwide. Current treatments slow symptoms but don’t stop the disease. We’ve discovered a new way that toxic proteins spread between brain cells - and we’ll test whether a specific drug can block that spread. If successful, this could lead to the first treatment that halts Alzheimer’s progression.”
2. Tell a story with human stakes
Give your reader a reason to care. Connect your research to a person, a community, or a real-world scenario. Non-scientist assessors are humans - they respond to narrative, not data tables.
3. Replace advanced terms with specific analogies
Don’t say “neural network optimisation algorithm.” Say “software trained to spot manufacturing defects in images - like a quality inspector, but faster and consistent across shifts.” Every technical term should earn its place. If it doesn’t add clarity, cut it.
4. Anchor credibility in who, when, where, and resources
Non-experts judge feasibility by logistics, not jargon. Show concrete plans: “We have preliminary quotes from three certified contractors. We’ll install during the summer planting window when water demand is lowest. Our team includes a clinical trial manager with 12 years of experience in similar studies.”
5. Use a readability checker
Aim for grade 8 level - that’s accessible to most adults. Free tools like Hemingway Editor or Readable will flag long sentences, passive voice, and complex words. One researcher’s draft dropped from grade 14 (graduate-level) to grade 8 after citizen review. Yours can too.
6. Test with someone outside your field
Find a friend, family member, or colleague from a different department. Ask them to read your summary aloud. Where do they pause? Frown? Ask “what does that mean?”? Revise those spots. If they can explain your project back to you, you’ve succeeded.
Practical Next Steps: From Draft to Submission
Now it’s time to turn your framework into a finished lay summary. Follow these five practical steps, in order, and you’ll submit a section that builds trust with non-scientist assessors-not confusion.
1. Write your first draft-fast
Use the four-question structure from earlier (why it matters, what you’ll do, who benefits, why your team can deliver). Don’t overthink word choice yet. Aim for 250-300 words. Write as if you’re explaining your project to your neighbour over a cup of tea.
2. Seek feedback from one non-scientist
Find a colleague outside your field-or a friend who isn’t a researcher. Hand them your draft and ask two questions: “What’s the main problem I’m solving?” and “What would you tell someone else about this project?” If their answer matches your intent, you’re on track. If they pause or misinterpret, revise.
3. Cut jargon and passive voice
Read your draft aloud. Every time you use a technical term ("neuroplasticity," "algorithmic optimization"), ask yourself: can I replace this with everyday language? Replace "It was observed that" with "We saw." Replace passive with active: "We will test" not "Testing will be conducted by the team."
4. Check funder rules-strictly
Most funders set a strict word count (often 250-300 words) and may require a specific font, spacing, or section format. Count every word. If you’re 10 words over, trim. Non-compliance can get your application rejected before anyone reads the science.
5. Use an AI readability tool to flag issues
Run your draft through a free tool like Hemingway Editor or the Flesch-Kincaid grade-level checker. Aim for reading grade 8-9 (accessible to most adults). If your text scores grade 14+, non-experts will struggle. Let the tool flag long sentences, passive voice, and unexplained acronyms. Revise accordingly.
Once your lay summary passes these checks, log in to GrantGunner to explore funders that match your project. A clear lay summary doesn’t just win grants-it helps you find the right ones.
Draft the next application in GrantGunner
Create a free account, add your documents, and draft the form with your team. Create a free account