Definition
Case report form (CRF): the paper or electronic form a trial site uses to record the protocol-required data on each participant and report it to the sponsor. Visits, measurements, medications and adverse events all go into the CRF. Most clinical trials now use an electronic case report form (eCRF) inside an electronic data capture (EDC) system.
- The protocol drives the CRF: it should collect what the protocol requires, and not much more.
- The CRF is usually not the source: data are copied from medical records, so the two must match or the difference must be explained.
- ICH E6(R3) calls the CRF a data acquisition tool that must be fit for purpose and validated before use.
Updated October 26, 2026
Working with CRFs, EDC and data queries? CRF purpose, structure and data queries are covered in the data management section of the VIARES Clinical Research Associate course.
Contents
- What is a case report form in clinical trials?
- Elements of a CRF: what it collects
- Paper CRF vs electronic case report form (eCRF)
- CRF design: principles and best practices
- The CRF design process, step by step
- Data entry, monitoring and data cleaning
- Example from trial practice
- Regulatory requirements for CRFs
- Practitioner note
- FAQ
- Sources
- Where you learn this at VIARES
Trial data live in hospital charts, lab reports and scans. The sponsor needs the same data points, in the same format, for every participant. The case report form makes that possible.
What is a case report form (CRF) in clinical trials?
CRF stands for case report form. Some older texts say “case record form”; the meaning is the same. The ICH E6(R3) Good Clinical Practice guideline defines it as a data acquisition tool designed to record protocol-required information to be reported by the investigator to the sponsor on each trial participant.
Three ideas sit inside that definition:
- Protocol-required. The protocol decides what to collect; the CRF turns its schedule of assessments into fields.
- Each participant. Every form carries a participant code, not a name, so data stay traceable without exposing identity.
- Reported to the sponsor. The CRF links the site to the sponsor’s clinical database.
E6(R3) groups CRFs with other data acquisition tools, such as patient diaries and wearables. In US law, 21 CFR 312.62 requires investigators to keep adequate and accurate case histories, and names case report forms as part of those case histories.
Elements of a CRF: what it collects
A CRF for a drug trial is built from modules, usually one per topic. Typical modules are:
- Demographics (age or date of birth, sex, and other characteristics the protocol requires)
- Eligibility checklist (inclusion and exclusion criteria) and informed consent date
- Medical history and baseline disease status
- Vital signs, physical exam, laboratory results, ECG and imaging data
- Study drug administration and accountability; concomitant medications
- Efficacy assessments that feed the endpoints
- Adverse events, with a separate path for serious adverse events
- End of study or early termination
Paper CRF pages also carry a header (protocol ID, site code, subject ID) and a footer (investigator signature, date, version and page number), as Bellary et al. (2014) describe. In an eCRF, the EDC system adds most of this automatically.
Paper CRF vs electronic case report form (eCRF)
Paper CRFs survive in some small or academic studies; most sponsor trials use eCRFs.
| Aspect | Paper CRF | Electronic CRF (eCRF) |
|---|---|---|
| Data entry | Handwritten at the site, later entered into a database (often double data entry) | Site staff enter data directly into the EDC system, usually web-based |
| Validation | Errors found later, during data entry or review | Edit checks fire at entry (range, format, consistency); conditional fields appear only when needed |
| Queries | Paper query forms sent to the site | Queries raised and answered in the system, field by field |
| Corrections | Single line through the old entry, new value, initials, date | Automatic audit trail: old value, new value, user, date/time and reason |
| Speed of access | Data reach the sponsor after pages are collected | Near real-time; supports remote and centralized monitoring |
| Regulatory focus | Legibility, storage, version control of printed forms | Computerized system validation, access control, audit trails (21 CFR Part 11, EMA guideline) |
An eCRF and an EDC system are not the same thing. The EDC is the software platform; the eCRF is the set of study-specific forms built inside it. One EDC platform can host eCRFs for hundreds of studies.
CRF design: principles and best practices
Good CRF design decides how clean the clinical data will be; a badly designed form creates queries for months. Widely used principles:
| CRF design principle | What it means | Example |
|---|---|---|
| Follow the protocol | Collect every protocol-required data point; question anything the analysis will not use | Map each field to an objective, endpoint or safety need |
| Define formats and units | Fixed boxes, decimal places and units remove guesswork | Pulse: [ ][ ][ ] beats/minute; Temperature: [ ][ ].[ ] °C; Date: DD/MM/YYYY |
| Prefer coded answers | Checkbox, single select or drop-down lists instead of free text where possible | AE severity: mild / moderate / severe |
| Avoid duplication | Collect each data point once; let the system calculate derived values | Record weight and height; calculate BMI, do not ask for it |
| Use standards | CDISC CDASH defines standard data collection fields that map to SDTM for submission | Reuse a standard vital signs or adverse events module |
| Follow site workflow | Order forms by visit and in the sequence the site collects the data | Vital signs before the dosing form at each visit |
| Clear questions and completion guidelines | No double negatives or leading questions; a CRF completion guideline explains each field | “Did the participant take any concomitant medication?” Yes/No, then a medication log |
For an eCRF, design also covers functionality: edit checks, skip logic (conditional fields), calculations, field-level help text and the user experience on different screens. Bellary et al. state the main goal plainly: CRF design should gather complete and accurate data, avoid duplication, and make transcription from source documents easy, with the primary safety and efficacy endpoints as the main goal of data collection.
The CRF design process, step by step
Details vary by sponsor and CRO, but a typical CRF designing process looks like this:
- Protocol review. Data management, the statistician and the clinical team list every data point the protocol and statistical analysis plan need.
- Draft CRF. The study designers build forms from a standard library where one exists and add study-specific modules.
- Cross-functional review. Clinical, medical, safety and statistics review the draft, ideally with a CRA or study coordinator.
- Build and edit checks. The eCRF is built in the EDC with its edit check specifications; an annotated CRF links each field to its database variable.
- Testing and validation. User acceptance testing confirms the forms and checks work. E6(R3) expects data acquisition tools to be validated and ready before they are used.
- Go-live and change control. Sites get completion guidelines and EDC access; protocol amendments trigger versioned, re-tested CRF changes.
Data entry, monitoring and data cleaning
Once a trial starts, the CRF sits at the center of clinical data management:
- Data entry at the site. Site staff transcribe data from source records into the CRF. E6(R3) section 2.12 requires the investigator to ensure the accuracy, completeness, legibility and timeliness of CRF data, and says data reported to the sponsor should be consistent with source records or the discrepancies explained.
- Source data verification. During monitoring, the CRA compares CRF entries with source documents, focusing on critical data such as consent, eligibility, endpoints and safety.
- Queries. Edit checks, data managers and monitors raise queries; corrections must be traceable and must not obscure the original entry.
- Sign-off and database lock. The investigator endorses the data at agreed milestones; after cleaning and coding, the database is locked for data analysis.
Every step protects data integrity: data that are attributable, legible, contemporaneous, original, accurate and complete.
Example from trial practice: one blood pressure value
This is an illustrative example, not a real study. Imagine a Phase III multicenter trial of a new blood pressure drug at 40 sites. The primary endpoint is the change in seated systolic blood pressure from baseline to week 12.
- At the week 4 visit, a study coordinator enters a systolic value of 1450 mmHg. An edit check flags any value outside the plausible range defined in the edit check specification, and the system asks for a correction before the value is saved.
- The coordinator checks the source: the nurse’s vital signs sheet says 145. The value is corrected. The audit trail keeps the record of the change.
- Two weeks later, the CRA performs source data verification. The nurse’s notes mention “dizziness after standing up”, but the adverse events form is empty. The CRA raises a query.
- The investigator assesses the event, and the site records it on the AE form with onset date, severity and relationship to the study drug.
CRF design stopped the first error; monitoring found the second. Without both, each would have reached the analysis.
Regulatory requirements for CRFs
There is no single “CRF law”. The main rules come from several places:
- ICH E6(R3) (adopted January 2025): investigator duties for CRF data (2.12), sponsor duties for validated, fit-for-purpose data acquisition tools (3.16.1), and CRF samples as essential records (Appendix C).
- FDA 21 CFR Part 11: electronic records and signatures, including audit trails, for eCRFs and EDC systems.
- FDA guidance: “Electronic Source Data in Clinical Investigations” (2013) and “Electronic Systems, Electronic Records, and Electronic Signatures in Clinical Investigations: Questions and Answers” (2024).
- EMA “Guideline on computerised systems and electronic data in clinical trials” (2023): audit trails per field, not per eCRF page, and timely investigator sign-off.
- CDISC CDASH: the data collection standard for CRF fields.
Practitioner note
FAQ
What does CRF stand for in clinical research?
CRF stands for case report form, sometimes called a case record form. It is the paper or electronic form used to record the protocol-required data for each trial participant and report them to the sponsor. An electronic version is called an eCRF.
What is the difference between an eCRF and an EDC system?
An EDC (electronic data capture) system is the software platform. An eCRF is the set of study-specific electronic forms built inside that platform for one protocol. The EDC also provides edit checks, queries, audit trails, user access and data export.
Is a case report form a source document?
Usually not. Most CRF data are transcribed from source records such as medical charts. But when data are entered directly into the eCRF with no earlier record, the CRF is the source. ICH E6(R3) expects the protocol or related documents to identify such data.
Who completes the case report form?
Authorized site staff, such as the investigator and study coordinator, complete the CRF. The investigator is responsible for the accuracy and timeliness of the data and signs off on them. The CRA verifies the data against source documents, and data managers review and query them. If you want to do this work yourself, our guide to becoming a CRA explains the typical route into the role.
Is there a standard case report form template?
There is no single universal template. CDISC CDASH defines standard data collection fields, and CDISC publishes example eCRFs. Many sponsors also keep libraries of standard CRF modules, such as demographics, vital signs and adverse events, and adapt them to each protocol.
Sources
- ICH. E6(R3) Guideline for Good Clinical Practice (2025): sections 2.12, 3.16.1, Appendix B.14, Glossary “Case Report Form” and “Data Acquisition Tool”.
- U.S. eCFR. 21 CFR Part 11: Electronic Records; Electronic Signatures.
- U.S. eCFR. 21 CFR 312.62: Investigator recordkeeping and record retention.
- FDA. Electronic Source Data in Clinical Investigations (2013).
- FDA. Electronic Systems, Electronic Records, and Electronic Signatures in Clinical Investigations: Questions and Answers (2024).
- EMA. Guideline on computerised systems and electronic data in clinical trials (EMA/INS/GCP/112288/2023).
- CDISC. CDASH (Clinical Data Acquisition Standards Harmonization).
- Bellary S, Krishnankutty B, Latha MS. Basics of case report form designing in clinical research. Perspect Clin Res. 2014.
- National Cancer Institute. NCI Dictionary: case report form.
Where you learn this at VIARES
Section 11, “Data Management for Clinical Research Associates”, of the VIARES Clinical Research Associate course covers how the CRF relates to the protocol and to regulatory, GCP and SOP requirements, collecting data with paper and electronic CRFs, monitoring and data validation plans, and when and how to raise and resolve data queries. In the section assignment you draw up a simplified case report form for a candidate malaria vaccine study and explain how results stay traceable to sites and individuals. Section 8, “Monitoring and Closing Clinical Trial Sites”, covers monitoring visits.
The Remote & Centralized Monitoring course (40 hours) includes an assignment in which you review data entered in an eCRF and identify potential issues. A free Micro Certificate CASE REPORT FORM builds on this article. Related terms: data collection and clinical trial.
