Clinical Research CoordinatorCourse 5 of 8

Clinical Research Coordinator

Full course · Participant Management: Screening to Retention

Documentation, reporting, and root cause analysis — Participant Management: Screening to Retention

Documentation, reporting, and root cause analysis

Document deviations with required elements, assess impact on safety and data integrity, conduct root cause analysis using 5-Whys methodology, and submit reports through required channels.

25 min

The deviation happened — now what?

You have identified a deviation. You have classified it. Now begins the work that transforms a recognized problem into a documented record that serves the participant, the data, and the quality system. This is where many sites falter — not because coordinators are careless, but because deviation documentation is often treated as a bureaucratic task rather than a quality tool.

I want to be direct about this: a deviation that is identified but poorly documented is almost as problematic as one that is never identified at all. If the documentation does not capture what happened, when it happened, who was affected, why it happened, and what the impact was, then the deviation record cannot serve its purpose. The monitor cannot assess the site's response. The sponsor cannot determine whether the data are usable. The IRB cannot evaluate whether participants are adequately protected. And the site itself cannot learn from the event, because a vague record generates vague analysis.

This lesson teaches the discipline of deviation documentation — what to record, how to analyze the root cause, how to assess the impact, and how to route the report through the correct channels. It also teaches something that is, in my view, the most underappreciated skill in deviation management: the ability to move beyond "the coordinator made an error" to the systemic insight that actually prevents recurrence.

What you will learn5 objectives

By the end of this lesson, you will be able to:

Document a protocol deviation with all required elements: description, dates, affected participants, protocol section violated, and circumstances
Assess deviation impact on participant safety and data integrity with documentation supporting both assessments
Conduct root cause analysis using the 5-Whys and fishbone methodologies, moving from surface explanations to systemic causes
Transform individual-blame explanations into systemic insights that inform preventive action
Submit deviation reports through required channels — sponsor, IRB/IEC, and internal systems — within specified timelines

Progress saves itself — finish reading and this lesson completes

This is just the beginning

The deviation happened — now what?