Research Sites

Referral partner handoff SOP for clinical trial recruitment

A practical SOP-style playbook for managing clinical trial referral partners, including approved language, handoff boundaries, routing, tracking, and follow-up.

Referral partners can help people learn that a study exists, but sites need approved language, clean routing, minimum-necessary tracking, and clear boundaries for what partners should not do.

In this guide

Key points

  • Referral partners need approved language and clear boundaries before they begin sending interested people to a site.
  • The handoff should be tested before volume arrives so attribution, ownership, and duplicate handling work.
  • Partner feedback should focus on operational quality without exposing unnecessary patient detail.

Define approved partner language

Give partners approved language for the study name or short description, who may contact the site, what the site will review, what not to promise, where interested people should go, and who handles questions.

Referral partners should not imply eligibility, enroll participants, answer consent questions beyond approved materials, or collect unnecessary sensitive information unless the study's approved process explicitly supports that role.

Test the handoff route

Define whether referrals move through patient self-referral, secure form, phone handoff, coordinator intake queue, source tag, duplicate check, and backup owner.

A test referral before launch is a simple way to catch broken routing, missing source attribution, or incomplete owner alerts before the partner starts sending volume.

Track the minimum necessary fields

Track enough to manage the workflow: source partner, study interest, date received, owner, status, next action, and close reason.

Do not put sensitive medical narratives into broad recruitment reports. The site can manage source quality without turning shared reporting into a patient-detail workspace.

Create a partner feedback loop

Partners should receive operational feedback, not patient details. Useful feedback includes referral volume, incomplete handoffs, wrong-study referrals, common expectation gaps, and whether approved materials need clarification.

TrialsNest can support this model by keeping referral source, owner, blocker, and next action connected to the lead record while preserving privacy-conscious reporting boundaries.

Case-style example

A specialty clinic refers patients by email, but the messages include detailed medical history. Coordinators then copy those notes into a spreadsheet, creating workflow and privacy risk.

A better SOP routes interested patients to the site intake path and records the clinic as the source without exposing unnecessary details in shared reports.

Sources and editorial notes

Published .

Operational SOP guidance for referral handoffs. It does not authorize referral partners to screen, consent, diagnose, or collect sensitive information outside approved study workflows.

This information is educational. Your study team makes medical, eligibility, and enrollment decisions.

See TrialsNest in action

Bring this workflow into one place.

Manage inquiries, follow-ups, records, and visits. Keep sponsors updated on progress.

Site clinical operations

Coordinator Today

Your inquiries, priorities, and upcoming visits.

Inquiries assigned
14
3 pending review
Visits today
6
4 in person · 2 virtual
Action priorities
4
Needs attention
Active studies
3
Study A · B · C
Daily priorities

Priority tasks

  • Review screening intakeInquiry 001 · Study A
    Completed
  • Verify specimen preparationStudy A · Due 10:00 AM
    Completed
  • Confirm visit windowInquiry 003 · Follow-up
    Pending
Today’s schedule

Upcoming visits

  1. In personInquiry 001

    Study A · Baseline visit

    View visit details →
  2. TelehealthInquiry 003

    Study A · Prescreen

    Review appointment →
  3. In personInquiry 004

    Study B · Week 4

    View visit details →

Keep reading