24.2 Version History, Resolution Evidence and Noncompliance

Version History, Resolution Evidence and Noncompliance

Under ICH E6(R3), essential documents must be filed in a timely and contemporaneous manner. Delayed filing—a systemic pathology known in clinical operations as "filing debt"—represents a severe regulatory vulnerability.

The Doctrine of Inspection Readiness

"Inspection readiness" requires that the Trial Master File and Investigator Site File be maintained in a continuous state of completeness, currency, and accuracy, such that an auditor or regulatory inspector could inspect the files at any given moment and reconstruct the conduct of the trial without supplemental verbal explanations.

Critical Filing Pitfalls & Pathologies

1. Post-Dating and Back-Dating (Fraudulent Practice): Site personnel or monitors must NEVER back-date a signature, document, or log entry to make it appear timely. Back-dating constitutes intentional fraud. If a document is executed or filed late, it must be signed with the actual current calendar date, accompanied by a clear, contemporaneous note explaining the delay (e.g., "Late entry: Form completed on 18-Oct-2026 reflecting training conducted on 12-Oct-2026.").
2. Orphaned Documents: Documents filed without required parent context (e.g., an IRB approval letter filed without the corresponding protocol amendment version, or a CV filed without a medical license).
3. Superseded Document Governance: When new protocol versions or revised consent forms are approved, the previous versions must not be discarded or destroyed. The superseded version must remain filed in the binder, clearly stamped or marked as "SUPERSEDED" with the effective date, to preserve the historical audit trail.

Electronic repository controls

Electronic essential records need suitable access controls, traceable changes, version history and reliable retrieval throughout the retention period. Sponsor and site responsibilities should remain clear when a service provider hosts the repository. Confirm how site records will be retained when a sponsor portal closes; a bookmark to an expiring service is not an archive.

A certified copy permanently replacing an original should preserve the same information, including relevant context, content and structure. Verify migrations rather than assuming a visible PDF contains every attachment, metadata field or electronic signature. Control the change and confirm readability with the people responsible for future access.

Distinguishing reports, communications and resolution evidence

A monitoring report can record that a missing consent page was identified, while a follow-up letter assigns the site an action. Neither alone proves that the page was located or that the participant-rights issue was evaluated. Reconciliation should follow the issue through the site's response, relevant evidence and sponsor review. If the page cannot be recovered, retain an honest limitation and the evaluated action rather than creating a replacement signature page.

A completed action tracker can refer to evidence held elsewhere. Verify the reference works and the responsible parties can retrieve the record. An email attachment that exists only in a departed employee's personal mailbox is a retention risk. An electronic repository can be appropriate if the content, metadata, access and ownership remain controlled.

Also distinguish a confirmed correction from a promise. A site response saying training will be completed next week is not evidence that staff were trained before already performed activities. Maintain the dates and prospective plan without rewriting the earlier gap. A useful record permits reconstruction of both the problem and the response, including remaining uncertainty and its impact.

The same principle applies to a sponsor-only monitoring report. The site need not hold every internal report, but it needs appropriate communication of findings affecting its responsibilities and records of its own response. File ownership and participant protection should both be clear rather than solved by indiscriminate copying.

Managing Serious Non-Compliance, Audits/Inspections & Site Close-Out (COV)

The final stages of a clinical trial test the robustness of a site's operational integrity. Whether managing critical protocol non-compliance, hosting federal regulatory inspectors, or executing the detailed multi-domain checklist of a Site Close-Out Visit (COV), the Clinical Research Associate serves as the critical operational anchor ensuring compliance, audit defensibility, and long-term inspection readiness.

Managing Serious and Persistent Site Non-Compliance (ICH E6(R3))

Non-compliance occurs whenever an investigator, site staff member, sponsor representative, or third-party vendor fails to adhere to the approved clinical protocol, standard operating procedures (SOPs), Good Clinical Practice principles, or applicable statutory regulations.

Official sources

Checked October 18, 2026: ICH E6(R3), Principles and Annex 1.