Candidate records can stop progressing at different points between referral and the site-controlled downstream stages. The reason may be operational, clinical, logistical, personal, protocol-related, or unknown. A useful review separates observed non-progression from assumed cause, then measures timing, status, unresolved items, and known disposition reasons at each transition.
Sites that track only total enrollments and screen failure rates are missing the majority of their enrollment story. Screen failure captures dropout at the formal screening stage. It does not capture the candidates who expressed interest, entered the pipeline, and dropped out before ever reaching screening. In most enrollment operations, this pre-screening dropout is larger in volume than screen failure and more amenable to operational correction.
Stage-specific dropout analysis disaggregates total conversion loss into its component parts: where candidates are leaving the pipeline, in what volume, and through what mechanism. This disaggregation is what makes enrollment management operational rather than reactive.
For the workflow design framework governing the transitions where dropout occurs, see referral-to-randomization workflow. For the bottlenecks that produce the structural conditions for dropout, see common referral-to-randomization bottlenecks.
At each stage, review what was observed, possible contributors, and what can be measured or tested. Do not assume a single cause from non-progression alone.
Volume
Observed status
Primary Cause
Possible contributors: contact timing, incomplete intake information, candidate choice, logistics, protocol fit, or unknown reasons
Correction
What to measure or test: elapsed time, contact attempts, unresolved items, disposition reasons, and local workflow ownership
Volume
Observed status
Primary Cause
Possible contributors: contact timing, channel availability, candidate choice, changing circumstances, or unknown reasons
Correction
What to measure or test: attempt history, intervals, permitted channels, response status, and local follow-up rules
Volume
Observed status
Primary Cause
Possible contributors: unresolved information, documentation, site availability, candidate logistics, or other study-specific factors
Correction
What to measure or test: handoff readiness, unresolved items, elapsed time, and site-defined handoff rules
Volume
Site-controlled downstream stage
Primary Cause
Track disposition separately. Do not infer an upstream cause without evidence.
Correction
What to measure or test: site-reported disposition, elapsed time, scheduling status, and known logistical factors
Volume
Site-controlled downstream stage
Primary Cause
Track disposition separately. Do not infer an upstream cause without evidence.
Correction
What to measure or test: site-reported outcomes and known reasons, separate from C2R pre-consent operational measures
Volume
Site-controlled downstream stage
Primary Cause
Track disposition separately. Do not infer an upstream cause without evidence.
Correction
What to measure or test: site-reported downstream disposition and known protocol, clinical, logistical, or participant factors
Early-stage non-progression may be worth reviewing because it occurs before formal site screening. Use local stage counts, elapsed time, contact history, unresolved items, and known disposition reasons to determine whether an operational issue is present rather than assuming the cause or relative volume.
If local evidence shows contact timing or unclear follow-up ownership is contributing to non-progression, a site can define engagement-specific response targets and follow-up rules. Those targets should follow the approved workflow and should not be presented as universal standards or guarantees.
Structured clinical trial intake and clinical trial prescreening together address early-stage dropout through prompt response, complete documentation, structured eligibility evaluation, and consistent follow-up. For the specific follow-up workflow that manages non-responsive candidates, see referral follow-up workflows for clinical trials.
Coordinator capacity may be one contributor when local workload, queue, and timing data show a constraint. Other operational, clinical, logistical, personal, protocol-related, and unknown factors may also explain non-progression.
Separating pre-site enrollment functions from clinical coordinator responsibilities through dedicated intake and prescreening support addresses both the dropout and the capacity problem simultaneously. For detailed guidance on reducing coordinator burden to improve this outcome, see how to reduce coordinator burden. For overall enrollment operations strategies, see enrollment operations. For the enrollment infrastructure systems that sustain these improvements across study cycles, see enrollment infrastructure.
Common questions about candidate dropout in the referral-to-randomization pathway and how to reduce it.
Related Resources
Continue Reading
If your site is losing candidates at one or more stages of the enrollment pathway, a structured dropout analysis can identify the specific failure points and the operational changes that will produce the greatest improvement in conversion.