Patient recruitment dashboard fields checklist

A patient recruitment dashboard should not collect fields because they look impressive in a report. The first test is whether the field helps a coordinator, site lead, sponsor, or operations team decide what to do next.

Core action fields include study, site, source, owner, current status, last meaningful action, next action, due date, blocker, prescreen progress, records readiness, scheduling readiness, and close reason.

The daily queue should prioritize action: who needs outreach, who needs review, who is missing records, who is scheduling-ready, and who is stale. Those fields need to be compact and fast to scan.

Reporting fields can summarize movement by source, site, status, blocker, and close reason. They should help the team explain progress without exposing unnecessary patient-level detail in sponsor-facing views.

Dashboard fields only work when everyone uses the same definitions. Define new inquiry, first outreach attempted, prescreen in progress, prescreen completed, records needed, reviewable, scheduling-ready, scheduled, stale, no response, and closed.

Those definitions should be written into the operating model, not left as memory. Otherwise a multi-site dashboard can compare labels that mean different things at different locations.

Source quality fields should go beyond source name and lead count. Useful measures include response rate, prescreen completion, reviewable candidates, records-ready candidates, scheduled next steps, stale rate, and close reasons.

These fields help teams decide whether the issue is sourcing, follow-up timing, patient-facing language, study criteria, missing records, or site capacity.

A dashboard checklist should also ask where sensitive details belong. Public pages and sponsor summaries should not become broad patient-detail workspaces.

TrialsNest keeps dashboard planning tied to operational movement while preserving the boundary that authorized study teams make final screening, eligibility, enrollment, and clinical decisions.

Turn the checklist into a recurring site review, not a one-time document. Assign an owner, define the status field it affects, name the blocker reason it should reveal, and decide which item belongs in the coordinator queue versus the sponsor update.

The practical output should be a cleaner next action: request records, clarify criteria, confirm visit capacity, update approved copy, close a stale lead, or escalate a sponsor question. If the checklist does not change a next action, it is probably still too generic.

For TrialsNest buyers, this is the operating test. The platform should make ownership, readiness, blocker, and reporting fields visible enough that the site can work the queue and explain progress without rebuilding the story in a spreadsheet.

Review each source by movement quality: response rate, completed prescreens, reviewable fit, records readiness, scheduled next steps, close reasons, and stale-lead patterns. A source with high form volume can still be weak if coordinators spend most of the time cleaning up low-fit or unreachable inquiries.

Separate source quality from site execution before making budget decisions. If a source produces reviewable candidates but the site is slow to follow up, the fix is workflow ownership. If follow-up is fast but close reasons cluster around mismatch or distance, the fix may be source targeting or patient-facing copy.

The review should end with a decision: keep, pause, adjust targeting, rewrite expectations, add records support, or change the follow-up cadence. That decision is the difference between a scorecard and another static report.