FDA’s Expedited IND Pilot Turns Parallel Startup Into a Readiness Test

What the pilot actually changes

Under the pilot, a sponsor will work with a qualified research institution, or QRI, that provides multidisciplinary expertise across nonclinical development, chemistry, manufacturing and controls, clinical design, clinical pharmacology, and regulatory affairs. FDA may review discrete IND components on a rolling basis during the pre-IND period rather than waiting for the complete IND package. The final submission still starts the formal 30-day IND review window. ([fda.gov](https://www.fda.gov/industry/fda-actions-accelerate-and-modernize-early-and-late-stage-clinical-development/fda-expedited-investigational-new-drug-ind-pilot-program))

FDA describes QRIs broadly. They may include academic medical centers, health networks, CROs, regulatory advisers, or other research organizations. A prospective QRI must also be able to support U.S. Phase 1 initiation through its own infrastructure or documented partnerships. FDA specifically identifies IRB review, contracting, and site readiness as activities that may proceed in parallel with IND review. ([fda.gov](https://www.fda.gov/industry/fda-actions-accelerate-and-modernize-early-and-late-stage-clinical-development/fda-expedited-investigational-new-drug-ind-pilot-program))

What the pilot does not do is waive the normal authorization threshold. An investigational drug cannot be administered until the IND is in effect, either after FDA provides earlier notification or 30 days after receipt if the study has not been placed on clinical hold. The investigation also requires IRB review and approval before initiation. ([fda.gov](https://www.fda.gov/drugs/types-applications/investigational-new-drug-application-ind?utm_source=openai))

Parallel work needs different levels of commitment

The phrase “parallel startup” can hide several very different activities. Reviewing a protocol synopsis is not equivalent to purchasing specialized equipment. Drafting a budget is not equivalent to scheduling participants. Evaluating pharmacy capabilities is not equivalent to receiving investigational product.

Sponsors and sites should divide startup work into levels based on reversibility, cost, and dependency on final regulatory documents. This makes acceleration deliberate rather than speculative.

• Low-regret planning: preliminary feasibility, investigator review, population assessment, facility mapping, identification of laboratory and pharmacy requirements, vendor lead-time review, and development of a draft responsibility matrix.
• Conditional preparation: draft budget and contract language, collection of regulatory documents, tentative staffing plans, draft source worksheets, preliminary IRB preparation, and evaluation of protocol-specific equipment or training needs.
• High-commitment execution: final IRB submission, nonrefundable vendor orders, staff scheduling, investigational product receipt, participant-facing recruitment, screening appointments, and other work that assumes stable study documents and authorization to proceed.
• Every conditional or high-commitment activity should have a named trigger, an accountable decision-maker, and a documented assumption about which protocol and Investigator’s Brochure versions are being used.

The protocol version problem becomes more important, not less

Rolling development means important clinical, nonclinical, or CMC questions may be resolved while site startup is already underway. Those resolutions can affect eligibility criteria, dose-escalation rules, sentinel dosing, observation periods, stopping criteria, safety assessments, sample schedules, pharmacy preparation, or emergency procedures.

A team can therefore appear to be ahead while building against a protocol that is no longer operationally valid. The visible result is rework. The less visible result is fragmented training, conflicting worksheets, outdated budget assumptions, and uncertainty over which document drove a decision.

The control is a live dependency log, not another generic startup tracker. For each operational workstream, the log should identify the source document, version date, unresolved assumptions, owner, and consequence of a change. A revised dose-escalation rule, for example, should automatically prompt review of staffing, pharmacy coverage, laboratory timing, monitoring windows, emergency support, and participant scheduling.

Site readiness should be demonstrated with evidence

FDA’s pilot materials refer repeatedly to site readiness, but a green status icon is not evidence that a first-in-human site can safely execute the protocol. ICH E6(R3) expects investigators to have qualified staff, adequate facilities, sufficient time, appropriate oversight, and operationally feasible trial processes. It also emphasizes prospective identification of factors critical to participant protection and reliable results. ([fda.gov](https://www.fda.gov/media/169090/download))

A useful readiness review should test whether the site can perform the most consequential protocol day under realistic conditions. For an early-phase study, that may be the first administration, a dose-escalation visit, an intensive pharmacokinetic day, or management of an acute safety event.

• Final protocol, Investigator’s Brochure, pharmacy manual, laboratory manual, informed consent form, and safety instructions are reconciled and version controlled.
• The investigator and delegated staff have completed role-appropriate training, with unresolved questions documented and closed.
• Pharmacy preparation, accountability, storage, temperature monitoring, and backup coverage have been rehearsed where appropriate.
• Timed procedures, specimen processing, courier cutoffs, meals, dosing, ECGs, vital signs, and pharmacokinetic collections have been mapped on one operational timeline.
• Medical escalation pathways, emergency equipment, transfer arrangements, and after-hours investigator coverage match the investigational product’s known and anticipated risks.
• The site has received explicit confirmation of IRB approval, IND status, sponsor authorization, investigational product release, and any protocol-specific enrollment restrictions before participant activity begins.

Contracting and budgeting must reflect uncertainty

Parallel startup transfers timing risk. If that risk is not addressed in the contract and budget, it usually lands with the site through unreimbursed labor, expired training, repeated IRB work, canceled staffing, or unused supplies.

Sponsors do not need to eliminate all at-risk work. They do need to define it. Startup agreements should specify which activities are authorized before the IND is effective, how protocol revisions will be handled, what costs are reimbursable if the program is delayed or placed on hold, and who can approve additional work.

Milestone payments should also reflect actual work. A single payment at site activation may be poorly aligned with a model in which the site performs substantial feasibility, pharmacy, IRB, and readiness work months earlier. Clear staged payments give both parties a more accurate view of cost and progress.

The real test is whether parallel startup produces a usable first day

FDA’s Expedited IND Pilot is small, voluntary, and initially limited to a handful of sponsor-QRI pairs. Still, it signals a meaningful change in how early development timelines may be evaluated. FDA is not looking only at the quality of an IND submission. It is also asking whether scientific preparation, regulatory interaction, and clinical startup can be coordinated more effectively. ([fda.gov](https://www.fda.gov/news-events/press-announcements/fda-launches-expedited-ind-pilot-begins-accepting-applications))

The best operational response is not to begin every task earlier. It is to identify which work can safely move left, define the evidence required to advance, and prevent unstable inputs from becoming participant-facing processes.

If the pilot succeeds, its most useful lesson may be that faster first-in-human initiation depends less on compressing individual tasks and more on connecting regulatory development to real site capabilities. A rolling IND process can create time. Only disciplined readiness management can turn that time into a safe, executable study.