Resources

Why Clinician Utilization Decides Telehealth Margins

Utilization = publish rate × booking rate × show rate × billable rate, and three modest leaks compound into a third of clinical payroll. The benchmarks we see across virtual networks, the $470K-per-point math, and the weekly review that moves it.

TL;DR: Clinician utilization is completed visit hours divided by paid clinical hours. On fee-for-service or attributed contracts it is effectively your margin. We compute this number for virtual care teams every week, and the finding is consistent: utilization is a chain of four multiplied leaks, published, booked, shown, billable, and three modest leaks quietly compound into a third of clinical payroll while every individual dashboard looks fine. Here is the formula, the benchmarks we see, and the weekly review that moves it.

The formula, and the three denominators that hide the problem

Completed utilization = completed, billable visit hours ÷ paid clinical hours. Most teams measure something easier and call it utilization. There are three denominators in circulation:

  • Contracted clinical hours: what you pay for. The only denominator your CFO cares about.
  • Published availability: what clinicians actually opened as bookable. The gap between contracted and published is availability shrinkage, the quietest leak in virtual care. Clinicians block their own calendars, hold slots, publish late. Almost nobody reports this gap as a metric. Measure it once and you will keep measuring it.
  • Booked hours: what the calendar says. No-shows, late cancels, and visits that turn out to be unbillable (wrong panel, lapsed license, ineligible member) all sit between the calendar and the claim.

Write it as a chain: completed utilization = publish rate × booking rate × show rate × billable rate. Put honest numbers in: 0.90 × 0.85 × 0.88 × 0.98 = 66%. Nobody in that chain failed. The compounding did. This is why the aggregate number tells you nothing useful, and why we always decompose it: each leak has a different fix and a different owner.

What is a good utilization rate for telehealth clinicians?

Across the salaried virtual networks we work with: published availability at 90%+ of contracted hours, booking at 80–90% of published slots, show rates of 85–92% for commercial populations and meaningfully lower in some Medicaid populations, which is a scheduling-design problem, not a patient problem. That nets to 70–80% completed utilization as strong, and under 60% as a margin fire. Do not chase 95%. A network run that hot has no surge slack, no documentation time, and a burnout bill arriving in two quarters. We set a managed band, not a maximum.

Where the hours go

  • Availability shrinkage. Contracted 30, published 25. Across two hundred clinicians that is a phantom clinic that never reached the booking page. The fix is unglamorous: report contracted-versus-published per clinician monthly, and make publishing windows a policy with a date.
  • Template scheduling. Recurring weekly templates are how a Tuesday 2pm surplus and a Thursday 7pm shortage coexist forever. Consumer demand peaks evenings and Sunday nights. Schedules built purely on clinician preference guarantee the mismatch.
  • No-shows and late cancels. Reminder cadence, deliberate overbooking on high no-show segments, and waitlist backfill that re-releases a cancelled slot to same-day demand in minutes. A slot recovered same-day is a utilization point you did not have to hire for.
  • Mis-mapped supply. Hours parked where the clinician cannot bill. Licensure and enrollment have to be hard constraints at booking time. If you are discovering these through denials, the data plumbing is the problem.
  • Intake-follow-up imbalance. Every intake commits future follow-ups. Max out intakes in a slack month and the wave lands in sixty days, mid-care, where continuity breaks hurt outcomes and quality scores. The intake-to-follow-up ratio per clinician per week is a number you manage, not one you discover.

What one point of utilization is worth

Two hundred salaried clinicians, 30 paid clinical hours a week, $150 fully loaded per hour: $900,000 of clinical payroll a week. One utilization point is 60 hours a week, roughly $470,000 a year. The distance between 70% and 80% on that network is about $4.7M a year with no change to headcount, pay, or care quality. Only the matching changes. We work with an 800-provider enterprise clinic delivering primary care and mental health services; at that scale, the same arithmetic is why utilization, not rate negotiation, is the largest unworked margin lever on the P&L.

On attributed contracts, utilization is the contract

Value-based arrangements relocate the problem. The payer attributes a population; demand arrives on their schedule against capacity you already bought. Under-provision and you miss the engagement and access targets that are the contract. Over-provision defensively and idle hours eat the case rate. The questions that matter: what share of attributed members have you engaged, what is time-to-first-appointment against the contractual standard, and how much paid capacity is pointed at states where attribution is not materializing. Utilization against attribution is not an input to the contract economics. It is the contract economics.

The weekly review that actually moves it

Thirty minutes, the same screens every week, decisions only:

  • Completed utilization by state, payer, and service line, this week versus trailing four. Any cell moving more than a few points gets investigated, in either direction.
  • The chain decomposed: publish, booking, show, billable. The decomposition tells you which lever to pull. The aggregate never does.
  • Hot cells (high utilization, wait times near a standard) trigger cross-licensing, flex offers, or template changes.
  • Cold cells (paid hours idle) get rebalanced toward intakes, outreach, or adjacent states before the month is gone.
  • Every decision gets an owner and a date.

One rule is non-negotiable: this runs on reconciled scheduling and visit data, weekly. Claims-based utilization arrives 30 to 90 days late, after the schedule that caused the problem has repeated four times. We built Untether so the chain is computed live; the review becomes thirty minutes because the data argument is already over.

See your own chain

The first thing we show a new team is their leak chain, decomposed by state and payer. It is usually the first time anyone has seen all four numbers on one screen, and one of them is usually worth seven figures. Book a demo and we will show you yours.

Want to request a demo?

Please reach out and we'll book some time.