Explain a study in a plain-language summary

A plain-language summary should make a study easier to understand without making its findings sound simpler or stronger than they are. The work is more than replacing technical words with shorter ones. You have to decide who the summary is for, what that reader needs to know, and how to retain the original study’s scope and uncertainty in a much shorter explanation.

The exact format varies. A journal may request a text paragraph beside the abstract, a graphical summary, key points, or a separate publication. Some journals make a plain-language summary mandatory; others make it optional or do not offer one. Check the current instructions for the specific journal and article type before drafting.

This guide shows how to turn one wholly fictional study into a concise summary for a defined audience. It is an editorial method, not a universal template or a substitute for the journal’s word limit, structure or submission rules.

Decide what kind of summary the journal wants

“Plain-language summary” can refer to different things. Taylor & Francis distinguishes a text summary within the research article, a graphical summary, and a standalone Plain Language Summary of Publication. These formats can have different lengths, authorship, permissions and review requirements. Its text summaries are recommended at 250 words or fewer; the standalone format is a different publication with its own requirements. AGU, for example, asks for a single paragraph of no more than 200 words for relevant journal submissions. Those are publisher-specific rules, not universal limits.

Before writing, check the journal’s instructions for authors and confirm:

• whether this article type needs a summary;
• whether the journal accepts a text, graphical or standalone format;
• who the intended readers are;
• the required heading, structure and maximum length;
• whether the summary is reviewed or submitted in a separate file;
• any requirements for definitions, figures, keywords, declarations or permissions.

A short text summary attached to an original research paper is not automatically the same as a standalone plain-language article. Sage’s current guidance for a standalone publication, for example, includes requirements about original-article author involvement and permissions in some cases. Do not assume one format’s rules apply to another. When needed, clarify the destination first; checking journal scope before reformatting is a related but separate task.

Name the reader before you simplify

“General audience” is too broad to guide every decision. A patient, a local policymaker, a practitioner and a researcher from another discipline may need different context even when they read the same study.

Write a short audience note before you draft:

This summary is for [specific reader] who wants to understand [what decision, question or interest], but may not know [specialist terms or field-specific context].

This is a planning aid, not necessarily a sentence to include in the final summary. It helps you decide which background needs explaining and which technical details can be removed without changing the message. If the journal asks authors to state the audience, use the requested place and wording.

A plain-language summary should still be accurate for readers within the field. Plain language means the reader can follow the explanation; it does not mean eliminating methods, uncertainty or limitations that matter to interpreting the finding.

Build a source-of-truth record from the completed paper

Start with the final manuscript, not a press release, an old abstract or an early proposal. Pull out the study’s purpose, design, participants or material, main result, uncertainty and most important limitation. Keep the exact units and comparison beside any number you may use.

On a narrow screen, scroll sideways to compare the fictional manuscript facts with the wording they allow.

All college names, figures and study details in this example are invented. They are teaching material, not research evidence. The arithmetic is 498 − 402 = 96 additional entries; 96 ÷ 402 is approximately 23.9%, rounded to 24%. The denominator is the earlier period’s entry count, and neither count represents unique users.

This record prevents an accessible rewrite from silently turning “more entries” into “more students,” or a before-and-after difference into an established cause. If the manuscript does not report a quantity or conclusion, do not add it to make the summary feel complete.

Draft the explanation in a reader-first order

A practical sequence is: why the question matters, what the researchers examined, how they examined it, what they found, and what can reasonably be taken from the result. Some journals prescribe different headings or ask for a single paragraph. Treat the sequence as a planning path and adapt it to the required format.

For the fictional library study, a first draft for students and campus decision-makers might read:

Why was the study done? Students may need access to study space before the usual weekend opening time. Researchers examined a six-week trial in which one college library opened two hours earlier on Saturdays. What did they find? Counters recorded 498 entries during the six pilot Saturdays and 402 during the same number of Saturdays in the previous term. In an optional survey, 41 of 62 respondents said the earlier opening helped them study that day. What does this mean? The pilot period had more recorded entries, and most survey respondents reported a same-day benefit. Because the comparison was with a previous term and the survey was optional, the study cannot show that the earlier opening caused the increase or that all students benefited.

This example is not a recommended word limit or heading set. A journal may require a shorter single paragraph. If you compress it, preserve the key comparison and the qualifications that change how the result should be read.

Translate concepts, not just vocabulary

A substitution can be technically accurate but still unclear. Explain what the concept does in this study, and use a brief definition only where the reader needs it.

On a narrow screen, scroll sideways to compare each technical phrase with a clearer version and its evidence check.

Plain wording should keep the actor and action clear. Prefer “researchers counted library entries” over “library usage was measured,” when that is what happened. Avoid decorative metaphors that imply a mechanism or result the paper did not test.

The Science Societies’ author guidance and AGU’s PLS guidance both recommend explaining the topic and findings without unnecessary jargon, and checking whether an intended reader outside the specialty can understand the result. A readability score can flag long or dense sentences, but it cannot tell you whether you changed a claim, used an unfamiliar everyday word, or removed an important limitation.

Keep uncertainty and boundaries visible

A plain-language summary may be the first part of a paper that someone reads, so its compact wording has to carry the same evidence boundaries as the manuscript. Check these items before you remove them:

• Design: Was the research observational, experimental, qualitative, a review, or another design? Use language that does not imply a stronger design than was used.
• Population or material: Who or what was studied? Do not turn one site, sample, document set or participant group into a claim about everyone.
• Comparison: What exactly was compared, over what time, and against which reference?
• Measurement: Are the reported counts people, visits, responses, samples or events? Keep the unit.
• Uncertainty: Does the study report an estimate, range, qualitative theme or mixed result? Do not replace it with certainty for readability.
• Limitations: Which limitation would change a reader’s interpretation? Keep at least the most consequential one within the available space.
• Implications: Does the paper support a possible implication, a practical suggestion or a proven outcome? Do not advance from one to another without evidence.

The journal-specific summary can be shorter than the discussion, but it should not have a stronger conclusion than the discussion. If you need help with the difference between a journal abstract and its headings, use the separate structured abstract guide. A plain-language summary changes the audience and expression; it should not quietly replace the abstract’s scientific function or introduce a new result.

Test the draft with the intended reader

Ask a reader who is reasonably close to the intended audience and unfamiliar with the paper to explain, in their own words:

1. What question did the researchers examine?
2. What did they do or compare?
3. What did they find?
4. What should a reader not conclude from this result?

If the reader repeats an overclaim, misses the main result or cannot explain a necessary term, revise the relevant sentence. Do not ask the reader to judge whether the research is methodologically sound unless that is their role. A comprehension check evaluates the explanation, not the study.

If a non-specialist reader is not available, read the draft aloud, circle field-specific terms, and check each one against the intended audience note. Then compare the final version sentence by sentence with the source record and manuscript. A readability formula can be one signal among several; it is not a pass/fail measure of access or accuracy.

A final summary audit

Before submission, confirm that:

• the summary type, audience, location, word limit and required structure match current journal instructions;
• each claim is present in the completed manuscript and does not add a new result or implication;
• the question, study design, population/material and main finding remain recognisable;
• numerical values retain their units, denominator, timeframe and comparison;
• technical terms are removed or explained without introducing a misleading synonym;
• the strongest relevant uncertainty and limitation survive the shortening;
• the wording does not turn association into cause, responses into all participants, or a single study into settled practice;
• an intended reader can explain the main finding and its limits;
• any additional rules for a graphical or standalone product have been checked separately.

A plain-language summary is a second route into the same study, for a reader who may not use its specialist vocabulary. Draft it from the completed evidence, test whether the intended reader understands it, and make sure it still says no more—and no less—than the research supports. For help preparing your own completed manuscript for submission, journal manuscript support can provide editing and development while leaving research decisions and authorship with the author.