A GCP inspection rarely finds something nobody knew about. It usually finds something that was known, recorded somewhere, and never connected to the place where it mattered. Inspection readiness is mostly about making those connections before an inspector does.
What inspectors actually look at
The trial master file first, because it is the record of how the trial was run. Then the systems that produced the data, and the people who made the decisions. ICH E6(R3), the revised GCP guideline finalised in 2025, puts more weight on risk-based quality management and on the reliability of the systems behind the data than its predecessor did.
In practice, an inspector picks something specific and follows it through. A protocol deviation, a consent form, a safety case. The question is always the same: can you show what happened, who decided, and why?
The trial master file
Most TMF problems are not missing documents. They are documents filed late, in the wrong place, or without the context that explains them. A TMF that is complete on paper but was filled in during the last fortnight before an inspection tells its own story.
The fix is boring and effective: file as you go, review completeness regularly rather than at the end, and treat late filing as a signal worth investigating.
Computerised systems
Every system that captures or processes trial data is in scope: EDC, IRT, eCOA, the safety database, and anything that moves data between them. Each needs evidence that it was fit for purpose and stayed that way.
The common gap is the join between systems. Data that moves from one system to another can lose its audit trail, change format or arrive late. Inspectors increasingly ask about those transfers, because that is where data integrity breaks. Our data integrity page covers the controls.
Documents that disagree
A frequent finding is inconsistency between documents that should agree: the protocol, the statistical analysis plan, the CSR and the safety reports. Each was written by different people at different times, and small differences accumulate.
Checking consistency across the document set before an inspection is far cheaper than explaining the differences during one. Source traceability, where each statement points back to its origin, makes that check quick. Our CSR authoring tool is built around it.
People and decisions
Inspectors also talk to people. They will ask the clinical lead why a deviation was classified as minor, the data manager how a query was closed, and the safety physician why a case was assessed the way it was. The answers need to match what the records say.
The best preparation is not rehearsed answers. It is records that explain decisions at the time they were made, so that anyone involved can open the file and walk through what happened. A decision recorded with its reasoning is easy to defend. A decision reconstructed from memory two years later rarely is.
A simple readiness check
Pick a subject at random and follow them through. Consent, eligibility, every visit, every deviation, every safety event, every data correction. If any step takes more than a few minutes to evidence, that is your gap, and it is better found by you than by an inspector.
If you want an independent readiness review, our audit readiness team can help.
Where to go next
Explore GxP Copilot for AI-native validation, TraceDraft for source-traceable clinical documentation, or book a demo to see either on your own data.