Regulatory authority and IRB/IEC approvals

The approval that does not exist

The approval letter arrives by email on a Thursday afternoon. The IRB has reviewed the protocol, the informed consent form, and the recruitment advertisement, and has granted a favorable opinion. The coordinator reads it, feels the familiar relief that accompanies a milestone achieved, and moves on to the next task.

Three weeks later, the monitor arrives for the site initiation visit. The first request: "May I see the IRB approval?" The coordinator opens the binder to the regulatory approvals section. The tab is there. Behind it: nothing. The approval letter is still sitting in an email inbox, unprinted, unfiled, unverified. And in the regulatory world, an approval that exists only in email does not exist at all -- not for the monitor, not for an auditor, and certainly not for an inspector from the FDA or a competent authority in the EU.

This is not a story about negligence. The coordinator knew the approval was obtained. What the coordinator had not yet internalized is a principle that governs everything in this module: the event is not complete until the record is in the binder. An IRB approval that has not been filed as an essential record is, for regulatory purposes, an IRB approval that cannot be verified. And a trial that cannot demonstrate documented approval before the first participant was enrolled has a problem that no amount of after-the-fact filing can fully repair.

This lesson teaches you how to handle regulatory approval documents -- the specific records, the verification checks, the timing requirements, and the organizational logic that makes the approval section of your binder inspection-ready from the day the trial begins.

The approval that does not exist

The approval that does not exist

What you will learn

Regulatory authority and IRB/IEC approvals

The approval that does not exist

What you will learn