Table of Contents
Mar 23, 2026 | Pavel Burmenko

A research survey found that around 12 hours of each data manager’s week, per study, is consumed by data review, cleaning, and reconciliation. These tasks – deemed as the most inefficient in the data management workflow by respondents – often rely on point solutions, spreadsheets, and manual processes. In a culture still driven by exhaustive data review, staff wellbeing and data quality are both at risk.

Regulatory shifts driven by ICH E6(R3) guidelines create pressure to adopt risk-based data management (RBDM) practices. But confusion around how to implement these practices within the risk-based quality management (RBQM) framework, and the lack of an achievable starting point, has hindered adoption of RBDM to date. For instance, only 57% of data managers think they will be incorporating more risk-based approaches in their roles over the next two years, compared with 83% of clinical research associates (CRAs) with risk-based monitoring.

Distinguishing RBDM from RBQM

RBQM is the overarching discipline that governs risk-based approaches for the trial, from concept to close-out. According to ICH E6(R3), it is defined by two fundamental principles that span the planning and execution phases: Quality-by-Design (QbD) and proportionality. These principles set the foundation for risk-based approaches in all aspects of trial design and conduct, with RBDM forming the clinical data-specific contribution to the overarching RBQM strategy [Table 1].

The guidance around QbD stipulates that clinical data management must shift its involvement upstream to protocol development, proactively defining Critical-to-Quality (CtQ) factors, identifying data risks, and collaborating with cross-functional teams to ‘de-risk’ the protocol. For study conduct, the principle of proportionality mandates that effort spent on data review must be proportionate to the risk and criticality of the collected data. This means reducing resource-heavy scrutiny of non-critical data, while maximizing efforts on primary and key secondary endpoints.

Table 1: Overview of RBQM and RBDM in their application to clinical trials

Processes that a connected clinical data workbench should automate:

  • Representation of critical data across all data displays and dashboards
  • Query creation in EDC when a discrepancy is identified in the workbench
  • Data issue notification to third party data providers
  • Protocol deviation creation in CTMS when identified based on clinical data in the workbench
  • Exploratory medical review including participant insights and clinical timeline
  • Key Risk Indicator action signals for centralized monitoring processes in CTMS
  • Quality Tolerance Limits for primary efficacy and safety endpoints
  • Safety case management review and reconciliation across all available clinical data
  • Payment triggers for on site assessments
  • Audit trail anomaly detection

Often, RBDM implementation efforts get entangled in broader RBQM initiatives before they get off the ground, forcing data teams to wait for the wider program to start. To break this dependency and gain meaningful traction, clinical data teams should focus on RBDM as an independent but related component of the broader RBQM framework. This decoupling of RBDM from RBQM will drive core data management efficiency, and help steer away from the current purgatory of risk-based talk but no action.

From point solutions to a centralized hub

Adopting RBDM requires a technological and operational shift. From a technology standpoint, the shift is a response to electronic data capture (EDC) becoming just one of many data sources, rather than the primary tool for data management. Legacy EDC-centric architecture lacks the real-time integration and automation required for risk-based workflows. The new central hub of clinical data is the workbench.

A clinical data workbench ingests and manages data from all sources, including EDC, labs, eCOA, and eSource. It automates data flows and manual processes across the clinical ecosystem. Data managers and other experts only need to review new or changed data with automated documentation and real-time reporting.

The operational shift involves three pillars of actionable RBDM, and requires the right workbench-centric architecture in place [Table 2]:

  1. Classification: The system must recognize the data defined as critical by data managers. Data managers define the data priorities so the system has an awareness of the meaning and the purpose of the data, and brings it together so that actions can be prioritized based on the data that matters most. By classifying critical data, endpoints, and clinical concepts, data managers can shift focus away from reviewing all data towards risk-based, targeted review.
  2. Automation: Today we can automate half of manual data management queries that compare collected data across sources or against expected values. But when the system understands the meaning and purpose of the data, cleaning and reconciliation can be automated at scale with minimal human intervention. This frees data managers to focus on the more strategic work of RBDM. Scaling in this way also requires a connected system, so we can automate data flows and actions in downstream systems. A connected ecosystem paves the way for the next wave of automation: AI-enabled aggregation, standardization, cleaning, and transformation.
  3. Orchestration: Data managers will focus on risk-based data review as a central pillar in clinical data activity. They will ensure data is with the right stakeholder at the right time, assign and prioritize review tasks, and monitor progress.

    This orchestration requires a system that provides a central point of access across functions and allows cross-functional collaboration on the same data in the same place. For example, a medical reviewer notices an unexpected lab result for a patient with no reported adverse events. The medical reviewer should be able to make an observation directly on the data and assign it for a data manager to action by querying the site as to whether the patient experienced any adverse events (AEs).

    As agentic AI capabilities gain acceptance, trust, and scale, the data manager’s orchestration responsibilities will expand beyond managing cross functional data review by today’s key stakeholders to multidisciplinary human and agentic data surveillance.

Table 2: Features of a clinical data workbench powering the three pillars of RBDM

Making RBDM a reality

Regardless of the organization’s RBQM maturity, clinical data management should prioritize RBDM and gain traction for the initiative, aligning with future RBQM programs further down the line.

Enabled by a clinical data workbench that centralizes data, understands its meaning, and automates rote, manual tasks, data managers can spend more time reviewing critical data. As clinical data stewards, they will be uniquely positioned to optimize strategies for the collection, quality assurance, and delivery of data, moving from reactive data processing to proactive risk-based strategic planning and execution.

As a data manager, you might begin soliciting details of the critical data points from clinical operations and biostatistics today, to inform your risk-based data review strategy.

“It’s important to have your workforce upskilled as you move from traditional data management to more of a data analytics role. Most importantly, there needs to be a mindset shift as you go from cleaning all data points to the same degree, to accepting that deprioritized data points won’t have the same level of cleanliness.” Senior Director Data Strategy and Management, Top 20 Biopharma

Connection with other core clinical trial systems like CTMS, RTSM, and Safety is important for a workbench to expand automation and eliminate manual data reconciliation. This will ultimately allow data managers to maximize the value potential of their time – a more measurable dimension than efficiency gains alone.

Register for Veeva R&D and Quality Summit in Copenhagen to hear from experts on RBDM.

Powerful Community, Fresh Ideas

Copenhagen | 28-29 May, 2026

Learn more