Unit cost is one of the most frequently misused numbers in community services. Providers present a “cost per visit,” “cost per member,” or “cost per day” and assume it proves value. Commissioners often disagree—not because they reject the math, but because the unit is not comparable across providers, populations, or models. A low unit cost can simply mean the unit is defined too narrowly, excludes critical functions, or reflects lower intensity. This article sets out a practical method to build a defensible unit cost that reflects real service intensity and can be used confidently in oversight, contracting, and rate discussions. It connects to measurement discipline in Data Collection & Data Quality and commissioning logic in Using Data for Commissioning & Oversight.
What commissioners are actually trying to compare
Commissioners use unit cost to answer two questions: (1) are we paying a fair price for a defined level of support, and (2) is the model efficient given the risk profile served? Two explicit expectations follow from this. First, the unit must include all activities required to deliver safe, compliant care—not just face-to-face time. Second, the unit must be stratified so that higher-acuity support is not compared against lower-acuity support as if they are the same service.
Start with a unit definition that matches operational reality
A defensible unit is one that can be explained in plain language, can be audited, and maps to how the service is staffed and governed. For many HCBS and LTSS services, a “member-month” unit works better than “visit” because it captures continuity functions like monitoring, coordination, and escalation. For other models—such as short-term stabilization—a “episode” unit may be more accurate.
Build the unit cost from activities, not assumptions
The most credible approach is activity-based costing: identify the real activities the service performs, estimate the typical time and resources required, and allocate overhead transparently. This prevents undercounting hidden work like supervision, documentation, travel, on-call, and clinical review.
Operational Example 1: Activity-based unit cost for a high-risk care coordination model
What happens in day-to-day delivery
A care coordination team supports high-risk members with weekly outreach, medication problem-solving, appointment scheduling, and escalation to clinicians when symptoms change. Staff document contacts in the record, use standardized triage tools, and hold daily huddles to review risk flags. Supervisors review caseload complexity weekly and adjust staffing to maintain response times.
Why the practice exists (failure mode it addresses)
This practice exists to prevent the failure mode where complex members fall between providers and problems escalate until ED use becomes the default. Coordination is an active workflow, not a passive referral function.
What goes wrong if it is absent
If the cost model only counts “member calls” and excludes huddles, documentation, and escalation time, the unit cost appears low but the model becomes under-resourced. Response times slip, staff burnout increases, and unplanned utilization rises—creating the impression the model “doesn’t work.”
What observable outcome it produces
By costing each activity (outreach, documentation, huddles, escalation) and linking it to timeliness indicators, the provider can evidence that the unit cost is aligned to the intensity required for stability. Audits show consistent activity completion and sustained response performance.
Use acuity bands to avoid false comparisons
A single unit cost across a mixed population is rarely credible. A better approach is to use acuity bands (for example: standard, enhanced, intensive) with clear criteria. The criteria must be observable and consistently applied—such as number of comorbidities, recent crisis episodes, functional dependence, or behavior support needs.
Operational Example 2: A three-band unit cost for community living supports
What happens in day-to-day delivery
The provider classifies members into three service bands at intake and reviews the band monthly. The band determines staffing ratios, supervision frequency, and on-call requirements. Movement between bands is documented with triggers such as increased incidents, medication changes, caregiver breakdown, or hospitalization.
Why the practice exists (failure mode it addresses)
This prevents the failure mode where “average cost” hides the fact that some members require far more support. Without banding, providers under-resource complex cases or cross-subsidize silently until quality failures appear.
What goes wrong if it is absent
Commissioners see a single low unit cost and assume efficiency, while complex members experience instability and crisis escalation. Providers cannot explain why certain cases “cost more,” and disputes over rate adequacy become subjective.
What observable outcome it produces
With banding, the provider can show that higher unit costs align with higher intensity and that outcomes remain stable across bands (for example, fewer crises in the intensive band over time). The audit trail demonstrates consistent classification rather than ad hoc labeling.
Include governance and compliance as part of the unit
Commissioners increasingly expect providers to show that the unit cost includes essential assurance: supervision, training, incident review, safeguarding response, and quality monitoring. Excluding these functions may temporarily reduce cost but creates compliance risk and system harm.
Operational Example 3: Costing supervision and quality assurance into the unit
What happens in day-to-day delivery
The provider allocates supervisor time per caseload (for example, weekly reflective supervision, monthly file audits, and incident review meetings). Quality staff sample records weekly for timeliness and completeness, and findings feed into coaching and process fixes. These activities are scheduled, tracked, and documented.
Why the practice exists (failure mode it addresses)
This practice exists to prevent silent drift: missed documentation, inconsistent practice, weak escalation, and unmanaged risk. Without structured oversight, services can appear “stable” until an incident exposes systemic weakness.
What goes wrong if it is absent
If the cost model excludes supervision and QA, these functions are reduced under pressure. Staff operate with less guidance, errors rise, and incident learning becomes reactive. Commissioners may then impose corrective action or terminate contracts.
What observable outcome it produces
Including supervision and QA in the unit cost allows the provider to evidence that delivery is controlled and auditable. Outcome measures improve alongside assurance indicators such as reduced documentation errors and faster escalation response.
How to present unit cost credibly in proposals and oversight
A defensible unit cost presentation includes: a clear unit definition, a breakdown of included activities, banding criteria if applicable, and an explanation of how the unit links to outcomes and safety. Commissioners are more likely to accept a higher unit cost when it is tied to explicit intensity and supported by evidence that the model prevents costly failure patterns.