Clinical data management is a team discipline. Turning raw trial data into a clean, locked dataset depends on several specialised roles working in sequence and in parallel — each accountable for a different part of the data lifecycle. Understanding who does what is essential whether you are building a data management team, entering the field, or coordinating with one as a sponsor or vendor.
This guide sets out the core roles in a clinical data management team, the functions that interface closely with it, and how responsibilities divide between a sponsor and a contract research organisation (CRO). It describes functional roles rather than system permissions: who is accountable for which activities, not which buttons each login can press.
Why clear roles and responsibilities matter
Good Clinical Practice expects clearly defined roles, documented responsibilities, and evidence that the people performing each activity are qualified and trained to do so. Beyond compliance, clarity is what keeps a complex, multi-party process running: when everyone knows who owns the data management plan, who builds the edit checks, who codes the adverse events, and who signs off the clean file, work moves without gaps or duplication. Ambiguous ownership is one of the quietest causes of delay and error in clinical trials.
The core clinical data management roles
Clinical Data Manager
The clinical data manager (often the lead data manager) owns the data management deliverables for a trial. They author and maintain the Data Management Plan, oversee the cleaning strategy, coordinate the other roles, and are accountable for delivering a clean, locked database on time. They are the central point of contact for data management questions and the person who ultimately answers for data quality and timelines.
Clinical Data Coordinator / Data Management Associate
Data coordinators and data management associates carry out the day-to-day work of data review and cleaning. They run and review listings, raise and track queries to sites, perform manual checks that automated edit checks cannot, and keep the discrepancy log moving. This is also the most common entry point into the field, with responsibility growing toward the data manager role over time.
Database Programmer / Developer
The database programmer builds and configures the study database in the electronic data capture (EDC) system: the eCRF, the edit checks, the data validation logic, the integrations with external sources, and the data exports. Their work during set-up determines how much can be caught automatically during conduct, which is why close collaboration between programmer and data manager early on pays off throughout the trial.
Medical Coder
Medical coders assign standardised dictionary terms to the verbatim terms recorded for adverse events, medical history, and medications, using dictionaries such as MedDRA and WHODrug. They apply coding conventions consistently, raise coding queries when a term is ambiguous, and prepare coded data for medical review. On smaller teams, coding may be handled by the data manager or coordinator rather than a dedicated coder.
Roles that interface with clinical data management
Several functions sit outside the core data management team but work so closely with it that their responsibilities are part of the same process.
Medical Monitor / Medical Reviewer
The medical monitor provides clinical judgement: reviewing adverse events and coded terms for clinical sense, assessing patterns in the data, and making the medical decisions that data managers are not qualified to make. Their review is especially important for safety-relevant data.
Biostatistician and Statistical Programmer
The statistics function defines how the data must be structured for analysis — including standards such as CDISC — and receives the locked dataset. Because their requirements shape the database design, they are involved from set-up, not only at the end. Clear hand-over between data management and statistics is a defining feature of a smooth close-out.
Quality Assurance and Quality Control
Quality functions provide independent oversight: confirming that processes are followed, documentation is complete, and the data and systems meet the required standards. QC checks are often built into the data management workflow itself, while QA provides the independent assurance and audit perspective.
Sites, monitors, and the safety team
Site staff — coordinators and investigators — enter the data and respond to queries. The investigator, in particular, is a formally defined responsibility owner under GCP: accountable for the integrity and accuracy of the trial data recorded at their site, which is why corrections to site-entered data flow back through queries to the site rather than being made by the sponsor.
Clinical research associates (monitors) verify data against source. The pharmacovigilance team maintains the safety database that data management reconciles against. None of these sit inside the data management team, but the data lifecycle cannot function without them.
Sponsor versus CRO: who is responsible?
Data management is frequently outsourced to a CRO, in whole or in part, but outsourcing changes who performs the work, not who is ultimately accountable. Under ICH E6 Good Clinical Practice, the sponsor retains responsibility for the quality and integrity of trial data and for oversight of any delegated activity. A CRO may run the database, clean the data, and code the events, but the sponsor must maintain documented oversight — reviewing deliverables, approving key documents, and confirming the work meets the required standard. This is why a clear division of responsibilities, often captured in a responsibility matrix, is agreed at the start of every outsourced engagement.
How the roles work together across the lifecycle
The roles are not a static org chart; they activate in sequence. During set-up, the data manager and programmer build the database and the data manager writes the plan, with statistics and medical input. During conduct, coordinators clean, coders code, reconciliation runs, and the medical monitor reviews. At close-out, the data manager confirms the clean file and hands the locked database to statistics. Quality oversight runs throughout, and the sponsor maintains oversight across all of it. For the career path into and through these roles, see our clinical data management career guide.
Frequently asked questions
What are the main roles in a clinical data management team?
The core roles are the clinical data manager, who owns the deliverables and the data management plan; data coordinators or associates, who handle day-to-day data review and query management; the database programmer, who builds the eCRF and edit checks; and the medical coder, who standardises terms using dictionaries such as MedDRA and WHODrug. On smaller teams, one person may cover several of these roles.
What does a clinical data manager do?
The clinical data manager owns the data management deliverables for a trial. They author and maintain the data management plan, oversee the data cleaning strategy, coordinate the other roles, and are accountable for delivering a clean, locked database on time. They are the central point of contact for all data management matters and answer ultimately for data quality and timelines.
What is the difference between a data manager and a data coordinator?
The data manager owns the strategy and is accountable for the deliverables, while the data coordinator (or data management associate) carries out the day-to-day cleaning work — reviewing listings, raising and tracking queries, and performing manual checks. Coordinator is typically the entry-level role, with responsibility growing toward the data manager position over time.
Who is responsible for data management — the sponsor or the CRO?
A CRO may perform the data management work, but under ICH E6 Good Clinical Practice the sponsor remains ultimately accountable for data quality and integrity and must maintain documented oversight of any delegated activity. Outsourcing changes who does the work, not who is responsible for it, which is why a clear responsibility matrix is agreed at the start.
Which roles interface with clinical data management?
Several functions work closely with the core team: the medical monitor provides clinical review, the biostatistician and statistical programmer define the data structure and receive the locked dataset, and quality assurance provides independent oversight. Site staff enter data and answer queries, monitors verify it against source, and the safety team maintains the database used for reconciliation.
Learn the roles in context with TriTiCon
Understanding how the roles fit together is part of understanding the data management process as a whole. TriTiCon's foundational training, Introduction to Clinical Data Management, sets out the key players and concepts, and the wider TriTiCon course platform follows the lifecycle stage by stage so you can see where each role contributes.
