Request a demo specialized to your need.
Subscribe to our Newsletter
Smit Shah
ICH E6(R3) asks sponsors to focus quality management on what matters most to participant safety and the reliability of results, and to make quality control proportionate to risk (ICH E6(R3), EMA Step 5). Many TMF teams still run a single QC process for every document: each one checked by a person, in the same way, before it is final.
That sounds thorough, but it has a cost that shows up in inspections. MHRA inspectors have repeatedly raised TMF findings with commercial sponsors, including documents not filed in a timely way (MHRA, Trial Master Files presentation). When every document waits for the same manual check, the QC queue becomes the reason documents are late, and the effort spent on low-risk correspondence is effort not spent on consent forms and safety reports.
|
Issue |
Uniform 100% QC |
Proportionate QC |
|---|---|---|
|
Effort |
Same for every document |
Highest for critical documents |
|
Queue |
Grows with volume |
Smaller, focused on what matters |
|
Timeliness |
Filing waits for QC |
Low-risk documents filed faster |
|
Error detection |
Spread thinly |
Concentrated where errors matter |
|
Evidence |
"Everything was checked" |
A documented, risk-based rationale |
A signed consent form template, an ethics approval or a safety report matter more to participant safety and inspection outcomes than routine correspondence. Treating them the same spreads attention evenly where it should be concentrated.
If every document must pass manual QC before it counts as filed, filing speed is limited by QC capacity. Large backlogs before milestones are a sign that QC, not collection, is the bottleneck.
Missing signatures, missing dates, wrong study or site, and incomplete metadata are the most common QC errors, and they can be checked automatically at upload. That leaves people to review content and judgement.
For lower-risk document types, checking a sample and tracking the error rate can give confidence with less effort. If the error rate for a type or site rises, QC for that type or site can be increased.
A proportionate approach needs to be written down: which document types get full review, which are sampled, what triggers escalation, and why. That rationale, in the TMF plan, is what an inspector will ask to see.
|
Tier |
Example documents |
QC approach |
|---|---|---|
|
Critical |
Consent forms, approvals, protocol and IB versions, safety reports, delegation logs |
Full review by a person |
|
Standard |
Monitoring reports, training records, site documents |
Automated checks plus targeted review |
|
Lower risk |
Routine correspondence, meeting notes |
Automated checks plus sampling |
Cloudbyz eTMF, built natively on Salesforce, is designed with configurable QC and approval workflows, metadata management, 21 CFR Part 11 electronic signatures and completeness dashboards. The Cloudbyz AI eTMF Agent is designed to classify incoming documents, extract metadata, validate it against the document content and raise QC issues for review. Auto-approval applies only within thresholds the team configures, and documents outside them go to a person.
Book a demo or visit cloudbyz.com.
Subscribe to our Newsletter