At the first site, the coordinator receives the monitor's pre-visit agenda on a Tuesday and responds within the hour. The regulatory binder is current through last week. Data entry is complete through the most recent participant visits, with only two open queries--both less than 48 hours old. The delegation log reflects the sub-investigator who joined the team three weeks ago, with training documentation already filed. The coordinator has been doing this work all along, in small increments, as a routine part of the weekly and monthly workflow. When the monitor arrives, the visit takes one day. There is one minor finding: a single laboratory report that was filed in the wrong section of a participant chart.

At the second site, the coordinator receives the same pre-visit agenda and feels a familiar wave of dread. There are 14 open queries, some dating back six weeks. The delegation log has not been updated since the sub-investigator started. Three sets of laboratory reports are sitting in a stack on the corner of the desk, unfiled. The regulatory binder has not been reviewed since the last monitoring visit, and the coordinator is not entirely sure whether the most recent IRB approval letter was filed or is still in an email attachment. The coordinator will spend the next several evenings catching up. When the monitor arrives, the visit takes two days. There are nine findings, including two that the monitor categorizes as significant: the outdated delegation log and the backlog of unresolved queries.

Here is what I want you to notice: the second coordinator is not less competent. The second coordinator is not less dedicated. The difference is not talent or commitment--it is the presence or absence of a system. The first coordinator has built monitoring readiness into the rhythm of the week and the month. The second coordinator treats readiness as an event, something that happens before a visit. And that distinction, seemingly small, produces compounding consequences over the life of a trial.

This lesson is about building the system.

At the first site, the coordinator receives the monitor's pre-visit agenda on a Tuesday and responds within the hour. The regulatory binder is current through last week. Data entry is complete through the most recent participant visits, with only two open queries--both less than 48 hours old. The delegation log reflects the sub-investigator who joined the team three weeks ago, with training documentation already filed. The coordinator has been doing this work all along, in small increments, as a routine part of the weekly and monthly workflow. When the monitor arrives, the visit takes one day. There is one minor finding: a single laboratory report that was filed in the wrong section of a participant chart.

At the second site, the coordinator receives the same pre-visit agenda and feels a familiar wave of dread. There are 14 open queries, some dating back six weeks. The delegation log has not been updated since the sub-investigator started. Three sets of laboratory reports are sitting in a stack on the corner of the desk, unfiled. The regulatory binder has not been reviewed since the last monitoring visit, and the coordinator is not entirely sure whether the most recent IRB approval letter was filed or is still in an email attachment. The coordinator will spend the next several evenings catching up. When the monitor arrives, the visit takes two days. There are nine findings, including two that the monitor categorizes as significant: the outdated delegation log and the backlog of unresolved queries.

Here is what I want you to notice: the second coordinator is not less competent. The second coordinator is not less dedicated. The difference is not talent or commitment--it is the presence or absence of a system. The first coordinator has built monitoring readiness into the rhythm of the week and the month. The second coordinator treats readiness as an event, something that happens before a visit. And that distinction, seemingly small, produces compounding consequences over the life of a trial.

This lesson is about building the system.