Clinical research professional conducting candidate follow-up by phone at a modern research site
Referral to Randomization

Referral Follow-Up Workflows for Clinical Trials

Candidate non-response is an operational status that requires a defined next step. Consent2Randomize follows the research site's approved plan for ownership, permitted communication channels, study-specific timing, attempt limits, documentation, escalation, and closure. Clinical and protocol questions are escalated to authorized site personnel, and the research site determines eligibility.

Why Unstructured Follow-Up Produces Inconsistent Results

In enrollment operations without a defined follow-up protocol, follow-up frequency, timing, and channel selection depend on individual staff availability and judgment. Some candidates receive immediate and persistent follow-up because they are assigned to a highly engaged staff member or arrive during a low-volume period. Others receive minimal or no follow-up because the queue is deep, the staff member has competing priorities, or there is no defined expectation of follow-up effort.

Without a defined workflow, the record may not show who owns the next attempt, which channels are permitted, whether contact requirements have been met, or when the candidate should be escalated or moved to a site-approved disposition. A structured workflow replaces that ambiguity with documented actions and a visible current status. It does not establish why a candidate did not respond or guarantee a future response.

For the broader context of how follow-up relates to referral conversion, see improving referral conversion in clinical research. For the complete bottleneck picture in which follow-up gaps appear, see common referral-to-randomization bottlenecks.

Five Elements of a Site-Approved Follow-Up Protocol

A complete follow-up protocol specifies five connected elements. Together they define what Consent2Randomize does, what gets documented, when an issue is escalated, and how the record reaches a site-approved closure, disposition, or handoff.

  • Ownership and attempt limits: The site-approved plan assigns responsibility for follow-up and defines the maximum number of permitted attempts before the record moves to a closure, escalation, or other site-approved disposition. The limit should reflect the study, candidate population, consent-to-contact requirements, and site policy.
  • Study-specific timing: The research site defines when follow-up begins and how attempts are spaced. Consent2Randomize applies that approved timing, records each attempt, and makes overdue or unresolved actions visible without treating one cadence as a universal benchmark.
  • Permitted communication channels: The plan identifies which channels are authorized for the study, how candidate communication preferences are documented, and what consent-to-contact or privacy requirements apply. Consent2Randomize uses only the permitted channels and records the channel and status of each attempt.
  • Message content and escalation rules: Site-approved messages state the purpose of the contact and the requested next step. Clinical, medical, and protocol questions are not answered by follow-up staff; they are documented and escalated to authorized site personnel.
  • Closure and disposition rules: The plan defines what happens after the approved attempt sequence, a request for no further contact, missing information, or a question requiring site review. Consent2Randomize documents the final outreach status and follows the site-approved closure, escalation, or handoff instruction. The research site determines eligibility and any clinical disposition.

Follow-Up Workflow and Intake Quality

A structured follow-up workflow depends on the intake fields required by the site-approved plan. Those fields can include contact details, candidate communication preferences, consent-to-contact status, assigned owner, completed preliminary steps, and unresolved questions. Connecting these fields to clinical trial intake gives the follow-up team a clear starting record.

Intake documentation standards and follow-up workflow design should be developed together. Consent2Randomize carries the approved intake fields into the follow-up record, documents every permitted attempt, and flags missing information or clinical and protocol questions for the appropriate site contact.

For the intake process standards that support effective follow-up, see referral intake best practices for research sites. For the full referral management framework that connects intake, follow-up, and prescreening into a unified workflow, see clinical trial referral management best practices.

Follow-Up Workflow and Coordinator Capacity

When follow-up is assigned to a dedicated intake and prescreening function, the agreed outreach and documentation work is handled outside the coordinator queue. Consent2Randomize provides the site with records for candidates who responded, candidates who remain unreachable, and questions that require authorized review. The effect on coordinator capacity depends on the site's volume, responsibilities, and implementation.

When coordinators own follow-up in addition to clinical responsibilities, contact attempts and documentation become part of the same workload. Defined ownership makes that workload visible and allows the site to decide which operational tasks remain with coordinators and which are assigned to a dedicated support function. For detailed guidance on organizing upstream enrollment tasks, see how to reduce coordinator burden.

Frequently Asked Questions

Common questions about referral follow-up workflow design, attempt protocols, and channel sequencing for clinical trials.

If your site does not have a defined referral follow-up protocol, we organize ownership, permitted channels, study-specific timing, attempt limits, documentation, escalation, and closure rules into a workflow the team can execute consistently.

Build Your Follow-Up Workflow