The Documents That Define Your Trial

Part of Clinical Project Management (PM) Training: What a Project Manager Owns.

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

Four documents, and what each one settles

The protocol. What the trial does and to whom. Every timeline assumption ultimately traces to it: visit schedule, number of participants, duration of follow-up.

The clinical trial agreement. What each site is obliged to do and what it is paid. When a site stops enrolling, this is where you find out whether you have any leverage.

The transfer of responsibilities. Who performs which activity, sponsor or CRO.

The monitoring plan. How, how often, and against what triggers a site is visited. It is the document that decides whether a problem is found in month two or month nine.

Version is not a formality

A timeline built on protocol version 2.0 and a site running version 3.0 is not a communication problem. It is two different trials being conducted at once.

Every amendment changes something you plan against: the visit schedule, the eligibility criteria, the number of sites needed to hit a recruitment target. Amendments are a project-management event, not only a regulatory one.

Where the documents live

They live in the trial master file, and the TMF is not an archive you fill in at the end. It is meant to be contemporaneous and complete enough that an inspector arriving unannounced can reconstruct how the trial was conducted.

A project manager who treats the TMF as a filing exercise for close-out will spend close-out reconstructing decisions from memory and email.

The question to ask on day one

For each of these four documents: which version is in force, who has it, and does the version the sites are working to match the version in the file?

If the answer takes more than a minute to establish, that is your first finding and it is about your own trial.