Inflation indexing is often treated as the default solution for HCBS rate maintenance, yet it only adjusts the numbersānot the assumptions. If the underlying model is wrong (productivity, travel, supervision, workforce mix, or compliance load), indexing simply scales a flawed baseline. Rebasing, by contrast, refreshes the whole model, but it is politically harder and operationally heavier. This article explains how commissioners can choose the right approach, design clear triggers, and evidence decisions in a way that protects access and withstands scrutiny. For related foundations, see Rate-Setting Mechanics & Cost Modelling and Funding, Rates & Payment Models.
What indexing can doāand what it cannot
Indexing is useful when the service model is stable and the main cost drivers move predictably: wage baselines, benefit load, and general operating costs. It is a āmaintenanceā tool. Indexing is not designed to correct structural mismatch, such as: unrealistic productivity targets, travel time understated for rural coverage, acuity complexity rising without an aligned tier/add-on, or new compliance requirements that add non-billable work.
Systems get into trouble when indexing is used as a substitute for governance. If providers are already showing access strainādeclining referral acceptance, missed visits, increased turnoverāan indexed uplift may be too small or misdirected, and the system remains fragile.
Organizations can improve long-term sustainability by using a commissioning and funding hub that supports stronger system design across provider networks.
What rebasing actually changes
Rebasing means re-validating each major model parameter against current delivery reality. This includes wage ladders (not just averages), billable-to-paid ratios, supervision cadence, training and competency requirements, documentation and incident follow-up load, travel patterns, and the true cost of meeting contract expectations. Rebasing is where you correct drift and ensure that the funded model still matches the model you expect providers to deliver.
A practical rule: index to prevent gradual erosion; rebase to correct structural misalignment.
Two oversight expectations for rate adjustments
Expectation 1: Adjustments must be transparent, explainable, and supported by evidence
Whether indexing or rebasing, commissioners should be able to show the method, inputs, and rationale. Oversight bodies and stakeholders increasingly expect that ārate updatesā can be traced to observable data: workforce metrics, access indicators, provider participation, and cost drivers tied to required service controls.
Expectation 2: Adjustments must not create incentives to inflate costs or reduce access
Indexing approaches can be gamed if they reward higher reported costs without verification, and rebasing can cause harm if it is implemented abruptly or without monitoring. Systems are expected to include guardrails: verification routines, phased implementation where needed, and post-change monitoring that checks access and quality impacts.
Operational example 1: A wage-linked indexing clause that reflects HCBS labor reality
What happens in day-to-day delivery: The commissioner defines an indexing method that separates labor and non-labor components. The labor portion is linked to a wage benchmark approach (such as a defined wage floor movement or a documented local market wage indicator), while the non-labor portion follows a general inflation factor. Contract language specifies timing (e.g., annual update), publication date of the index, and how the updated rate is applied across service codes. Providers are required to attest that wage uplifts were implemented through payroll evidence and that recruitment/retention actions were taken consistent with the funded change.
Why the practice exists (failure mode it addresses): General CPI-style indexing can under-adjust in labor-driven services, especially when DSP wages move faster than general inflation. This practice exists to prevent slow workforce collapse caused by rates that rise āon paperā but lag actual hiring conditions.
What goes wrong if it is absent: Providers face widening labor gaps, increasing overtime and cancellations. They restrict coverage areas, decline higher-need referrals, and reduce supervisory capacity to protect billable hours. Access deterioration then appears as āprovider performance issues,ā when the root driver was a structurally inadequate update method.
What observable outcome it produces: A labor-responsive indexing clause supports measurable workforce stability: improved fill rates, reduced missed visits, and steadier turnover trends. Evidence shows up in provider HR metrics, visit completion data, and reduced escalation tied to staffing gaps.
Operational example 2: A rebasing trigger tied to access and market signals, not politics
What happens in day-to-day delivery: The commissioner defines objective triggers that require a rebasing review, such as: sustained increases in referral rejection due to ārate/staffing,ā repeated provider contract terminations, persistent missed-visit rates above a threshold, or documented expansion of compliance requirements (new reporting, monitoring, or clinical oversight expectations). When a trigger is met, a time-limited rebasing process starts: providers submit standardized cost and workflow inputs, the commissioner validates a sample against operational records, and the model parameters are refreshed. Findings and decisions are documented in an evidence pack with clear before/after assumptions.
Why the practice exists (failure mode it addresses): Rebasing often happens too late, after market damage has occurred, or it is avoided because it is administratively difficult. This practice exists to prevent drift becoming a crisis by using transparent signals to trigger governance action.
What goes wrong if it is absent: Indexing continues while structural misalignment grows. Providers absorb pressure until they exit or fail suddenly, leading to emergency contracting, higher unit costs, and avoidable disruption for people receiving services.
What observable outcome it produces: Trigger-based rebasing produces earlier corrections and fewer emergency interventions. Evidence includes documented trigger events, rebasing reports, stabilized provider participation, and improved access indicators after implementation.
Operational example 3: Post-update verification and monitoring that prevents āpaper fixesā
What happens in day-to-day delivery: After an indexed update or rebased rate change, commissioners run a short monitoring cycle (e.g., 90ā180 days) focused on access and delivery controls: acceptance rates, time-to-start, missed visits, continuity, incident reporting timeliness, and supervision compliance. Providers submit a brief implementation statement describing what changed operationally (wage increases, supervision coverage, scheduling capacity, training completion). Contract managers sample-check supporting evidence and compare trends to pre-change baselines.
Why the practice exists (failure mode it addresses): Rate increases do not automatically translate into improved delivery, and rate reductions can cause harm before commissioners notice. This practice exists to prevent rate updates becoming āpaper eventsā with no accountability for intended outcomes.
What goes wrong if it is absent: Systems assume the problem is solved (after increases) or underestimate harm (after cuts). Access deterioration, quality incidents, and complaints rise, and the commissioner lacks timely evidence to intervene or to demonstrate responsible oversight.
What observable outcome it produces: Monitoring produces a defensible link between funding decisions and service reality. Evidence includes post-change dashboards, sampled records showing implementation actions, and faster corrective adjustments when indicators move in the wrong direction.
Closing: choose the method that matches the problem
Indexing is a maintenance tool; rebasing is a correction tool. Sustainable HCBS systems use both: index to prevent erosion and rebase when assumptions no longer match delivery reality. The defensibility comes from transparent triggers, clear documentation, and monitoring that proves whether the update protected access and supported safe practice.