What's included

What goes into the summary

  • Study purpose, design, and key results translated out of clinical and statistical terminology into plain language
  • Content structured to match participant-facing plain language summary expectations and templates
  • Readability checked against target reading level before the draft goes to review
  • Figures and visuals simplified or redrawn where a technical table wouldn't communicate the point clearly
  • Terminology kept consistent with the full CSR so the two documents never appear to disagree
  • Draft routed through medical and regulatory review before release to participants or the public

Same facts, different audience

The lay summary is written from the same underlying results as the full CSR, so nothing gets simplified into something the technical report doesn't actually say.

Written for the reader, not the reviewer

Where a CSR narrative describes a case in clinical terms, the corresponding plain language content — built alongside patient narratives writing — is drafted for a participant audience instead.