Tracking Authorizations and Budgets in Self-Directed Care

The authorization is the control point in a self-directed program. It defines what services a consumer may receive, over what period, up to what amount. Everything downstream refers to it: visit verification validates against it, payroll pays against it, billing cites it, and utilization reporting summarizes it.

Get authorization tracking right and most other things become manageable. Get it wrong and the errors propagate into every module that touches it.

Units and dollars are not the same limit

Authorizations are commonly expressed in units — hours, quarter-hours, days, visits — and just as commonly in dollars. Many carry both.

Tracking only units is the more common mistake, and it fails in a specific way. If a consumer is authorized 400 hours at $18/hour, the budget is $7,200. If the wage rate rises to $20 partway through, a system tracking only units will happily deliver all 400 hours — and consume $7,600. The consumer received exactly what was authorized in units and overspent by $400.

The reverse also happens. Tracking only dollars while the rate falls leaves units unused that could have been delivered.

Both limits have to be tracked, and whichever binds first has to be the one enforced. That requires calculating consumed dollars using the rate in effect on the date of service, not the current rate — otherwise a retroactive rate change silently rewrites history.

Committed is not the same as paid

A remaining-balance figure that only counts paid amounts will always overstate what is actually available.

At any moment, a consumer’s budget has money in three states: paid (payroll has run and disbursed), committed (time worked or vendor invoices approved, but not yet paid), and available (genuinely uncommitted).

Someone looking at a balance mid-pay-period, seeing only paid amounts, will authorize additional services against money already spoken for. By the time payroll runs, the budget is over.

The number shown to consumers, case managers, and program staff has to net out committed amounts. It is the difference between a balance people can act on and one that misleads them.

Real authorizations are messier than the model

Concurrent authorizations. A consumer may hold several at once — different services, different funding sources, different date ranges. Each service has to be applied to the correct one automatically, based on service code and date of service. Manual allocation at month end is both slow and where allocation errors originate.

Mid-period amendments. Authorizations get increased, decreased, extended, and shortened. An amendment must adjust the balance without destroying history — the record needs to show what the authorization was before, what it became, who changed it, and when. A payer reviewing a service delivered in March needs the authorization as it stood in March.

Retroactive authorizations. Services are sometimes delivered before the authorization is issued, then backdated to cover them. The system needs to accept a retroactive authorization and correctly apply already-delivered services to it.

Program transfers. When a consumer moves between programs, prior history has to remain intact and attached rather than being orphaned by a new record.

Rate changes. Effective-dated rates, with consumed dollars calculated at the rate that applied on each date of service.

Prevention beats detection

The distinction that matters most operationally is when an overspend is caught.

Validating at the point of entry — when a caregiver checks in, when a timesheet is submitted, when a vendor invoice is entered — means the answer is available before the commitment is made. The service can be redirected, or the authorization increased, or the schedule adjusted.

Detecting the same overspend after payroll has run means the work has happened and the caregiver still has to be paid for it. Now the organization is choosing between absorbing the cost, seeking a retroactive authorization, or attempting a recovery from a family member. None of those are good outcomes, and all of them cost staff time far exceeding the amount in dispute.

Point-of-entry validation should check the date against the authorization period, the service code against covered services, remaining units and dollars against what the entry would consume, and whether the employee is authorized to deliver that service. Some programs configure a hard stop; others accept with a supervisor flag. Either is defensible. Discovering it a month later is not.

Spend-down monitoring

Budgets fail in two directions, and underspending is the one people forget.

An authorization exhausted three months early means a gap in services. An authorization with half its budget unspent at period end means the consumer received less care than they were entitled to, and the next authorization may be reduced on the basis of demonstrated need.

Useful spend-down monitoring shows burn rate — spend per week or month against remaining time — and a projected exhaustion date based on current pace, compared against the authorization end date. The gap between those two dates is the actionable number.

Thresholds should trigger notifications at meaningful points: seventy-five percent consumed, ninety percent consumed, pace projecting exhaustion more than thirty days early, and pace projecting significant underspend. Different thresholds reasonably go to different audiences.

The reporting people actually ask for

Case managers want utilization for their own caseload: authorized, used, committed, remaining, and whether pace is on track. They want it without calling your office, which means portal access scoped to their assigned consumers.

Consumers and representatives want a plain answer to “how much is left” that accounts for committed amounts, plus service history showing where it went.

Payers want aggregate utilization by program, service type, and period, in their prescribed format — which means export definitions that can be saved and re-run rather than rebuilt each quarter.

Program administrators want the outliers: consumers tracking well over or under plan, authorizations expiring soon, services delivered without a valid authorization, and utilization trends across the book of business.

Auditors want retrospective accuracy — what the authorization said on a specific past date, what services were applied to it, and who amended it. That requires versioned history rather than a current-state record.

Getting the foundation right

Authorization tracking is unglamorous, and it is the single highest-leverage thing in a fiscal agent operation. Accurate authorizations make EVV validation meaningful, payroll safe, and billing clean. Inaccurate ones produce denied claims, overspent budgets, and recoveries.

ArborSoft tracks authorizations by units and dollars together, validates at the point of entry against committed as well as paid amounts, versions every amendment, and surfaces spend-down trajectory to the people who can act on it.

See how it connects to the rest of the platform in self-directed care and FMS software, or request a demo.