It is the most common trigger event we see in independent practices, and the pattern is remarkably consistent: the resignation itself is survivable — it’s the improvised thirty days afterward that do the damage. Here is how to spend them instead.
First, stabilize the mechanics — this week
Before any conversation about replacement, make sure the things with dates on them cannot fail quietly. Payroll runs. The schedule publishes. Claims go out and deposits get posted. Vendor payments that keep the lights on stay current.
Then handle access: every system the administrator alone could reach — bank portals, payer portals, the practice-management system’s admin account, the alarm codes — needs a second credentialed person before their last day. This is dull work, and it is the difference between an orderly transition and discovering three weeks later that nobody can reset the billing system password.
Map what the role actually was
Job descriptions describe the role as designed. What you need is the role as lived — and in most practices, a long-tenured administrator has quietly absorbed responsibilities nobody wrote down: the payer relationship they alone maintained, the informal HR mediation, the report only they knew how to pull.
Spend the notice period building that real map. Have them walk the calendar of a typical week and a typical month-end. Write down every recurring task, who it touches, and where the instructions live (usually: nowhere). You are not just documenting a job — you are surfacing the single points of failure that were previously invisible because they never failed.
Resist the fast hire
The instinct under pressure is to post the job immediately and hire the most plausible résumé within the month. We’d counsel against it, for a simple reason: you are about to hire for a role you haven’t defined yet, under time pressure, evaluated by people who’ve never done the job themselves.
The fast hire tends to fail in one of two expensive ways: an under-qualified candidate inherits an undocumented role and drowns politely for a year, or a capable candidate inherits a mess that was never their fault and leaves within one. Either way you are back here, twelve months older.
Decide the model before you hire the person
The vacancy is also an opportunity most practices never get: the chance to ask whether the old shape of the role was right. Three questions sort it quickly:
- Was the role executive or administrative? If your administrator was really running the business — finance, staffing, payers, strategy — you may need a stronger role than the one that just emptied, or an executive layer above a lighter one.
- What should be systematized rather than re-hired? Some of what lived in the administrator’s head belongs in written systems and standing rhythms, not in the next person’s head.
- What does the practice need for the next five years — not the last five? Growth, a new site, a partner transition: the right hire depends on where you’re going.
Only when those answers are written down is a job posting worth publishing. Interim coverage — internal or outside — buys you the time to answer them properly, and it is almost always cheaper than the wrong permanent hire.
Where this goes wrong
The failure pattern is rarely dramatic. It’s drift: the office manager “temporarily” absorbs the role and quietly burns out; billing follow-up slips because no one owns it; small vendor and staffing decisions stall; and six months later the practice is explaining a cash decline that started the week of the resignation. If the numbers are already moving, the problem has graduated from a staffing question to a stability question — treat it as one.
If you want help
Covering this exact gap is part of what AHA does — as a defined transition project when the practice is otherwise steady, or as standing fractional leadership when the role turns out to have been holding up more than anyone knew. Either way, a first conversation is confidential and costs nothing: tell us where things stand.