A close-reason taxonomy helps recruitment teams explain why inquiries stopped moving instead of collapsing no-response, not-a-fit, travel, scheduling, records, and capacity issues into one stale bucket.
In this guide
Key points
- Close reasons should explain the operational barrier, not just mark a record inactive.
- No-response, declined, not-a-fit, travel, scheduling, records, duplicate, site-capacity, and study-status issues need separate categories.
- Sponsors need aggregate close-reason visibility without unnecessary patient-level detail.
Close reasons are recruitment intelligence
A recruitment queue should not close every inactive inquiry as not qualified. That single label hides whether the patient was not a study fit, could not be reached, declined, had a travel barrier, lacked records, or stalled because the site could not schedule quickly enough.
ClinicalTrials.gov points record managers to structured data element definitions for registration and results information. Recruitment operations benefit from the same principle: use structured fields when the team needs consistent interpretation later.
Start with operational categories
A useful starter taxonomy includes not-a-fit after review, could not reach, patient declined, travel or location barrier, schedule barrier, records not available, duplicate inquiry, study not currently accepting, site capacity unavailable, investigator review did not proceed, referred elsewhere, and other with required note.
The taxonomy should fit how coordinators work. If the list is too long, teams will avoid it. If it is too short, every sponsor update becomes a manual explanation.
Use close reasons to decide the fix
A source with many not-a-fit closes may need better targeting or clearer public copy. A source with many no-response closes may need timing, channel, or callback-window changes. A site with many capacity closes may need scheduling support before more traffic is useful.
TrialsNest can help by keeping source, study, owner, status, blocker, next action, and close reason connected in the same workflow so close reasons become decision data instead of cleanup labels.
Illustrative example
Case-style example
A sponsor sees 400 inquiries and 15 scheduled screenings. The first report labels most inactive records as not qualified, so the sponsor considers changing source targeting.
The team cannot tell whether the issue is source quality, follow-up speed, travel burden, or screening capacity.
A close-reason taxonomy shows many records were no-response, a smaller group declined because of travel, and several waited on records review. The next action changes by category.
Reporting note
A site that closes everything as not qualified loses the diagnosis. The same low enrollment number can come from source mismatch, slow follow-up, travel burden, or site capacity.
Common mistakes
Using one broad stale status
Stale does not say whether the patient could not be reached, declined, lacked records, hit a travel barrier, or waited too long for scheduling.
Letting free text replace categories
Notes can add context, but reporting needs structured categories that are consistent enough to compare by source, site, and study.
Before you start
- Define required close reasons: Start with not-a-fit after review, could not reach, declined, travel barrier, schedule barrier, records unavailable, duplicate, study not accepting, site capacity, and referred elsewhere.
- Make each reason actionable: If the reason does not point to a possible next action or reporting insight, it may belong as a note rather than a top-level category.
- Review weekly by source and site: Close reasons should be reviewed with source, study, site, owner, and last meaningful movement so teams can see the pattern behind the count.
- Can the site distinguish no-response from declined and not-a-fit?
- Can sponsors see close reasons in aggregate without patient-level detail?
- Which close reasons should trigger copy, source, staffing, scheduling, or protocol-review conversations?
Sources and editorial notes
Published .
Operational recruitment reporting guidance only. Close reasons should be configured to match approved study, site, sponsor, privacy, and reporting requirements.
- ClinicalTrials.gov protocol data element definitions — ClinicalTrials.gov
- Recruiting Study Subjects — FDA
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 source quality scorecard
A scorecard for comparing recruitment sources by response, fit, records readiness, scheduled movement, stale risk, and close reasons.
Patient recruitment source quality checklist
A source quality checklist for reviewing patient recruitment channels by response, fit, records, scheduled movement, and close reasons.
Sponsor recruitment reporting guides and templates
Resources for sponsor and CRO teams comparing clinical trial recruitment reporting software, dashboard views, site blockers, source quality, and next actions.
Clinical trial recruitment dashboard examples for sites and sponsors
A recruitment dashboard earns its keep when a coordinator, site lead, or sponsor can glance at it and know what needs attention.
