Your Screen Failures Are Your Best Recruitment Pool

Most sites treat a screen failure as a dead end. The chart gets closed, the reason code gets logged for the sponsor, and the person disappears. That's a waste of the most expensive thing your site does: finding, consenting, and fully characterizing a motivated human being.

Someone who screen failed has already proven three things you normally spend weeks trying to establish. They showed up. They consented. And you now have lab values, vitals, med lists, and diagnostic history that most of your database lacks. That's a better-qualified prospect than anyone who ever filled out a web form.

Start with the reason code

Not every screen failure is reusable. Sort them into three buckets at the moment of failure, not months later.

• Permanently ineligible. A structural exclusion that won't change — prior therapy they can't undo, a surgical history, a genetic marker. These people may still qualify for a different indication, but not for a re-screen.
• Temporarily ineligible. Washout not complete, A1c or LDL just outside window, recent infection, BMI near the cutoff, a lab that was drawn on a bad day. These are your highest-value group. Many of them become eligible in 30 to 90 days.
• Protocol-specific. They failed this protocol's narrow criteria but are otherwise a healthy, engaged patient with the condition. They're a strong candidate for the next study in that therapeutic area.

Sites commonly find that the temporary and protocol-specific buckets together make up the majority of failures. If your database only records "screen fail — exclusion criteria," you've thrown that distinction away.

Capture a re-contact date, not just a reason

When you code the failure, add two fields: why and when to try again. If the washout ends March 14, the record should say March 14. If the value was 0.2 outside the window, note that it was borderline and worth a repeat draw in a future study.

This takes the coordinator about ninety seconds at the end of a failed visit, while the details are fresh. Reconstructing it later from source documents takes twenty minutes and usually doesn't happen.

Get consent for future contact

You need explicit, documented permission to keep someone in a re-contact pool after a study ends. Build this into your site's general research registry consent or a future-contact authorization signed at screening, cleared through your IRB. Don't rely on the protocol consent — it typically covers only that study.

Tell the participant plainly at the failure visit: "You didn't qualify for this one, but we run studies in this area regularly. Can we keep your information and call you when something fits?" Most people say yes. They came in because they wanted help.

Close the loop at the visit itself

The worst version of a screen failure is a voicemail two days later saying "you didn't qualify" with no next step. That person will not answer when you call about the next study.

Instead:

1. Explain the specific reason in plain terms.
2. Say whether it's likely to change over time.
3. Name a rough timeframe for when you might call again.
4. Give them something useful — a referral, a copy of their labs, a note for their physician.

Work the pool when a study opens

When a new protocol lands, query your failure pool before you spend a dollar on advertising. Filter by indication, by reason code, by date. In most site datasets, a well-maintained failure pool will produce consented candidates faster and cheaper than any external channel, because the pre-screen work is already done.

The screen failure isn't a loss. It's an unbilled asset sitting in your database waiting for the right protocol.