Expired PARs: the quietest way agencies lose revenue

Of every way a Colorado host home agency loses money it has already earned, this is the one that stings most. Nobody made a mistake at the point of care. The caregiver showed up. The support was delivered exactly as planned. The note was even written well.

And the unit is worthless, because the prior authorization request behind it expired three days earlier.

Why good agencies still get caught

PAR lapses are not a diligence problem. They are a visibility problem, and they share a structure that makes them almost invisible in daily operations:

• The expiration lives in a different system than the work. The caregiver's day comes from the plan of care. The authorization sits with billing. Nothing in the caregiver's workflow changes when a PAR lapses.
• Renewal depends on someone outside your agency. Case manager availability, assessment scheduling, and CCB processing all sit outside your control, and all of them slip.
• The failure is silent. There is no alarm on the day an authorization ends. The first signal is usually a denial, arriving well after the service month closed.
• The gap compounds daily. One missed day is a rounding error. A three-week gap across a full caseload is a five-figure hole.

The three windows that matter

1. Thirty days out — renewal window

This is the only window where the fix is free. A renewal started a month before expiration usually completes without a gap in service. Most agencies do not have a reliable list of which authorizations expire in the next thirty days, because producing that list requires querying authorization data nobody looks at until billing.

2. The week before — escalation window

If a renewal has not moved with a week to go, it needs a name attached and a follow-up on the calendar. The failure mode here is assuming a submitted renewal is a completed renewal. It is not, and the assumption is what turns a manageable delay into a lapse.

3. After expiration — containment window

Once the date passes, you have two decisions to make, and you should make them deliberately rather than by default. Do you continue delivering service? Almost always yes — the person still needs support, and abruptly withdrawing care is both wrong and its own compliance problem. Do you submit those units for payment? Not yet. Units billed against an expired authorization generate denials, and denials generate scrutiny across your whole claim population.

Hold them. Get the authorization renewed, confirm whether the renewal covers the gap period retroactively, and submit clean. A held unit can still be paid. A denied unit is a fight.

What a working control looks like

The agencies that do not lose money to this all have the same thing in common: the authorization status is checked against the units before the batch goes out, automatically, every time. Not monthly. Not by memory.

Practically, that means:

• A standing expiration horizon. Every authorization ending in the next 30, 14, and 7 days, visible to the person responsible for renewals, refreshed continuously.
• A hard gate on the billing side. Units whose service dates fall outside an active authorization never enter a batch. They stop, get flagged, and wait.
• Ownership by name. "Billing watches PARs" is not ownership. A named person with a named backup is.
• A log of every catch. When the gate holds a unit and you fix it, record it. That log is both your evidence of a functioning control and the number that tells you what the control is worth.

General information for Colorado HCBS providers, not legal or billing advice. Requirements vary by waiver, service code, and payer; confirm specifics against current HCPF and CDPHE guidance.