âAffordableâ is not a vibeâit is a unit cost the system can defend, fund, and monitor. Under Budget Impact & Affordability, commissioners and finance teams scrutinize whether a serviceâs per-member, per-episode, or per-contact cost is built from real delivery mechanics rather than optimistic averages. This connects directly to Cost vs Outcomes, but the affordability question is narrower: can the rate be sustained in-year, audited, and scaled without hidden cost growth?
Why unit costing is where affordability wins or fails
Unit costing translates a service model into a budgetable price: who delivers the work, how often, at what intensity, with what supervision and infrastructure. If the unit cost is too low, delivery quality degrades, staff churn rises, and safety incidents create downstream spend. If the unit cost is inflated or poorly evidenced, approvals stall and procurement becomes adversarial. The goal is not the cheapest rate; it is a rate that aligns with required practice and can be governed under real-world variation.
Oversight expectations you must design for
Expectation 1: Clear cost allocation and overhead logic. Funders expect you to show what is direct (frontline time, travel, supplies), what is indirect (supervision, QA, training), and what is organizational overhead (HR, finance, IT). âOverhead 20%â without a rationale is a red flag.
Expectation 2: Assumptions must be auditable and linked to operating controls. If your unit cost assumes a 75% productive time ratio, commissioners will want to know how you manage scheduling, documentation, travel, cancellations, and no-showsâand how youâll evidence it month to month.
Choose the right unit: per member, per episode, or per contact
The unit you choose shapes incentives. Per-contact pricing can encourage high volume and low depth. Per-episode pricing fits defined pathways but must address complexity variation. Per-member-per-month (PMPM) supports continuity and proactive work but needs strong eligibility rules and caseload controls to prevent unbounded demand. A defensible model often uses a blended approach: a base unit plus defined add-ons for verified complexity, out-of-hours response, or step-up capacity.
Operational Example 1: Building a per-episode cost for a 30-day step-down pathway
What happens in day-to-day delivery
A step-down pathway is defined as a 30-day episode with a structured weekly rhythm. Intake begins with a same-day handoff from the referring setting, a medication and risk reconciliation call, and a first-72-hours stabilization plan. Weeks 1â2 involve higher-contact frequency (daily check-ins plus two in-person visits), while weeks 3â4 taper to planned contacts and coordinated transition. Staffing time is captured through scheduling and documentation systems, and supervision time is scheduled (e.g., weekly case review plus ad hoc escalation support). The provider reports episode-level completion, step-down adherence, and escalation events.
Why the practice exists (failure mode it addresses)
Per-contact pricing can unintentionally reward extended involvement and inconsistent tapering. A per-episode unit exists to ensure the pathway is delivered as a coherent package with a built-in taper, preventing âendless service driftâ that erodes affordability.
What goes wrong if it is absent
Without a defined episode unit, contact intensity varies widely by staff preference and referral pressure. Some participants receive insufficient early stabilization (leading to re-escalation), while others remain at high frequency long after stability. Costs become unpredictable, and commissioners cannot determine whether spend reflects need or practice variation.
What observable outcome it produces
A per-episode model produces stable cost forecasting and a clear audit trail of expected contacts and supervision. Outcomes can be evidenced through episode completion rates, timeliness of tapering, escalation frequency, and reconciliation accuracyâallowing commissioners to verify that cost aligns with standardized delivery.
Operational Example 2: Cost allocation for mobile crisis response across shifts and geographies
What happens in day-to-day delivery
A mobile crisis team operates 24/7 coverage with defined shift patterns. The costing model separates readiness (minimum staffing for safe response) from activity (responses delivered). Dispatch logs track response times, travel distance, time on scene, de-escalation interventions, referrals, and follow-up. Supervisors review a sample of encounters for documentation quality and risk decisions. Overhead allocation includes clinical governance time (incident review, restrictive practice oversight), IT/telephony costs, and training/competency checks tied to the risk profile of the work.
Why the practice exists (failure mode it addresses)
Crisis services are financially fragile when readiness costs are hidden inside a per-response price. When volume fluctuates, providers either carry unreimbursed readiness cost or cut staffing, which damages safety and performance. Explicit allocation prevents that failure mode.
What goes wrong if it is absent
If readiness is not separated, low-volume periods appear âoverpricedâ and trigger pressure to reduce staffing. Response times worsen, high-risk events increase, and commissioners face reputational and safety risk. Alternatively, providers inflate per-response charges to protect readiness, which becomes indefensible in audits.
What observable outcome it produces
A transparent allocation produces predictable budgets and clearer accountability: commissioners can see readiness cost, utilization, and unit cost movement over time. Evidence includes dispatch performance, staffing stability, and incident trendsâlinking affordability to safety and governance rather than guesswork.
Operational Example 3: PMPM pricing with caseload controls and intensity tiers
What happens in day-to-day delivery
A PMPM community support model enrolls participants using explicit eligibility rules and assigns them to intensity tiers based on acuity scoring. Tier 1 receives scheduled check-ins and coordination; Tier 2 receives weekly structured contacts; Tier 3 receives high-frequency stabilization with defined step-down milestones. Caseload caps are set per tier, and supervisors review tier changes weekly. The provider produces a monthly utilization and tier-mix report showing contact intensity, escalation events, and time allocation across roles.
Why the practice exists (failure mode it addresses)
PMPM models become unaffordable when âmembershipâ expands without intensity management. Tiers and caps exist to prevent uncontrolled growth in time per member and to ensure higher intensity is time-limited and clinically justified.
What goes wrong if it is absent
Without tier controls, staff respond to rising risk by increasing contacts indefinitely. Caseloads become unmanageable, documentation slips, and adverse events rise. The PMPM rate then looks inadequate or the service demands renegotiationâeither outcome undermines affordability and trust.
What observable outcome it produces
Tiered PMPM produces stable forecasting and measurable intensity control. Evidence includes tier migration rates, timeliness of step-down, overtime trends, and incident review outcomesâshowing the system how affordability is protected through operational discipline.
Practical checklist: what finance teams expect to see
Defensible unit costing typically includes: a clear unit definition; role-based time assumptions grounded in workflow; explicit supervision and governance time; transparent overhead allocation; travel and non-productive time handling; and a monitoring plan that detects unit cost drift (e.g., rising intensity, increased cancellations, extended episode length).
Affordability is a control system, not a spreadsheet
The best unit costs are paired with operating controls that keep delivery inside assumptions. When commissioners can see how you manage intensity, supervision, and variance in real time, âaffordableâ becomes a credible commitment rather than a hopeful estimate.