Making funding applications clear

Plain-English summaries help readers understand the purpose, methods and relevance of proposed health and care research without needing specialist knowledge.

Person reviewing notes for a research application

Archive guidance

Plain-English summaries in research funding applications

A good summary explains a proposed study as a whole, using everyday language and a structure that people can follow.

This archived guidance concerns research funding applications that ask teams to provide a clear, concise summary for reviewers and panel members. The summary is an important part of an application because it helps a wider range of readers understand what is being proposed and why it matters.

For funding applications, a plain-English summary should stand on its own. It should give a balanced account of the research question, the planned approach and the people or communities the work may affect.

What to cover

What problem or question the research will explore.
Why the topic matters and who may benefit from better knowledge.
What the research team plans to do, in clear and proportionate detail.
Who may be invited to take part and what taking part could involve.
How public perspectives have informed, or could inform, the work.
How the team intends to share findings when the research is complete.

Write for real readers

Avoid unexplained abbreviations, technical terms and long sentences. When a specialist term is essential, explain it the first time it appears. Ask people outside the research team to read the summary before it is submitted; their feedback can reveal where an explanation is unclear or where important context is missing.

How to write a summary Explore plain-English summaries

Before submission

Build clarity into the process

Writing clearly is easier when it is planned early and checked by people with different perspectives.

Start with the essentials

Set out the main question, the reason for the work and the intended approach before adding detail.

Use accessible language

Choose familiar words, explain necessary terms and keep one main idea in each sentence.

Ask for feedback

Invite readers who are not part of the research team to test whether the summary is clear and complete.

A practical sequence

From first draft to final summary

Use feedback to improve understanding, rather than simply shortening the text.

Identify the audience

Consider the range of people who may read the application and what context they need.

Draft the core story

Describe the question, the need and the proposed work in a straightforward order.

Test understanding

Ask independent readers what they think the study is trying to achieve.

Revise and check

Act on useful feedback, check terminology and make sure the summary matches the application.

Questions to consider

Plain-English summary FAQ

Is a plain-English summary just a shorter abstract?

No. An abstract is usually written for specialist readers. A plain-English summary is written for a wider audience and should explain the research without assuming prior technical knowledge.

Who should review the summary?

It is helpful to involve people who are not members of the research team, including people with relevant lived experience where appropriate. Their comments can show whether the language and structure work for intended readers.

How much detail about methods is needed?

Include enough information to show what the study will involve, while avoiding procedural detail that does not help a general reader understand the plan.

Should abbreviations be used?

Use abbreviations sparingly. Write a term out in full and explain it before using an abbreviation, or avoid the abbreviation if it is not needed.

How can public involvement be described?

Explain plainly how contributors have influenced the proposal and what opportunities there will be for involvement as the research progresses. Be specific about roles and possible influence.

Where can I find more support?

Explore the plain-English summaries resource area, read the briefing notes for researchers or consult the jargon buster.

Need a starting point?

Find the right resource for your application

Send a concise description of the stage your work has reached and the guidance you are looking for.

Email Involvestory