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 turns a list into a control, because it catches a session booked after the auth runs out. Check the tracker at 30, 14 and 7 days out.
Why Spravato Sessions Go Unpaid
When a Spravato program writes off sessions, it’s almost always the same story: the patient was doing well, the schedule kept generating appointments, and the authorization, approved months earlier for a fixed number of sessions or date range, ran out unnoticed. The clinic had a biller and a spreadsheet. It lacked a join, because 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 pays back the most of any revenue control, because a lapsed auth costs the visit, the staff time and, under buy-and-bill, the drug itself. Our prior authorization playbook covers the full lifecycle. This page covers only tracking mechanics.
The Fields That Matter
A workable tracker carries, per patient and payer:
- Payer and plan, including whether the drug rides the medical or the pharmacy benefit, since 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 miss at approval time.
- Sessions approved vs. sessions used, decremented automatically from completed appointments, not by hand when someone remembers.
- Approved dose and frequency: treating outside those parameters can void an otherwise live auth.
- 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 response evidence is on file when the reauth asks for it.
- Next scheduled appointment: the field that turns a list into a control, because it catches 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
Spreadsheets are passive. Nothing happens as an end date approaches unless someone opens the file, sorts the column and does the arithmetic, 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 where calendar and authorization meet, and the spreadsheet only holds one side. No sheet will 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 donate sessions to payers.
When To Escalate An Authorization Delay
Whatever tool you use, a fixed schedule of checks protects you. Ours:
- 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, 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. Review upcoming appointments for coverage risk in advance, so any treat versus hold decision is made on purpose, with the financial conversation held early 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 everything else depends on it.
What An Authorization Tracker Should Show
The version 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 from 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 anyone touching a counter.
- Schedule aware warnings: Any appointment that’d fall outside an auth’s date range or session count gets flagged when it’s booked. The system looks forward, not back.
- Deadline surfacing, not deadline storage: Expiring auths reach the responsible person 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, 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?
It needs, at minimum, 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 for 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 two behaviors prevent lapses. Test what your system does rather than going 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 approval isn’t promised, and under buy-and-bill the drug cost for denied sessions is yours. Preventing a lapse costs far less than appealing one.
How Does Authorization Tracking Connect To Scheduling?
The lapse always happens where calendar and authorization meet: 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, 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 their owner. It’s $1,250 a month for four months, or $5,000 total, 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.
About The Author
Ryan Berg is the founder of AdvanceAPractice. He has run the business side of medical, dental and behavioral health practices for more than 16 years, including claims work at OHSU and operations at a multi provider psychiatry practice.