But something is not right. The protocol file is labeled "v4.0" in the portal, yet the file itself--when the coordinator opens the PDF and checks the cover page--says "Version 3.0, dated 22 August 2025." The portal label and the document do not match. And the Investigator's Brochure? Edition 7, dated 15 January 2026. But the IRB approval letter, issued three weeks ago, lists "Investigator's Brochure Edition 6" as the reviewed document. So either the IRB approved an outdated edition, or the sponsor uploaded a newer edition after the IRB submission and the coordinator now has a version that has not been reviewed by the IRB.

The site initiation visit is in nine days. These discrepancies must be resolved before the monitor walks through the door.

I have seen this scenario--or something uncomfortably close to it--more times than I care to count. Sponsor portals are imperfect. Document labels are applied by human beings who occasionally mislabel. Version numbers on portal download pages do not always match version numbers on document cover pages. And sponsors sometimes upload updated editions without proactively notifying every site. The coordinator who downloads everything, files it without checking, and assumes the versions are correct will discover the problem at the worst possible moment: during the site initiation visit, during a monitoring visit, or--worst of all--after a participant has been enrolled using an unapproved consent form that references a superseded protocol.

This lesson teaches the discipline of receiving sponsor-provided documents properly. Not just downloading them. Receiving them: verifying versions, confirming consistency across all regulatory documents, reviewing the Investigator's Brochure for content that directly affects your work, and tracking what is still missing so that nothing arrives as a surprise during the SIV.

But something is not right. The protocol file is labeled "v4.0" in the portal, yet the file itself--when the coordinator opens the PDF and checks the cover page--says "Version 3.0, dated 22 August 2025." The portal label and the document do not match. And the Investigator's Brochure? Edition 7, dated 15 January 2026. But the IRB approval letter, issued three weeks ago, lists "Investigator's Brochure Edition 6" as the reviewed document. So either the IRB approved an outdated edition, or the sponsor uploaded a newer edition after the IRB submission and the coordinator now has a version that has not been reviewed by the IRB.

The site initiation visit is in nine days. These discrepancies must be resolved before the monitor walks through the door.

I have seen this scenario--or something uncomfortably close to it--more times than I care to count. Sponsor portals are imperfect. Document labels are applied by human beings who occasionally mislabel. Version numbers on portal download pages do not always match version numbers on document cover pages. And sponsors sometimes upload updated editions without proactively notifying every site. The coordinator who downloads everything, files it without checking, and assumes the versions are correct will discover the problem at the worst possible moment: during the site initiation visit, during a monitoring visit, or--worst of all--after a participant has been enrolled using an unapproved consent form that references a superseded protocol.

This lesson teaches the discipline of receiving sponsor-provided documents properly. Not just downloading them. Receiving them: verifying versions, confirming consistency across all regulatory documents, reviewing the Investigator's Brochure for content that directly affects your work, and tracking what is still missing so that nothing arrives as a surprise during the SIV.