Spravato Operations Series
Spravato Authorization Tracking: How to Make Sure No Auth Ever Lapses
The fields that matter, why spreadsheets fail at scale, the escalation cadence that catches expiries early, and what purpose-built tracking looks like.
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 did not 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. It is the single highest-leverage revenue control in an esketamine program, because a lapsed auth costs you the visit, the staff time, and — under buy-and-bill — the drug itself. The full authorization lifecycle is covered in our prior authorization playbook; this page is 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 pharmacy benefit, because reauthorization may live on the pharmacy side.
- Authorization number, start date, end date — the end date is the field programs most often fail to 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 — treating outside the approved 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 for renewal, such as PHQ-9 rechecks at roughly 4-week and 8-week marks and on a maintenance cadence, so the response evidence exists before the reauth asks for it.
- Next scheduled appointment — the field that turns the tracker from a list into a control, because it lets you flag any booked session that would land after the auth ends or beyond 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–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. They are how programs at forty patients quietly donate sessions to payers.
The Escalation Cadence
Whatever tool you use, the cadence is the control. Ours:
- 30 days / 6 sessions remaining: Auth flagged; reauthorization packet opened; assessment scores confirmed current or a recheck scheduled.
- 14 days / 4 sessions remaining: Reauth must be submitted. If it is not, the flag escalates from the auth owner to the practice’s operations lead — a named person, not a queue.
- 7 days / 2 sessions remaining, no approval on file: Payer follow-up call logged; the clinical team is warned; upcoming appointments are reviewed for coverage risk before they occur, so any treat-versus-hold decision is made deliberately, with the financial conversation had in advance — not 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 is 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 Anthem, Providence, and 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 booked appointment that would fall outside an auth’s date range or session count is flagged the moment it is booked — the system looks forward, not backward.
- Deadline surfacing, not deadline storage: Expiring auths appear in front of the owner on the cadence above; 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 — readable by the front desk at booking time, not just by the biller at claim time.
You can build a disciplined manual version of this and it will work until volume breaks it. When it does, this is exactly the class of tooling we build for practices — see custom software and automation, where you can watch a live scheduler built for an interventional psychiatry workflow. And if the leak has already reached the claims side, our revenue cycle management team works the denial and appeal end while the tracking gets fixed upstream.
How Many of Your Active Auths Expire in the Next 45 Days?
If you cannot answer in thirty seconds, that is the gap. We build and run authorization tracking for interventional psychiatry programs.
Common Questions
What fields should a Spravato authorization tracker include?
At minimum: payer and benefit pathway, auth number, start and end dates, sessions approved versus used, approved dose and frequency, reauthorization trigger date and status, assessment due dates (e.g., PHQ-9 rechecks), and the patient’s next scheduled appointment. The last field is what turns a list into a control.
When should a Spravato reauthorization start?
Our standing rule: 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?
Sometimes partially. Many EHRs store auth numbers and dates but do not decrement sessions from completed visits or warn when a booked appointment falls outside the auth — which are the two behaviors that actually prevent lapses. Verify what your system genuinely does rather than what the field labels imply.
What happens if we treat a patient after the authorization expired?
The claims typically deny as not authorized. Some payers consider retro-authorization or appeals with good cause, but approval is never assured, and under buy-and-bill the drug cost for denied sessions is yours. Prevention is dramatically cheaper than appeal.
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.