Chasing Documents Without Losing the Site

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

Most of the documents you need come from people who do not report to you, are busier than you, and did not choose to work with you. How you chase determines whether the file closes on time and whether the site takes your next request seriously.

This is a genuine competency. Sites remember which sponsors were easy to work with, and that shows up in enrollment.

Ask once, precisely

A request that names exactly what is needed, in what format, by when, and why, gets answered. A request that says "please send outstanding documents" does not, because the recipient has to do your work before they can do theirs.

Precise means: the document, the version if relevant, whose signature, wet or electronic, and the date you need it by with the reason. "We need Dr Okafor's signed CV, dated within the last two years, before we can add her to the delegation log and she cannot consent participants until we do" is a request somebody can action in five minutes.

Batch, and keep one list

Sites receive requests from the monitor, the project manager, the safety group and you. If those arrive separately the site experiences the study as chaotic and prioritizes accordingly.

Keep a single outstanding-items list per site, share it, and update it rather than sending new messages. The list is also your evidence of what was requested and when, which matters if the gap is never closed.

Escalate on a defined trigger, not on frustration

Decide the trigger before you need it. Two chases without a response, or any item that blocks screening, goes to the study manager. That is not a complaint about the site; it is information the study needs.

Escalating on a schedule protects the relationship, because the site experiences it as process rather than as a judgment about them.

Know which items actually block

A missing laboratory reference range blocks data review. A missing CV blocks a delegation. A missing translated consent form blocks consenting a participant who speaks that language.

Other items are genuinely important and do not block anything this week. Treating everything as urgent teaches people that nothing from you is.

When the site simply will not respond

Document the attempts, escalate, and say plainly what the consequence is. The failure mode to avoid is quiet absorption: continuing to chase for months while the study proceeds as though the document exists. If a site cannot produce an essential document, that is a fact about the study that its leadership needs, not a personal problem for you to solve.

A worked request

Weak: "Hi, following up on outstanding start-up documents. Please send when you can."

Strong: "Two items are blocking activation at your site. First, Dr Okafor's signed and dated CV; she cannot be added to the delegation log without it and cannot consent participants until she is. Second, the laboratory's current accreditation certificate, which expired on 31 May per the copy we hold. We need both by Thursday 12th to keep the 19th activation date. Everything else on the list is with us."

The second version does four things the first does not. It names the documents precisely. It says what each blocks, so the recipient can prioritize correctly. It gives a date with a reason rather than an urgency adjective. And it says what is not their problem, which is disproportionately reassuring to a site that feels buried.

The outstanding-items list

One per site, shared, with five columns: item, who holds it, what it blocks, requested on, expected by.

Update it rather than sending new messages. A site that receives one maintained list instead of eleven emails will answer faster, and you gain an accurate record of what was asked and when, which you will need if an item is never produced.

Review it before every monitoring visit and every sponsor call. An item that has been outstanding for six weeks and has never been escalated is a decision you made by not making it.

Key takeaways