A recruitment cadence is only useful when it is visible in the queue: who tried, when they tried, what happened, what is allowed next, and when the lead should be closed or reviewed.
In this guide
Key points
- Cadence should define timing, channel, owner, status change, and close reason for each follow-up step.
- The first response should happen quickly, but reminders should stay within approved communication boundaries.
- Stale-lead review is easier when every message updates the queue instead of living only in an inbox.
Define first outreach before volume increases
The first follow-up step should name who owns new inquiries, how quickly the site attempts contact, which channels are approved, and what status is applied if the person cannot be reached. Without that definition, coordinators often create their own cadence under pressure.
The first message should be clear that the site is reviewing interest and next steps. It should not suggest that the person qualifies, has been selected, or should make care decisions based on a recruitment message.
Use reminders with documented boundaries
A practical cadence may include a first outreach attempt, a reminder, a records or scheduling follow-up if applicable, and a final no-response step. The exact timing should match the study's approved communication plan and site policy.
Each reminder should update the recruitment record with date, channel, owner, result, and next step. That makes the cadence auditable and prevents multiple team members from unknowingly contacting the same person.
Separate no response from not a fit
No-response leads, not-interested leads, records-blocked leads, and study-not-a-fit leads should not collapse into one stale bucket. The site needs different next actions and different reporting for each close reason.
This distinction matters for source quality. A source that produces reachable but ineligible people is different from a source that produces people the site cannot contact at all.
Make cadence visible in reports
A sponsor-ready update should show how many inquiries are new, contacted, awaiting response, records-blocked, scheduled, closed, or stale. It should also show where the cadence is breaking down.
TrialsNest helps sites connect follow-up cadence to coordinator ownership, stale-lead review, source quality, and reporting so recruitment work does not disappear into separate inboxes and spreadsheets.
Illustrative example
A three-attempt review without inbox archaeology
A coordinator sees a lead with one call, one approved reminder, and no response. The queue shows the next allowed step, who owns it, and when the no-response close should be reviewed.
Before: the team searches email and phone notes to figure out whether another contact is appropriate.
After: contact attempt, result, next step, owner, and close threshold are visible in the recruitment record.
The moment cadence breaks
The risky point is usually not the first call. It is the second or third attempt, when the first coordinator is busy, the inbox has moved on, and nobody can tell whether another reminder is appropriate.
Common mistakes
Counting attempts without changing status
A message that does not update owner, date, result, and next step still leaves the queue dependent on memory.
Treating every stale lead the same
No response, records blocked, not interested, and likely not a fit need different handling and different reporting.
Before you start
- Timing defined: Does each stage have an approved timing window and channel rule?
- Queue updated: Does every attempt change the recruitment record instead of living only in messages?
- Close reason ready: Can the team distinguish no response from not interested, records blocked, duplicate, or not a fit?
- What is the approved next step after each unanswered contact attempt?
- When does a coordinator stop trying and document a close reason?
- Which cadence signals should appear in the sponsor update?
Sources and editorial notes
Published .
Operational recruitment workflow guidance only. Follow-up cadence should follow sponsor, IRB, protocol, privacy, and site-approved communication requirements.
- Recruiting Study Subjects — FDA
- Informed Consent FAQs — HHS Office for Human Research Protections
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
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.
Clinical trial patient communication checklist for research sites
A patient communication checklist for research sites standardizing follow-up, records requests, scheduling, and review boundaries.
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.
Clinical trial lead aging: how sites can prioritize stale recruitment work
Lead aging should combine timing, action history, owner, source context, and next-step risk instead of sorting every recruitment queue by newest inquiry first.
