Let's do the math the way a CRC feels it. Pick one trial. Two hundred patients in the eligibility pool. Each chart takes twenty-five minutes of careful review — comorbidities, line of therapy, biomarker status, washout windows, prior radiation, ECOG. That's roughly eighty-three hours of chart review per site, per trial, before a single patient consents.
Now multiply by three concurrent trials. By ten sites running them. By the two or three amendments each protocol takes during the enrollment window. The math has a number at the bottom. It's not on any budget. It's in your week.
This post is for the site coordinators. The sponsor/CRA audience gets the amendment-cascade post — this one is about the workflow that's actually in front of you on Monday: which charts to pull first, which exclusions actually apply to the patient in front of you, how to log a screen without losing two hours to a CTMS that insists on field-by-field entry, and how to respond to the query that arrived Friday at 4:55pm.
"The sponsor budget line says 'site coordination.' The CRC calendar says I'm doing three amendments' re-screening on top of new patient intake for a fourth trial that opened last Tuesday."
Where the hours actually go
There are four concrete cost categories that eat CRC hours on a multi-trial oncology program. They aren't glamorous. Nobody's writing them down in the trial budget. They're in every coordinator's week.
What the math looks like on one trial
One oncology trial. Twenty-five sites. A 200-patient enrollment target. Two substantial amendments during the enrollment window. A CRC team that runs, on average, three concurrent trials at the site level.
Twelve weeks in, the chart-review hours, the eligibility-verification wait, the screening-log entry, and the query-response hours add up. Per site. Per coordinator. Per week.
Of those hours, roughly 40% are chart review. Roughly 25% are screening-log entry and EDC reconciliation. The remaining 35% splits across eligibility verification, query response, and the re-matching work that arrives with every amendment. None of it produces enrolled patients. All of it sits between you and the next cohort.
The shape of the problem: the workload scales with trials and amendments, but the CRC team size does not. Sites running three concurrent protocols carry three times the chart-review load — and three times the amendment impact. The hours get eaten; the patients waiting to be screened do not.
The shift that gives hours back
The reason coordinator hours are draining this fast isn't the workload per se — it's that the coordination between trials is manual. When two trials run on the same site with overlapping patient pools, the coordinator is the integration point. Every patient who could fit both trials gets reviewed twice. Every amendment on one trial means re-screening the patients already in the screening queue for the other. Every sponsor query is handled independently, even when three queries are about the same patient.
A multi-site coordinator changes the shape of the work. Instead of three separate screening queues — one per trial — there's one queue that knows about all three. Patient overlap is detected once, not three times. Amendment impact is computed once and propagated to all eligible patients automatically. Queries cluster around the patient they belong to. The chart review is the same twenty-five minutes, but it happens once per patient per protocol version, not redundantly across trials.
For a CRC team running three concurrent trials with overlapping patient pools, the savings stack: see a live model of what coordinated vs. siloed screening looks like across 10 sites and 400 patients →
The hours that come back aren't abstract. They're the hours spent on a candidate who actually matches — the conversation with the treating physician, the informed consent conversation with the patient, the day-one visit that produces a real enrollment. That's the work coordinators were hired to do.
When the protocol changes
Substantial protocol amendments are the single largest event that drains coordinator weeks. The amendment arrives. The new inclusion/exclusion logic is parsed. Every patient in the active screening queue gets re-read against the new criteria. Patients who matched the old criteria and don't match the new ones get triaged out. Patients who didn't match the old criteria and now do get surfaced. The cohort gets re-ranked.
Done manually, this re-matching takes weeks. During those weeks, the trial is effectively paused at the screening level. New patient intake slows because the cohort landscape has changed and the coordinator is still figuring out the new shape. Patients who could have enrolled in the window between amendment and re-match aged out. The cost of the amendment is two weeks of frozen screening, not the amendment itself.
An agent-based screening layer that has been continuously screening can re-match the entire patient pool against the updated criteria in hours. Not weeks. The new ranked cohort is ready the morning after the amendment is approved, and the screening pipeline resumes — at the speed it was running before the amendment interrupted it. Run the protocol-change re-screening demo →
"The CRC doesn't need to be told the protocol changed. They need to know which of the patients in front of them are still in the eligible pool, and which just dropped out."