Don't Accept This Site-Level Start-Up Bottleneck— Instead, Learn How To Stop It

By Celin Sabu, MSc

Ask any clinical operations leader what the biggest threat to a trial timeline is and site activation comes up almost immediately. Ask them why it takes as long as it does, and the answer is usually a shrug paired with “That’s just how long it takes.”

In most global Phase 3 programs, two major events sit early in the start-up sequence: the investigator meeting (protocol training, safety reporting, and logistics) and the site initiation visit, or SIV, (essential documents, contracts, pharmacy, and lab setup all verified). Convention treats these as two separate events, often weeks or months apart, and each requires its own scheduling, travel, and site coordination. On many  global oncology studies, the combined sequence adds up to several months between site identification to first-patient-in readiness.

Five months is not a regulatory requirement; it is an artifact of process design. And once I understood that, it became a solvable problem rather than a fact of life.

Questioning The Sequence

On one high-priority oncology program, the timeline pressure was real enough that “the way we’ve always done it” wasn’t going to be good enough. My team asked a simple question: Did the investigator meeting — which covers protocol and site training — and the SIV actually need to remain two separate events, weeks apart, or could both happen in the same visit?

Looking closely at who actually attends each event made the case obvious. The core sponsor team delivering protocol and safety training at the investigator meeting largely overlapped with the team needed at the SIV — meaning the same people were scheduling, traveling to, and running two separate engagements with the same site staff, who in turn sat through much of the same content twice. Layering two full scheduling cycles on top of each other — coordinating calendars across sponsor teams, CRAs, and site staff twice instead of once — was itself a major source of delay, independent of any actual readiness work. From our assessment, the separation reflected organizational practice rather than an explicit ICH- GCP requirement. So, the real project wasn’t just a scheduling change; it was building a compliance-sound case for combining the two.

Building The Case For Change

To support the proposed approach, I developed a structured change proposal demonstrating that all required readiness, training, and oversight activities would be maintained while consolidating site engagement. The request had to satisfy quality and regulatory stakeholders on a few key points: that every essential document and readiness item normally verified at a stand-alone SIV would still be verified, in the same order of rigor, just within a single combined visit; that training content would not be compressed or diluted simply because it now shared a visit with initiation activities; and that oversight and sign-off checkpoints remained exactly as they were, just consolidated into one site engagement instead of two.

Getting this approved requires alignment across clinical operations, quality, regulatory affairs, and site contracts — functions that don’t always share a workflow model and that don’t always move at the same pace. The waiver went through several rounds of review before it was approved.

Part of what made the request easy to approve was that we didn’t propose it as a blanket approach for every site. The combined visit was limited to sites with recent sponsor experience and established operational familiarity. For a site we were engaging for the first time, with no recent facility knowledge, we kept the traditional two-visit sequence — the unknowns were exactly the kind that benefit from a stand-alone SIV. Scoping the change this way gave our quality team a clear, defensible boundary rather than an open-ended exception.

What Changed, And What It Delivered

Once approved, the investigator meeting and site initiation visit ran as a single coordinated event. Site staff received their protocol and safety training and completed activation readiness in the same visit, rather than waiting through two separate scheduling cycles. The redesigned process substantially reduced site activation timelines while maintaining compliance oversight. The redesigned process exceeded the objectives established for the initiative.

A Second Lever: Making Feasibility Numbers Mean Something

Site activation speed only matters if the sites you’re activating are the right ones — and that depends on feasibility data that is actually accurate. On another operational initiative, we ran a KOL-led mass feasibility model rather than the traditional site-by-site feasibility survey. KOLs convened prospective sites together rather than each site being queried in isolation, which itself compressed the feasibility timeline significantly.

But the more important change was a control we built into the process: participating investigators could not simply estimate patient numbers from memory or optimism. Feasibility figures had to be justified against the site’s own patient database or EMR records before we accepted them. This closed a well-known failure mode in feasibility assessment, where enthusiastic but unverified projections lead to sites being selected that can’t actually deliver — a problem that surfaces months later, when it’s far more expensive to fix.

What I Would Tell Someone Trying This

If you’re looking to take a similar approach, consider the following:

Question the convention, not just the calendar. The investigator meeting and SIV were separate because that’s how it had always been done, not because compliance required it. The same is probably true of at least one fixed sequence in your own start-up process.

Map who actually attends each event. If the same core team and the same site staff are sitting through two separate engagements with substantial content overlap, that’s a strong signal the events can be consolidated — and a concrete way to make the case to stakeholders who aren’t yet convinced.

Scope the exception before you ask for it. We didn’t propose combining events for every site — only those the sponsor already knew from recent activation, where facility and staff were already familiar. A bounded, criteria-based request is far easier for the quality team to say yes to than an open-ended one.

Bring in the quality team early, not at the end. The waiver succeeded because QA helped shape the safeguards not because they were asked to approve a finished plan. Framing the conversation as “help me make this safe” rather than “approve what I’ve already decided” changes the dynamic.

Don’t let combining events mean cutting corners. Every readiness item that a stand-alone SIV would check still needs to be checked. The value is in the scheduling, not in doing less.

Verify feasibility numbers against something real. A KOL-led format speeds up feasibility collection, but speed without data integrity just moves the problem downstream. Requiring EMR or patient database justification for site-level estimates is a small process addition with an outsize effect on site selection quality.

Expect this to be organizational work, not just operational work. The hardest part of both changes was not the redesign itself. It was persuading functions that hadn’t needed to coordinate this closely before  to do so on a compressed timeline.

A Bottleneck, Not A Law Of Nature

Site activation timelines are treated as fixed because they have always been sequential, not because sequencing is required. In an environment where every month of start-up delay pushes back first-patient-in, data readouts, and ultimately patient access to new therapies, that assumption is worth challenging on every program — carefully, with quality as a partner, but without accepting “that’s just how long it takes” as the final word.

About The Author:

Celin Sabu, MSc, is a clinical operations leader with more than 17 years of global experience across multiple biopharma organizations, including oncology and cell therapy.