Within 72 hours, the coordinator needs to submit to the IRB, track that submission, brief the principal investigator, and set up the filing sequence that will eventually include the amendment text, the IRB approval letter, an updated consent form, staff notification records, and an implementation acknowledgment. The filing system the coordinator has built -- or has not built -- determines whether this is a manageable, methodical process or a scramble that leaves documents unfiled for weeks and creates gaps that the monitor will discover at the next visit.

This lesson is about that filing system. Not the science of what the amendment changes, and not the operational process of how the site adapts its workflows -- those belong to other courses. This is about the documentation architecture that tracks an amendment from the moment it arrives through its IRB approval and site implementation, and that keeps the continuing review cycle running without lapse throughout the trial's life.

If Module 3 taught you to populate the regulatory binder before the trial begins, this lesson teaches you to maintain it as the trial moves. And I will tell you plainly: more filing errors occur during ongoing conduct than during startup, because the urgency that drives pre-enrollment preparation dissipates once participants are enrolled and the daily rhythm of the trial takes over. The binder becomes something the coordinator will "get to later." Later, in my experience, arrives at the monitoring visit -- and by then, the gaps are documented as findings.

Within 72 hours, the coordinator needs to submit to the IRB, track that submission, brief the principal investigator, and set up the filing sequence that will eventually include the amendment text, the IRB approval letter, an updated consent form, staff notification records, and an implementation acknowledgment. The filing system the coordinator has built -- or has not built -- determines whether this is a manageable, methodical process or a scramble that leaves documents unfiled for weeks and creates gaps that the monitor will discover at the next visit.

This lesson is about that filing system. Not the science of what the amendment changes, and not the operational process of how the site adapts its workflows -- those belong to other courses. This is about the documentation architecture that tracks an amendment from the moment it arrives through its IRB approval and site implementation, and that keeps the continuing review cycle running without lapse throughout the trial's life.

If Module 3 taught you to populate the regulatory binder before the trial begins, this lesson teaches you to maintain it as the trial moves. And I will tell you plainly: more filing errors occur during ongoing conduct than during startup, because the urgency that drives pre-enrollment preparation dissipates once participants are enrolled and the daily rhythm of the trial takes over. The binder becomes something the coordinator will "get to later." Later, in my experience, arrives at the monitoring visit -- and by then, the gaps are documented as findings.