Supporting the monitor: what to provide, when to be available, and what to expect

Free Lesson Preview

This is just the beginning

The full CRC track covers 8 courses from study start-up to close-out — the skills sponsors actually look for.

Already enrolled? Sign in

The monitor has arrived

The workspace is ready. The investigator's time is blocked. The team has been briefed. The operational logistics from the previous lesson are handled. Now the monitor opens the regulatory binder, pulls up the EDC system on the laptop, and begins working. And here is the question that separates a coordinator who merely hosts a monitoring visit from one who actively supports it: do you know what the monitor is actually doing at each stage of the day, and do you know what you should be doing in parallel?

I have spent a good part of my career watching this interaction from both sides -- training monitors and training the coordinators who support them. The pattern I observe most often at struggling sites is not hostility or incompetence. It is misalignment. The coordinator does not understand the monitor's workflow, so the coordinator cannot anticipate what the monitor needs next. The monitor asks for a document, the coordinator retrieves it, the monitor asks for another, the coordinator retrieves that one too -- and the entire visit becomes a reactive chain of requests and responses rather than a coordinated effort. At the best sites, the coordinator is not waiting for requests. The coordinator is staging the next set of documents before the monitor finishes the current set, because the coordinator understands the sequence.

That understanding is what this lesson provides. Not the logistics of workspace and scheduling -- you learned those in the previous lesson. This lesson is about what happens inside the visit itself: the monitor's workflow, the documents each stage requires, the questions the monitor will ask and which ones you can answer, and the investigator meeting that typically closes the day.