Lead aging should combine timing, action history, owner, source context, and next-step risk instead of sorting every recruitment queue by newest inquiry first.
In this guide
Key points
- Newest-first queues can hide untouched or stalled high-priority leads.
- Separate no-first-action leads, stalled leads, and dependency-blocked leads before assigning follow-up.
- A useful stale-lead report produces owners and next actions, not just a larger spreadsheet.
Newest first is not enough
A lead that arrived yesterday may be less urgent than a lead from four days ago who already completed a prescreen and is waiting for a coordinator call.
Lead aging works best when the site combines age, last action, current stage, owner, source, and next-step risk.
Tier 1: no first action
These leads should be reviewed first. If a participant expressed interest and no coordinator action occurred, the site has a workflow gap.
Track submission date, source, assigned coordinator, first contact attempt, and time to first action so the team can see whether the issue is routing, ownership, or capacity.
Tier 2: started but stalled
Started-but-stalled leads include records with voicemail left but no second attempt scheduled, prescreen started but no outcome recorded, participant question unanswered, or coordinator note added without a status update.
This category is where recruitment pipelines often lose operational clarity because the record looks touched but no decision path exists.
Tier 3: waiting on a dependency
Some leads are not stale because a coordinator forgot them. They are waiting on investigator review, medical record requests, sponsor clarification, site scheduling availability, or a participant callback window.
Those records need a dependency label and owner, not the same escalation as untouched leads.
Use a weekly aging report
A practical weekly report should show leads with no first action after 24 hours, no update after three business days, status without next action, no owner, study-level blocker, and closed records without a reason.
TrialsNest supports this model by keeping owner, status, source, blocker, and next action together so site leaders can prioritize work without rebuilding context from notes.
Sources and editorial notes
Published .
Operational workflow guidance for recruitment queues. Sites should follow approved communication, privacy, consent, and sponsor requirements.
- ClinicalTrials.gov protocol data element definitions — ClinicalTrials.gov
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.
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
Priority tasks
- Review screening intakeInquiry 001 · Study ACompleted
- Verify specimen preparationStudy A · Due 10:00 AMCompleted
- Confirm visit windowInquiry 003 · Follow-upPending
Upcoming visits
- In personInquiry 001
Study A · Baseline visit
View visit details → - TelehealthInquiry 003
Study A · Prescreen
Review appointment → - In personInquiry 004
Study B · Week 4
View visit details →
Keep reading
Multi-site clinical trial recruitment dashboard
A practical dashboard guide for site networks comparing recruitment movement, source quality, stale leads, records blockers, scheduled visits, and sponsor-ready next actions.
Clinical trial recruitment follow-up SLA examples
Operational SLA examples for clinical trial recruitment follow-up, including first response, prescreen review, records requests, scheduling readiness, and stale-lead review.
Site recruitment workflow for clinical trials
See the site recruitment workflow for clinical trials, from patient intake and records readiness to patient recruitment tracking dashboards, scheduling, and sponsor updates.
How to track patient recruitment across locations
Tracking patient recruitment across locations requires shared definitions and local accountability. The goal is to compare movement by site, source, blocker, owner, and next action without flattening the context each coordinator needs to work the queue.
