When deviations happen: documentation, reporting, and corrective thinking
Learn to document protocol deviations with the standard elements, conduct root cause analysis that distinguishes proximate from systemic causes, develop corrective and preventive actions that address root causes, and report deviations to the IRB, sponsor, and site leadership.
A deviation happened. Now what?
The previous lesson was about prevention--the checklists, the human factors awareness, the hotspot vigilance that stops deviations before they start. That lesson was optimistic by design. This one is not.
This lesson begins where prevention failed. A protocol deviation has occurred. It has been identified--perhaps by the coordinator during a routine review, perhaps by the monitor during a site visit, perhaps by a participant who mentions something that does not match the protocol timeline. However it surfaced, the deviation is real, and it cannot be undone.
What happens next is, in my view, the truest measure of a coordinator's professionalism. Anyone can follow a protocol when everything goes according to plan. The real test comes when something goes wrong, and you must document it honestly, analyze it rigorously, correct it systematically, and report it transparently. I have seen coordinators at every career stage handle deviations brilliantly--with candor, thoroughness, and genuine corrective thinking. And I have seen others handle them badly--with defensiveness, vague documentation, and superficial fixes that all but guarantee recurrence. The difference is not talent or experience. It is training.
That is what this lesson provides. Not a lecture on the importance of compliance--you already understand that from the previous three lessons in this module. Instead, a practical framework for responding to deviations with the rigor that regulatory authorities expect, that sponsors require, and that participants deserve.
What you will learn
By the end of this lesson, you will be able to: