Designing Acuity Add-Ons in HCBS: Paying for Complexity Without Creating Perverse Incentives

Acuity add-ons exist because “average” HCBS rates often fail people with complex needs: intensive behavioral support, unstable medical conditions, high safeguarding risk, or environments where two-person support is required. But add-ons are also a high-scrutiny area—if tiers are vague or documentation is weak, systems see over-assignment, inconsistent decisions, and provider distrust. This article explains how to build acuity tiers that are operationally usable and audit-defensible. For related modelling context, see Rate-Setting Mechanics & Cost Modelling and Rate-Setting Mechanics & Cost Modelling.

What “acuity” must mean in a rate model

Acuity should be tied to observable cost drivers, not labels. A defensible add-on links higher payment to specific resource requirements such as: two-person support, enhanced supervision frequency, higher training/specialist competence, increased travel time due to limited provider options, more non-billable coordination, or elevated incident-response workload. If the tier definition cannot be operationalized into staffing, supervision, and risk controls, it will not hold up in reviews.

The goal is not to pay more “because needs are complex,” but because the system expects a different delivery model that costs more to run safely.

Organizations working across multiple service lines may benefit from a commissioning and funding systems resource for more coherent community care design.

Two oversight expectations acuity add-ons must satisfy

Expectation 1: Tier assignment must be consistent, reviewable, and evidence-based

Oversight teams expect to see a standardized decision record: the tier criteria met, the evidence used, who approved it, and when it will be reviewed. Inconsistent tiering across similar cases is treated as a governance weakness, even if overall spending is within budget.

Expectation 2: The model must include anti-gaming controls and verification

Where add-ons exist, incentives exist. Regulators and funders expect controls that detect “tier drift” (people remaining in a higher tier without ongoing justification) and ensure documentation matches the delivery reality—especially for staffing ratios, restrictive practices, and incident response.

Operational example 1: Building tier criteria around delivery requirements, not diagnoses

What happens in day-to-day delivery: The commissioner and provider agree a tier matrix that is written in operational terms (e.g., “requires two-person support for personal care and community access due to documented risk of aggression,” “requires RN oversight weekly plus medication delegation checks,” “requires enhanced supervision: minimum 2 formal supervisions per month with incident debrief”). Care coordinators complete a standardized tiering form at assessment, attach the supporting evidence (risk assessment, behavior support plan summary, medication risk profile), and route it to an approval queue with clinical/quality sign-off where required.

Why the practice exists (failure mode it addresses): Diagnosis-led tiers (IDD label, mental health label) create inconsistency and inequity because diagnoses do not reliably predict resource intensity. This practice exists to prevent subjective, variable tiering that cannot be defended against comparator cases.

What goes wrong if it is absent: Tiering becomes a negotiation rather than a decision. Similar individuals are funded differently depending on who advocates hardest, providers feel compelled to “code up,” and oversight sees unexplained spending variation that triggers corrective action or clawback risk.

What observable outcome it produces: Operational criteria produce more consistent tier assignment and clearer service design. Evidence includes decision logs showing criteria met, fewer disputes/appeals on tiering, and stable tier distribution without unexplained spikes.

Operational example 2: Verification that the funded model is actually being delivered

What happens in day-to-day delivery: For higher tiers, the provider submits a brief monthly verification pack: staffing pattern (including two-person coverage where applicable), supervision records, incident summaries, and any restrictive practice authorizations or reviews. Commissioners run a light-touch sample audit: matching timesheets/EVV (where used) to the required staffing model, checking that supervision cadence occurred, and confirming that high-risk incidents triggered the expected escalation pathway.

Why the practice exists (failure mode it addresses): Add-ons often fail because the system pays for a higher-intensity model but does not confirm it is in place. This practice exists to prevent “paper acuity” where funding increases but the operational controls do not, leaving risk unmanaged.

What goes wrong if it is absent: Two-person support is authorized but not reliably scheduled, supervision is skipped to cover vacancies, and incidents rise. When an adverse event occurs, the commissioner cannot evidence that the funded safeguards were implemented, creating liability and reputational risk.

What observable outcome it produces: Verification improves alignment between payment and delivery. Evidence includes higher compliance with staffing ratios, fewer repeat incidents linked to missed safeguards, and an auditable trail showing how funding decisions were monitored.

Operational example 3: Tier review cycles that prevent drift and protect access

What happens in day-to-day delivery: Each tier assignment includes a review date and a review trigger set (e.g., “no incidents for 90 days,” “medication stability achieved,” “behavior support plan stepped down,” “hospitalizations reduced”). The care coordinator schedules the review, requests updated evidence from the provider, and records whether the tier continues, steps down, or escalates. Exceptions (e.g., long-term two-person support) require documented rationale and periodic re-authorization.

Why the practice exists (failure mode it addresses): Without structured reviews, tiers tend to ratchet upward and stay there, regardless of improvement. This practice exists to prevent uncontrolled growth in acuity spending and to ensure resources are targeted to current needs.

What goes wrong if it is absent: The add-on becomes a permanent entitlement; budgets tighten; commissioners respond by bluntly cutting rates or restricting access. Providers then struggle to accept truly high-acuity referrals because the add-on no longer reflects real resource intensity.

What observable outcome it produces: Review cycles stabilize acuity spending while maintaining access for those who need it most. Evidence includes tier distribution stability, documented step-downs where outcomes improve, and reduced conflict between commissioners and providers about “unfunded complexity.”

Closing: pay for the model you expect, then prove it happened

Acuity add-ons work when they are specific, testable, and verified. If your tier definitions translate directly into staffing, supervision, and risk controls—and you can evidence review and drift prevention—the add-on becomes a tool for access and safety rather than a source of audit anxiety.