ClinicOps / Briefings / Operations Guide
Operations Guide · Published Jul 27, 2026
Your Practice Manager Just Quit: The 30-Day Operations Rebuild Plan
When the person who ran everything walks out, the panic is real, but the fix is a sequence, not a scramble. Stabilize, capture, systematize, then hire. Here is the 30-day plan, and how to make sure the next departure is a transition, not a crisis.
Jareer Ali·
Research & field notes·
10 min read
When a practice manager quits, work the problem in order: week one stabilize the things that stop money or care, week two capture what only she knew, week three turn that into systems, week four hire or redistribute. The real risk is not the empty chair, it is undocumented knowledge, and documenting the role is what turns the next departure into a transition.
Key takeaways
- The danger is not the vacancy, it is how much ran out of one person's head with nothing written down.
- Work in sequence: stabilize, capture, systematize, hire. Reorganizing before you stabilize makes things worse.
- Week one is triage: protect payroll, prior auths in flight, credentialing deadlines, and every login.
- Capture the role before you decide how to fill it, so you hire against the real job, not a guess.
- Documenting operations protects the manager and the practice both. It frees her and it removes the single point of failure.
A practice manager leaving feels like the floor dropping out, because for most independent practices, she was the floor. She knew the payer quirks, the logins, the deadlines, the workarounds, and almost none of it was written down. That last part is the problem, and it is worth being precise about whose problem it is: it is the practice's, not hers. She did her job. The practice just never built a system that could survive her doing it somewhere else.
What actually walked out the door
Before the plan, understand the loss clearly, because it tells you what to protect first. When an undocumented manager leaves, what you lose is not a set of tasks, those you can see. What you lose is the invisible layer: which payer needs which form, where the Medicaid login lives, when the malpractice renews, which vendor to call, the small daily judgments that kept things from slipping. Front-office roles turn over often, and every departure that was never documented forces the practice to re-learn things it already paid to learn once. That is the real cost, and it is why the first job is not to replace her but to recover and protect what she knew before it fades. Read the weeks below as a recovery operation, in strict order.
Week 1: stabilize
Do not reorganize anything. Find and protect the things that stop money or care if they lapse. Payroll runs on schedule, no matter what. Prior authorizations in flight get identified and owned, because an auth that expires now is a procedure cancelled and revenue lost. Credentialing and CAQH deadlines in the next 60 days get found and covered. Every login, payer portals, the clearinghouse, the practice management system, banking, gets located and secured, because a lost login is a wall you hit at the worst moment. This week is triage. The only goal is that nothing critical slips while you catch your breath. Pair it with the prior auth tracker so in-flight auths are visible immediately.
Week 2: capture
Now get the invisible knowledge onto paper before it evaporates. Walk every recurring rhythm of the practice and write it down: the daily, weekly, and monthly tasks and who touched them; the deadlines that repeat, credentialing, CAQH re-attestation, license and DEA renewals, insurance filings; the logins and where they live; the vendor and payer contacts and what each is for. If the departing manager is reachable for even one exit conversation, this is what to ask about, not opinions, but the concrete where-is-it and when-is-it details. The recurring tasks tracker is built to hold exactly this, so you are capturing into a structure rather than a pile of notes.
Trackers and SOPs to capture the role into a system, so nothing lives in one person's head again.
Get the free Rescue KitWeek 3: systematize
Captured knowledge in a document still depends on someone remembering to read it. Turn it into systems that run on their own. Put the recurring deadlines into a tool that reminds an owner automatically rather than waiting to be checked. Turn the prior auth and credentialing workflows into pipelines with owners and alerts, so the process pushes work forward instead of relying on memory. Write short SOPs for the handful of procedures that matter most, so any capable person can run them. The point of this week is to convert a person's habits into a practice's system, which is the difference between knowledge that leaves and knowledge that stays. The prior auth handoff SOP and the submission checklist are ready-made pieces of this.
Week 4: hire or redistribute
Only now, with the role visible on paper, decide how to fill it. Sometimes the honest answer is that the job was really several jobs bolted together, and the pieces fit better across existing staff plus a system than into one new hire. Sometimes it is a clear full-time role, and now you can hire against an accurate description instead of a vague one. Either way, onboard the person or the redistribution against the systems you just built, not against tribal memory, using the onboarding checklist so week one is structured. If the gap is real but a full-time manager is not the right answer, fractional operations help is one way to cover the systems work without a salaried hire.
Make the next departure a non-event
Here is the part that changes everything, and it is worth saying plainly because it is easy to misread. Documenting a manager's role does not make her replaceable. It makes her safer and the practice stronger at the same time. A manager backed by documented systems can take a real vacation without the practice holding its breath. She is not blamed for a slip that happened while she was out, because the system, not her memory, was carrying the load. She is not trapped as the single point of failure, which is exhausting for the person in that seat. And the practice is no longer one resignation away from chaos. The best time to build this was while your last manager was still here. The second best time is now, before the next one gives notice. When operations live in a system instead of a person, a departure becomes a scheduling problem instead of an emergency, and that protects everyone, most of all the manager who currently keeps it all from slipping.
Where to go next
- Free Prior Authorization Tracking Spreadsheet (Sheets, Excel, and ClickUp) live
A free prior authorization tracking spreadsheet for Sheets, Excel, and ClickUp. One board per.
- Recurring Tasks Every Practice Forgets: Calibrations, Contracts, Renewals (Template) live
A free recurring tasks tracker for a medical practice: every daily-to-annual duty with an owner.
- Train Your Front Desk to Run Prior Auths Without You: The Handoff SOP live
The handoff SOP that moves prior auth from the physician to a trained front-desk owner: who.
Find the leak before you fix it
Two ways to start, both free.
Run the free Rescue Kit and its tools yourself, or book a 20-minute Leak Audit where we put a real number on what this is costing, using your own volume. A diagnosis, not a pitch.
Frequently asked questions
My practice manager just quit. What do I do first?
Stabilize before you rebuild. In week one, find and protect the things that stop money or care if they lapse: payroll, prior auths in flight, credentialing deadlines, and payer logins. Do not try to reorganize anything yet, just keep the critical items from slipping.
How long does it take to recover when a practice manager leaves?
Plan for about 30 days to get from crisis to stable: a week to stabilize, a week to capture what only she knew, a week to turn that into systems, and a week to hire or redistribute. The timeline is shorter the more was already written down.
What is the real risk when a manager leaves?
Not the empty chair, the empty documentation. The danger is how much ran out of one person's head with no written trace. When the role was never documented, her knowledge walks out with her, and that is the practice's gap to close, not her fault.
Should I hire a replacement immediately or redistribute the work?
Capture the role first, then decide. Once the tasks, logins, and deadlines are written down, you can see whether the job is one full-time role or several pieces that fit existing staff. Deciding before you can see the whole role usually leads to a bad hire.
How do I keep this from being a crisis next time?
Document the operations while someone is still in the seat. When the recurring tasks, deadlines, and logins live in a system instead of a person, a departure becomes a transition instead of an emergency.
What should I document before anyone quits?
The recurring task calendar, every login and where it lives, the credentialing and CAQH deadlines, the prior auth workflow, and vendor and payer contacts. These are the things that hurt most when they are only in someone's memory.
Doesn't documenting her job just make her replaceable?
The opposite. Documented systems protect the manager: she can take a real vacation, is not blamed when she is out, and is not trapped as the single point of failure. They make the practice resilient without making her disposable.
- CAQH ProView, provider re-attestation required about every 120 days to keep an enrollment application current with participating payers. proview.caqh.org