Preliminary Eligibility-Information Collection Best Practices

Six Best Practices for Site-Approved Preliminary Information Collection

• Build the preliminary checklist from the site-approved workflow, not from experience: Authorized site personnel define the preliminary questions and documentation fields for each study. Consent2Randomize uses that site-approved checklist to collect candidate-reported information consistently and does not interpret the protocol or substitute prior study experience for the site's instructions.
• Distinguish preliminary information collection from formal site assessment: Candidate-reported information can be collected before formal screening when the research site has approved the questions and workflow. Clinical interpretation, protocol questions, laboratory or imaging review, and all eligibility decisions remain with authorized site personnel and are escalated accordingly.
• Document candidate-reported responses in real time: The team records responses, unanswered questions, contact status, and follow-up needs during the preliminary contact. If a contact is interrupted or rescheduled, the record shows what was collected and what remains unresolved for the next authorized step.
• Apply consistent workflow statuses to every record: A standard set of workflow statuses keeps records organized and supports the correct next action. Site-approved statuses can include preliminary intake completed, information incomplete, clinical or protocol question escalated, candidate requested no further contact, unreachable after the approved attempt sequence, and record prepared for site review.
• Review preliminary workflow data against site feedback: Authorized site personnel can compare formal screening feedback with the preliminary questions and documentation process. That review identifies missing fields, unclear questions, or escalation gaps that the site may choose to address in its approved workflow.
• Maintain a protocol amendment log and update checklists after site approval: When an amendment changes the site's preliminary workflow, authorized site personnel approve the revised questions and instructions. Consent2Randomize then applies the current approved version and documents which version was used for each candidate record.

Common Preliminary Information-Collection Errors and Their Impact

Common operational errors at the preliminary stage include using a generic or outdated checklist, failing to document candidate-reported responses during the contact, omitting unresolved questions from the record, and leaving scheduling information or escalation ownership unclear. These gaps can require additional site review or candidate re-contact before the next step is clear.

A second category of error is scope overreach. Preliminary support should not interpret candidate-reported medical information, resolve protocol ambiguity, or evaluate findings that require clinical judgment, diagnostic testing, laboratory results, or investigator review. Consent2Randomize documents the information provided and escalates those questions; authorized site personnel interpret the information and determine eligibility.

For a full breakdown of documentation, scope, and workflow errors at the preliminary stage, see common prescreening mistakes in clinical research. For the broader operational costs associated with enrollment delays, see the cost of enrollment delays.

Building a Consistent Preliminary Information-Collection Process

A consistent preliminary review process requires three structural elements: a site-approved checklist that defines what information is collected, a documentation standard that captures candidate-reported responses and unresolved items in a format usable by the coordinator team, and an escalation process that routes clinical or protocol questions to authorized site personnel.

These elements create a repeatable operational record across contacts and make workflow gaps easier to identify. Site feedback can then guide updates to questions, documentation fields, statuses, and handoff requirements while all interpretation and eligibility decisions remain with the research site.

For guidance on the complete prescreening workflow that surrounds eligibility review, see prescreening workflows for research sites. For the intake foundation that feeds the eligibility review process, see referral intake best practices for research sites.