Pre-screening is not research

This is the single most important principle in this lesson, and I want to be precise about it because the practical consequences are significant.

Pre-screening — including telephone pre-screening — is an activity that occurs before a person becomes a research participant. Its purpose is to determine whether a formal screening visit is warranted. It is a triage function. The coordinator asks a limited set of questions to assess whether the caller meets the basic eligibility criteria, provides enough information about the study for the caller to decide whether they want to learn more, and — if the caller appears potentially eligible and interested — schedules a screening visit where the actual research process begins.

Formal screening, by contrast, is a research procedure. It occurs after informed consent has been obtained. It involves protocol-specified assessments — laboratory tests, physical examinations, ECGs, questionnaires — that generate research data. A participant who undergoes screening is a research participant, even if they ultimately fail to meet eligibility criteria.

The distinction matters because it determines what regulatory protections apply. Research procedures require prior informed consent per 21 CFR 50 and ICH E6(R3) Annex 1, Section 2.8. Pre-screening activities, because they are not research, do not require formal consent. But this freedom has a boundary: the moment you begin conducting activities that look, feel, or function like research — collecting medical data, providing clinical assessments, disclosing detailed risk information that presumes enrollment — you have crossed from pre-screening into consent territory without a signed consent form.

The FDA has addressed this distinction directly. The agency's 1998 Guidance for Industry on Recruiting Study Subjects states that the use of advertising and other recruitment methods to identify potential research subjects is not, in itself, a research activity. The IRB still reviews and approves recruitment materials and scripts — that is the M1-L2 requirement you already learned — but the act of using those materials to identify candidates is a pre-research activity.

This has a practical implication that many new coordinators miss. Because pre-screening is not research, the information gathered during a pre-screening call is not research data. It does not go into a case report form. It is not source data. It is operational information — documented in the pre-screening log (covered in Lesson 4 of this module) — that supports the recruitment process.

But here is where I have seen coordinators get into trouble: just because pre-screening is not research does not mean it is unregulated. The pre-screening script must be IRB-approved. The questions asked and information shared must fall within the scope the IRB approved. And the coordinator's conduct during the call must not cross into informed consent territory. The fact that something is "not research" does not make it a free zone. It makes it a zone with different, specific rules.

Building the pre-screening script

A well-constructed pre-screening script is not a casual outline. It is a structured document — IRB-approved, version-controlled, and followed consistently — that accomplishes four things in a defined sequence. Each component serves a specific purpose, and the order matters.

Component 1: Study introduction. Before you ask a single eligibility question, the caller needs to know what they are being asked about. The introduction identifies the research site, names the condition being studied, describes the purpose of the study in general terms, and explains what the phone call is for. This is not the consent discussion. It is a two- to three-sentence orientation that gives the caller context for the questions that follow.

Component 2: Key eligibility questions, ordered by most exclusionary first. This is the operational heart of the script. You ask a series of questions designed to identify clear exclusions as early as possible. If a caller does not have the target diagnosis, there is no reason to ask about their medication history, their lab values, or their willingness to attend biweekly visits. The ordering principle is the same one you applied to chart review in Lesson 1 — most exclusionary first — but adapted for a conversation with a non-medical person.

Component 3: Basic study information. For callers who appear potentially eligible, you provide enough information for them to decide whether they want to learn more at a screening visit. This includes the general nature of the study (what it involves), the approximate time commitment (number and duration of visits), and any major logistical requirements (travel, fasting, medication changes). This is not a summary of the informed consent document. It is enough information to support a decision about whether to come in.

Component 4: Next-steps language. The call closes with clear direction. If the caller appears potentially eligible: explain what happens next (screening visit scheduling, what to expect, what to bring). If the caller is clearly ineligible: thank them for their interest, explain in general terms why the study is not a match, and — when appropriate — suggest they ask their physician about other research opportunities.

The script in practice

Let me walk through what each component sounds like in practice — not as a verbatim script (your IRB will approve site-specific language), but as a structural model that illustrates the principles.

The introduction might sound like this: "Thank you for calling. My name is [coordinator name], and I am a clinical research coordinator at [institution]. We are currently conducting a research study for people with Type 2 diabetes. The purpose of this call is to ask you a few questions to see if the study might be a good fit for you. This is not a commitment to participate, and you are free to end this call at any time. May I ask you some questions?"

Notice what this accomplishes. It identifies the caller's contact as a research inquiry. It names the condition. It sets expectations for the call's purpose. It establishes voluntariness. And it asks permission to proceed — a small but important gesture that models the respect for autonomy that characterizes ethical research conduct.

The eligibility questions proceed from most exclusionary to least. For a Type 2 diabetes trial, the sequence might be:

There is an art to framing these questions for a lay audience. Protocol eligibility criteria are written in clinical language — "eGFR greater than 30 mL/min/1.73m2" or "HbA1c between 7.0% and 10.5%." You cannot ask a caller for their eGFR. Most people do not know it. And asking them to report specific laboratory values converts a pre-screening call into a data collection exercise.

Instead, translate clinical criteria into questions a non-medical person can answer. "Have you been told you have kidney problems?" captures the intent of the eGFR criterion well enough for pre-screening purposes. The precise value will be assessed at the screening visit with actual laboratory testing. Pre-screening is a filter, not a definitive assessment.

But be careful not to translate so loosely that the question loses its screening value. "Do you have any health problems?" is too broad to exclude anyone. "Have you been diagnosed with kidney disease or been told your kidneys are not working well?" is specific enough to capture the most clearly ineligible callers while remaining accessible.

Where the boundary falls: scope versus consent territory

The most common mistake in telephone pre-screening is not asking the wrong eligibility question. It is sharing too much information in response to the caller's questions. A caller who appears potentially eligible and interested will, naturally, want to know more. And a coordinator who is enthusiastic about enrollment will, naturally, want to help.

But there are categories of information that belong exclusively in the informed consent discussion — a discussion that occurs in person (or through the protocol's approved remote consent process), with the consent document in hand, after the caller has had time to review it. Sharing this information on the phone does not merely jump ahead in the process. It raises a regulatory concern: if the caller makes a decision to participate based on information conveyed informally over the phone, without the structured protections of the informed consent process, the voluntariness and comprehension requirements of 21 CFR 50.20 may be compromised.

Handling common telephone challenges

Every coordinator who has staffed a pre-screening phone line has encountered these situations. They are not edge cases. They are the standard repertoire of challenges, and your response to each one reflects the quality of your training and the structure of your script.

Challenge 1: "I want to sign up right now."

The eager caller. The one who has already decided, before the screening visit, before the consent discussion, before a single eligibility assessment. This enthusiasm is understandable — and it must be managed carefully.

The appropriate response is not "Great, you are enrolled!" and it is not a lengthy explanation of why they cannot enroll yet. It is a warm, clear redirect: "I am glad you are interested. Before anyone participates in a research study, there is an important process where you learn about the study in detail and have a chance to ask questions. That happens at a screening visit. I would like to schedule that visit for you — can we find a time that works?"

What you are doing is honoring the caller's enthusiasm while ensuring the regulatory process is preserved. Enrollment requires informed consent. Informed consent requires the structured consent process. The consent process occurs at the site, not on the phone. This is not a bureaucratic obstacle — it is a participant protection.

Challenge 2: "What are the side effects? Is this drug safe?"

This is the most common boundary question, and it is the one that tempts coordinators most strongly. The caller is expressing a legitimate concern. You have the information. It feels unhelpful — even evasive — to defer the answer.

But defer you must. Risk disclosure is the cornerstone of informed consent. Per 21 CFR 50.25(a)(2), the consent document must include "a description of the risks or discomforts to the participant which are reasonably foreseeable." Sharing those risks informally on the phone, without the consent document, without time for reflection, without the opportunity for questions — that is not informed consent. It is a partial, uncontrolled disclosure that may distort the caller's understanding.

The response: "That is an important question, and it is exactly the kind of question you will be able to discuss in detail at the screening visit. You will receive a document that explains the study's potential risks and benefits, and you will have time to review it and ask the study team any questions before deciding whether to participate."

Challenge 3: "My doctor told me to call, so I am definitely eligible."

Physician referrals are valuable. But a physician's recommendation is not an eligibility determination. The referring physician may not have reviewed all of the protocol's inclusion and exclusion criteria. They may not know about the concomitant medication restrictions, the laboratory value thresholds, or the washout period requirements. A referral means someone with clinical judgment believes the patient might be appropriate. It does not replace systematic eligibility assessment.

The response: "It is great that your doctor thought you might be a good fit. I do need to ask a few questions to make sure the study matches your specific situation. Some of the study's eligibility requirements are very specific, and we want to make sure we are not asking you to come in for a visit if there is something we can identify now that would not work."

This validates the physician's referral while making clear that the coordinator's role — asking the eligibility questions — is not redundant.

Challenge 4: Ambiguous eligibility.

The caller answers a question and the answer is not clearly yes or clearly no. "I think I used to take insulin, but I am not sure if I still do." "My doctor said something about my kidneys, but I do not know the details." "I was in a study a few years ago — does that count?"

This is where the distinction between pre-screening and screening earns its keep. Pre-screening is a filter, not a definitive assessment. You do not need to resolve ambiguity on the phone. You need to decide whether the ambiguity warrants a screening visit or whether the caller is clearly ineligible despite the uncertainty.

The principle: when in doubt, invite to screen. The screening visit is where precise assessments happen — laboratory tests, medical record review, investigator evaluation. A caller who "might" have kidney disease and "might" be on a disqualifying medication is a candidate for the screening visit, where those questions will be answered definitively. The cost of an unnecessary screening visit is real but modest. The cost of excluding a genuinely eligible participant because of phone-based ambiguity is a missed enrollment and a disservice to the research.

Documenting telephone pre-screening contacts

Every telephone pre-screening contact — whether the caller qualifies, does not qualify, or falls into the ambiguous category — must be documented. This documentation serves three purposes: it populates the pre-screening log (the subject of Lesson 4 in this module), it supports recruitment funnel metrics, and it creates an operational record of the site's recruitment activity that sponsors and monitors will review.

What to document for each call is straightforward.

A critical documentation boundary carries forward from Lesson 1: the pre-screening log is an operational document, not a research record. The information recorded should support the recruitment process — who called, when, what the outcome was, why they were excluded or invited to screen. It should not contain detailed clinical information that the caller shared during the conversation.

If a caller mentions that her HbA1c was 8.2% at her last visit and that she takes metformin and a sulfonylurea, you do not record those specific values and medications in the pre-screening log. You record that the caller appeared potentially eligible based on self-reported information and that a screening visit was scheduled. The clinical details will be assessed formally — with laboratory testing and medical record review — at the screening visit.

This discipline serves two purposes. It prevents the pre-screening log from becoming a de facto research database before consent has been obtained. And it protects the site from a situation where pre-screening documentation is later compared against screening data and found to be inconsistent — a discrepancy that raises questions during monitoring visits but one that is entirely avoidable by not recording clinical data you were never supposed to collect.

Key takeaways

Telephone pre-screening is a skill that looks simple and is not. The coordinator must simultaneously manage the conversation's flow, apply the eligibility criteria, respect the scope boundaries, handle the caller's questions, and document the outcome — all within a call that may last five minutes.

Know the line. Pre-screening is not research. But the line between pre-screening and consent territory is not drawn in the middle of an empty field — it runs through the center of a conversation where a real person is asking real questions about something that matters to them. Know where the line is. Stay on the right side of it. And do so without making the caller feel dismissed.

Script structure matters. Study introduction, eligibility questions ordered by most exclusionary first, basic study information, next-steps language. This sequence is not arbitrary. It maximizes efficiency (ineligible callers are identified early), manages scope (information is shared in the right order), and models the respect for process that characterizes high-quality research.

Defer with warmth, not rigidity. When callers ask questions that belong in the consent discussion, redirect them — but do so by explaining that they will get a thorough answer in a better setting, not by citing regulations. "That is an important question, and you will have the chance to discuss it in detail at your screening visit" is a complete and respectful response.

Document operationally, not clinically. The pre-screening log captures who called, when, from what source, what the outcome was, and why. It does not capture the caller's laboratory values, medication list, or medical history. That boundary keeps the log clean and the site compliant.

When in doubt, invite to screen. Pre-screening excludes the clearly ineligible. It does not definitively confirm eligibility — that is the screening visit's purpose. If a caller's answers leave you uncertain, the default should be to schedule the visit and let the formal assessment resolve the question.

In the next lesson, we move from direct conversation to systematic identification — using electronic health record queries and research registries to find candidates at scale.

Pre-screening is not research

This is the single most important principle in this lesson, and I want to be precise about it because the practical consequences are significant.

Pre-screening — including telephone pre-screening — is an activity that occurs before a person becomes a research participant. Its purpose is to determine whether a formal screening visit is warranted. It is a triage function. The coordinator asks a limited set of questions to assess whether the caller meets the basic eligibility criteria, provides enough information about the study for the caller to decide whether they want to learn more, and — if the caller appears potentially eligible and interested — schedules a screening visit where the actual research process begins.

Formal screening, by contrast, is a research procedure. It occurs after informed consent has been obtained. It involves protocol-specified assessments — laboratory tests, physical examinations, ECGs, questionnaires — that generate research data. A participant who undergoes screening is a research participant, even if they ultimately fail to meet eligibility criteria.

The distinction matters because it determines what regulatory protections apply. Research procedures require prior informed consent per 21 CFR 50 and ICH E6(R3) Annex 1, Section 2.8. Pre-screening activities, because they are not research, do not require formal consent. But this freedom has a boundary: the moment you begin conducting activities that look, feel, or function like research — collecting medical data, providing clinical assessments, disclosing detailed risk information that presumes enrollment — you have crossed from pre-screening into consent territory without a signed consent form.

The FDA has addressed this distinction directly. The agency's 1998 Guidance for Industry on Recruiting Study Subjects states that the use of advertising and other recruitment methods to identify potential research subjects is not, in itself, a research activity. The IRB still reviews and approves recruitment materials and scripts — that is the M1-L2 requirement you already learned — but the act of using those materials to identify candidates is a pre-research activity.

This has a practical implication that many new coordinators miss. Because pre-screening is not research, the information gathered during a pre-screening call is not research data. It does not go into a case report form. It is not source data. It is operational information — documented in the pre-screening log (covered in Lesson 4 of this module) — that supports the recruitment process.

But here is where I have seen coordinators get into trouble: just because pre-screening is not research does not mean it is unregulated. The pre-screening script must be IRB-approved. The questions asked and information shared must fall within the scope the IRB approved. And the coordinator's conduct during the call must not cross into informed consent territory. The fact that something is "not research" does not make it a free zone. It makes it a zone with different, specific rules.

Building the pre-screening script

A well-constructed pre-screening script is not a casual outline. It is a structured document — IRB-approved, version-controlled, and followed consistently — that accomplishes four things in a defined sequence. Each component serves a specific purpose, and the order matters.

Component 1: Study introduction. Before you ask a single eligibility question, the caller needs to know what they are being asked about. The introduction identifies the research site, names the condition being studied, describes the purpose of the study in general terms, and explains what the phone call is for. This is not the consent discussion. It is a two- to three-sentence orientation that gives the caller context for the questions that follow.

Component 2: Key eligibility questions, ordered by most exclusionary first. This is the operational heart of the script. You ask a series of questions designed to identify clear exclusions as early as possible. If a caller does not have the target diagnosis, there is no reason to ask about their medication history, their lab values, or their willingness to attend biweekly visits. The ordering principle is the same one you applied to chart review in Lesson 1 — most exclusionary first — but adapted for a conversation with a non-medical person.

Component 3: Basic study information. For callers who appear potentially eligible, you provide enough information for them to decide whether they want to learn more at a screening visit. This includes the general nature of the study (what it involves), the approximate time commitment (number and duration of visits), and any major logistical requirements (travel, fasting, medication changes). This is not a summary of the informed consent document. It is enough information to support a decision about whether to come in.

Component 4: Next-steps language. The call closes with clear direction. If the caller appears potentially eligible: explain what happens next (screening visit scheduling, what to expect, what to bring). If the caller is clearly ineligible: thank them for their interest, explain in general terms why the study is not a match, and — when appropriate — suggest they ask their physician about other research opportunities.

The script in practice

Let me walk through what each component sounds like in practice — not as a verbatim script (your IRB will approve site-specific language), but as a structural model that illustrates the principles.

The introduction might sound like this: "Thank you for calling. My name is [coordinator name], and I am a clinical research coordinator at [institution]. We are currently conducting a research study for people with Type 2 diabetes. The purpose of this call is to ask you a few questions to see if the study might be a good fit for you. This is not a commitment to participate, and you are free to end this call at any time. May I ask you some questions?"

Notice what this accomplishes. It identifies the caller's contact as a research inquiry. It names the condition. It sets expectations for the call's purpose. It establishes voluntariness. And it asks permission to proceed — a small but important gesture that models the respect for autonomy that characterizes ethical research conduct.

The eligibility questions proceed from most exclusionary to least. For a Type 2 diabetes trial, the sequence might be:

There is an art to framing these questions for a lay audience. Protocol eligibility criteria are written in clinical language — "eGFR greater than 30 mL/min/1.73m2" or "HbA1c between 7.0% and 10.5%." You cannot ask a caller for their eGFR. Most people do not know it. And asking them to report specific laboratory values converts a pre-screening call into a data collection exercise.

Instead, translate clinical criteria into questions a non-medical person can answer. "Have you been told you have kidney problems?" captures the intent of the eGFR criterion well enough for pre-screening purposes. The precise value will be assessed at the screening visit with actual laboratory testing. Pre-screening is a filter, not a definitive assessment.

But be careful not to translate so loosely that the question loses its screening value. "Do you have any health problems?" is too broad to exclude anyone. "Have you been diagnosed with kidney disease or been told your kidneys are not working well?" is specific enough to capture the most clearly ineligible callers while remaining accessible.

Where the boundary falls: scope versus consent territory

The most common mistake in telephone pre-screening is not asking the wrong eligibility question. It is sharing too much information in response to the caller's questions. A caller who appears potentially eligible and interested will, naturally, want to know more. And a coordinator who is enthusiastic about enrollment will, naturally, want to help.

But there are categories of information that belong exclusively in the informed consent discussion — a discussion that occurs in person (or through the protocol's approved remote consent process), with the consent document in hand, after the caller has had time to review it. Sharing this information on the phone does not merely jump ahead in the process. It raises a regulatory concern: if the caller makes a decision to participate based on information conveyed informally over the phone, without the structured protections of the informed consent process, the voluntariness and comprehension requirements of 21 CFR 50.20 may be compromised.

Handling common telephone challenges

Every coordinator who has staffed a pre-screening phone line has encountered these situations. They are not edge cases. They are the standard repertoire of challenges, and your response to each one reflects the quality of your training and the structure of your script.

Challenge 1: "I want to sign up right now."

The eager caller. The one who has already decided, before the screening visit, before the consent discussion, before a single eligibility assessment. This enthusiasm is understandable — and it must be managed carefully.

The appropriate response is not "Great, you are enrolled!" and it is not a lengthy explanation of why they cannot enroll yet. It is a warm, clear redirect: "I am glad you are interested. Before anyone participates in a research study, there is an important process where you learn about the study in detail and have a chance to ask questions. That happens at a screening visit. I would like to schedule that visit for you — can we find a time that works?"

What you are doing is honoring the caller's enthusiasm while ensuring the regulatory process is preserved. Enrollment requires informed consent. Informed consent requires the structured consent process. The consent process occurs at the site, not on the phone. This is not a bureaucratic obstacle — it is a participant protection.

Challenge 2: "What are the side effects? Is this drug safe?"

This is the most common boundary question, and it is the one that tempts coordinators most strongly. The caller is expressing a legitimate concern. You have the information. It feels unhelpful — even evasive — to defer the answer.

But defer you must. Risk disclosure is the cornerstone of informed consent. Per 21 CFR 50.25(a)(2), the consent document must include "a description of the risks or discomforts to the participant which are reasonably foreseeable." Sharing those risks informally on the phone, without the consent document, without time for reflection, without the opportunity for questions — that is not informed consent. It is a partial, uncontrolled disclosure that may distort the caller's understanding.

The response: "That is an important question, and it is exactly the kind of question you will be able to discuss in detail at the screening visit. You will receive a document that explains the study's potential risks and benefits, and you will have time to review it and ask the study team any questions before deciding whether to participate."

Challenge 3: "My doctor told me to call, so I am definitely eligible."

Physician referrals are valuable. But a physician's recommendation is not an eligibility determination. The referring physician may not have reviewed all of the protocol's inclusion and exclusion criteria. They may not know about the concomitant medication restrictions, the laboratory value thresholds, or the washout period requirements. A referral means someone with clinical judgment believes the patient might be appropriate. It does not replace systematic eligibility assessment.

The response: "It is great that your doctor thought you might be a good fit. I do need to ask a few questions to make sure the study matches your specific situation. Some of the study's eligibility requirements are very specific, and we want to make sure we are not asking you to come in for a visit if there is something we can identify now that would not work."

This validates the physician's referral while making clear that the coordinator's role — asking the eligibility questions — is not redundant.

Challenge 4: Ambiguous eligibility.

The caller answers a question and the answer is not clearly yes or clearly no. "I think I used to take insulin, but I am not sure if I still do." "My doctor said something about my kidneys, but I do not know the details." "I was in a study a few years ago — does that count?"

This is where the distinction between pre-screening and screening earns its keep. Pre-screening is a filter, not a definitive assessment. You do not need to resolve ambiguity on the phone. You need to decide whether the ambiguity warrants a screening visit or whether the caller is clearly ineligible despite the uncertainty.

The principle: when in doubt, invite to screen. The screening visit is where precise assessments happen — laboratory tests, medical record review, investigator evaluation. A caller who "might" have kidney disease and "might" be on a disqualifying medication is a candidate for the screening visit, where those questions will be answered definitively. The cost of an unnecessary screening visit is real but modest. The cost of excluding a genuinely eligible participant because of phone-based ambiguity is a missed enrollment and a disservice to the research.

Documenting telephone pre-screening contacts

Every telephone pre-screening contact — whether the caller qualifies, does not qualify, or falls into the ambiguous category — must be documented. This documentation serves three purposes: it populates the pre-screening log (the subject of Lesson 4 in this module), it supports recruitment funnel metrics, and it creates an operational record of the site's recruitment activity that sponsors and monitors will review.

What to document for each call is straightforward.

A critical documentation boundary carries forward from Lesson 1: the pre-screening log is an operational document, not a research record. The information recorded should support the recruitment process — who called, when, what the outcome was, why they were excluded or invited to screen. It should not contain detailed clinical information that the caller shared during the conversation.

If a caller mentions that her HbA1c was 8.2% at her last visit and that she takes metformin and a sulfonylurea, you do not record those specific values and medications in the pre-screening log. You record that the caller appeared potentially eligible based on self-reported information and that a screening visit was scheduled. The clinical details will be assessed formally — with laboratory testing and medical record review — at the screening visit.

This discipline serves two purposes. It prevents the pre-screening log from becoming a de facto research database before consent has been obtained. And it protects the site from a situation where pre-screening documentation is later compared against screening data and found to be inconsistent — a discrepancy that raises questions during monitoring visits but one that is entirely avoidable by not recording clinical data you were never supposed to collect.

Key takeaways

Telephone pre-screening is a skill that looks simple and is not. The coordinator must simultaneously manage the conversation's flow, apply the eligibility criteria, respect the scope boundaries, handle the caller's questions, and document the outcome — all within a call that may last five minutes.

Know the line. Pre-screening is not research. But the line between pre-screening and consent territory is not drawn in the middle of an empty field — it runs through the center of a conversation where a real person is asking real questions about something that matters to them. Know where the line is. Stay on the right side of it. And do so without making the caller feel dismissed.

Script structure matters. Study introduction, eligibility questions ordered by most exclusionary first, basic study information, next-steps language. This sequence is not arbitrary. It maximizes efficiency (ineligible callers are identified early), manages scope (information is shared in the right order), and models the respect for process that characterizes high-quality research.

Defer with warmth, not rigidity. When callers ask questions that belong in the consent discussion, redirect them — but do so by explaining that they will get a thorough answer in a better setting, not by citing regulations. "That is an important question, and you will have the chance to discuss it in detail at your screening visit" is a complete and respectful response.

Document operationally, not clinically. The pre-screening log captures who called, when, from what source, what the outcome was, and why. It does not capture the caller's laboratory values, medication list, or medical history. That boundary keeps the log clean and the site compliant.

When in doubt, invite to screen. Pre-screening excludes the clearly ineligible. It does not definitively confirm eligibility — that is the screening visit's purpose. If a caller's answers leave you uncertain, the default should be to schedule the visit and let the formal assessment resolve the question.

In the next lesson, we move from direct conversation to systematic identification — using electronic health record queries and research registries to find candidates at scale.