Line item seven on the budget reads “Week 12 Visit” and carries a number. What the number covers is a participant arriving, being consented on an amendment, completing four questionnaires, undergoing a physical assessment, providing three tubes of blood that need processing within thirty minutes, and answering a set of questions about medications they take but cannot name.
Then the coordinator enters all of it, resolves two queries from the prior visit, and calls a participant who missed a different appointment. None of that second half appears anywhere in line item seven.
Justin Coffeen’s route into research ran through a chiropractic practice and a medical chronic pain clinic, where he instructed physical rehabilitation and conducted Functional Capacity Evaluations. He is based in Lakewood Ranch, Florida. Running a practice teaches you quickly that time you do not bill is still time you spend.
Per-visit rates hide the work between visits
Budgets are built around visits because visits are countable. The work that keeps a study running is largely not visit-shaped.
Query resolution, participant retention calls, pharmacy coordination, specimen shipment tracking, regulatory maintenance, and monitoring visit preparation all consume staff hours that no per-visit line item covers. Coffeen’s view is that a site accepting a budget without accounting for that work has agreed to subsidize the study, and the subsidy comes out of the same staff hours that would otherwise go to data quality.
A useful exercise during budget review is to list every activity a study will require and mark which ones map to a payable line item. The unmapped list is rarely short. Seeing it written down changes the negotiation from a discussion about rates to a discussion about scope.
Screen failures are real work at a discounted rate
A participant who screens and does not qualify still consumed a consent conversation, a medical history review, laboratory work, and coordinator time. Many budgets reimburse a fraction of that, and some cap the number of reimbursed screen failures entirely.
In studies with demanding eligibility criteria, the screen failure rate can be the single largest driver of site effort. Knowing that rate before signing matters more than negotiating the per-visit rate upward by a small margin. Coffeen looks at the eligibility criteria and the expected failure rate together, because the two numbers determine each other.
The rate is also not static. Screen failure rates tend to run higher early, before the site has calibrated its pre-screening to the protocol’s actual criteria. A budget built on the steady-state rate will underestimate the first several months.
Somebody pays for the equipment either way
Protocols specify equipment, calibration, temperature monitoring, storage, and sometimes dedicated space. Those requirements do not become cheaper because they were not itemized in the budget.
A site that agrees to a protocol requiring monitored refrigeration has committed to a monitored refrigerator, its validation, its maintenance, and its documented temperature log. Coffeen reads protocols with an eye for what they oblige the site to own rather than only what they oblige the site to do.
Payment timing is part of the budget
A favorable rate paid quarterly in arrears, contingent on data entry being current, is a different financial arrangement than the same rate paid monthly. Sites that do not read the payment terms alongside the rates sometimes find themselves carrying months of study costs.
This is not a finance department concern that coordinators can ignore. Payment terms tied to data currency change what the site has to prioritize, and a coordinator who does not know that constraint exists cannot work within it.
A budget is a description of the work the site is expected to perform. When the description is wrong, the work still happens. It just happens with fewer people, at a lower standard, and the place it shows up is in the data.
Coffeen’s practical position is that whoever runs the study should read the contract, not just the budget grid. Obligations about data entry timelines, monitoring visit access, and what happens if enrollment targets are missed all live in language that coordinators are rarely shown and always affected by.