Clinical Study Report Template: CSR, SAP and DMP
Create separate CSR, statistical analysis and data management outlines with the right ICH anchors. One free input set; editable draft exports.
What this is not: a clearance, approval, consent, signed record or submission. Responsible professional review is required. Jurisdiction: ICH regions; confirm local implementation and data law.
Structured information
Only de-identified, non-confidential information. No names, birth dates, contact details or patient record numbers. Examples are synthetic.
Provider: local deterministic template engine; no AI call or document upload. Inputs and drafts remain in this tab’s memory; reload clears them. Only the allowance and input hash are stored in your browser. Copy or download before leaving. Not a controlled clinical record system.
Build the supporting evidence
Copy or download your draft first. Signup opens the AnswerThis app and does not transfer this result.
How to use this workspace
- Choose the document and confirm its jurisdiction and institutional owner.
- Enter structured information or load the synthetic example, then confirm the de-identification attestation.
- Generate the outline and complete the unfinished prompts in the editor.
- Review the result with its responsible owner and export it into the controlled project workflow.
What to check
- Source edition and local applicability are distinct from the date of your document.
- Use only supported facts; a blank does not establish a negative finding.
- Keep identifiers, population, document versions and evidence consistent.
- Review drafts in the responsible institution’s controlled system before use.
Keep three document purposes separate
This page groups three related authoring tasks without treating their standards as interchangeable. A clinical study report describes and interprets a completed study. A statistical analysis plan specifies how the study questions will be analysed. A data management plan describes how the study’s data will be handled through their lifecycle. The shared metadata connects the documents, but choosing a different option changes the section structure and the source anchors.
The CSR outline uses ICH E3. The SAP uses ICH E9 and the E9(R1) estimand addendum. The DMP uses ICH E6(R3) data-governance and recordkeeping references, alongside the need to identify applicable local privacy requirements. There is no claim of an ICH E3-compliant DMP. Enter the jurisdiction and responsible institution so that the next reviewer can check local implementation and the actual controlled procedures that apply.
Use document-level dates and aggregate population descriptions only. A reporting period or data lock point helps establish which version of the evidence a document should address, but the template does not verify that a lock occurred. Never enter participant identifiers, patient-level tables or confidential trial data into this public page. The synthetic example demonstrates structure rather than a real study outcome.
Complete each outline against its evidence
The CSR prompts provide an organised route through study administration, methods, participant disposition, efficacy, safety and supporting material. They do not generate results. Before replacing a blank, identify the controlled source that supports the statement and check that the dataset, analysis version and table references agree. A favourable conclusion cannot be inferred from an empty safety or efficacy section.
For the SAP, resolve the clinical question and its estimand before choosing an estimator. The outline distinguishes population, treatment condition, variable, intercurrent events and population-level summary, then provides places for the analysis approach and sensitivity work. The page does not choose missing-data assumptions or a strategy for multiplicity. A statistician must assess those decisions in relation to the protocol and record whether they were made before or after access to relevant study data.
For the DMP, describe the actual systems and handoffs. Name responsible roles, data sources, validation and query processes, coding, reconciliation, transfer specifications, access controls, finalisation, retention and disposal procedures in the controlled document. A generic statement that data will be secure is not an operational plan. The section prompts help locate missing work but cannot validate an EDC system, establish an audit trail or confirm that a vendor followed a procedure.
Check consistency across versions
Switching among CSR, SAP and DMP for unchanged inputs uses the same successful allowance. Each output remains an independent editable draft. The page does not automatically merge edits across documents or compare their completed content. Preserve the protocol version, analysis-plan version, data-cutoff conventions and supporting report identifiers when you move the drafts into your controlled authoring environment.
A practical review can begin by following one endpoint through all three documents: how it was collected, how it was analysed and how its result was reported. Resolve inconsistent populations, units, windows or missing-data definitions before writing conclusions. Record deviations and their implications in the appropriate controlled document. The outline does not establish that an analysis was prespecified merely because it appears under a planning heading.
Blank content is explicitly marked [To be completed]. Complete it with verified project information or a reviewed applicability explanation. Markdown, rich copy and Word-compatible text exports retain the draft warning, and editing or re-export does not use another run. Rendering is deterministic and local, with no AI call. The output is not approved, signed or submitted; responsible clinical, statistical and data-management review remains necessary before any external use.
Sources, versions and jurisdiction
Jurisdiction: ICH regions; confirm local implementation and data law. Source review as of 2026-09-14. Source retrieval: 2026-09-13T22:50:11Z (editorial review, not a live document lookup). No agency endorsement. Original concise outlines with links; source documents remain the work of their respective owners. ICH materials © ICH; prompts are adapted summaries, not official templates.
- ICH E3 — 1995-11-30
- ICH E9 — 1998-02-05
- ICH E9(R1) — 2019-11-20
- ICH E6(R3), principles and Annex 1 — 2025; corrected 2025-10-24
Frequently asked questions
When should I choose CSR, SAP or DMP?
Use CSR to organise study reporting, SAP for planned analyses and DMP for data handling responsibilities. They remain separate documents with different source anchors.
Where do estimands belong?
The SAP prompts the treatment effect and handling of intercurrent events under E9(R1). The CSR reports the analysis actually performed and explains relevant departures; it does not retrospectively approve a plan.
Who completes the data-management plan?
The responsible data-management and study teams define capture, validation, reconciliation, access, transfer and retention. An E6-based DMP is not an E3 clinical study report.
How should the documents hand work between teams?
For example, the DMP defines the reconciled analysis dataset; the SAP defines its analysis population; the CSR reports the resulting counts. Keep the dataset version, study identifier and amendments consistent across all three exports.
Can I enter patient records or confidential information?
No. Use only de-identified, non-confidential information. Do not enter names, birth dates, contact details, record numbers, signed forms or source records. The tools do not de-identify records for you.
How many free runs are included?
This page includes one successful free input set per browser. Failed requests and re-exporting a result are free. Subtemplates share the allowance; the same inputs can be used across them freely.
Does signup transfer my work or unlock more page runs?
Signup opens the AnswerThis app. It does not unlock more runs here or transfer your draft. Copy or download the result first.