The Outdated Site File
Part of Clinical Trial Assistant (CTA) Training: Essential Documents and Start-Up.
About 4 minutes. Free, in your language, no account needed.
Why this matters
A site file that was correct at start-up decays. Staff change, certificates expire, protocols are amended, and consent forms are superseded. Nothing announces this. The file looks the same.
Staleness is the characteristic failure of the conduct phase, and it is more common than absence.
What goes stale, and how fast
Laboratory certification and reference ranges. Accreditations have expiry dates and ranges are periodically revised. An expired certificate means the data produced under it is harder to defend.
CVs and training records. People are promoted, change qualifications and move institutions. A CV that predates a change no longer evidences the qualification claimed.
The delegation log. Somebody leaves and the log still lists them. Somebody joins and starts working before the entry exists. Both are findings, and the second is worse.
Consent forms. A new version is approved and the old one stays in the folder. If the site consents anyone on the old version after the new one took effect, that is a deviation with a participant consequence.
The investigator's brochure. A new edition is issued and the site never acknowledges receipt, so nothing proves the investigator had current safety information.
Contact and insurance details. Unglamorous, and the first thing an inspector notices is wrong.
Detection is a scheduled activity
Staleness is found by looking, on a schedule, for things with dates. Build a review that asks: what in this file has an expiry, and when is it. Run it quarterly, and always after an amendment, a staff change or a monitoring visit.
An amendment is the highest-risk moment, because it can supersede several documents at once and the downstream effects are easy to miss. A protocol amendment may require a new consent form, new ethics approval, revised delegation, new training, and updated laboratory ranges.
Correcting without making it worse
Obtain the current document. File it, mark the previous version superseded, and leave the history in place. Then ask the question that matters: was anything done under the stale version that should not have been.
That second question is the one people skip. An expired certificate is administrative. Participants consented on a superseded form are not, and the answer determines whether you are filing a document or reporting a deviation.
A worked review
Take a site file that has been open eighteen months and run the expiry sweep.
Laboratory accreditation. Expired four months ago, renewed certificate never sent. Samples have been analyzed throughout. Two actions: obtain the certificate, and confirm the accreditation was continuous rather than lapsed, because those are different facts with different consequences.
Investigator CV. Signed at start-up, and since then the investigator has moved institutions. The CV now describes a post they no longer hold, which means the file does not evidence the qualification of the person actually running the trial.
Delegation log. Two coordinators listed who left last year, one current coordinator absent. The absent one has been entering data since August. That is a delegated task performed without delegation and needs escalating today.
Consent form. v4.0 approved in March, v3.0 still in the folder unmarked. Check consent dates against versions before anything else.
Investigator's brochure. Edition 7 issued in January, site holds edition 6, no acknowledgement of edition 7 on file. The investigator may not have current safety information, which is not administrative.
Five findings from one afternoon, and three of them have participant or data consequences.
Making the sweep routine
Build a single table per site listing every document that carries a date, with its expiry or review point. Review quarterly, and always after an amendment, a staff change or a monitoring visit.
The table takes an hour to build once per site and turns an open-ended worry into a scheduled twenty minutes.
Key takeaways
- Site files decay silently. Staleness is more common than absence during conduct.
- Anything with an expiry needs a scheduled review; amendments and staff changes are the trigger points.
- Supersede and retain history; never remove the old version.
- Always ask whether anything was done under the stale version. That decides whether it is filing or a deviation.