.jpg){kind=link}
- Published
- Updated
A participant-facing summary requires more than shortening technical protocol sentences. Readers need to connect the study purpose, activities expected of them and important uncertainties. A short usability discussion can reveal where a summary creates an unintended or misleading expectation.
Define the workflow
Define the summary’s purpose and avoid presenting it as a replacement for consent documentation. Plain-language terms should preserve scientific meaning. Identify the content owner and required review pathway, then consider reader suggestions for both accuracy and understandability.
Worked example
For example, readers interpret the phrase “close follow-up” as continuous personal health surveillance. The team replaces it with a concrete description of visits and contact. They test the revised version again; producing a shorter document is not itself evidence that people understand it better.
Practical checks
- Ask readers to explain in their own words what participation would involve for them.
- Compare positive but vague phrases with the actual activities and frequency described by the study.
- Have the content owner review wording changes for protocol meaning and consistency with approved information.
Decision and boundaries
Acceptance means core questions are understood while important uncertainty remains visible. Do not claim that a summary works for everyone; describe the limits of the group who tested it. Reassess the summary after protocol changes or a different intended use, and appropriately control distribution of older versions.
Frequently asked questions
- Can the summary replace the consent form?
- Do not assume this without confirming purpose and required approvals. Supporting material and the consent process have distinct roles.
- Is a readability score sufficient?
- A score can help, but assess what readers actually understand and which unintended expectations the wording creates.