The two-week notice is sitting on your desk, still warm from the printer. Your B-tech, the one who ran the alignment rack and three of this week’s drop-offs, is leaving for the dealership across town. You shake his hand, you mean it, and then you walk back to the office and realize you have no idea how many open tickets have his name on them. His login still works. His phone still gets the customer texts. And nobody has written down what happens to the half-finished brake job on the lift in bay three.
That gap is where shop management software quietly saves you or quietly burns you. A departure is messy enough on the floor. It should not also leave a live login, orphaned jobs, and a customer wondering why nobody called them back.
The Day Notice Lands: Freeze Nothing, Note Everything
Your first instinct might be to yank the departing tech’s access on the spot. Resist it for working techs who gave honest notice. You still need the work done. What you do need is a clear snapshot. The cleanup starts with knowing exactly what is attached to that person inside your shop management software.
- Pull every open job assigned to the departing tech and write down the count. Say there are seven active tickets and two waiting on parts.
- Flag any job where that tech is the only one who knows the story, like the intermittent no-start that only acts up cold.
- Note which customers have been texting that tech directly if your system routes messages by assigned advisor.
- Check whether that person holds any admin-level permissions beyond their job. A tech who can edit labor rates or void invoices is a bigger cleanup than one who just clocks jobs.
If you have never set those permission levels deliberately, that is the real lesson here. Our breakdown of who can see the numbers and how to set user roles is worth a read before your next hire, not after your next resignation.
The Final Two Weeks: Hand Off Work, Not Just Keys
The window between notice and last day is when jobs quietly get stranded. A realistic example: a tech leaves with four cars mid-repair, and because nobody reassigned them in the software, two sit an extra day while the shop figures out who owns them. At a loaded cost of a few hundred dollars a day in bay time, that stall adds up fast.
- Reassign open tickets to the techs who will actually finish them, inside the software, so the job board reflects reality instead of a name that is leaving.
- Move the two parts-hold jobs to whoever will chase the supplier, so the follow-up call does not vanish.
- Make sure any customer-facing updates now come from the shop or the new assigned tech, not a person who will be gone Friday.
- Document the weird ones. A two-line note in the ticket about the cold no-start is worth more than a verbal handoff that nobody remembers.
This is also a good moment to look at how work actually flows through your bays. If reassigning four jobs feels like detective work, the problem is bigger than one departure. Our piece on shop workflow management covers how to keep the job board honest even on a normal week.
The Last Day: Close the Access, Keep the Record
This is the step most owners skip, and it is the one that bites months later. When someone walks out the door, their ability to log in should walk out with them. Not next week. That day.
- Deactivate the login at end of shift. Do not delete the account outright, because their name is attached to historical jobs and invoices you may need.
- Confirm they can no longer receive customer texts or portal messages routed to their old assignment.
- Revoke any payment, refund, or invoice-void permissions immediately, even if you trust the person. This is about clean books, not suspicion.
- If they used a shared shop tablet, change the device passcode and any saved logins.
Deactivating instead of deleting matters for one simple reason. Six months from now a customer calls about a comeback, and you need to see who did the original job. A deleted account can turn that history into a blank. For more on keeping those records intact, our year-end data hygiene checklist walks through the cleanup that keeps your history usable.
After They’re Gone: The Quiet Follow-Up
A week or two out, the dust settles and a few loose ends surface. This is the cleanup pass that separates a smooth transition from a slow leak.
- Audit the reassigned jobs. Did all seven close out, or is one still sitting in limbo under nobody’s name?
- Watch for customers who only ever dealt with the departed tech. A short note from the shop keeps that relationship from leaving too. Say a long-time customer booked only when that tech was on, worth a few hundred dollars a year in steady work. A simple call protects it.
- Review the permissions you just revoked and ask whether anyone else is holding access they do not need. A departure is a free excuse to tighten the whole list.
- Reassign any recurring tasks, like fleet check-ins, that were silently living on one person’s plate.
Done right, this whole cycle is maybe twenty minutes of software work spread across two weeks. Done wrong, it is a live login nobody closed and a customer who felt forgotten. The difference is having a system where a person, their jobs, and their access are all in one place instead of scattered across a whiteboard, a group text, and a phone that just left the building.
Frequently Asked Questions
Isn’t deactivating a login overkill for a tech who left on good terms? It has nothing to do with trust. An open login is a loose end for your records and your customers, no matter how the person left. Deactivating cleanly also protects the tech, since nothing done under their name after they leave can land on them.
Why not just delete the account and start fresh? Because that person’s name is tied to every job and invoice they ever touched. Delete it and you risk losing the service history behind comebacks, warranty questions, and customer calls months later. Deactivate to close access, but keep the record intact.
My whole handoff lives on the whiteboard and a group chat. Does software really change this? It does when the job board, assignments, customer messages, and user access all sit in one platform instead of three. See how DriveLine keeps a shop’s work and access in one place so a resignation becomes a twenty-minute cleanup instead of a two-week scramble.