Manuel B. Garcia

Manuel B. Garcia serves as the Senior Director for Educational Technology and Digital Learning at FEU Institute of Technology, Manila, Philippines. Read More

Contact Info

1607, FEU Tech Building,
P. Paredes St, Sampaloc,
Manila, Philippines
mbgarcia@feutech.edu.ph

Follow Me

How Simple Should Participant Information Be Without Leaving Out Important Information?

Participant information should be as clear and accessible as possible without removing information people need to make an informed decision. Plain language means making complex ideas understandable, not pretending the complexity does not exist.

111
How Simple Should Participant Information Be? Guide 111 of 398
01 · The Question

How simple can participant information become before it stops being adequately informative?

"Use simple language" sounds like straightforward advice until the study involves a complicated procedure, uncertain risk, randomization, data sharing, genetic analysis, or another concept that cannot honestly be reduced to a cheerful sentence.

Researchers then face two competing concerns. Write too technically and participants may not understand the information. Simplify too aggressively and important qualifications can disappear.

The goal is therefore not to make the research sound simple. It is to make the research understandable while preserving the information that matters.

02 · The Short Answer

Simplify the language, not the participant's decision

In Brief

Participant information should use the clearest language and structure appropriate for the intended participants while preserving the risks, procedures, uncertainty, choices, limitations, and other information they need to make an informed decision.

Plain language does not mean deleting complexity or replacing precise information with vague reassurance. When a difficult concept matters to participation, explain it rather than hiding it behind jargon or simplifying it away.

03 · What You Need to Know

What meaningful simplification actually looks like

The strongest participant information often feels simple to read even when considerable work went into making it that way. The researcher has already decided what matters, removed unnecessary jargon, organized related information, and translated technical concepts into concrete explanations.

That is different from merely deleting words.

Plain language is not the same as childish language

Adults do not need to be spoken to like children merely because they are unfamiliar with research terminology.

Plain language respects the reader by reducing unnecessary interpretive work. It uses familiar words when they are accurate, explains unfamiliar concepts, makes relationships between ideas explicit, and helps readers find information.

OHRP states that informed-consent procedures should communicate with the participant population in terms they can understand. The U.S. Common Rule similarly requires information to be provided in language understandable to the participant or legally authorized representative.

In medical research, the 2024 Declaration of Helsinki requires relevant information to be communicated in plain language and calls for particular attention to individual information and communication needs.

Replace jargon when an ordinary word does the same job

Some technical language survives in consent forms simply because researchers are accustomed to it.

"Venipuncture" can usually become "a blood draw using a needle." "Approximately" can often become "about." "Utilize" can usually surrender gracefully to "use."

These changes reduce linguistic difficulty without sacrificing substantive information.

Unnecessary technicality "Participants will undergo venipuncture at three study time points."
Plain but accurate "A trained member of the research team will take blood from a vein in your arm at three study visits."

Explain technical concepts when the concept itself matters

Some terminology cannot responsibly be solved by substitution.

Consider randomization. Replacing the word with "you will be placed into a group" removes an important feature if participants need to know that neither they nor the researcher simply chooses the group.

A better explanation might state that participants will be assigned to one of the study groups by chance, similar to a random process, and then explain any implications relevant to the study.

The principle is simple: remove unnecessary technical vocabulary, but preserve necessary technical meaning.

Concrete descriptions are often simpler than abstract summaries

"You will undergo a series of assessments over the study period" is short, but not especially informative.

"You will complete three online questionnaires: one today, one in four weeks, and one in eight weeks. Each takes about 15 minutes" is longer and considerably easier to understand.

Simplification should therefore not be confused with reducing word count. Sometimes a few additional concrete words remove a great deal of ambiguity.

Short sentences help only when the ideas remain connected

Breaking a complicated paragraph into shorter sentences can improve readability. Breaking every idea into isolated fragments can make relationships harder to follow.

The revised U.S. Common Rule specifically requires consent as a whole to avoid merely providing lists of isolated facts and instead to facilitate understanding of why someone might or might not want to participate.

Participants need relationships between information, not just simpler individual sentences.

Do not simplify away uncertainty

Research often contains uncertainty by definition.

An experimental intervention may or may not help. A risk may be possible but its exact probability may be unknown. Researchers may not know whether a new procedure is better than an established alternative.

Statements such as "This treatment will help your condition" may be easy to understand but ethically misleading when benefit is uncertain.

Clearer wording might be: "We do not know whether this treatment will help you. One reason for doing this study is to learn whether it works."

The second version is simple precisely because it communicates the uncertainty rather than smoothing it away.

Do not simplify away risk

"You may experience some discomfort" sounds accessible, but it may be inadequate if the actual foreseeable risk involves severe pain, significant emotional distress, a meaningful privacy consequence, or another more specific harm.

Plain language should make risk easier to understand, not make it sound smaller.

The nature, seriousness, likelihood, duration, and reversibility of a risk may all be relevant depending on the study and available evidence. Researchers should communicate the dimensions participants reasonably need without manufacturing precision that the evidence does not support.

Do not simplify away choices

Consent becomes less useful when simplification removes the alternatives that make the decision meaningful.

For some research, participants may need to know that ordinary treatment remains available outside the study. In other studies, they may be able to agree to one optional procedure while declining another, depending on the protocol.

If the participant has meaningful choices, simplifying the document should make those choices clearer rather than collapsing them into a single yes-or-no impression.

Prioritize before you simplify

One reason participant information becomes confusing is that every fact receives similar emphasis.

Before rewriting sentences, decide which information is central to the decision. For research governed by the revised U.S. Common Rule, consent must begin with a concise and focused presentation of the key information most likely to help a prospective participant understand why they might or might not want to participate.

Prioritization can make a document feel simpler even when no substantive information has been removed.

Reading grade level is a diagnostic tool, not the definition of plain language

Readability formulas can identify long sentences and difficult words. They cannot determine whether the reader understands a concept.

An integrative review of research consent forms found that consent documents frequently exceeded recommended reading levels. Yet other research has shown that lowering reading level alone does not consistently guarantee improved comprehension.

This distinction matters. You can write "random assignment" using short words and still fail to explain what randomization means.

Use readability metrics, where helpful, to identify possible problems. Do not use them as proof that the document is understandable.

Formatting can support understanding

Plain language is partly visual.

Descriptive headings, manageable paragraphs, adequate spacing, readable typography, and appropriately used lists can help readers locate and process information. Expert consensus guidance for clinical research participant information has similarly emphasized both writing and document design when improving accessibility.

Formatting should reveal structure rather than decorate the page. Bold text loses its usefulness when half the document is bold.

Visuals can help when they explain something real

Some procedures, timelines, probabilities, or study pathways may be easier to understand with diagrams or other visual explanations.

Electronic consent can also incorporate audio, video, graphics, and interactive features. These approaches may be valuable for particular populations or concepts, but multimedia is not inherently superior to well-written text. A systematic review of consent interventions found mixed effects across multimedia approaches, while enhanced forms and extended discussions showed more consistent benefits in the studies reviewed.

Use visuals when they clarify a difficult concept, not because the consent form looked lonely without an infographic.

Translation requires more than translating difficult prose

If the source consent document is dense and confusing, translating it faithfully can produce dense and confusing prose in another language.

Participant information should be understandable in the language in which it is delivered. Researchers should also consider whether examples, concepts, or assumptions transfer appropriately across linguistic and cultural contexts.

Applicable institutional and regulatory requirements may specify how translated consent materials must be prepared, reviewed, or approved.

Accessibility is broader than reading level

Participants may encounter barriers unrelated to vocabulary.

Visual impairment, hearing impairment, dyslexia, cognitive disability, limited digital access, unfamiliarity with research, and other communication needs can influence whether information is usable.

The 2024 Declaration of Helsinki specifically calls for attention to the information and communication needs of individual potential participants in medical research.

Researchers should therefore ask not merely "Is this text simple?" but "Can the people we plan to recruit access and use this information?"

Test the communication, not just the prose

Researchers are poor judges of what their own participants will find obvious. Months spent developing a protocol make specialized concepts feel much more ordinary than they are.

Where feasible, review participant materials with people who resemble the intended audience or with lay reviewers who are unfamiliar with the study. Cognitive interviewing, usability review, participant advisory input, or other forms of pretesting can reveal unclear wording and hidden assumptions.

Such testing does not guarantee comprehension in every future participant, but it can expose problems before recruitment begins.

Watch Out

Never improve readability by changing the substance of the study. If a risk is serious, say so clearly. If benefit is uncertain, preserve the uncertainty. If participants have meaningful alternatives or limitations on withdrawal, explain them. Plain language should remove linguistic barriers, not inconvenient facts.

04 · A Practical Example

Simplifying a difficult concept without changing its meaning

Hypothetical Example

Explaining random assignment in a two-group intervention study

A researcher is preparing participant information for a study comparing a new educational program with the university's usual program. Participants cannot choose which program they receive.

Too technical "Participants will undergo 1:1 randomization to either the experimental intervention arm or the active comparator arm using a computer-generated allocation sequence."
Too simplified "You will be placed in one of two groups."
What was lost The shorter version fails to explain that group assignment is determined by chance and that participants cannot choose their group. Those facts may matter to someone's willingness to participate.
Plain but complete "If you join the study, a computer will assign you by chance to one of two groups. You have an equal chance of being placed in either group, and you cannot choose which group you join. One group will use the new program, while the other will use the university's usual program."
Interpretation The improved version is longer than the oversimplified sentence but easier to understand because it preserves the concept while removing unnecessary technical language.
05 · What Researchers Often Get Wrong

Common mistakes when simplifying participant information

Misconception

"Plain language means making everything shorter."

No. Sometimes a technical expression requires a slightly longer explanation in ordinary language. Clarity is the objective, not minimum word count.

Misconception

"A sixth-grade reading score means participants will understand."

Readability scores describe selected textual features. They do not establish comprehension of study concepts, risks, probabilities, procedures, or choices.

Misconception

"Technical concepts should be removed because participants may find them difficult."

If a concept could affect the participation decision, difficulty is a reason to explain it better rather than conceal it. Unnecessary jargon can go; necessary meaning should remain.

Misconception

"Simplifying risks means making them sound less alarming."

No. The purpose is accurate comprehension, not reassurance. Serious or uncertain risks should remain serious or uncertain after editing.

Misconception

"One plain-language version should work for everyone."

Participant populations differ in language, literacy, age, research familiarity, accessibility needs, and other characteristics. Materials should be appropriate for the people who will actually receive them.

06 · What This Means for You

Edit for comprehension while protecting the meaning

A useful editing strategy is to separate the technical wording from the underlying information. Ask first what the participant needs to understand. Then find the clearest accurate way to communicate it.

A simple editing framework

If a technical word has an accurate familiar equivalent
Use the familiar word.
If the technical concept itself matters to the decision
Explain the concept concretely rather than deleting it.
If shortening a sentence removes uncertainty, risk, choice, or an important qualification
Restore the meaning even if the explanation becomes slightly longer.
If the information is required but difficult
Improve organization, examples, formatting, discussion, or other communication supports instead of omitting it.
If you are unsure whether your intended participants will understand the material
Where feasible, obtain feedback from people unfamiliar with the study or representative of the intended audience before recruitment.

The result should still contain the information participants need before they can meaningfully consent. What changes is the amount of unnecessary work participants must do to understand it.

And if you need to decide whether simplification has actually worked, that moves beyond document design into assessing participant understanding.

07 · A Quick Checklist

Before calling participant information "plain language"

Review the participant information and check:
Have unnecessary technical terms, abbreviations, and specialist expressions been replaced with familiar accurate language?
When a technical concept matters, have you explained rather than deleted it?
Are procedures described concretely enough for participants to picture what will happen?
Have uncertainty and limitations been preserved rather than rewritten as reassuring certainty?
Are risks described accurately without euphemisms that minimize their nature or seriousness?
Are meaningful participant choices and alternatives still visible after simplification?
Does the document use headings, paragraphs, lists, spacing, or other structural features to make information easier to locate?
Is the language and format appropriate for the intended participant population rather than an imagined universal reader?
Have readability scores, if used, been treated as editing aids rather than proof of comprehension?
After simplification, does the material still satisfy the approved protocol and applicable consent requirements?
08 · Frequently Asked Questions

Questions about simplifying participant information

What reading level should participant information use?

There is no single reading level appropriate for every population and research setting. Some institutions recommend particular targets, but readability scores should be interpreted as editing tools rather than guarantees of understanding. The language should be appropriate for the intended participants and comply with applicable requirements.

Should I remove all medical or scientific terminology?

No. Remove unnecessary jargon, but explain terminology or concepts that participants genuinely need. Eliminating a difficult word is not helpful if doing so also eliminates an important feature of the study.

Is plain language less scientifically accurate?

It should not be. Good plain-language writing preserves substantive accuracy while reducing unnecessary linguistic complexity. If simplification changes the scientific or ethical meaning, the wording has been oversimplified rather than successfully translated.

Can pictures or videos replace written explanations?

They can supplement or sometimes communicate particular information effectively, especially in electronic consent, but their adequacy depends on the information, participants, and governing requirements. Visual or multimedia presentation should not omit disclosures that participants still need.

Should participant information be as short as possible?

No. It should be concise enough to remain usable while containing sufficient information for the decision and applicable requirements. Too much information can create problems, but so can too little.

How can I tell whether my simplification went too far?

Compare the revised version with the information participants actually need. If the revision removes or distorts a material risk, procedure, uncertainty, alternative, privacy issue, choice, limitation, or required disclosure, simplicity has been achieved at the expense of informed consent.

Does translating a consent form make it understandable to non-English-speaking participants?

Translation addresses language access, but it does not automatically solve difficult structure, jargon, conceptual complexity, or cultural assumptions. The translated information should itself be understandable and should follow applicable translation and ethics-review requirements.

09 · The Bottom Line

Make the information easier to understand without making the research easier than it really is

The Bottom Line

Participant information should be as simple as it can be without losing the risks, uncertainty, procedures, choices, limitations, and other facts that make the decision genuinely informed.

Replace jargon, explain necessary concepts, write concretely, prioritize important information, and design for the people you are actually recruiting. If simplification changes what participants would reasonably understand about the research, it has gone too far.

10 · Sources and Further Reading

Authoritative and scholarly sources on plain-language consent

11 · Cite this Guide

How to Cite This Guide

This guide is intended to be read, shared, and used in research, teaching, and academic work. If you draw on its ideas, explanations, or other content, please acknowledge the source by citing the guide. Doing so gives appropriate credit and helps your readers locate the original resource.

Has the Field Guide helped your research?

If a guide helped clarify a question, inform a research decision, or move your work forward, I would love to hear about your experience. Your story may also help other researchers discover the Field Guide.

Share Your Experience
Takes only a few minutes