There is a scenario that everyone working in clinical research knows well. The site is under pressure, priorities keep shifting, and the electronic Case Report Form — which should reflect the real-time status of the study — stops being updated. The data exists: it is in the source documents, often correctly recorded. But it does not enter the system. Queries accumulate. Follow-up windows begin to close. And the real risk, at that point, is not the delay itself: it is the undetected delay.
When the data exists but does not reach the system
A clinical investigation is a tightly regulated ecosystem. Every visit, every follow-up, every adverse event has a protocol-defined time window — and the eCRF is its official record. Every empty field, every unresolved query, every unregistered visit is not merely an administrative inconsistency: it is a potential regulatory vulnerability that can compromise the validity of the entire dataset.
The causes are often recurring:
- sudden turnover of site staff, with consequent loss of study-specific knowledge;
- extraordinary workload shifts that displace priorities;
- errors in managing the protocol’s follow-up schedule;
- technical issues with the Electronic Data Capture (EDC) system;
- ambiguity in roles and responsibilities between the clinical team and the research team.
Whatever the origin, the mechanism is identical: data does not enter the system, and every passing day narrows the space available for recovery. The critical node, however, is not the delay in itself — it is the undetected delay.
The regulatory framework: accountability and obligations
Before addressing solutions, it is essential to clarify the accountability structure — because this is where many sites generate confusion, and confusion can have significant regulatory consequences.
The principal sources governing timely and traceable data management in clinical studies are three.
- ICH E6(R3) establishes Good Clinical Practice (GCP) standards and places explicit obligations on sites and sponsors regarding data timeliness and integrity.
- EU MDR (EU 2017/745), for medical device investigations, integrates with ISO 14155:2020 and defines data quality requirements across the lifecycle of a clinical investigation.
- ISO 14155:2020 itself specifies the responsibilities of Clinical Research Organizations (CROs) in monitoring data integrity continuously — not only at predefined intervals.
In this framework, a delay in eCRF completion is not an exclusively operational problem: it is a regulatory risk that can compromise the validity of the dataset. Data integrity is a shared responsibility and it requires a structured approach at every stage.
A real case: recovery at a site under operational stress
In a multicentre clinical investigation, the CRO holds the broadest perspective on overall conduct and carries the responsibility of translating that perspective into timely action. Remote eCRF monitoring is not passive reading of a database: it is a system of continuous interpretation of the actual study state, carried out through the role of the monitor.
The monitor is not simply a function that checks and flags non-conformities. It is an activator of processes: identifying signals through longitudinal eCRF reading, evaluating them within the regulatory context, and initiating a chain of preventive actions before critical escalation occurs.
During one such investigation, the remote monitoring team began detecting a series of signals at one of the participating sites. Taken individually, each appeared marginal. Analysed together, they outlined a concerning picture from both a clinical and regulatory standpoint:
- Queries open for more than 30 days without resolution
- Follow-up visits not recorded and outside the protocol-defined windows
- Incomplete eCRF sections across multiple enrolled patients
The site had not reported any difficulties — not out of negligence, but because it was going through a critical operational period that had generated discontinuity in CRF management. All data were present, legible, and verifiable in the patients’ source documents and the site’s own information system. The problem was that they had not been transferred to the study platform, and the available time was running out.
The CRO initiated a systematic escalation through emails, calls, and structured communications, until direct contact was established with the site. Once the operational situation was fully understood, a shared recovery plan was defined — with clearly assigned roles and responsibilities, time-bound actions, and a process for documenting each deviation in compliance with applicable regulations.
Operational Compliance: How the intervention was managed
THE SITE, via PI-delegated staff, performed:
- Systematic review of source documents and source data against eCRF entries
- Chronological reconstruction of all visits within the affected timeframe
- Verification of protocol-defined time windows for each visit and follow-up
- Entry of missing data into the eCRF, with full traceability of each correction
THE CRO ensured:
- Prioritisation of recovery actions, with focus on the highest-risk time windows and primary endpoint data
- Verification of correct and complete data recording in the eCRF after each entry session
- Structured, continuous communication with site staff throughout every phase of the recovery process
Outcome
Within a few weeks, a significant visit backlog was recovered. The number of open queries was substantially reduced and the site returned to full compliance with the study timeline — with dataset integrity preserved and no protocol deviations requiring escalation to the Ethics Committee or the Sponsor.
Why remote monitoring is a strategic competence
Remote eCRF monitoring is not an ancillary activity. It requires specific and compounding capabilities that go far beyond administrative oversight.
The first is longitudinal reading of site behaviour. The eCRF does not only return data: it returns the site’s behaviour over time. Those who interpret it correctly can distinguish the normal physiology of a study from an early signal of deterioration — and intervene while the margin for recovery is still meaningful.
The second is regulatory risk grading. Not all deviations carry the same weight. An unresolved query on a demographic field does not have the same impact as a missed follow-up window for the primary endpoint. The ability to distinguish genuine urgency from a negligible inconsistency is what separates effective monitoring from a purely formal exercise.
The third is proactive management of protocol time windows. Follow-up windows are often tight, and their observance has direct implications for the statistical validity of the data. Identifying at-risk visits in advance and activating the site through a structured escalation process requires continuous monitoring, regulatory judgement, and rapid decision-making.
The support provided in cases like the one described is regulatory before it is operational: knowing which data can be recovered and how, which deviations must be notified and how to document them, are all activities that are prerequisites for preserving dataset integrity.
Signals that must not be ignored
The real question that every Principal Investigator and Clinical Research Coordinator should ask is: “Are we structured to prevent this from happening?”
Recognising risk signals early allows intervention before delays become compliance problems. The following warrant immediate attention:
- EDC queries remaining open for more than 30 days without resolution
- Site staff managing multiple simultaneous studies with no dedicated resource allocation per study
- Protocol follow-up visits not managed through a structured reminder and escalation system
- No internal procedure to manage the sudden absence of the data entry responsible
- No internal KPIs defined for tracking eCRF completion timeliness
If one or more of these conditions is present, the risk is not future: it is already in progress.
Data integrity is not a destination, it is a process
Sites that maintain clean, timely eCRFs throughout a study do not do so because they have fewer problems. They do so because they have built the processes to detect problems early and act before they compound. Remote monitoring, when conducted with the rigour that clinical data demands, is precisely that process — not a control mechanism imposed from outside, but an early warning system built into the fabric of study conduct. The distinction between sites that recover gracefully and those that do not is rarely about the severity of the initial problem. It is almost always about when the problem was seen.
Working with We4CR
Remote eCRF monitoring, site operational support, and protocol deviation management in compliance with ICH E6(R3), EU MDR (EU 2017/745), and ISO 14155:2020 are core competencies of our team.
If your study is accumulating delays or you want to prevent eCRF-related compliance issues before they escalate, contact us — we will assess your situation and define a targeted intervention together.