Clinical trial recruitment source launch checklist

Before a source launches, confirm the approved recruitment language, study description, contact path, privacy boundary, and what the source is allowed to say about the study.

The source should not promise eligibility, enrollment, compensation, medical benefit, or a specific appointment outcome unless the approved materials support that language.

The checklist should verify where inquiries land, which fields arrive, whether source attribution is captured, who gets notified, how duplicates are detected, and what happens if a record is incomplete.

A test inquiry before launch is often the simplest way to catch broken routing while there is still time to fix it.

A source launch should include first-response expectations, owner assignment, backup coverage, no-response cadence, and escalation criteria.

If a new source creates volume but no ownership rule, it can make the queue look busier while producing slower patient follow-up.

Source quality should be reviewed through response rate, prescreen completion, records readiness, scheduling movement, screen-failure patterns, close reasons, and stale risk.

Raw volume is useful, but it does not tell the team whether a source is creating reviewable candidates or avoidable workload.

Before launch, agree on when a source should be paused, revised, or stopped. Examples include repeated wrong-study inquiries, low response after follow-up, poor records readiness, high duplicate rate, or misleading source expectations.

That makes source management an operating discipline instead of a monthly debate about whether volume feels good or bad.

Review each source by movement quality: response rate, completed prescreens, reviewable fit, records readiness, scheduled next steps, close reasons, and stale-lead patterns. A source with high form volume can still be weak if coordinators spend most of the time cleaning up low-fit or unreachable inquiries.

Separate source quality from site execution before making budget decisions. If a source produces reviewable candidates but the site is slow to follow up, the fix is workflow ownership. If follow-up is fast but close reasons cluster around mismatch or distance, the fix may be source targeting or patient-facing copy.

The review should end with a decision: keep, pause, adjust targeting, rewrite expectations, add records support, or change the follow-up cadence. That decision is the difference between a scorecard and another static report.

Turn the checklist into a recurring site review, not a one-time document. Assign an owner, define the status field it affects, name the blocker reason it should reveal, and decide which item belongs in the coordinator queue versus the sponsor update.

The practical output should be a cleaner next action: request records, clarify criteria, confirm visit capacity, update approved copy, close a stale lead, or escalate a sponsor question. If the checklist does not change a next action, it is probably still too generic.

For TrialsNest buyers, this is the operating test. The platform should make ownership, readiness, blocker, and reporting fields visible enough that the site can work the queue and explain progress without rebuilding the story in a spreadsheet.