ICH E6(R3) came into effect in the EU on 23 July 2025, and its sponsor section is explicit about outsourced work. The sponsor may transfer any or all trial-related activities to a service provider, but keeps ultimate responsibility for them (ICH E6(R3), section 3.6).
Three clauses in that section shape what a CRO has to provide:
In the US, 21 CFR 312.52 sets the same principle in regulation. A CRO that assumes sponsor obligations in writing becomes subject to the same regulatory action as the sponsor for failing to meet them.
Taken together, these rules mean sponsors will ask CROs for evidence, not assurances. Status reports assembled by hand from several trackers are hard for a sponsor to verify; metrics drawn from a system of record are not. A CRO that can produce those quickly is easier to choose and easier to keep.
Most oversight questions a sponsor asks are simple. Which sites are active? Which visit reports are overdue? Which action items are still open? What has each site been paid? The difficulty is that the answers often live in different places: a CTMS, a site payment spreadsheet, a TMF and email.
|
Oversight question |
Spreadsheets and disconnected tools |
Connected CTMS |
|---|---|---|
|
Site activation status |
Tracker updated weekly by a study manager |
Milestones update when the linked tasks are completed |
|
Monitoring visit compliance |
Visit dates in one sheet, report status in another |
Visit schedule, report due dates and sign-off in one record |
|
Open action items and issues |
Listed in visit reports, chased by email |
Tracked to closure with owner and due date |
|
Protocol deviations |
Logged per site, rolled up by hand |
Captured centrally and reported by site and category |
|
Site payments |
Finance sheet reconciled to visit data monthly |
Payments driven by completed visits and milestones |
|
Evidence in the TMF |
Reports downloaded and uploaded |
Signed reports filed to the TMF automatically |
|
Sponsor reporting |
Slide deck built for each governance meeting |
Dashboards and scheduled reports from live data |
Each manual step adds delay and a chance of mismatch. When a sponsor auditor compares the status deck with the TMF and the payment records, mismatches become findings.
Site activation involves feasibility, contracts, ethics approval, essential documents and training. When each milestone is linked to the tasks behind it, completing the tasks updates the milestone at site and study level. The sponsor sees activation status that reflects work done, not a date someone typed into a tracker.
E6(R3) expects monitoring to be risk-based and documented. The CTMS should hold the visit schedule, the report, its due date, review and sign-off in the same record. Visit-report timeliness then becomes a metric the CRO can share under section 3.6.8.
Findings from monitoring visits only count as oversight if they are closed. Each action item needs an owner, a due date and a status, carried from one visit report into the next. Sponsors and auditors often ask for the list of open items older than a set number of days.
Deviations logged in site spreadsheets are hard to trend. A central deviation log, categorised consistently across sites and studies, lets the CRO spot patterns and report them to the sponsor before they become a quality issue.
When CTMS and financial management share a platform, the CRO can confirm a site's agreement is executed before activation. Payments can then follow completed visits and milestones, so finance and operations report the same numbers.
Every monitoring report, approval and site document the CTMS produces is evidence that belongs in the TMF. Filing signed reports straight to their TMF artifacts closes the gap between what the CTMS says and what the TMF can prove.
Under 3.6.8, sponsors should have access to performance metrics. Dashboards and scheduled reports from live CTMS data give each sponsor a view of its own studies. That replaces a status deck rebuilt for every governance meeting.
For a CRO, study count rises with every new contract. A CTMS charged and configured per study gets more expensive and harder to maintain as the CRO grows. Ask how cost and setup effort change between your tenth and fiftieth study.
Mid-size full-service CROs run start-up, monitoring and close-out for several sponsors at once. Sponsor-specific dashboards (7) and per-study cost (8) decide whether the CTMS keeps up with growth.
Regional and specialist CROs often win work on speed of site activation in their markets. Task-driven milestones (1) and agreement checks before activation (5) give sponsors evidence of that speed.
Functional service providers supply monitors or study managers into a sponsor's process. Visit compliance (2) and action-item closure (3) are the metrics their sponsors watch most closely.
|
Role |
What they need from the CTMS |
Capabilities |
|---|---|---|
|
ClinOps directors and associate directors |
Portfolio view across sponsors for governance meetings |
1, 7, 8 |
|
ClinOps and clinical trial managers |
Activation status, visit compliance and open issues per study |
1, 2, 3 |
|
QA directors |
Deviation trends and evidence of closed actions |
3, 4, 6 |
|
CRAs |
Visit schedules, report deadlines and follow-up items in one place |
2, 3, 6 |
Platforms like Cloudbyz, among others, are built so that operational data, payments and TMF evidence come from the same records. How much reporting effort that removes depends on how your workflows and sponsor reports are configured.
|
Capability |
How Cloudbyz CTMS handles it |
|---|---|
|
Milestones (1) |
Tasks linked to milestones update site and study status automatically as they are completed |
|
Visit compliance (2) |
Monitoring visit management with audit trails and role-based access |
|
Action items (3) |
Issue and action tracking across visits |
|
Deviations (4) |
Central issue and deviation tracking with reports and dashboards |
|
Agreements and payments (5) |
With Cloudbyz CTFM on the same platform, the team can confirm a site agreement is executed before activation, and milestone-linked payments follow completed work |
|
TMF filing (6) |
With Cloudbyz eTMF, signed monitoring visit reports file to predefined TMF artifacts automatically |
|
Sponsor reporting (7) |
Configurable dashboards and reports, with sponsor collaboration and visibility |
|
Cost as you grow (8) |
Study setup and maintenance cost is tied to licence count rather than study count, so cost per study falls as more studies are onboarded |
The CRA Monitoring Copilot supports the monitors behind capabilities 2 and 3. It assembles a pre-visit briefing, drafts follow-up letters from signed reports, and chases open action items between visits. It never sends, signs or changes a record: every judgement stays with the CRA.
Book a demo to see milestone tracking, visit compliance and sponsor dashboards configured around a study model you already run.
Book a Cloudbyz CTMS demo or email info@cloudbyz.com.