The Startup Bottleneck Hiding Between Site Activation and First Patient In

Why source preparation deserves attention now

The Tufts CSDD and CRIO study was based on a global survey of 209 investigative site professionals conducted from September through December 2025. Respondents described the documents, roles, systems, and effort involved in translating protocol requirements into practical data-collection tools. More than 80 percent of respondents working on high-complexity studies reported spending at least 21 hours on source preparation. Sites also reported waiting an average of nearly six weeks, and in some cases as long as 20 weeks, to receive the inputs needed to complete the work. ([appliedclinicaltrialsonline.com](https://www.appliedclinicaltrialsonline.com/view/characterizing-protocol-guided-source-preparation-process-investigative-sites))

Those figures should be interpreted with appropriate caution. The research involved a clinical technology provider, and the experience of an individual site will depend on therapeutic area, protocol complexity, staffing model, and source system. Still, the findings describe a recognizable operational problem: startup trackers tend to measure contracts, regulatory documents, training, and system access, while the actual construction and testing of visit workflows may remain unmeasured.

Separate operational data published by CRIO in July reported a median of 11 days from source creation to publication among studies in its system, compared with five days in the top quartile and 26 days in the bottom quartile. That measurement captures only part of the process because sites may not begin building final templates until the necessary study documents are available. ([clinicalresearch.io](https://clinicalresearch.io/blog/what-it-takes-to-start-a-study-site-start-up-benchmarks/))

The real task is protocol translation, not form creation

Calling this work “building source” can make it sound like a formatting exercise. In practice, the site is converting protocol language into a sequence of time-sensitive clinical and administrative actions. Staff must determine what happens before the visit, what can occur within a visit window, which assessments must precede dosing, where results originate, what must be reviewed before the participant leaves, and what requires investigator confirmation.

The difficulty increases when study documents do not agree. A laboratory manual may specify collection or processing instructions that do not align with the schedule of activities. An eCRF may request information that has no clear source. A vendor portal may divide an assessment differently from the protocol. Eligibility criteria may require external records that cannot be obtained within the anticipated screening period. Each inconsistency creates a clarification cycle, and every clarification can lead to another source revision.

Community sites also need to account for realities that are easy to miss in a centrally designed workflow. These include bilingual participant interactions, records arriving from outside healthcare systems, transportation constraints, courier pickup times, fasting requirements, caregiver availability, and participants balancing study visits with work. A source template that merely mirrors the eCRF will not necessarily guide staff through those conditions.

Source readiness is a quality issue

The FDA’s September 2025 implementation of ICH E6(R3) reinforces why this work cannot be treated as optional administrative preparation. The guidance states that investigators should define what constitutes the source record, the method of capture, and its location before the trial begins. It also advises avoiding unnecessary transcription and requires source records to be attributable, legible, contemporaneous, original, accurate, and complete. ([fda.gov](https://www.fda.gov/media/169090/download))

A poorly prepared workflow can produce predictable failure modes. Staff may record the same information in multiple places, use an outdated worksheet, miss the timing of an assessment, or discover after a visit that a required field was never captured. These are not simply documentation inconveniences. Depending on the data involved, they can affect eligibility decisions, safety review, endpoint reliability, and the site’s ability to reconstruct what happened.

Electronic source systems can improve traceability and reduce transcription when implemented appropriately. FDA guidance supports electronic source capture and emphasizes reliability, integrity, traceability, authorized data originators, audit trails, investigator review, and record retention. Technology, however, must follow a defined data flow. Moving an unresolved workflow from paper into software only digitizes the ambiguity. ([fda.gov](https://www.fda.gov/regulatory-information/search-fda-guidance-documents/electronic-source-data-clinical-investigations))

What sponsors and CROs can change

Sponsors and CROs should add source readiness to startup planning rather than assuming every site will independently solve the same protocol questions. This does not require forcing all sites onto one source system. It requires giving sites stable, internally consistent inputs early enough to configure and test their workflows.

• Release the protocol, draft eCRF, completion guidelines, laboratory manual, pharmacy manual, imaging instructions, vendor guides, and approved consent materials according to a coordinated document plan.
• Run a cross-functional consistency review before site distribution. Compare visit schedules, time points, eligibility requirements, safety reporting instructions, and vendor workflows across documents.
• Provide a structured channel for operational questions with named owners and expected response times. Frequently repeated questions should trigger a broader clarification to all sites.
• Allow locally configurable source templates when sites have different EHR, eSource, paper, language, or institutional requirements.
• Include source preparation and amendment-related rebuilding in budgets. Treating substantial startup work as unrecognized overhead can weaken site capacity before enrollment begins.
• Assess readiness using a mock participant visit or tabletop exercise, especially for complex screening, dosing, pharmacokinetic, vaccine, imaging, or specimen-processing visits.

What sites should control internally

Sites should not wait for perfect documents before identifying the workflow. Early review can surface questions while regulatory and contracting activities are still underway. The goal is to separate tasks that can proceed with a draft protocol from those that require final sponsor instructions.

A strong internal process has a clear owner, defined version control, investigator input, and a quality check performed by someone other than the original builder. The site should be able to show how each critical procedure and data element flows from the protocol into the source record and, when applicable, into the sponsor’s data-acquisition system.

• Create a document-readiness checklist showing which materials are received, final, reviewed, or still pending.
• Maintain one controlled source master rather than coordinator-specific copies stored in personal folders.
• Document the source location for eligibility evidence, safety data, dosing decisions, external results, and primary endpoints.
• Test the workflow against realistic scenarios, including screen failures, rescheduled visits, missing external records, abnormal laboratory results, and assessments completed outside sequence.
• Require investigator review of clinically important sections, not only administrative approval of the finished template.
• After amendments, perform a documented impact assessment that covers source documents, visit checklists, recruitment materials, participant instructions, system configuration, and staff retraining.

A better definition of activation

Formal activation is a sponsor-controlled milestone. Operational readiness is a shared condition. The two should not be assumed to occur at the same time.

A genuinely ready site has more than approval and portal credentials. Its staff can walk through the first visit, identify the authoritative source for critical data, find the current instructions, manage vendor and laboratory handoffs, document protocol-required decisions, and escalate unresolved questions before they affect a participant.

Making source preparation visible will not eliminate every startup delay. It can, however, expose preventable waiting, reduce duplicated effort, and improve the quality of the first participant’s visit. That is a practical improvement available now, without waiting for a new platform or another industry transformation program.