Clinical Operations

Close-reason taxonomy for clinical trial recruitment queues

A practical taxonomy for clinical trial recruitment close reasons so sites and sponsors can distinguish no-response, not-a-fit, scheduling, travel, source quality, and capacity issues.

By TrialsNest editorialUpdated 4 min read

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.

Practical scenario

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.
Field notes

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.

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.

Checklists and questions for your team

Decision checklist

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.

Before you start

What does clinical trial recruitment close reasons need to change in the daily workflow?
Which team owns the next action when a patient, site, or sponsor handoff stalls?
What signal would prove the workflow is improving instead of only adding more data?

Questions for your team

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?

Ways to use this guide

Compare it with the real queue

Read it next to the way your team already works. The gaps usually show up around ownership, missing records, follow-up timing, or sponsor-update prep.

Mark the handoffs

For each section, ask where the work changes hands. If the handoff depends on memory, a spreadsheet tab, or a buried message, that is probably worth fixing.

Leave with one operating change

The guide should point to one next status, owner, report field, review cadence, or patient-facing boundary that gets clearer.

Common questions

What should teams know about clinical trial recruitment close reasons?

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. The practical value is in connecting the concept to ownership, follow-up, records readiness, scheduling, reporting, and clear next actions.

Who is this resource written for?

This resource is written for clinical operations sorting through practical questions around clinical trial recruitment close reasons and the workflow decisions that usually come with it.

Does this guide replace study-team review or medical advice?

No. TrialsNest resources are educational and operational. They do not provide medical advice, diagnosis, treatment, emergency care, or final clinical trial eligibility decisions.

How would a team use this workflow guidance in practice?

Use it to compare the current workflow with what actually happens day to day: where leads wait, where records get lost, where follow-up slows down, and what needs a clearer owner. The best next step is to turn the article takeaways into a short review checklist for clinical trial recruitment close reasons.

Sources and editorial notes

Published . Reviewed by TrialsNest clinical operations review on .

Operational recruitment reporting guidance only. Close reasons should be configured to match approved study, site, sponsor, privacy, and reporting requirements.

This information is educational. Your study team makes medical, eligibility, and enrollment decisions.

TrialsNest can organize intake, prescreening, and workflow context, but it does not make final eligibility, enrollment, treatment, or medical decisions.

Sponsor-ready updates should show source quality, movement, blockers, and next actions without becoming a broad patient-detail workspace.

These resources explain clinical recruiting workflows and buying decisions. Sensitive study details belong in the appropriate secure workflow.

See TrialsNest in action

Bring this workflow into one place.

Manage inquiries, follow-ups, records, and visits. Keep sponsors updated on progress.

Example TrialsNest platform workspace using sample data.

Keep reading