How to Recover When Your Star Rad Tech Gives Two Weeks Notice

I was sitting in my office at Mercy Regional, going through routine hiring paperwork, when Sarah walked in with that specific look. Composed. Apologetic. And carrying a resignation letter.

Sarah had been with us for seven years. She was the tech every difficult case got assigned to. New people trained with her. Other departments requested her for procedures. She covered absences without complaining. She actually cared about the quality of the images we produced.

My first instinct was to panic. My second was to ask her to stay—significantly more money, better schedule, whatever she wanted. I didn't panic-counter-offer though, and looking back, that was the right call. This essay is about what happened after that moment, and what I learned about actually recovering when you lose someone who matters.

The First 24 Hours: Breathing Room Before Chaos

Here's what I did, and what you should do immediately:

Immediately contact your director and HR. Don't sit on this. Let them know before they hear about it in the break room. You need resources aligned before staff morale starts spiraling. One tech leaving turns into three if people think the department is sinking. Move fast on messaging.

Call a team meeting—same day or next morning. Before rumors start, be direct: Sarah's moving on, we'll handle this professionally, here's what happens next. I said something like: "I want you to hear this from me. Sarah accepted a position elsewhere and will be with us through [date]. This means [specific impact]. Here's how we're covering, and here's how we're supporting the transition."

Transparency kills panic. Silence creates it.

Assess your actual capacity immediately. Not tomorrow. Today. How many shifts does Sarah cover? What specialties does she carry? Which procedures does she primarily tech? What knowledge lives in her head that isn't documented? I made a quick audit with my senior staff: Sarah was 16% of our CT volume, 22% of our interventional procedures, and literally the only person trained on our legacy fluoroscopy machine.

That's a problem.

Secure her remaining time. Don't assume she'll just finish out two weeks and leave on good terms. I had one tech—excellent person—who mentally checked out the day she gave notice. Someone else checked out but stopped showing up to team meetings. Set expectations: We appreciate your commitment, we're going to do this professionally, we expect the same from you. Make it clear that burning bridges affects references and industry reputation (which it does).

The Knowledge Transfer Problem Nobody Plans For

This is where most departments fail.

Sarah knew things that weren't written down. The trick for getting clean images on the 75-year-old with scoliosis who usually comes in Thursdays. Why our IR suite's power injector sometimes acts weird and what you do about it. Which radiologists prefer which patient positioning. The workaround for the PACS issue we've never officially fixed. Relationships with vendors. Subtle cues about which patients are anxious and need extra time.

That knowledge walks out the door unless you actively prevent it.

Within 48 hours, schedule knowledge-transfer sessions. I blocked off four hours—two separate two-hour sessions—with Sarah and my senior techs. We documented specific workflows:

Complex procedures and her approach
Difficult patient populations (elderly, anxious, bariatric, etc.) and how she handles them
Equipment troubleshooting
Relationships with referring physicians
Quality standards and how she maintains them
Any workarounds or best practices unique to our department

I had someone documenting this in real time. If you don't write it down while it's being explained, it's lost.

Get her to train the next person before she leaves. Not after. If she's leaving on a Friday, the new person should shadow her for at least three of those days. Better to have two weeks of structured overlap than to try to teach someone from notes.

Record specific procedures if possible. Some hospitals are starting to create video documentation of complex procedures or equipment workflows. It's not a replacement for hands-on training, but it's better than nothing. I had Sarah walk through fluoroscopy troubleshooting while someone recorded—just on an iPad, not fancy. That video has been invaluable for training.

The Retention Conversation You're Not Having

Here's the hard part: you need to know why she's leaving.

Not so you can counter-offer. That rarely works. But so you can understand what you're actually broken at, and whether it's fixable.

I sat down with Sarah privately and asked directly: What would need to be different for you to stay?

She was honest. The schedule was inflexible—she'd been requesting four-day weeks for a year and got turned down every time. The pay was decent but hadn't increased meaningfully in five years. She felt undervalued—not dramatically mistreated, just... not appreciated. She'd gotten offers for better-paying positions with actual flexibility, and she was going to take one.

None of these were surprises. I'd seen the requests. I'd sent the salary emails to finance showing we couldn't match external offers. I'd watched us deny scheduling flexibility for policy reasons while losing staff.

Was I surprised she left? Not really. Should I have been? Yes.

The point is: ask. Listen. Don't argue. Don't immediately start negotiating. Just understand what you failed to do, and whether it's a failure you can fix.

Here's what I learned: the department's salary band hadn't been adjusted in three years despite inflation. Our schedule approval process required director sign-off, which meant flexibility was rare. We'd taken her for granted—assumed someone this good would just stay.

Immediate Staffing: The Triage Phase

Okay, she's leaving. You've got two weeks. Here's how to survive it:

Renegotiate shifts immediately. Can anyone pick up extra hours? Can you reduce non-essential procedures temporarily? Can you call in your pool of per-diems? I reached out to three former per-diems and offered premium rates to come back for 2-3 weeks. One said yes. We survived.

Bring in temporary staffing early. Don't wait until her last day. Bring temp techs in during her last week so they can at least observe and get oriented, even if they're not fully productive. I booked two agency techs for weeks 2-4 after her departure. Yes, it was expensive. But canceling procedures is more expensive.

Protect your core staff from overload. This is where managers fail. You cannot ask your remaining good people to absorb Sarah's entire load. That's how you lose two and three. I made a hard decision to reduce our elective procedure volume by 18% for 4 weeks. It meant rescheduling some outpatients, but it meant my remaining staff didn't burn out. That was worth it.

The Exit Interview That Actually Matters

Don't skip this. Do it properly.

I had HR conduct a formal exit interview, but I also sat down with Sarah separately and said: I want to understand what we got wrong, so we don't do it again.

She told me:

The salary compression was real (we were paying new grads only 12% less than her after 7 years)
The schedule inflexibility felt personal, even though it wasn't
She'd asked for professional development support (continuing ed, conferences) and never got it
She felt like her expertise wasn't leveraged—we'd kept her doing general work instead of building her into a specialized role

Some of this was about me. Some was about the institution. All of it was actionable.

The Recovery Phase: Weeks 2-8 After Departure

Once she's gone, the real work starts.

Rebuild your team's confidence. My department was demoralized. We lost our best person and had to reduce service volume. I made sure to publicly acknowledge what Sarah contributed, celebrate the team's ability to adapt, and articulate a path forward. I said: We're covering. We're surviving. And we're going to hire someone excellent to fill this role. This is temporary hardship.

Accelerate hiring. Don't move slowly. Your remaining staff is watching to see if you're serious about replacing capacity. I restructured our posting that day, increased the salary band by 8%, added scheduling flexibility to the job description, and committed to a three-week hiring timeline. We offered the position within 21 days.

Train your new hire aggressively. Bring them in during overlapping time with someone stable. I paired our new hire with my second-most-experienced tech for the first month. Not a trial by fire. An actual partnership.

Conduct stay interviews with your remaining strong people. Ask them directly: What would you need to stay and thrive? Don't make promises you can't keep, but actually listen and respond. I did these with my three senior staff. Turns out two of them also wanted better scheduling flexibility and both wanted professional development support. I made those changes immediately—and it mattered.

The Structural Changes That Prevent This Again

Here's what I changed after losing Sarah:

Salary bands: We benchmarked against regional competitors and actually adjusted pay. No more letting inflation erode competitive advantage.

Schedule flexibility: We created clear policies for 4-day and 3.5-day options. If someone wanted it and coverage allowed, we said yes.

Professional development: We budgeted for continuing education and actually encouraged certifications. Sarah wanted to pursue advanced credentials. I should have supported that.

Retention check-ins: I started having brief one-on-ones every quarter with key people. Not formal reviews. Just: How are you doing? What would make this better? Early warning system.

Specialization opportunities: Instead of keeping Sarah as a generalist, I should have helped her build a specialty practice. More fulfilling work, harder to replace, better for the department.

The Real Lesson

Losing Sarah was painful, but it was also a mirror. The department had gotten complacent. We weren't investing in people; we were relying on them. We weren't competitive; we were assuming loyalty would cover it.

Two weeks of chaos, four weeks of temporary staffing costs, reduced procedure volume—all of that was expensive. But less expensive than what I should have paid attention to: that losing excellent people is usually a management failure, not a market failure.

The next time someone gives notice, you're going to panic. That's normal. But do the work I outlined here. Transfer knowledge. Understand why they're leaving. Protect your remaining team. And then—this is the key part—actually fix the things that made you lose them.

Because the person walking in with that resignation letter is always avoidable. You just have to decide to avoid it while they're still there.