The card goes around the office on a Thursday. Someone signs it twice by accident, there's a grocery-store cake in the break room, and by Friday the paralegal who's been with you six years is gone to a firm closer to home. Good terms, warm goodbye, the whole thing.
Then nobody thinks about it again. Two months later you're glancing at the login history on your client portal, and there's her name, still active, still able to open every file she ever touched. Her email still forwards. Her passcode still opens the front door after hours.
Here's the uncomfortable part. For a practice that holds confidential client files, a privileged medical history, a tax return, a signed settlement, a login that outlives the job isn't a loose end. It's a live exposure, and in most offices nobody actually owns the job of shutting it off.
Why the login outlives the person
The farewell gets planned. The access almost never does, because closing it is split across too many people and belongs to none of them.
Your office manager handles the final paycheck. IT, if you have IT, waits to be told. The practice-management vendor needs someone to log in and deactivate the seat. The phone system is its own little kingdom with its own admin. Each person assumes another one already pulled the plug.
It's the same reason the small stuff slips in a busy practice. Everyone's chasing billable work, the referral that came in Tuesday, the filing due Friday. Offboarding a login has no deadline screaming at anyone, so it loses every time to the thing that does.
So the account just sits there. Not out of malice, usually. It sits because revocation is everybody's job, which is a polite way of saying it's nobody's.
Keep one living list of what each role can touch
You can't shut off access you can't name. The fix starts with a single document, kept current, that maps every role in the office to every system it can reach.
Not every person, every role. A front-desk hire and the next front-desk hire touch the same set of tools, so write it once per seat and reuse it. When someone new starts, you hand them the role's list. When someone leaves, you work the same list backward.
- Email and calendar, including any shared inbox or auto-forward rules
- The client portal and document storage, cloud drives, shared folders
- Practice-management software, your case, patient, or client system
- The phone system, voicemail, and any texting line
- Billing and payments, the card processor, the bookkeeping login
- Building access, key fobs, alarm codes, and physical keys
- Any password manager (a shared vault that stores logins) and what's inside it
Keep it boring and complete. A spreadsheet is plenty, and fancier isn't better here. The only rule that really matters is that the list changes the same day a tool gets added or dropped, so it never drifts from what's actually true in the office.
The same-day revocation checklist
The moment someone gives notice, the clock starts. Not their last day, notice day, because the window you actually care about is the one where goodwill might already be gone.
Build a short checklist you run every single time, so nothing rides on memory. It looks something like this:
- Reset the email password and turn off any forwarding, then set an auto-reply pointing clients to whoever's covering.
- Deactivate the practice-management seat and confirm the account shows inactive, not just logged out.
- Pull portal and shared-drive access, and check for files synced to a personal device.
- Remove them from the phone system, voicemail box, and any texting line.
- Revoke building and alarm codes, and collect fobs and keys.
- Rotate any shared passwords they knew, especially the ones in a shared vault.
- Reassign their open work and client relationships to a named person.
Assign one owner to the whole checklist. One person signs off that every box is checked, even if three different people did the actual clicking. That single point of ownership is the thing that's usually been missing.
Where software helps, and where it can't
This is the part worth being honest about. A fair amount of this can be automated, and a stubborn part of it can't.
If your logins run through single sign-on (one account that opens several apps at once), switching off that one account can close many doors in a single step. A simple workflow tool can email the checklist to the owner the instant a departure gets logged, track which boxes are done, and nag until the last one's closed. That turns a thing you hope happens into a thing you can watch happening.
What software won't do is know about the one-off accounts. The vendor portal only the bookkeeper ever logged into. The personal email someone used to share a file in a pinch. The password taped inside a drawer. Automation works the list you give it, so the list has to be real, and keeping it real is still human work.
Be careful with the confident-sounding tools, too. An AI assistant can draft your checklist and point out gaps you'd miss, but it can't confirm a seat is truly deactivated inside a vendor's system. Someone still has to open that system and look.
Worth doing this week
You don't need a project for this. You need an afternoon and a short list.
- Write down every system a departing employee could reach, by role, in one document you'll actually keep updated.
- Turn the backward version of that list into a revocation checklist, and name one owner for it.
- Run the checklist against your last two or three departures and see what's still open. You'll probably find one.
- Add a single trigger: notice given means the checklist starts today, not on the last day.
- Put a recurring reminder on the calendar to review active logins each quarter, the way you already review renewals and deadlines.
Access should end when the employment does, on the same day, every time. If building that habit feels like one more thing you don't have time to babysit, that's exactly the kind of quiet, repeatable process we help Massachusetts practices set up so it runs without you having to remember it.