Study Startup Checklist: Sequenced Along the Critical Path

At a glance

• Study startup is everything between deciding to run a trial and a site being green-lit to enroll. The hard part is not the task list; it is the order and the handoffs.
• Most startup delays are sequencing and handoff failures, not missing tasks. A flat checklist hides exactly where time is lost.
• This checklist is sequenced along the real critical path: feasibility and site selection, then regulatory/IRB-EC submissions, then contracts and budget, then essential-document collection, then the site initiation visit and activation.
• Every line has an owner (sponsor, CRO, or site) and a typical bottleneck, because “who is waiting on whom” is where activation dates slip.
• A site is “activated” only when the green-light conditions are met: approvals in hand, agreements signed, essential records collected, and the site initiated.

Most study startup checklists you find dump an undifferentiated list of activities with no order, no owner, and no sense of where the time actually goes. That is the opposite of useful, because startup is a critical-path problem: tasks depend on each other, and a slip in one handoff cascades. This guide gives you a phase-sequenced, copy-pasteable checklist with an owner and a typical bottleneck on each line, plus a clear green-light boundary. It deliberately stays on the startup activity sequence; the full TMF essential-document index, budget line-item construction, and the project-management discipline each have their own guides.

What “study startup” covers (and where it ends)

Study startup is the set of activities that take a trial from a green protocol to a site that may begin enrolling participants. It spans site selection, regulatory and ethics submissions, contract and budget negotiation, essential-record collection, and the site initiation visit. It ends at activation: the point where the site is permitted to screen and enroll.

Startup vs ongoing conduct, the green-light boundary

The boundary that matters is the green light. A site may not begin until the gating conditions are met, and several are GCP requirements, not internal preferences. A trial must be conducted in compliance with a protocol that received prior IRB/IEC approval or favourable opinion (ICH E6(R3) §II, principle 3), and the sponsor must ensure it has obtained documented IRB/IEC approval before the site proceeds (ICH E6(R3) §3.8.2). Before initiating the trial, the sponsor (or sponsor and investigator) must submit any required applications to the appropriate regulatory authority for review, acceptance, or permission to begin (ICH E6(R3) §3.8.1). And informed consent must be obtained from every participant before any trial participation (ICH E6(R3) §II, principle 2). Until those are satisfied for a site, startup is not finished.

The study startup checklist, by phase

The phases below are the critical path. Each runs largely in sequence, though some activities overlap. The owner and bottleneck notes are where startup actually lives or dies.

Phase 1: Feasibility and site selection

Choosing the right sites is the foundation, and it is a GCP-anchored sponsor duty: the selection and oversight of investigators is a fundamental feature of sponsor oversight (ICH E6(R3) §3.9.5), and investigators must be qualified by education, training, and experience for their tasks (ICH E6(R3) §II, principle 5).

• Confirm protocol feasibility and target population access — Owner: sponsor — Bottleneck: over-optimistic enrollment assumptions
• Identify and qualify candidate sites; assess resources and experience — Owner: sponsor/CRO — Bottleneck: slow site responses to feasibility questionnaires
• Confirm investigator qualifications and site capacity — Owner: sponsor/CRO — Bottleneck: investigator availability and competing trials

Phase 2: Regulatory, IRB/EC, and competent-authority submissions

Nothing downstream can complete until these approvals are in motion, so they should start as early as the protocol allows.

• Prepare and submit regulatory authority application(s) before initiation — Owner: sponsor — Bottleneck: review timelines outside your control (ICH E6(R3) §3.8.1)
• Prepare and submit to IRB/IEC; obtain documented approval/favourable opinion — Owner: sponsor or site (per region) — Bottleneck: ethics committee meeting cadence (ICH E6(R3) §3.8.2)
• Track and file the documented initial approval before activation — Owner: sponsor — Bottleneck: waiting on the formal approval letter

Phase 3: Contracts, budget, and CTA negotiation

Contracts run in parallel with submissions but frequently become the longest pole.

• Negotiate the clinical trial agreement (CTA) and define roles and responsibilities — Owner: sponsor/site legal — Bottleneck: indemnification and IP clauses
• Agree the site budget and financial terms; document them — Owner: sponsor/site — Bottleneck: per-procedure rate negotiation
• Execute agreements with clearly defined, documented responsibilities — Owner: sponsor — Bottleneck: institutional signatory turnaround (ICH E6(R3) §II, principle 10)

Phase 4: Essential-document collection and site file setup

The site file and essential records must be established at the outset, because the investigator must control the essential records they generate before and during the trial (ICH E6(R3) §2.12.11), and essential records are established before and during conduct (ICH E6(R3) Appendix C.1).

• Collect investigator and site staff CVs, qualifications, and the delegation log — Owner: site — Bottleneck: incomplete or outdated CVs
• Set up the investigator site file / essential-records repository — Owner: site/CRO — Bottleneck: late establishment, then a scramble (route document-completeness detail to the TMF checklist guide)
• Confirm the protocol, investigator’s brochure, and consent forms are current and distributed — Owner: sponsor — Bottleneck: version control across sites

Phase 5: Site Initiation Visit (SIV) and activation/green light

The SIV is the verification step that the site is ready. ICH E6(R3) frames monitoring as including verification of the investigator and site staff qualifications and site resources, training, and review of trial documents (ICH E6(R3) §3.11.4), which is exactly the SIV’s job at the front of the trial.

• Conduct the SIV: confirm training, procedures, IP handling, and readiness — Owner: sponsor/CRO monitor — Bottleneck: scheduling around site and monitor availability
• Confirm IMP is supplied and ready before enrollment — Owner: sponsor — Bottleneck: depot/shipping lead time (ICH E6(R3) §3.15)
• Confirm all green-light conditions met (approvals, agreements, records, SIV) and document activation — Owner: sponsor — Bottleneck: one missing approval holding the whole site

How long does study startup take, and what causes delays?

Startup is routinely the longest non-conduct phase of a trial, commonly measured in months rather than weeks, and it is the phase most likely to slip the first-patient-in date. The duration is driven less by the number of tasks than by the long-lead approvals and negotiations that gate everything else. Two of those gates are largely outside your control: regulatory authority review of the application you must submit before initiating (ICH E6(R3) §3.8.1), and the IRB/IEC’s own meeting cadence before it issues the documented approval you need (ICH E6(R3) §3.8.2). Contract and budget negotiation is the third long pole, and unlike the approvals it is partly within your control if you start it early.

The practical lesson is to schedule backward from those gates rather than forward from the task list. Begin the regulatory and ethics submissions and the contract negotiation as early as the protocol allows, and run them in parallel, because they do not depend on each other. Teams that treat startup as a sequential checklist, finishing one phase before opening the next, lose weeks waiting on reviews they could have started sooner. The activities themselves are rarely the constraint; the waiting between handoffs is.

Who owns what: sponsor vs CRO vs site

Ownership is where handoffs fail, so make it explicit. In broad strokes:

• Sponsor owns regulatory submissions, the protocol and IB, investigator selection, IMP supply, and the final activation decision. Even when work is delegated, the sponsor retains responsibility for the conduct of the trial (ICH E6(R3) §II, principle 10).
• CRO owns whatever is transferred in the agreement, often feasibility, monitoring, and document collection. Transfers must be documented with clear responsibilities (ICH E6(R3) §II, principle 10).
• Site/investigator owns site-level documents, CVs, the delegation log, the site file, and obtaining informed consent (ICH E6(R3) §2.12.11, §II principle 2).

A RACI-style table on these lines, agreed before startup begins, prevents the “I thought you were doing that” handoff that stalls activation.

Where startup stalls (the common bottlenecks)

Startup rarely stalls because a task was forgotten. It stalls at the seams:

• Submission timelines. Ethics and regulatory review run on their own clock; start them first and build the schedule around them (ICH E6(R3) §3.8.1, §3.8.2).
• Contract negotiation. CTA and budget talks routinely outrun submissions; start them in parallel, not after.
• Document handoffs. A site file set up late becomes a pre-SIV scramble; establish it in Phase 4, not Phase 5 (ICH E6(R3) §2.12.11).
• Single-point gates. Activation is all-or-nothing: one missing approval blocks the green light, so track the gating items as a set, not a list.
• Unclear ownership. Every unowned task is a handoff waiting to drop.

The pattern underneath all of these is the same: startup work is highly interdependent, so the constraint is almost never a single team working slowly. It is the gaps between teams, the days a document sits in someone’s inbox, the week lost because a contract was not started until approvals came back, the SIV that could not be scheduled because the site file was not ready. Mapping the dependencies up front, then assigning an owner to each handoff (not just each task), is what turns a slipping activation date into a predictable one. A standing tracker that shows who owes what next, and flags items that have stalled, is worth more here than any amount of additional task detail.

Copy-paste study startup checklist

PHASE 1 — FEASIBILITY & SITE SELECTION
[ ] Protocol feasibility confirmed (sponsor)
[ ] Candidate sites identified & qualified (sponsor/CRO)
[ ] Investigator qualifications & capacity confirmed (sponsor/CRO)

PHASE 2 — REGULATORY / IRB-EC SUBMISSIONS
[ ] Regulatory authority application submitted (sponsor)
[ ] IRB/IEC submission made (sponsor/site)
[ ] Documented IRB/IEC approval received & filed (sponsor)

PHASE 3 — CONTRACTS & BUDGET
[ ] CTA negotiated (sponsor/site legal)
[ ] Site budget & financial terms agreed and documented (sponsor/site)
[ ] Agreements executed with documented responsibilities (sponsor)

PHASE 4 — ESSENTIAL DOCUMENTS & SITE FILE
[ ] CVs, qualifications, delegation log collected (site)
[ ] Investigator site file / essential-records repository set up (site/CRO)
[ ] Current protocol, IB, consent forms distributed (sponsor)

PHASE 5 — SIV & ACTIVATION
[ ] Site Initiation Visit conducted; training & readiness confirmed (monitor)
[ ] IMP supplied and ready (sponsor)
[ ] All green-light conditions met; activation documented (sponsor)

A note on tooling: a tool like TrialTrack can track startup tasks and their owners so handoffs do not slip. It does not file submissions, manage budgets, or hold the TMF; it keeps the sequence and ownership visible so nothing stalls unnoticed.

The bottom line

Study startup is a critical-path problem, not a checklist-completeness problem. Sequence the work along the real path, start the long-lead items (regulatory, ethics, contracts) first and in parallel, put an owner on every line, and treat the green light as a single gated set of conditions, several of which are GCP requirements. Do that, and the activation date stops slipping at the handoffs where most teams lose their weeks.

Sources

• ICH E6(R3) Good Clinical Practice