Why IVD Study Startup Slips (and What Actually Fixes It)

Ask a sponsor why their last IVD study ran long and you will usually hear something about enrollment. Ask what the calendar actually looked like and the answer is often different: enrollment went more or less to plan once it started, but starting took far longer than anyone budgeted.

Startup is the least glamorous phase of a diagnostic program and the one most likely to consume a quarter. It is also where the largest, most avoidable savings sit.

Where the time actually goes

Four activities dominate, and they tend to run sequentially when they could overlap.

Site identification and qualification. Finding sites that match the intended use, confirming they have the patient volume, the equipment, the storage, and the staff, and then visiting to verify it. For a cold network, this alone routinely runs one to three months.

Contracting and budgets. Each site negotiates separately. Legal review, budget back-and-forth, and signature cycles stack up, and a single slow institution can gate the whole activation.

IRB submission and approval. Turnaround varies widely, and every protocol amendment restarts part of the clock. Sites with an existing IRB relationship move materially faster than sites setting one up.

Supply and logistics. Devices, controls, kits, and shipping conditions have to reach every site, with accountability documentation in place before the first subject.

None of these are difficult individually. They are slow because they are serial and because each one is gated on a party with no particular urgency.

The avoidable half

Here is the useful distinction: some of that time is inherent, and some of it is being paid for repeatedly because it was not done in advance.

Site qualification is the clearest example. If qualification happens after you sign a CRO, you are paying for it inside your study timeline. If a network was qualified and contracted before your study existed, that work is already sunk and your activation collapses to protocol-specific tasks. This is the difference between activation measured in months and activation measured in weeks.

The same logic applies to IRB. A standing, pre-approved protocol for common specimen types means a collection can begin in about a week rather than waiting on a fresh submission for each study.

The delays that are your side of the table

It would be dishonest to blame all of this on sites and CROs. A meaningful share of startup slip originates with the sponsor, and these are worth naming because they are the ones fully within your control.

Unsettled predicate or intended use. If the predicate strategy is still moving, the protocol is still moving, which means IRB submissions and site selection are being done against a target that has not stopped shifting. Settle the regulatory strategy before the protocol goes out.

Protocol churn after release. Every amendment costs IRB time at every site, and the cost multiplies by site count. A protocol that gets one careful regulatory review before release is cheaper than three amendments after.

Late supply decisions. Device availability, kit configuration, and shipping conditions decided late become the critical path regardless of how well the sites were prepared.

Slow internal legal review. Sites are frequently blamed for contracting delays that are, on inspection, symmetrical.

Seasonality is real, and it is planning-relevant

For infectious disease diagnostics especially, missing a season does not cost weeks. It costs a year. A respiratory panel that is not enrolling by late fall is waiting for the next one.

That single fact should drive backward planning. If enrollment must begin in October, activation has to complete in September, which means contracting and IRB need to be underway in summer. Programs that plan forward from “when will we be ready” instead of backward from “when must we enroll” are the ones that miss.

A practical way to compress it

• Settle predicate and intended use before writing the protocol.
• Get one regulatory review of the protocol before release, not after.
• Work with sites already contracted and IRB-experienced, so activation is protocol-specific rather than relationship-building.
• Run contracting, IRB, and supply in parallel rather than in sequence.
• Plan backward from the enrollment window, especially for seasonal conditions.
• Ask any CRO to break their timeline into activation versus enrollment. If they will not separate the two, the estimate is not reliable.

---

Because our sites are pre-qualified and contracted before a study exists, Studybox activations typically run about four weeks rather than the three to six months a cold network requires. If you want to sanity-check a startup timeline you have been quoted, send it over.