Independent guidance for better public participation in health and care research
Person reviewing notes and a clear written guide
Make it clear

Support and resources

Reference material and practical prompts for turning complex research into clear, useful plain-English summaries.

Clear writing matters

Help readers find the point of the research

A summary is often the first part of a research application or report that people read. It should explain the essential question, why it matters and what the work will involve without assuming specialist knowledge.

Writing plainly is not about removing important detail. It is about choosing useful words, explaining necessary terms and giving readers a clear route through the information. Review the summary with people outside the research team before it is finalised.

Start here

Build a summary readers can use

These guides provide a workable sequence for planning, drafting and reviewing a plain-English summary.

Decide what to say

Identify the research question, why it is important, who may benefit and what the project will involve.

See what to include →

Write for readers

Use familiar language, short sections and direct explanations. Define technical terms only when they are necessary.

Learn how to write →

Check with others

Invite public contributors to review the draft, note what needs clarification and explain how their feedback was used.

Read about review and support →
Reference material

Resources to support clear communication

Use these established starting points alongside your team’s own review process and the needs of your intended audience.

Plain English guides

Plain English Campaign has downloadable guides on writing in plain English, including guidance for medical information.

Open the plain English guides

Access to Understanding

Guidance for researchers preparing information about biomedical and health research for a non-specialist audience.

Read the guidance

Writing a lay summary

A Digital Curation Centre how-to guide covering information, prompts and resources for preparing lay summaries.

View the how-to guide

Plain-language summary examples

Examples created with family contributors to help shape the headline, content and style of research information.

View summary examples

Lay summary advice

Practical material developed with public members to help teams create an accessible overview of research.

Open the advice

Further writing support

Additional guidance on preparing a lay summary for health research audiences.

Read the guide
A working process

From first draft to final check

Give the summary enough time. Clear communication improves through drafting, feedback and careful revision.

Gather the essentials

Write down the question, purpose, approach, likely contribution and practical commitments in one place.

Choose the reader

Be specific about who needs this information and what they may already know about the topic.

Draft in plain language

Prefer everyday words, active sentences and headings that make the structure easy to scan.

Review and revise

Ask readers for focused feedback, make changes and record what was strengthened through review.

Before you share

A final quality check

  • Purpose is visibleCan a reader quickly tell what the research is trying to understand or change?
  • Language is explainedHave unavoidable technical terms been defined in clear, everyday language?
  • Information is proportionateDoes the summary include enough detail without repeating specialist material?
  • Public feedback is usedHas someone outside the research team reviewed the draft and had time to respond?
Common questions

Support for clear research summaries

Who should review a plain-English summary?

Ask people who are likely to be part of the intended audience, including public contributors where possible. Their feedback can identify terms, assumptions and gaps that a research team may not notice.

How long should a summary be?

Follow the requirements of the application, report or publication. Prioritise the information a reader needs first, then use headings and short paragraphs to make it easier to follow.

Should technical terms be removed?

Not always. Keep a technical term when it is necessary for accuracy, but explain it in clear language the first time it appears.

What should happen after feedback is received?

Review the comments, update the draft where appropriate and let contributors know how their input helped improve the final text.

Where can I find help with research terminology?

The jargon buster is a useful place to start when checking language used in public-facing material.

Need a starting point?

Find the right guidance for your summary

Send a concise description of the research and the stage your draft has reached. Involvestory will help you identify relevant material on this site.

Email Involvestory