On this page:
- What Is a Clinical Data Management Plan?
- What Is a Research Data Management Plan?
- CDMP vs RDMP: Side-by-Side Comparison
- Common Questions Answered
- Why the Distinction Matters for Research Administrators
- Looking Ahead
A clinical data management plan and a research data management plan are two of the most frequently conflated documents in the clinical trial lifecycle. Both use the acronym “DMP” in casual conversation, both get drafted before a study starts, and both concern “data” in the broadest sense — but they answer to different masters, cover different lifecycle stages, and are read by different audiences. Submitting the wrong one to the wrong reviewer is a recurring, avoidable compliance headache for trial units and research offices alike.
What Is a Clinical Data Management Plan?
A Clinical Data Management Plan (CDMP) is an operational, trial-specific document that describes exactly how data will move from case report form (CRF) to locked database. It is written by or with the clinical data management (CDM) function — not the principal investigator’s grants office — and it sits alongside the protocol as one of the working documents that Good Clinical Practice (GCP), per ICH E6, expects a sponsor to maintain and be able to produce on inspection.
A CDMP typically specifies:
- CRF or eCRF design and the electronic data capture (EDC) system to be used
- Database build, edit-check specifications and data validation rules
- Data entry conventions (single vs double entry, query turnaround)
- Medical coding dictionaries and versions, such as MedDRA and the WHO Drug Dictionary
- Discrepancy management and serious adverse event reconciliation procedures
- Roles, responsibilities and sign-off authority for database lock
Because it is inspected against GCP, a CDMP is a living, version-controlled document updated through the study rather than filed once and forgotten.
What Is a Research Data Management Plan?
A Research Data Management Plan (RDMP) is a funder- or institution-facing document submitted at the grant proposal stage, well before a trial’s CDMP would even exist. Its job is compliance with funder and institutional data policy, not trial operations. UK Research and Innovation (UKRI) requires a data management plan for relevant grant applications, Horizon Europe applicants complete one through the Data Management Plan template built into the Horizon Europe Programme Guide, and the NIH Data Management and Sharing (DMS) Policy has required a DMS plan for NIH-funded research since January 2023.
An RDMP typically covers:
- What data types and volumes the project will generate or reuse
- How data will be described, documented and made findable (metadata, identifiers)
- Storage, security and access-control arrangements during the project
- Ethical, consent and legal constraints on sharing (particularly for identifiable participant data)
- Long-term preservation and repository plans, often with a DOI issued via DataCite
- Alignment with the FAIR principles — Findable, Accessible, Interoperable, Reusable
Unlike a CDMP, an RDMP is reviewed once (or at defined milestones) by a funder or research office, not audited line-by-line by a regulator during a GCP inspection.
CDMP vs RDMP: Side-by-Side Comparison
The table below sets out where the two documents genuinely diverge, so institutions running funded clinical trials know they usually need both — not one instead of the other.
| Dimension | Clinical Data Management Plan (CDMP) | Research Data Management Plan (RDMP) |
|---|---|---|
| Primary purpose | Ensure trial data is accurate, complete and audit-ready for database lock | Satisfy funder/institutional policy on data stewardship and sharing |
| Governing framework | ICH E6 Good Clinical Practice; sponsor/CRO SOPs | Funder mandates (UKRI, NIH, Horizon Europe); institutional RDM policy |
| Typical author | Data manager / clinical data management lead | Principal investigator, often with library or research office support |
| Created at | Study set-up, before first patient enrolled | Grant proposal stage, before funding is awarded |
| Primary audience | CDM team, biostatisticians, sponsor, regulatory inspectors | Funder, ethics/IRB reviewers, institutional research office |
| Content focus | CRF design, edit checks, coding, database lock procedures | Data description, storage, ethics, sharing, long-term preservation |
| Review cadence | Continuously updated through study conduct; inspected on audit | Reviewed at proposal and, for some funders, at defined milestones |
Common Questions Answered
What does a clinical data management plan include?
A clinical data management plan includes CRF or eCRF specification, database design, data entry and validation procedures, edit-check logic, medical coding dictionaries such as MedDRA, discrepancy and adverse-event reconciliation processes, and clearly defined roles and responsibilities through to database lock, all maintained as a living, version-controlled document inspected under Good Clinical Practice.
What should a data management plan include?
A funder-facing research data management plan should describe the data types and volumes a project will generate, how data will be documented and made findable through metadata, storage and security arrangements, ethical and consent constraints on sharing identifiable data, and the eventual repository and preservation route, typically aligned to the FAIR data principles.
What are the three phases of clinical data management?
Clinical data management is generally organised into three sequential phases: study set-up, covering database build and CRF design; study conduct, covering data entry, cleaning and query resolution; and study close-out, covering final reconciliation, coding sign-off and database lock ahead of statistical analysis.
Why the Distinction Matters for Research Administrators
Institutions running externally funded clinical trials almost always need both documents, produced by different teams on different timelines. A funder reviewer looking for a FAIR-aligned sharing and preservation strategy will not find it in a CDMP’s edit-check specification — and a GCP inspector auditing database lock will not accept an RDMP’s high-level data-sharing statement as evidence of query resolution procedure.
This is precisely the coordination gap that research administration functions increasingly exist to close: aligning the pre-award compliance document (the RDMP, owned by the grants office) with the operational trial document (the CDMP, owned by clinical data management) so that neither is quietly missing when a funder audit or a regulatory inspection arrives. Institutions that treat the two as interchangeable risk both funder non-compliance and GCP findings — for two entirely separate reasons.
Consistent terminology helps here. Reviewers, auditors and research offices benefit from a shared reference for what each document is called and what it covers; the CASRAI research administration dictionary maintains definitions for terms that span exactly this pre-award-to-conduct boundary.
Looking Ahead
The line between the two documents is not static. ICH’s ongoing revision of E6 Good Clinical Practice has pushed sponsors toward more explicit, risk-based data governance language inside the CDMP itself, while funders such as UKRI and the NIH continue to tighten expectations for FAIR-aligned sharing inside the RDMP. Institutions that keep the two plans distinct — but explicitly cross-referenced — will be best placed to satisfy both regulators and funders as each side’s requirements keep evolving.
