Spravato Operations Series
Spravato Authorization Tracking: How To Make Sure No Auth Ever Lapses
A Spravato authorization tracker needs the auth number and end date for each patient, the sessions approved vs. used, and the next scheduled appointment. That last field is what turns a list into a control, because it’s the one that catches a session booked after the auth runs out. Check the tracker at 30, 14 and 7 days out.
Every Unpaid Spravato Session Has The Same Autopsy
When a Spravato program writes off sessions, the story is almost always identical: the patient was doing well, the schedule kept generating appointments, and the authorization, approved months earlier for a fixed number of sessions or a fixed date range, ran out without anyone noticing. The clinic didn’t lack a biller or a spreadsheet. It lacked a join: nothing connected the next scheduled appointment to the authorization that pays for it.
Authorization tracking is that join, run as a discipline. In an esketamine program it’s the revenue control that pays back the most, because a lapsed auth costs you the visit, the staff time and, under buy-and-bill, the drug itself. Our prior authorization playbook covers the full lifecycle. This page is only about the tracking mechanics.
The Fields That Actually Matter
A workable tracker carries, per patient, per payer:
- Payer and plan, including whether the drug rides the medical or the pharmacy benefit, because reauthorization may live on the pharmacy side and you don’t want to learn that at renewal.
- Authorization number, start date, end date: the end date is the field programs most often don’t capture at approval time.
- Sessions approved vs. sessions used, decremented automatically from completed appointments, not updated by hand when someone remembers.
- Approved dose and frequency: treat outside those parameters and you can void an auth that’s otherwise live.
- Reauthorization trigger and status, the date the renewal must start, who owns it, and where it stands (not started / submitted / pended / approved).
- Assessment due dates: the follow-up documentation your payers expect at renewal, such as PHQ-9 rechecks at roughly 4-week and 8-week marks and on a maintenance cadence, so the response evidence is already on file when the reauth asks for it.
- Next scheduled appointment: the field that turns a list into a control, because it’s how you catch a booked session that’d land after the auth ends or past the approved session count.
Why The Spreadsheet Fails At Scale
It Depends On A Human Remembering To Look
A spreadsheet is passive. Nothing happens when an end date approaches unless someone opens the file, sorts the column, and does the arithmetic, on the exact week it matters, every week, forever.
Sessions-Used Goes Stale Immediately
Manual decrementing drifts from reality within days at any real volume. At 12 to 15 sessions a day, a hand-updated counter is fiction by Friday, and a fictional counter is worse than none because people trust it.
It Cannot See The Schedule
The failure happens at the intersection of calendar and authorization, and the spreadsheet only holds one side. No sheet will ever warn you that Thursday’s booked session is number 25 of 24 approved.
It Has No Owner When It Matters
Shared spreadsheets diffuse responsibility. When a lapse surfaces, the honest answer to “who was watching this?” is usually “everyone,” which means no one.
Spreadsheets are fine at five patients. At forty, they’re how programs quietly donate sessions to payers.
The Escalation Cadence
Whatever tool you use, a fixed schedule of checks is what protects you. Here’s the one we use:
- 30 days / 6 sessions remaining: Auth flagged; reauthorization packet opened; assessment scores confirmed current or a recheck scheduled.
- 14 days / 4 sessions remaining: The reauth has to be in. If it isn’t, the flag escalates from the auth owner to the practice’s operations lead, who’s a named person and not a queue.
- 7 days / 2 sessions remaining, no approval on file: Log a payer follow-up call and warn the clinical team. Then review the upcoming appointments for coverage risk before they happen, so any treat-versus-hold decision gets made on purpose, with the financial conversation had in advance instead of discovered in the denial queue.
- Weekly, always: One standing review of every auth expiring in the next 45 days. It takes ten minutes, and it’s the whole ballgame.
What Good Tooling Looks Like
The version of this we run for a roughly 70-patient interventional psychiatry program in Oregon tracks authorizations across Regence, Providence Health Plan, and Optum Behavioral Health (UnitedHealthcare), with an automated appointment feed out of the Tebra (Kareo) EHR keeping sessions-used current without hand entry. The properties that matter, in any implementation:
- Automatic session counting: Completed appointments decrement the auth without a human touching a counter.
- Schedule-aware warnings: Any appointment that’d fall outside an auth’s date range or session count gets flagged the moment it’s booked. The system looks forward, not back.
- Deadline surfacing, not deadline storage: Expiring auths show up in front of the person responsible on the schedule above, so nobody has to remember to look.
- One view per patient: Auth status, sessions remaining, next assessment due, reauth status and next appointment on a single line. The front desk can read it at booking time, which is where it counts, and the biller still has it at claim time.
You can run a disciplined manual version. It’ll work until volume breaks it.
Common Questions
What Fields Should A Spravato Authorization Tracker Include?
At minimum, it needs the payer and benefit pathway, auth number, start and end dates, sessions approved versus used, approved dose and frequency, the reauthorization trigger date and status, assessment due dates (such as PHQ-9 rechecks) and the patient’s next scheduled appointment. That last field is what turns a list into a control.
When Should A Spravato Reauthorization Start?
We open the packet at 30 days or 6 sessions remaining, submit by 14 days or 4 sessions remaining, and escalate to a named operations owner if either deadline slips. Payer turnaround is too variable to run thinner buffers.
Can We Just Track Authorizations In Our EHR?
Partly, sometimes. Many EHRs store auth numbers and dates but don’t decrement sessions from completed visits or warn you when a booked appointment falls outside the auth, and those are the two behaviors that actually prevent lapses. Test what your system actually does. Don’t go by the field labels.
What Happens If We Treat A Patient After The Authorization Expired?
The claims typically deny as not authorized. Some payers will consider retro-authorization or an appeal with good cause, but there’s no guarantee of approval, and under buy-and-bill the drug cost for denied sessions is yours. Preventing a lapse is much cheaper than appealing one.
How Does Authorization Tracking Connect To Scheduling?
The lapse always happens at the calendar-authorization intersection: appointments keep generating whether or not the auth is alive. Good tracking checks every booked session against auth end date and sessions remaining at booking time, which also protects the twice-weekly induction cadence payers expect to see at reauthorization.
When The Spreadsheet Stops Keeping Up
An Automation Program builds this tracker into the systems your team already uses: sessions counted from completed appointments, a warning when a booking falls outside an authorization, and expiring auths in front of the person who owns them. It’s $5,000, or 5 monthly payments of $1,000, with a staff walkthrough and 30 days of fixes after go-live, and the custom software page shows a live scheduler built for an interventional psychiatry workflow. If denials have already piled up, see our billing and A/R recovery prices.