The Site
Perspective

Money & business·4 min read

The Visit Ends. The Work Doesn’t.

Clinical trial visits create work before and after the appointment. A practical look at site budgets, coordinator capacity, and the follow-up worth planning.

A coordinator reviews a folder as a participant leaves, connected by a long teal ribbon.
Original AI-assisted editorial illustration for The Site Perspective. Not a depiction of real staff or participants.

The participant leaves. The room is ready for the next person. On the calendar, the visit is finished.

For the coordinator, there may still be a lab result to follow up on, information to enter, a transportation question to resolve, and a call to make about the next appointment.

That work does not become imaginary because the appointment block ended.

When I look at a clinical trial site budget, I want to understand what we are actually agreeing to deliver. A visit fee can look reasonable until you walk through everything attached to that visit. The useful conversation starts there, with the work itself.

A visit is a chain of responsibilities

Think of a hypothetical follow-up appointment. Preparation happens before the participant arrives. The visit happens. Documentation, review, and coordination may continue afterward.

Some tasks belong in the negotiated visit payment. Others may have a separate agreed payment mechanism. Some are general site costs. The point is to identify them before everyone assumes they are someone else's responsibility.

This is not an argument for sending an invoice every time a phone rings. It is an argument for making the assumptions visible.

If a budget assumes one straightforward follow-up call, what happens when the study's workflow requires several attempts, an external record request, and another conversation with a vendor? We should be able to discuss that without treating the question as a complaint.

Describe the work before debating the rate

“We need more money” gives the other side very little to work with.

A clearer explanation might be: this procedure requires preparation, participant time, staff time afterward, and a separate review. Here is who is involved. Here is what the proposed payment appears to include. Here is the part we cannot locate in the budget.

That gives the sponsor or CRO a specific issue to evaluate. It also gives the site a chance to discover that something is already covered elsewhere.

Good budget discussions need enough detail to find both missing work and double counting.

I would rather correct our own assumption early than build a relationship around a misunderstanding that resurfaces six months later.

Predictability helps both sides

Sponsors need to plan spending. CRO teams may be working within delegated limits and may not have authority to approve every requested change. An unexplained fee can create another review cycle instead of a solution.

Sites need enough clarity to staff the study and understand how payment will work. A coordinator's workload does not disappear while a budget question travels between departments.

Those needs can fit together if the parties agree on the work, the assumptions, and the process for exceptions.

  • Map one visit from preparation to follow-up. Include the people doing the work, not just the procedures on the schedule.
  • Separate routine tasks from conditional work. Identify the trigger, supporting documentation, and approval process for anything paid separately under the agreement.
  • Review what actually happened. Use a small sample of completed visits to check whether the planning assumptions were realistic, without sharing participant-identifying details in budget discussions.

The goal is a budget that someone can understand and administer. A long list of vaguely defined fees will not help either side.

Capacity lives outside the appointment calendar

This matters for staffing as much as payment. A calendar with open slots does not necessarily mean a coordinator has room for another participant. Yesterday's visits may still carry work into today.

Before adding more appointments, ask what is waiting behind them. Are follow-ups assigned? Is there protected time for documentation? Does the team know which questions require investigator review?

If the answer is always “we will catch up later,” later becomes an unofficial shift that nobody planned.

I want sites to make realistic commitments and sponsors to receive dependable work. Recognizing the full visit workload supports both. It also makes the next conversation about protocol amendments and site budgets much easier, because there is already a shared understanding of what the original plan included.

What part of post-visit work is most often missing from the first budget conversation?