Healthcare capacity is usually a matching problem, not a headcount problem

Short answer: when a healthcare service says it is at capacity, the aggregate figure is often true and the operational reality often is not. Capacity exists in specific slots, with specific clinicians, for specific patient types, at specific times. Demand arrives with its own shape. Where booking rules do not let those shapes meet, capacity is stranded — and recruitment adds cost faster than it adds care.

By Ian McPhee — former VP of Operations, Optum Behavioural Care (United Health Group)

The test that settles it

Ask for three numbers: reported utilisation, unfilled usable slots last week, and enquiry-to-first-appointment conversion. Organisations that are truly capacity-constrained can answer all three. Organisations that are mismatched usually cannot, or the numbers contradict each other — a waiting list beside empty diaries is the classic signal.

Having built and scaled a patient access organisation of more than 150 people, and led operations across 236 clinics and telehealth services at Optum Behavioural Care, I see the same pattern across private providers, behavioural health and digital health in the UK and US.

Where capacity hides

Slot-type rigidity

Protected sessions and clinician-patient matching rules leave usable time unused while the wrong patient type waits.

Booking horizons

Rules that prevent short-notice fill or same-day backfill strand slots that demand would happily take.

Case-mix blindness

Utilisation targets that treat assessments, follow-ups and supervised sessions as interchangeable disguise where time actually goes.

Access leakage upstream

Demand never reaches the calendar because enquiry-to-booking conversion fails before a slot is even offered.

Non-attendance untreated

No-shows are treated as weather rather than a controllable lever, with no rebooking discipline or pull-forward process.

Documentation and supervision load

Hours that never appear in the utilisation target but consume the rota — invisible in the plan, very real in the week.

The access leakage point is the one most often missed entirely — I have set out why in patient access is a growth function. Supervision and documentation load bite hardest in behavioural health, where I cover them in why behavioural health growth plans fail.

What good capacity management looks like

  • Demand and capacity planned in the same conversation
  • Utilisation reported by case type and seniority, not a single headline figure
  • A named owner for stranded-slot recovery
  • Booking rules redesigned before headcount approvals are signed
  • Access metrics reviewed on the same cadence as utilisation

None of this starts with recruitment. It starts with treating the clinic calendar as a commercial asset whose rules are owned, measured and redesigned.

Why investors should care

Growth cases often assume near-perfect utilisation. Operational diligence should test whether reported capacity has ever actually been achieved under real case-mix — or whether the utilisation line in the model is an assumption wearing a spreadsheet.

How Clarendum helps

Clarendum works with healthcare providers on patient access, capacity and operating-model design — starting with what the calendar and the front door are actually doing, then redesigning the rules that strand usable capacity before headcount decisions are made.

Frequently asked questions

How do I know if I need more clinicians or better matching?
If waiting lists grow while usable slots go unfilled, start with matching. Recruit when true available capacity under improved booking rules is still insufficient for demand.
What utilisation target is realistic?
It depends on case-mix, supervision and documentation load. A single benchmark without that context is usually misleading — model productivity by session type, not against a headline number.
Does this require a new EHR?
Usually not. Most stranded capacity is a rules and ownership problem that the system then encodes. Fix the rules and the ownership first; the platform rarely needs to change.

Think you are at capacity — or mismatched?

A short call is usually enough to separate stranded slots from a true headcount constraint.