Prior authorization sits at the center of home-care billing. Almost every Medicaid and managed-care service requires a payer's formal approval before care is delivered. The authorization defines what is covered: which service code, how many hours or visits, for which client, over what date range. When a claim hits the payer without a matching active authorization behind it, the claim denies. No matter how good the care was. No matter how clean the visit record is.

This is not news to anyone who has worked in home-care billing. But authorization management is one of those problems that looks simple from the outside and turns out to be genuinely hard to execute well at scale. The agencies that keep their authorization-related denial rate low are not doing anything exotic. They are doing a few specific things that the agencies with persistent auth denials are not.

Why authorization gaps happen even in well-run agencies

Authorization gaps are not usually the result of someone ignoring the process. They happen because the process is fragile in specific, predictable ways.

Authorizations expire on a calendar, but care does not pause on weekends

Most authorizations have hard expiration dates. A Medicaid waiver authorization for personal care services runs from a start date to an end date. The payer expects a renewal request before that end date. If the renewal is not in and the old authorization expires, any visits delivered after the expiration date have no coverage behind them.

The problem is timing. Renewal requests take time — the coordinator has to gather the clinical documentation, submit the request through the payer's portal, wait for processing, and receive the new authorization back. That cycle can take two weeks with a cooperative payer and considerably longer with one that has a claims backlog. If the agency starts the renewal process the week the authorization expires, they are almost certainly going to have a gap.

And clients do not stop receiving care while the renewal is in process. The coordinator keeps scheduling visits against the expired authorization because the client needs the care and stopping service over a paperwork delay is not an acceptable option. By the time the new authorization comes back, three weeks of visits may have been delivered without active coverage. Those visits will deny.

Service changes that require a new authorization get overlooked

When a client's care needs change — more hours, a different service type, an added visit on weekends — that change often requires a new or amended authorization from the payer. The clinical assessment gets updated. The care plan gets updated. But if someone does not also initiate a payer authorization request for the changed services, the visits go out under the old authorization parameters. The payer adjudicates based on what was authorized, not what was delivered, and denies the difference.

This is particularly common when service changes happen in the middle of an authorization period. A client is authorized for 20 hours per week of personal care. A family event increases the need to 28 hours for a month. The coordinator adjusts the schedule. The billing team does not know an authorization amendment was needed. The overage claims deny.

Authorization records that do not match what billing submits

Even when an active authorization exists, a claim can deny if the service code on the claim does not match the service code on the authorization, or if the units billed exceed the authorized units, or if the authorization was entered with a typo in the client's Medicaid ID. These are not cases where the authorization is missing. They are cases where the authorization and the claim do not agree, and the payer resolves that disagreement by denying the claim.

Data entry errors in authorization records compound over time. An authorization entered with a wrong start date looks active until someone compares it carefully against the actual payer-issued document. A service code entered as S9122 when the authorization says S9123 will generate denials on every claim until someone identifies the discrepancy.

An authorization in the system is not the same thing as a correct authorization in the system. The difference lives in the denials.

Multi-branch and multi-coordinator environments where accountability gets diffuse

Authorization management is an inherently manual, relationship-intensive process. Someone has to watch the expiration dates, initiate renewals on schedule, follow up when payers are slow, and flag service changes that require amended authorizations. In a single-branch agency with a dedicated billing coordinator, that accountability is usually clear. In a multi-branch agency where each branch coordinator manages their own caseload, or where billing is centralized but scheduling is local, the handoffs between the people who know about service changes and the people who manage authorizations are where the gaps appear.

The coordinator at the branch knows the client's hours changed. The billing team at the central office does not know until the claim denies. By then, the visits have already been delivered and the window to get a retroactive authorization may be closing.

What the renewal calendar should actually look like

The operational fix for expiration gaps is a renewal calendar that is not reactive but anticipatory. The question to answer is: which authorizations expire in the next 45 days, and has a renewal request been initiated for each one?

Forty-five days is the right horizon for most payers. It gives 15 days to gather clinical documentation, 15 days for payer processing, and a 15-day buffer for follow-up if the payer is slow or requests additional information. Agencies that start renewals 14 days before expiration are building in no buffer at all — they are betting on every payer being prompt, which is not a safe bet.

The renewal calendar should be a standing item in whatever operational cadence the agency runs — weekly, if the volume warrants it. Every authorization expiring in the next 45 days needs a status: renewal requested, in process, received. Any authorization within 30 days of expiration without a received renewal should be a flag that requires immediate action.

When to pursue a retroactive authorization — and what it takes

When visits have already been delivered in an authorization gap and the denial has come back, the first question is whether the payer will grant a retroactive authorization. The answer varies significantly by payer and by how far outside the window the request falls.

Most Medicaid fee-for-service programs have formal retroactive authorization processes with specific documentation requirements. The request typically needs to establish that the care was clinically necessary, that there was a legitimate reason the prior authorization was not in place before service delivery, and that the request is being made within whatever retroactive window the program allows.

Managed-care organizations are more variable. Some have clear retroactive authorization policies. Others handle retroactive requests on a case-by-case basis with no guaranteed outcome. The billing team should know, for each managed-care payer in the mix, whether retroactive authorizations are available and what documentation the payer requires.

For visits that are within the timely filing window and the retroactive authorization is granted, the path is clear: attach the authorization to the corrected claim and resubmit. For visits outside the timely filing window, even a successful retroactive authorization may not save the revenue — the claim has to get out while it can still be accepted. This is why the window between a denial and a resolution matters so much. For more on denial timelines and recovery paths, the piece on why home-care claims get denied covers the full denial management picture.

Building authorization tracking into the daily workflow, not the monthly audit

The agencies with the lowest authorization-related denial rates treat authorization status as a daily operational metric, not a monthly reconciliation task. That means someone — a specific person, not a process — is looking at authorization status on a regular schedule and flagging anything that is expiring, has a mismatch, or lacks a renewal request.

In practice, this looks like a report pulled from the EMR or the billing system that shows, for every active client, the authorization on file, its expiration date, the authorized service codes and units, and whether visits in the current period are within the authorized parameters. The report is reviewed on a cadence that allows action — weekly, not monthly.

The alternative is discovering authorization gaps on the remittance. By then, the visits are delivered, the window may be partially closed, and the work to recover the revenue is harder and less certain than it would have been if the gap had been caught before the visits went out.

Where authorization tracking fits in the margin picture

Authorization failures are one of several places where home-care margin disappears between what was authorized, what was delivered, and what was collected. The full landscape — including unbilled hours, EVV gaps, and rate mismatches — is covered in the overview of where home-care margin leaks. Authorization gaps are notable because they are the most directly preventable of the major leak categories. The visit has to happen before you can bill it. The authorization has to be in place before the visit happens. That ordering makes authorization management the upstream intervention that protects everything downstream.

An agency that has clean authorization tracking does not stop generating denials entirely — rate mismatches, EVV gaps, and timely filing issues will still appear. But it removes the largest single driver of home-care billing losses from the picture, which is a meaningful place to start.

Find out where your authorizations are leaking before the denials arrive.

Reeve reads your EMR data read-only and identifies every authorization gap, expiring auth, and visit-to-auth mismatch in your current book. Free teardown, no commitment.

Schedule a free teardown ↗