In Billing, Claims & Revenue Cycle Management, one of the most persistent sources of revenue leakage is not incorrect billing, but ungoverned change. As participant needs evolve, services often expand informally before authorizations are updated. These pressures typically emerge after intake, when initial decisions made in Intake, Eligibility & Triage Operating Models no longer reflect real-world delivery conditions.
The reality of change in HCBS delivery
Community-based care is dynamic. Participants experience crises, functional decline, caregiver loss, or behavioral escalation. Frontline teams respond appropriately to need, often increasing frequency or intensity of support. The risk arises when this change is not translated into updated authorizations before billing continues.
Service drift is rarely malicious. It is usually driven by compassion, operational pressure, or slow payer response times. Without structured controls, however, it creates significant financial and compliance exposure.
Oversight expectations related to authorization management
Expectation 1: Services must align with current, documented authorization
Payers expect billed services to match the authorization in effect at the time of delivery. Retrospective justification rarely succeeds if formal authorization was not updated.
Expectation 2: Providers must demonstrate proactive change management
Auditors and plans look for evidence that providers identify changes in need and initiate authorization updates promptly, rather than allowing informal expansion to persist.
Operational example 1: Change detection embedded in supervision and scheduling
What happens in day-to-day delivery: Supervisors review schedules and service patterns weekly, looking for increases in frequency, duration, or intensity. Triggers (for example, consecutive weeks above baseline units) automatically flag cases for review. When triggers fire, supervisors assess whether the change reflects temporary variance or a sustained shift requiring authorization update.
Why the practice exists (failure mode it addresses): Without systematic detection, service expansion happens quietly and becomes normalized before billing or intake is aware.
What goes wrong if it is absent: Providers deliver weeks of unauthorized services, leading to denials or forced write-offs when billing eventually identifies the mismatch.
What observable outcome it produces: Earlier identification of service drift and faster initiation of authorization updates.
Operational example 2: Formal authorization change workflows
What happens in day-to-day delivery: When a change is identified, a standardized workflow is triggered: updated assessment, documentation of rationale, payer notification, and tracking of submission and response timelines. During pending periods, services are delivered under clearly defined interim rules approved by leadership.
Why the practice exists (failure mode it addresses): Informal requests and ad hoc payer communication often stall or get lost, extending unauthorized delivery.
What goes wrong if it is absent: Teams assume “we’re waiting on the payer,” while billing accumulates non-billable units with no clear plan.
What observable outcome it produces: Shorter authorization turnaround times and clearer financial forecasting during change periods.
Operational example 3: Billing safeguards during pending authorizations
What happens in day-to-day delivery: Billing systems flag services delivered during pending authorization periods. Leaders decide in advance whether these units are billable, held, or written off if denied. Decisions are documented and consistently applied.
Why the practice exists (failure mode it addresses): Unclear handling of pending periods leads to inconsistent billing and audit risk.
What goes wrong if it is absent: Claims are submitted inconsistently, increasing denial rates and weakening appeal credibility.
What observable outcome it produces: Predictable financial impact of service changes and stronger audit defensibility.
Leadership signals that matter
Strong leaders monitor the percentage of services delivered under pending authorization, average authorization update time, denied units due to service drift, and recurrence of similar issues. These metrics guide whether the organization is learning or repeatedly absorbing the same losses.