Preparing a Site, and the Fourteen-Day Case

Part of Clinical Trial Assistant (CTA) Training: Inspection Readiness.

About 4 minutes. Free, in your language, no account needed.

Why this matters

When notice arrives the study has a fixed amount of time and an unbounded list of things it could do. Choosing well is the whole task.

The first day

Establish scope. Which inspectorate, which trial or trials, which sites, which dates, and what have they asked for in advance. Everything else depends on this and it is often ambiguous in the first communication. Ask.

Name an owner and a single point of contact. Inspections go wrong when an inspector receives three different answers from three people.

Start a request log immediately, on day one, before anything is requested. Every document asked for, when, who provided it, what was provided, and when. That log is the study's own record of what the inspector saw, and it is worth more than anyone expects afterwards.

Triage, ruthlessly

With fourteen days you cannot fix everything, so fix what an inspector will look at first and what carries consequence.

High value. Consent documentation for the participants likely to be sampled. The delegation log against who actually appears in the data. Investigational product accountability and reconciliation. Ethics approvals matched to the versions in use at the time. Deviation log and its closure. Safety distribution records.

Lower value under time pressure. Formatting, folder structure, and administrative items with no dependency.

A perfectly ordered file with an unexplained accountability discrepancy will go badly. A slightly untidy file that answers every substantive question will not.

Preparing people

Site staff are usually more anxious than the file warrants, and anxiety produces the two failure modes: speculating, and over-answering.

The guidance is short. Answer the question asked. If you do not know, say you do not know and that you will find out. Do not speculate about why something was done if you were not there. Do not volunteer documents that were not requested. Do not guess at another person's reasoning.

Rehearse the timeline reconstruction with them, because being asked to walk a participant's journey while an inspector watches is the moment people freeze.

During

Provide exactly what was asked for. Log it. If a document does not exist, say so plainly rather than producing something adjacent.

Note every observation as it is made rather than relying on memory at the end of the day. A daily debrief while everyone is still present is worth more than a reconstruction afterwards.

A worked fourteen days

Notice arrives on a Monday for an inspection starting in a fortnight at two sites.

Monday. Establish scope: which inspectorate, which trial, which sites, which dates, what has been requested in advance. Name one point of contact. Open the request log before anything is requested.

Tuesday to Thursday. Run the timeline drill on four participants per site. Everything that cannot be answered from the file goes on a single list, ranked by consequence rather than by effort.

Friday. Triage. Consent documentation, delegation against who actually appears in the data, product accountability and reconciliation, approvals matched to versions in use, the deviation log and its closures, safety distribution records. Anything outside that list waits.

Week two. Close what can be closed honestly. Obtain documents that exist. For anything that does not exist, write the explanation now, calmly, with dates and a named decision-maker, rather than producing it under pressure on the day.

The Friday before. Brief the site. Answer the question asked; say you do not know when you do not; do not speculate; do not volunteer documents.

The temptation, named

Somewhere in week two, someone will suggest creating a document to fill a gap, and it will be framed reasonably: the training definitely happened, the meeting definitely occurred, we just need something in the file.

The answer is no, and the reason is worth saying out loud in the room. A gap that is acknowledged and explained is survivable and common. A document created in week two describing events from last year will be identified by its metadata, and it converts a documentation finding into a question about whether anything in the file can be trusted.

There is no version of that trade that is worth it.

Key takeaways