Page renewal summary

This page provides a practical introduction to planning and reviewing plain-English summaries for health, public health and social care research.

Independent guidance for better public participation in health and care research
Resource centre

Plain-English summaries that people can use

A clear summary helps readers understand what a research project is asking, why it matters and what will happen next—without requiring specialist knowledge.

Notebook and clear written notes on a desk
Start with clarity

Explain the work, not just the terminology

A plain-English summary is a short explanation of research written for people who may not know the subject, the methods or the usual technical vocabulary.

It should give enough context for someone to understand the purpose of the work and decide which questions they want to ask. It is not a simplified version of every detail: it is a focused account of the information people need first.

Involving members of the public in drafting or reviewing a summary can reveal unclear phrases, missing context and assumptions that a research team may not notice.

What to include

The essentials of a helpful summary

Use headings and short paragraphs so readers can find the part of the explanation that matters to them.

The research question

State what the team wants to find out. Put the central question before background detail or formal study language.

Who the work concerns

Explain who may be invited, affected or interested, using respectful and specific language where it is relevant.

What will happen

Describe the approach in everyday terms, including the main activities, timescale and what information will be collected.

Write and review

Make each sentence earn its place

When you draft

  • Lead with the purpose of the research.
  • Use familiar words where possible and explain necessary terms.
  • Prefer short, direct sentences with one main idea.
  • Say who is doing what rather than relying on passive phrasing.
  • Use examples only when they make the point clearer.

When you review

  • Check that abbreviations are written out or removed.
  • Look for unexplained assumptions and missing context.
  • Check whether the order answers a reader's likely questions.
  • Ask public contributors what feels unclear or overly formal.
  • Revise after feedback and explain how comments shaped the text.
A simple process

From technical draft to accessible explanation

Clarity improves through deliberate review, not by removing every detail at once.

Identify the audience

Consider what readers may already know, what they need to decide and what information could otherwise be confusing.

Choose the key points

Set out the question, relevance, approach and expected contribution before adding supporting detail.

Write in plain English

Use everyday language, concrete descriptions and helpful headings to create a readable route through the material.

Test and improve

Invite feedback from people outside the project, revise the wording and record the learning for future summaries.

Related guidance

Continue building clear involvement

These resources can support teams as they plan communication, participation and review.

01 / Understand

Getting involved

Learn more about public roles in research and the questions contributors may want to ask.

Read the introduction
02 / Plan

Guidance for researchers

Find practical prompts for designing involvement that is purposeful, supported and responsive.

Explore researcher resources
03 / Build skills

Training resource

Use structured material to develop confidence and shared understanding across a team.

View training guidance
04 / Learn together

Resource libraries

Browse further material, examples and reference resources for public involvement practice.

Browse the libraries
Common questions

Plain-English summary FAQ

Who is a plain-English summary for?

It is for people who may be interested in the research but do not use specialist terms every day. This can include members of the public, potential contributors, participants and colleagues outside the field.

How long should a summary be?

There is no single length. Focus first on the reader's essential questions, then use headings, short paragraphs and links to fuller information where appropriate.

Should every technical term be removed?

No. Some terms may be important, but they should be explained in clear language when first used. A term that does not help the reader understand the message can usually be omitted.

Can public contributors help review a summary?

Yes. They can identify language that feels unclear, check whether the context is sufficient and suggest questions that the text should answer.

What is the difference between involvement and participation?

Participation means providing data as part of a study. Involvement means helping to shape decisions, materials, priorities or communication about research.

Where can I find more guidance?

Visit the frequently asked questions page or return to the resource centre.

Need a starting point?

Ask about clear research communication

Send a concise description of the research material you are trying to explain and the stage your work has reached. Involvestory will help you identify relevant material on this site.

Email Involvestory