All articles
Recruitment StrategyNovember 7, 2026·3 min read

How to Run Recruitment When Six Studies Need the Same Patients

Running several protocols at once turns recruitment into an allocation problem. Here's how to route overlapping candidates, protect screening capacity, and manage the portfolio instead of each study in isolation.

By Trialflow Team

Most sites don't fail at recruitment because they can't find patients for a study. They fail because they're trying to find patients for seven studies at once with the same two coordinators, the same database, and the same ad budget. The hard part isn't any single protocol — it's the allocation problem underneath all of them.

Studies compete, whether you manage it or not

When three cardiology protocols are open simultaneously, every inbound call becomes an implicit decision about which one gets the patient. If nobody has made that decision deliberately, it gets made by whoever answers the phone, based on whichever protocol they remember best. That usually means the newest study, or the one with the loudest sponsor.

The fix is to decide in advance, in writing, how overlapping candidates get routed. A simple priority order works:

  • Enrollment deadline pressure. Studies closing enrollment in weeks outrank studies with a year left.
  • Window of eligibility. If a patient's eligibility is time-bound — post-event windows, washout constraints, acute presentations — that study gets first look.
  • Difficulty of replacement. If a patient fits a narrow protocol and a broad one, give them to the narrow one. You'll find another candidate for the broad study.
  • Site commitment risk. Studies where you're behind your contracted target get priority over ones where you're ahead.

Write it on one page. Review it at every recruitment meeting. The point is that nobody has to improvise.

Separate the funnel from the protocol

Sites that juggle well tend to run a single intake funnel rather than parallel per-study funnels. Inbound interest goes into one queue. A trained screener does a general medical and demographic intake first, then matches against the open portfolio.

This matters for two reasons. First, a patient who fails one protocol is often a strong candidate for another, and a per-study funnel throws them away. Second, it lets you advertise around conditions rather than protocols, which is cheaper and more durable than spinning up and tearing down campaigns every time a study opens.

Keep a running list of near-misses with the specific reason they didn't qualify. In most site datasets, a meaningful share of enrollments on new studies come from people who were screened months earlier for something else.

Protect capacity before you protect enthusiasm

The most common multi-study failure is accepting a new protocol when your screening visit capacity is already saturated. Enthusiasm is free; exam rooms, PI chart review time, and coordinator hours are not.

Before signing on for another study, calculate:

  1. Screening visits per week each open study requires at its current conversion rate.
  2. Hours of coordinator time per screening visit, including pre-screen chart review and source documentation.
  3. PI availability for eligibility sign-off, which is usually the real bottleneck.

If the math doesn't close, you either decline, hire, or delay the start. Taking the study anyway means underperforming on two studies instead of performing on one.

Review the portfolio weekly, not each study separately

Hold one recruitment meeting that covers everything, with a single view of candidates by study and stage. Per-study meetings hide the tradeoffs — you can't see that the study everyone's excited about is quietly starving the one with a deadline.

Fifteen minutes, every week: what moved, what stalled, where the screening slots went, and which study gets the next ten candidates. That cadence does more for multi-study performance than any single channel tactic.

Enrolling studies shouldn't be this hard

Trialflow gives research sites one platform for lead management, AI trial matching, and recruitment analytics.

Request a Demo