What a Plain-Language Summary Must Contain

A plain-language summary of clinical-trial results must let a member of the public understand what was studied, why it was studied, who participated, what happened, what benefits and adverse reactions were observed, and how certain the conclusions are. It is not a promotional abstract and not a version of the scientific summary with technical terms merely deleted.

For medicinal-product trials governed by the EU Clinical Trials Regulation, Article 37 requires a results summary accompanied by a summary understandable to laypersons. Annex V specifies eleven content areas. The obligation applies irrespective of the trial's outcome. A summary must therefore report a trial that was favorable, negative, inconclusive, or stopped early with the same commitment to completeness.[1][2]

Key takeaways#

• EU Annex V requires trial identifiers, sponsor contact information, trial context, participant information, treatments, adverse reactions, results, outcome comments, follow-up plans, and links to more information.
• Plain language preserves meaning and uncertainty; it does not replace data with “worked,” “safe,” or other vague conclusions.
• Group sizes, denominators, time frames, absolute numbers, estimates, and limitations make results interpretable.
• Benefits and harms need balanced prominence, and adverse-reaction frequency should be tied to the relevant treatment group.
• Comprehension testing, translation review, accessibility, privacy checks, and consistency with the scientific results are part of quality.

Which rule is being applied#

“Plain-language summary” can refer to several documents. A journal may publish a plain-language abstract. A sponsor may return an individual participant's own results. A medical-device investigation may require a summary understandable to the intended user. A research funder may impose another format. Those duties are related but not interchangeable.

This article focuses on the public results summary for medicinal-product clinical trials under Regulation (EU) No 536/2014. Since 31 January 2025, all clinical trials in the EU and EEA have been required to operate under the Clinical Trials Regulation through the Clinical Trials Information System, or CTIS.[4] Historical trials and trials in other jurisdictions can follow different rules.

Article 37 generally sets a deadline of one year after the end of the trial in all Member States concerned, though the regulation permits later submission when scientific reasons described in the protocol make the results unavailable within that year; the protocol must state and justify when submission is expected. Separate pediatric and historical-trial provisions may create other timelines, so check which regime applies to your trial rather than applying one deadline to every record.[2]

The public lay summary is different from returning an individual's allocation or personal measurements. It reports group-level trial results. Any participant communication plan must also address consent, privacy, timing, incidental findings, and whether individual data are validated and suitable to return.

The eleven Annex V elements#

Annex V requires information on the following areas:

1. Clinical-trial identification, including the title, protocol number, EU trial number, and other identifiers.
2. The sponsor's name and contact details.
3. General trial information, including where and when it took place, its main objectives, and why it was conducted.
4. The participant population, including numbers in the Member State, across the Union, and in third countries, age and gender breakdowns, and key inclusion and exclusion criteria.
5. The investigational medicinal products used.
6. Adverse reactions and their frequency.
7. The trial's overall results.
8. Comments on the outcome.
9. Whether follow-up trials are planned.
10. Where additional information can be found.
11. Where the scientific results summary can be found.[2]

Treating these as headings can improve coverage, but compliance is not a check-box exercise. The content has to form a coherent account. Your reader has to connect each product with its group, each result with its outcome and time point, and each adverse reaction with a denominator.

The trial's public identifiers should be exact and searchable; a short public title can appear with the formal title, but it should not replace the protocol number or EU trial number. Sponsor contact information should lead to a maintained function rather than one person's temporary address.

Explain why the trial was done#

The background should describe the condition, current care, unresolved question, and trial objective without overstating need or novelty. Explain whether the study tested efficacy, safety, dose, prevention, diagnosis, another purpose, or several purposes.

A useful objective names the comparison and outcome. “To study medicine A” is too vague. “To compare medicine A with placebo, both added to usual care, on average symptom score after 24 weeks” tells readers what the study could answer.

Explain the phase only if it adds meaning. A phase number does not tell the reader whether the trial was randomized, controlled, blinded, or designed around a surrogate outcome. Those design features should be stated directly.

Context must not become marketing. Words such as breakthrough, revolutionary, excellent, or highly successful require scrutiny and usually removal. The reason for a trial can be compelling without promotional framing.

Describe the design in usable terms#

Whoever reads the summary should know how participants entered groups, whether the groups were compared concurrently, who knew the assignments, how long treatment and follow-up lasted, and what other care was allowed. Translate the concept before introducing the term.

For randomization, explain that assignment was determined by chance to make the groups comparable. For blinding, say which people did not know the assignment and why that reduces biased measurement or behavior. For placebo, describe what it contained and whether all groups continued usual care. Avoid saying placebo means “no treatment” when background treatment was provided.

State how many participants were assigned, treated, completed, withdrew, or were lost to follow-up in each group. Explain major reasons for non-completion. A participant flow diagram can help, but it needs labels, text alternatives, and numbers that match the narrative.

If the trial stopped early, say who made the decision, when, and why. Stopping for benefit, harm, futility, recruitment difficulty, supply failure, or a business decision has different implications. “The study ended” is not enough.

Describe who participated#

Population descriptions should help your reader judge relevance without exposing anyone's identity. Report the required geographic totals, age groups, and gender breakdowns, along with important disease features and eligibility criteria. Very small cells may need privacy-aware aggregation under the applicable disclosure rules.

Explain how the study population differed from people likely to receive the treatment. Excluding older adults, pregnant people, those with kidney impairment, or people using common co-treatments can limit generalizability. A trial is not defective merely because eligibility was narrow, but the summary should preserve that boundary, and it should not imply that demographic representation establishes equal effectiveness across every subgroup. Subgroup conclusions require appropriate analyses and adequate precision; reporting the participant mix is necessary, and claiming subgroup-specific benefit is a separate question.

Name treatments and regimens clearly#

For each group, state the medicinal product, dose, route, frequency, treatment duration, titration if any, and relevant background care. Use a nonproprietary name where possible and explain unfamiliar terms. Group labels should remain consistent across text, tables, and figures.

Describe the comparator honestly. If participants received placebo plus standard care, say so. If an active comparator was used at a particular dose, identify it. If treatment switched or rescue medicine was permitted, explain the rule and how it affected the analysis. Nobody should have to infer whether your numbers refer to everyone assigned, everyone treated, or only the participants with complete observations, so label the analysis population in ordinary language and then give the relevant count.

Report results with enough numbers#

Plain language does not mean number-free language. “Symptoms improved” leaves the magnitude, comparator, and time frame unknown. “At week 24, the average score decreased by X points in one group and Y points in the other” is more informative, provided the scale and direction are explained.

Prefer absolute results alongside relative comparisons. If 2 of 100 participants had an outcome in one group and 4 of 100 in another, a “50 percent reduction” alone exaggerates how much you have actually told them. Give denominators, time points, units, and the direction of better scores.

For continuous outcomes, state the group values or changes and the difference between groups. For time-to-event results, explain the follow-up and avoid translating a hazard ratio into a simple probability reduction. For binary outcomes, give counts or percentages in each group before a relative measure.

Uncertainty can be described without a statistics lecture. A confidence interval can be called a range of values reasonably compatible with the estimate under the analysis assumptions. If the range includes no effect and effects that would matter, say that the trial did not distinguish among those possibilities precisely. The article on what a confidence interval is not provides additional context. Avoid equating p above 0.05 with “no difference” or p below 0.05 with proof. The p-value explainer shows why magnitude, precision, design, and multiplicity are needed.

Report adverse reactions in balance#

Annex V calls for adverse reactions and their frequency. Distinguish adverse events, serious adverse events, adverse reactions judged related to treatment, discontinuations due to events, and deaths where relevant. The categories answer different questions.

Use the same denominator discipline as for benefits. “Headache was common” is weaker than the number and percentage in each group over the stated period. If participants can have more than one event, explain whether a table counts people or events. State the coding period and any threshold used to select which reactions appear.

Do not place benefits in the opening and bury harms at the end. Comparable prominence helps the person reading it make sense of benefit and risk. At the same time, a summary should not imply causation for every event observed after treatment. Explain the category used and preserve uncertainty about attribution.

Rare harms may not appear in a trial of modest size, and a truthful summary can state that the study was too small or too short to rule out uncommon or delayed problems. Absence of an observed event is not proof that the event cannot occur.

Explain limitations and the outcome#

“Comments on the outcome” should help your reader understand what the results support. State whether the main objective was met according to the prespecified analysis, but do not stop at that label. Report the effect and uncertainty, secondary findings, and important departures from the plan.

Common limitations include small sample size, short follow-up, missing observations, high discontinuation, open-label design, changed endpoints, early stopping, narrow eligibility, low event rates, imprecise estimates, and analyses selected after results were known. Not every limitation needs equal space. Prioritize those that could change interpretation.

An inconclusive trial still produces information: it may show that estimates are too imprecise, the endpoint did not perform as expected, recruitment was inadequate, or several effects remain compatible with the data. A negative result should not be rewritten as a “positive trend.” Separate trial evidence from later decisions. A regulatory authorization, product withdrawal, or decision not to develop further can be noted when relevant, but it does not alter what the trial measured.

Make the language understandable and test it#

Use familiar words, short sentences, informative headings, and one term for each concept. Define technical language at first use. Prefer “high blood pressure” to “hypertension” unless both are useful, and explain outcome scales rather than naming them alone.

Readability formulas can flag long sentences and difficult vocabulary, but they cannot prove comprehension. Your text can score well while hiding the comparator, reversing the meaning of a scale, or oversimplifying uncertainty. Review by people from the intended audience is more informative. Ask them to explain the design, main result, harms, and limitations in their own words.

Tables and graphics should answer a defined question. Start axes at sensible values, label denominators, identify time points, use accessible colors, and provide text alternatives. Decorative graphics can distract from small absolute differences.

Translations need conceptual review, not only word substitution. Medical terms, number formats, sentence structure, and health-literacy conventions vary by language. A native-language reviewer should check accuracy and usability. The source-language and translated versions must tell the same statistical story.[1][3]

Quality control before submission#

Reconcile every number with the scientific results summary and analysis output. Confirm trial identifiers, dates, group labels, participant totals, outcome values, adverse-reaction counts, and links. Verify that changed analyses and early stopping are described consistently.

Four checks close the file. Run privacy and confidential-information checks without removing information the law requires to be public, confirm the contact details will still be maintained after the team that ran the trial has moved on, test the links to the scientific summary and the registry record, and open the document on a phone and with assistive technology where you can.

Keep a version history showing source tables, reviewers, translation controls, audience testing, and final approval. That record turns plain-language quality from an impression into a reproducible process. The site's research approach uses the same traceability principle.

References#

1. European Commission: Summaries of Clinical Trial Results for Laypersons
2. Regulation (EU) No 536/2014, Article 37 and Annex V
3. EudraLex Volume 10: Clinical Trials Guidelines
4. European Commission: Clinical Trials and CTIS