Ask a study start-up manager why a site took four months to activate, and you will rarely hear a single dramatic reason. You hear four small ones — each of which could have been cleared before the protocol even landed.
Sites that activate fast are not lucky. They are prepared. Below are the four items that hold up activation most often, and what your site can do about each one now, while nothing is pending.
1. Documents that expired quietly
CVs more than two years old. A GCP certificate that lapsed last spring. A medical license renewed but never re-uploaded. A lab certification that sits in a folder somewhere on a shared drive.
None of these are difficult to fix. They are simply invisible until a sponsor’s start-up team asks for the regulatory packet and discovers that three of the eleven documents need to be regenerated — which means chasing a PI who is in clinic all week.
What to do: keep one folder, maintained by one named person, with a review date on every document. CVs, licenses, GCP and human-subjects training, financial disclosure forms, lab certifications and normal ranges, delegation-of-authority templates. Set a calendar reminder each quarter. The entire task takes twenty minutes when nothing is urgent, and days when something is.
2. The contract and budget conversation starting from zero
Contract and budget negotiation is consistently one of the largest single contributors to start-up delay, and much of that time is spent on positions your site has already taken on every previous study — payment terms, indemnification language, invoiceables, overhead rate, screen-failure reimbursement.
If those positions live in the heads of two people rather than in a document, every negotiation restarts the same debate.
What to do: write down your standard positions once. What is your overhead rate and what does it cover? What payment terms will you accept, and which are non-negotiable? What is your per-procedure floor for the ten procedures you perform most? Which contract clauses have you never agreed to and why? A two-page internal position paper turns a three-week negotiation into a three-day one.
3. Ethics review routed the slow way
Where the ethics review goes matters more than most sites expect. Analysis published by ACRP found a median approval time of 78 days for centralized IRB review compared with 165 days for local review — and a median total start-up duration of 199 days versus 287 days. That is roughly a three-month difference in when a site can enroll its first patient.
What to do: know in advance whether your institution requires local review, permits reliance on a central IRB, or can do either. If reliance is possible, have the reliance agreement and the local context requirements ready to send. If local review is mandatory, know your committee’s submission deadlines and meeting calendar, and build them into every feasibility response you give.
4. Capacity that was assumed rather than confirmed
The last delay is the least comfortable one. A site says yes to a study, and only afterwards discovers that the coordinator who would run it is already at capacity, or that the freezer space is committed, or that the PI’s clinic schedule cannot accommodate the visit windows.
What to do: before returning a feasibility questionnaire, confirm three things in writing internally — who the coordinator will be, whether the PI has reviewed the visit schedule, and whether equipment and storage are genuinely available for the study’s duration. Saying “not this one” early costs a site far less credibility than activating and under-enrolling.
The pattern underneath all four
Every item on this list is administrative, not clinical. None of them reflect the quality of your investigators or your patient population. They are exactly the kind of friction that a well-run site can eliminate permanently with a few hours of preparation — and exactly the kind that quietly costs sites study opportunities they would otherwise have won.
This is a large part of what a network does. BNZ Research Network holds site profiles, capability data and standing documentation centrally, so that when a matched study appears, most of the packet is already assembled and your team is answering questions rather than hunting for files.
Joining the network is free, with no upfront cost — our team reviews every application and responds within 1–2 business days.
