All articles
Recruitment StrategyOctober 27, 2026·3 min read

Rebuilding a Pre-Screening Script That Actually Filters

Most pre-screening scripts are protocol eligibility lists in disguise. Here's how to reorder, rephrase, and revise them so calls get shorter and screen failures drop.

By Trialflow Team

Most pre-screening scripts are built backwards. Someone copies the inclusion/exclusion list out of the protocol, numbers it, and hands it to a coordinator. The result is a call that sounds like an interrogation, takes eleven minutes, and still misses the one disqualifier that shows up at visit one.

A good pre-screening script is a decision tool, not a questionnaire. Here's how to rebuild one.

Lead with the fastest disqualifiers

Order questions by how many people they eliminate per second spent asking. Age, geography, and a hard diagnosis requirement usually knock out the largest share of callers and take under thirty seconds. Washout periods, prior biologic exposure, and nuanced lab history belong later, because you only need them for the callers who survive the first filter.

Sites that reorder an existing script this way commonly cut average call time substantially without changing a single question's wording. You're asking the same things, just not wasting four minutes on someone who lives three hours away.

Translate protocol language into plain questions

"Documented history of moderate-to-severe plaque psoriasis involving ≥10% BSA" is not a question. "About how much of your body does your psoriasis cover — can you cover it with one hand, or is it bigger than that?" is.

For every eligibility criterion, write the version you would actually say out loud to a stranger. Then test it on a coworker who hasn't read the protocol. If they ask a clarifying question, your phrasing is wrong.

Two specific traps:

  • Dosage and frequency questions. Most patients don't know milligrams. Ask about pill color, how many times a day, and who prescribed it, then reconcile against records later.
  • Yes/no questions on symptoms. Patients under-report when asked "do you have any trouble sleeping?" and over-report when asked "how many nights a week is your sleep disrupted?" Pick the framing that matches whether you'd rather over- or under-capture at this stage.

Build in branching, not just skip logic

Scripts fail when a caller gives an answer the script didn't anticipate. Add a short decision note under any question where the answer is likely to be "sort of." For example: if someone reports a condition that might be exclusionary, the note should say what to do — collect details and flag for PI review, or disqualify outright. Coordinators should never have to guess whether a borderline answer ends the call.

Make the first ninety seconds about them

Open by confirming what they inquired about and why. "You reached out about the migraine study — tell me a little about what you're dealing with right now." You learn more about likely eligibility from thirty seconds of open-ended talk than from the first five closed questions, and the caller stops feeling screened.

Close with a scheduled next step, always

End every qualifying call with a specific appointment, a confirmation message, and a plain-language summary of what to bring and what to expect. Ending with "someone will call you back" is where most pre-screening value evaporates.

Revise against actual screen failure reasons

Once a month, pull the reasons candidates failed at the screening visit. Any reason that appears repeatedly and could have been caught by phone belongs in the script as a new question. Any question that has never once disqualified anyone should be cut. A script that isn't revised monthly during active enrollment is just documentation.

Enrolling studies shouldn't be this hard

Trialflow gives research sites one platform for lead management, AI trial matching, and recruitment analytics.

Request a Demo