Clinical Trial Enrollment Tracking Template: What to Log and Why
Published September 2026 · 7 min read · By Clinical Enroll
Most sites start enrollment tracking with a shared spreadsheet, or whatever the last coordinator built before handing off the role. That works fine until a sponsor asks for a screen fail rate broken out by referral source, or a new coordinator inherits a tracker nobody can fully explain.
A fixed set of fields, updated the same way every time, closes both gaps before they surface in a monitoring visit. Below is the field list, a copy-ready template, and how the log turns into the metrics sponsors already expect to see.
37%
of investigative sites under-enroll their target (Tufts CSDD, 2008-2010)
11%
of sites enroll zero patients over the life of a study (Tufts CSDD, 2008-2010)
Why an Ad Hoc Spreadsheet Runs Out of Room
A tracker that grows organically tends to drift. One coordinator adds a column for a sponsor request. Another abandons a field nobody uses anymore. Eighteen months in, the spreadsheet can answer some questions well and others not at all, and the gaps are rarely the ones you expect until a monitoring visit exposes them.
None of this reflects poorly on the coordinator who built it. A tracker built under deadline pressure, one screening event at a time, is going to look different from one designed up front with the end reports in mind. The fix is not a better spreadsheet author. It is a fixed structure that does not depend on any one person remembering what a column means.
The Fields Worth a Column
Eight fields cover almost everything a site or a sponsor will ask for later. Fewer than that and a monitoring visit surfaces a question the log cannot answer. More than that and coordinators start skipping fields under time pressure, which defeats the point.
Screening ID
An internal, de-identified reference (S-014, S-015) rather than a name or initials. It is the row's anchor for every other field.
Referral source
Where the screen originated: EHR pull, physician referral, community outreach, or a recruitment campaign. This is the field that turns a flat enrollment count into a channel-level view of what is actually working.
Screening date
The date the patient was assessed against eligibility criteria. Paired with the referral date, if tracked separately, this is what exposes a slow-moving referral pipeline before it becomes a missed target.
Eligibility outcome
Pass, fail, or pending, with a short reason code for a fail (age, lab value, exclusion criterion). The reason code is what makes a screen fail rate diagnostic instead of just a number.
Consent date
The date informed consent was signed. Distinct from the screening date, since the gap between the two is itself worth watching when it starts to stretch.
Randomization date
The date the patient entered the study. This single field, tracked against the monthly target, is what a sponsor is really asking about when they ask how enrollment is going.
Visit schedule status
On schedule, delayed, or a note on the next required visit. This is what catches a protocol deviation risk before it becomes one.
Query or data entry status
Open, resolved, or the date entered. A field that sits open for weeks is a pattern sponsors notice well before they say anything about it.
A Template You Can Copy Today
Copy the structure below into a spreadsheet or your CTMS. The two rows underneath the header are illustrative, not real patient data, and show how a completed row should read.
| Screening ID | Referral Source | Screening Date | Eligibility Outcome | Consent Date | Randomization Date | Visit Status | Query Status |
|---|---|---|---|---|---|---|---|
| S-014 | EHR pull | 3/2 | Pass | 3/9 | 3/16 | On schedule | Resolved |
| S-015 | Physician referral | 3/4 | Fail (lab value) | — | — | — | — |
A screen fail row still earns a full entry. It is what makes the screen fail rate calculation possible in the first place.
Update Cadence and Ownership
Update the log at the event, not in a weekly batch. A screening logged the same day is accurate. A week of screenings reconstructed from memory on a Friday afternoon is not, and the gaps tend to land in exactly the fields that matter most.
One person owns the log. Not because only one person is capable of updating it, but because a shared file with no clear owner is how fields quietly stop getting filled in. The coordinator who owns it does not have to be the one entering every row, just the one who notices when a row goes missing.
Not sure your current study is worth the tracking overhead?
Sites weighing whether a specific study's enrollment target is realistic can check if it qualifies for a randomization commitment before investing more coordinator time in it.
Check if a study qualifiesFrom Log to the Numbers Sponsors Ask For
The eight fields above are not just a record. They are the raw material for the metrics sponsors already track on their end: enrollment rate against target, cumulative screen fail rate, and time from activation to first randomization. A site keeping this log has those numbers on hand before a monitoring visit asks for them, not after.
The full breakdown of which metrics matter, how often to review them, and where the thresholds sit is in the site performance metrics guide. For sites specifically working on the screen fail number this log tracks, see reducing screen fail rates.
Where Tracking Habits Slip
The log usually breaks down in three predictable places, and none of them are about a site being careless. Time pressure at the point of screening pushes data entry to later, and later never quite arrives. A patient's record lives across paper, an EDC system, and a sponsor portal, and the site's own log is the one nobody is required to keep current. A coordinator who built the tracker leaves, and the next person inherits a structure they were never shown.
All three are what happens when a tracking system depends on one person's memory instead of a fixed structure everyone uses the same way. A copy-ready template does not fix time pressure or turnover on its own, but it removes the guesswork about what a column means for whoever picks it up next.
Two studies from the Clinical Enroll portfolio show what consistent tracking supports on the enrollment side, even under a narrow protocol:
Narrow Eligibility, Type 1 Diabetes (vTv Therapeutics)
$1,818 CPP
11 randomized patients across three site locations · $20,000 investment
Read the case studyRestrictive Pediatric Protocol, RSV Vaccine (Blue Lake Biotechnology)
$2,000 CPP
15 randomized patients across three site locations · $30,000 investment
Read the case studyVisibility a Sponsor Already Expects
Sponsors and CROs are already tracking enrollment rate, screen fail rate, and time to first patient from their side. A site with the same numbers on hand, in the same format, every time a report is requested, reads as a site running a tight operation. That is a reputation that carries into the next study offer.
None of this requires new software or a CTMS purchase. It requires eight fields, one owner, and updating the log the same day the event happens.
Sources: Tufts Center for the Study of Drug Development (site-level enrollment benchmark data, 2008-2010: 11% of sites enroll no patients, 37% under-enroll); Clinical Enroll (first-party CPP data from published case studies: $1,818 vTv Therapeutics, $2,000 Blue Lake Biotechnology).
See if our guaranteed approach is the right fit for your study.
Book a free consultation to walk through your current enrollment pipeline, tracking log included. We will tell you whether our guaranteed approach is a fit before you commit anything.
Book a Free ConsultationAll campaigns developed for IRB review and deployed in accordance with FDA guidance on clinical trial advertising.