A screen failure is recorded when a patient who has begun the formal screening process — typically after giving informed consent and completing at least some screening assessments — is found to be ineligible for a trial. In Phase II and Phase III trials, screen failure rates of 30–40% are typical at sites without structured pre-screening protocols. At sites that rely primarily on physician referrals or patient self-referral without EHR-based eligibility filtering, rates above 50% are not unusual.
The operational cost of a screen failure is not trivial. Depending on the protocol, a screen visit may involve a physical exam, an ECG, a fasting blood draw, patient questionnaires, and 60–90 minutes of coordinator time for consent documentation and data entry. A screen failure represents the full cost of that effort with no enrollment outcome. At sites running 50–60 screen failures to enroll 30 subjects, the screen visit overhead consumes a substantial fraction of the site's operational capacity.
This guide focuses on the practical interventions that reduce screen failure rates, with emphasis on interventions that can be implemented at the site level without sponsor protocol amendments. We will cover EHR-based pre-screening filters, coordinator workflow structure, outreach scripting that surfaces common exclusion criteria before the screen visit, and the role of protocol amendments in downstream failure patterns.
Classifying screen failures before trying to reduce them
Not all screen failures have the same cause, and the interventions that reduce one type may not address another. Before implementing changes to a pre-screening workflow, it is useful to classify the prior period's screen failures by reason.
Screen failures fall into three broad categories: protocol-ineligible (the patient did not meet objective I/E criteria that should have been identifiable from EHR data before the screen visit), screening-ineligible (the patient met EHR-identifiable criteria but failed a criterion that could only be assessed at the screen visit — a live ECG finding, a physical exam measurement, a fasting lab value not available pre-visit), and patient-withdrawn (the patient met eligibility criteria but declined to continue after consent and before or during screening).
Protocol-ineligible failures are the category most directly addressable through pre-screening workflow changes. If a patient fails screen because they had prior insulin use within the exclusion window, or because their eGFR measured at the screen visit is below threshold, and that information was available in the EHR before the screen visit was scheduled — that is a pre-screening failure, not a protocol failure. The intervention is upstream: better EHR data extraction before the outreach call, not better screening form design.
Screening-ineligible failures (ECG findings, live exam measurements) are harder to prevent through pre-screening and may require protocol amendment discussions with the sponsor if they account for a large fraction of failures. Patient-withdrawn failures are addressed through patient communication and consent quality, not EHR workflows.
Categorizing failures by reason takes roughly an hour per trial per quarter if data is already being captured in the CTMS. Sites that do not currently capture screen failure reason codes in their CTMS should add that field — it is one of the most actionable data elements in enrollment operations.
EHR-based pre-screening filters: which criteria to run first
Not all I/E criteria are equally efficient as pre-screening filters. The most efficient pre-screening criteria are those that: (a) have a low pass rate in the general population of interest (high discriminating power), (b) can be confirmed from EHR data without a live assessment, and (c) are binary or near-binary rather than requiring clinical judgment to evaluate.
For a T2DM trial with HbA1c inclusion and eGFR exclusion criteria, the eGFR threshold is often the more powerful pre-filter. A proportion of the T2DM population has CKD stage 3 or higher; if the trial excludes eGFR <45, querying eGFR against the EHR population first will eliminate a meaningful fraction of the pool before any other criteria are evaluated. The HbA1c window (e.g., 7.5–11%) captures a large fraction of uncontrolled T2DM patients and is less discriminating as a first filter.
Medication exclusions are often the most powerful pre-screening filters in cardiometabolic and rheumatology trials, where prior or current use of a specific drug class is a common exclusion criterion. A patient on a GLP-1 receptor agonist is excluded from a GLP-1 mechanism trial regardless of their lab values — running the medication exclusion filter first reduces the population that needs lab value evaluation. The EHR's MedicationRequest and MedicationStatement resources should be queried with a full list of RxNorm identifiers for the excluded drug class, not just a few brand-name matches.
The efficient pre-screening workflow applies filters in order of discriminating power, from most to least, so that each filter reduces the population evaluated by the next. A coordinator building a manual pre-screening checklist should sequence the criteria the same way — not in the order the criteria appear in the protocol document, but in the order that minimizes chart review time per ineligible patient identified.
Structuring the pre-screen outreach call
The outreach call to a candidate patient is the first live interaction in the screening process and the most efficient point to surface common exclusion criteria that require patient-reported information. An outreach call that spends four minutes on scheduling and one minute on eligibility screening is wasting the opportunity to prevent a screen failure before the screen visit is booked.
A well-structured outreach call sequences eligibility-relevant questions before scheduling. The coordinator opens with a brief description of the trial, confirms that the patient has no objection to being contacted about research opportunities (per relevant IRB protocol), and then moves to a short set of patient-reported questions targeting exclusion criteria that EHR data cannot reliably confirm.
Patient-reported information is most useful for: current medication use (the patient may be on a medication not in the EHR), recent clinical events (the patient may have had a hospitalization, procedure, or diagnosis since their last EHR encounter), and travel or schedule constraints that affect protocol visit requirements (which can prevent completion of the trial even in an eligible patient).
A coordinator who discovers on the outreach call that a patient started insulin two months ago has prevented a screen failure at zero additional cost. The same information discovered at the screen visit after consent has cost the site a full screen visit workup and is recorded as a screen failure in the CTMS. The two outcomes are operationally identical in terms of eligibility outcome; the difference is entirely in when the information surfaced.
The outreach script should be reviewed against the trial's historical screen failure reasons. If the prior quarter's failures included a disproportionate number due to a specific exclusion criterion that patients could have reported on the phone (e.g., recent cardiovascular event, ongoing chemotherapy, current immunosuppressive therapy), that question should be added to the outreach call script.
Coordinators stay in the loop — the role of the ranked candidate list
A point worth stating explicitly: the goal of structured pre-screening is to give coordinators better information faster, not to remove coordinator judgment from the process. An EHR-based pre-screening tool that returns a ranked candidate list is not making eligibility determinations — it is telling the coordinator which patients have the most EHR-confirmable evidence supporting eligibility, and which specific criteria remain uncertain.
The coordinator reviews the list, evaluates the data completeness signals, decides which patients to prioritize for outreach, and uses their clinical knowledge of the patient population to fill in judgment gaps that the EHR data cannot resolve. A patient with an eligibility confidence score of 78 because their BMI was last recorded 14 months ago might be a high priority to contact (if the coordinator knows from prior encounters that the patient's weight has been stable) or a lower priority (if the coordinator knows the patient has been actively trying to lose weight). That judgment sits with the coordinator, not the tool.
This division of labor — automated EHR-to-criteria mapping for objective data elements, coordinator judgment for clinical context and patient-reported information — is what makes pre-screening workflows sustainable. A system that tries to remove coordinator judgment from the process entirely is not viable in a regulated trial environment. A system that automates the objective data extraction step while preserving coordinator control of the final eligibility determination is both practical and defensible.
Protocol amendment impact on screen failure patterns
Protocol amendments that modify I/E criteria have a direct and sometimes dramatic effect on screen failure rates, and not always in the direction sponsors intend. An amendment that broadens an inclusion criterion — expanding the HbA1c range from 7.5–11% to 7.0–11.5%, for example — will increase the candidate pool but may not decrease screen failure rates if the population newly included by the amendment has different characteristics that run into other exclusion criteria.
When an amendment is issued, sites should re-run their pre-screening population analysis against the updated criteria before assuming the amendment will resolve enrollment shortfalls. An amendment that removes a strict eGFR lower bound may increase the candidate pool but bring in patients with higher rates of comorbidities that trigger other exclusion criteria. Identifying that pattern before investing outreach effort in the expanded pool saves screen visit overhead.
The CTMS screen failure data is the most valuable resource for protocol amendment discussions with the sponsor or CRO. A site that can show that 35% of its screen failures in the prior quarter were due to a single exclusion criterion — with specific counts, not anecdote — is in a much stronger position to support a targeted amendment request than a site that can say only that enrollment is behind target. Capturing screen failure reason codes accurately and consistently is the prerequisite for that conversation.
Realistic expectations for screen failure rate reduction
Structured pre-screening with EHR-based eligibility filtering will not eliminate screen failures. Some failures are unavoidable — criteria that require live assessment cannot be pre-screened, patient health status changes between pre-screening and the screen visit, and some patients who pass all EHR-confirmable criteria will fail on a screening-specific assessment. A site that reduces its protocol-ineligible screen failure rate by 50–60% through better pre-screening has achieved a meaningful operational improvement even if the overall screen failure rate remains above 20%.
The benchmark to target is not a zero screen failure rate. It is a screen failure distribution where the protocol-ineligible category (failures that should have been preventable by better pre-screening) accounts for a small minority of total failures, and the majority of failures occur due to screening-specific assessments that genuinely could not have been evaluated before the screen visit. That distribution represents a site operating at the practical efficiency frontier for its protocol and patient population.
Getting there requires two things: accurate screen failure classification in the CTMS (so you know what you're trying to reduce) and a pre-screening workflow that systematically applies EHR-confirmable criteria before the outreach call rather than after. Neither requires new technology if the team has the time to implement it manually. But the time investment scales with trial volume — which is why sites running more than two or three concurrent active protocols increasingly find that automated EHR querying is the only way to maintain pre-screening rigor without adding headcount.
A worked example: rheumatology trial at a mid-size academic center
To illustrate how these principles interact in practice, consider a Phase III biologic trial in rheumatoid arthritis at a mid-size academic rheumatology practice. The protocol requires: confirmed RA diagnosis (ICD-10 M05.x or M06.x), moderate-to-severe disease activity (DAS28 ≥3.2), inadequate response to at least one conventional synthetic DMARD, and no prior exposure to any biologic or JAK inhibitor. The exclusion list includes active or latent tuberculosis (positive QuantiFERON or T-SPOT within 12 months, or clinical evidence of active TB), recent serious infection within 6 months, and current use of more than 10 mg/day oral prednisone equivalent.
The site had a 44% screen failure rate in the previous quarter across this trial. A retrospective classification of those failures revealed: 18 percentage points were due to undisclosed prior biologic use (patients on biosimilar adalimumab prescribed by an out-of-network rheumatologist, not reflected in the institutional EHR), 9 percentage points were due to QuantiFERON results drawn at pre-screening that came back positive, 8 percentage points were protocol-ineligible for reasons identifiable from EHR data (DAS28 documentation not meeting threshold at most recent recorded assessment), and the remaining 9 percentage points were patient-withdrawn after consent.
The classification reveals that 18 of the 44 percentage points — the prior biologic exposure failures — were preventable at the outreach call. The outreach script had no question about prior biologic therapy prescribed by outside providers. Adding a single question — "Have you ever been treated with a biologic injection or infusion for your rheumatoid arthritis, including at any other practice or hospital?" — to the pre-screen call would have identified those patients before the screen visit was scheduled. The 8 percentage points of DAS28-related failures were addressable through better EHR pre-screening: the protocol's disease activity requirement could have been evaluated against documented DAS28 scores in the EHR (recorded at prior rheumatology visits and present as structured data in the FHIR Observation record). The 9 percentage points of QuantiFERON positives and the 9 percentage points of patient withdrawals are largely not preventable at the pre-screening stage.
By that analysis, the site's addressable screen failure rate — the fraction genuinely reducible through pre-screening workflow changes — was approximately 26 of the 44 percentage points. Implementing the outreach script change and adding DAS28 EHR pre-screening would have been expected to bring the failure rate toward 18–20%, which is within the range of what a Phase III RA trial should expect given the screening-specific assessments that cannot be pre-evaluated.
Integrating pre-screening data back into the CTMS
One operational gap that undermines pre-screening workflow efficiency at many sites is the disconnect between the pre-screening record and the CTMS. Pre-screening activity — candidate identification, outreach calls, pre-screen questionnaire results — is often tracked in a separate spreadsheet or informal log rather than in the CTMS itself. When a patient progresses to the formal screen visit, the coordinator re-enters information that was already captured during pre-screening. When a patient fails pre-screening and is not taken to a screen visit, there is frequently no CTMS record at all.
The consequence is that the site's pre-screening funnel is invisible to the sponsor and CRO. A sponsor reviewing a site's CTMS data sees consented subjects and screen failures; they do not see the 60 patients who were contacted, found to be ineligible at the outreach call, and appropriately never brought to a screen visit. That invisible pre-screening work is the primary driver of the site's screen failure rate improvement, but it is not documented in a way that demonstrates the workflow to the sponsor.
Sites that capture pre-screening activity in the CTMS — whether through a formal pre-screening module in Medidata Rave or Veeva Vault Clinical, or through a structured log that feeds into the CTMS — have two advantages. First, the coordinator has a single source of record for candidate status rather than a CTMS and a parallel spreadsheet. Second, the pre-screening funnel data is available for sponsor review and for the site's own retrospective analysis of where the outreach-to-consent conversion is breaking down. ICH E6(R2) GCP guidance does not require pre-screening activity to be logged in the CTMS, but sites that maintain that log are better positioned to demonstrate the rigor of their screening process at monitoring visits and in protocol deviation discussions.
The CTMS integration question is worth raising with the sponsor's clinical operations team before or shortly after the SIV. Some sponsors have specific expectations about how pre-screening activity should be documented; others leave it to site discretion. Knowing the sponsor's preference before the enrollment period starts avoids a documentation correction later.