How to Retain Rad Techs During Their First Year

I have a spreadsheet somewhere from 2015 that I still pull out when I'm talking to imaging directors about retention. It's got every tech who left our department that year, their start date, and their exit date. Looking at it now, the pattern is almost embarrassingly obvious.

Seventy-three percent of the technologists we lost that year left within their first year.

That was the year I actually looked at the data and realized we weren't running a radiology department. We were running a constant recruitment machine. We'd hire someone, they'd be gone in six months, we'd spend $18,000 recruiting and training their replacement, and then that person would leave too. Meanwhile, our existing staff was burning out from coverage gaps and constant training.

The problem wasn't that we were hiring the wrong people. The problem was that we had no idea how to keep them.

Over the next five years, I systematically changed almost everything about how we approached first-year technologists. And you know what happened? We went from 73% first-year turnover to 28%. That's the difference between chaos and stability. That's the difference between a department that feels sustainable and one that feels like a crisis.

If you're a hospital leader, an imaging director, or anyone involved in hiring radiology technologists, I need you to understand something: your new hire's first year is the make-or-break period. Everything that happens during those twelve months determines whether they stay for a decade or leave in six months.

Here's exactly what changed things for us.

The First Week is Everything (And We Were Getting it Wrong)

Let me be honest about what we were doing wrong in 2015. We had new technologists show up at 6:45 a.m. on a Monday morning. They filled out paperwork for two hours. Then we threw them into the department with a senior tech as a shadow, usually someone who'd been asked to mentor as an add-on to their regular duties, usually someone with no training on how to actually mentor someone.

By Wednesday, the new tech would be expected to know where everything was, understand department workflow, and have started scanning. By the following week, they were mostly on their own with spot checks from whoever had time.

It was chaos. And I didn't even realize it was the problem because, from the department's perspective, it seemed fine. They got oriented. They started working. What else is there?

What we were missing is that the first week is when new technologists are figuring out if they belong here. Not technically. Technically, they're overwhelmed and trying to survive. Emotionally and psychologically, they're asking: Do these people like me? Is this department functional? Is this the right choice?

Here's what I changed: we restructured the entire first week.

Day one is no longer a paperwork morning. It's a department immersion. New tech comes in at the regular shift start time. First task: walk the department with the department manager (me or my assistant). Not a formal tour. Actual walkthrough. We're showing them where the bathrooms are, where the break room is, where they'll put their things, where the supply closets are, what each imaging suite is used for. We introduce them to everyone they'll be working with that day. We talk about the vibe and culture of the department. It's informal. It's human.

Days one through three are paired with their assigned mentor, and they're not scanning. They're observing. They're watching protocols. They're learning the rhythm of the department. We're showing them how we handle a rush. We're introducing them to our regulars—the patients who come in weekly, the doctors who work here regularly. We're being intentional about integration.

Day four and five, they might do their first scan under very close supervision. Not because they're ready. Because we're ready to see how they handle it.

Week two, we increase independence, but we're checking in constantly.

The result? New techs felt integrated immediately. They weren't a nervous outsider trying to figure out where the bathroom is. They were a person who belonged. And that psychological shift matters tremendously.

The Mentor Assignment Determines Everything

Here's the thing about mentorship in radiology departments: it's often accidental. You pair a new tech with whoever's available or whoever was decent at their last mentoring assignment. That's a missed opportunity.

In my department, mentor assignment became strategic. And I'm talking about real strategy.

We identified senior technologists who were excellent clinically but also genuinely wanted to mentor. Not people who could tolerate mentoring. People who actually wanted to help develop new talent. We gave them a structured mentorship framework—actual training on how to mentor someone. We clarified expectations: mentors were responsible for the new tech's development, and their performance reviews reflected that.

And here's the part that actually made a difference: mentors were released from some of their regular duties so they could actually mentor. Not as an afterthought. As a real job responsibility.

We'd typically assign a mentor for the first six months, with some check-ins extending into month nine. The mentor wasn't just answering questions. They were actively evaluating development, identifying gaps, celebrating wins, and building a relationship.

And then—this matters—we would formalize a transition. Around month six, we'd have a conversation. "You're doing well. You're going to transition off primary mentor support. Here's who you'll go to if you have questions. Here's how we're going to check in." It wasn't abrupt. It was planned.

New techs who had that structured mentorship stayed. The data is clear on this. We went from random mentorship to strategic mentorship, and retention literally jumped.

The 90-Day Reality Check (And Why It's Critical)

About ninety days in, something happens. New technologists go through what I think of as the reality crash. The initial adrenaline of being new wears off. The technical demands get real. The pace feels relentless. And sometimes—often—they start wondering if they made a mistake.

This is when we lose people. Not because they're not capable. Because nobody checks in.

We built a formal 90-day check-in into our process. Department manager—that was me—met with every new tech around day 85. We talked about how they were doing. How was the pace? Were they getting support they needed? What was harder than they expected? What was easier?

And here's what was important: we actually listened. If something was genuinely broken, we fixed it. If a mentor wasn't working out, we made a change. If the pace was genuinely unsustainable, we adjusted.

Most new techs just wanted someone to acknowledge that day ninety was hard and that it was normal to feel overwhelmed. That conversation alone made a difference. It said, "We see you. We know this is hard. You're still welcome here."

We also used this check-in to identify people who weren't going to make it technically. Not because they were lazy. Some people get through school and training and realize they actually don't like this work. Better to identify that at ninety days than at six months. And honestly, when we had those conversations with compassion—"This might not be the right fit, and that's okay"—most people appreciated it.

The Onboarding Checklist That Actually Matters

I'll be honest: we had an onboarding checklist that was a disaster. It was 47 items long. It was checking boxes that didn't matter. "Completed tour of CT equipment." "Attended hospital orientation." Meaningless stuff that created the appearance of onboarding without actually developing a technologist.

We completely rebuilt it around what actually mattered for someone to be functional and successful in our department:

• Can they perform basic positioning and take diagnostic quality images (month one goal)
• Do they understand our infection control protocols and follow them consistently (week one)
• Can they communicate with patients in a way that reduces anxiety (ongoing, months 1-3)
• Do they understand the workflow and can they anticipate what's next (month two)
• Can they problem-solve when something doesn't go as planned (month three)
• Do they feel integrated into the team and know who to ask for help (week one)
• Can they handle the pace and complexity without showing signs of burnout (month three)

That's it. Seven things. And they weren't checkbox items. They were actually evaluated. A mentor would assess: Is this tech at this level? What do they need to get there?

The Culture Component (Which Everyone Skips)

Here's where departments really mess up with new hires: they focus on technical training and completely ignore culture.

A new technologist will tolerate an imperfect training if the culture is good. A new technologist will not tolerate perfect training if the culture is toxic. I've seen it over and over.

Your new techs are watching: Do senior techs respect each other? Is there backstabbing or support? When something goes wrong, is there blame or problem-solving? Are there cliques, or is the team actually inclusive?

New people are incredibly perceptive about this. And they decide fast whether they're in an environment where they can thrive.

The biggest single thing we changed around culture was how we handled mistakes from new technologists. Historically, if a new tech made a mistake, senior techs would get annoyed or judgmental. "That's not how we do it" was common. "That's a safety issue" was wielded like a weapon, even for minor deviations.

We completely shifted to a learning mindset. A new tech messes something up? We talk about it. "Here's why we do it this way. Here's why what you did created a problem." But it's not shame-based. It's educational. And it's clear that mistakes are expected while you're learning.

That shift—from blame to learning—changed the culture. New techs felt safe. They asked questions. They learned faster. And they stayed.

The Actual Numbers on Why This Matters

Let me break down the financial case, because every director understands this language:

We were losing one tech every 2-3 months in 2015. That's roughly 4-5 departures yearly out of a team of 22. Cost per hire-and-train cycle: $20,000. So we were spending $80,000-$100,000 just on turnover recruitment and training.

The coverage gaps from constant turnover meant we were paying $40,000-$50,000 yearly in overtime to cover shifts. And we weren't even covering all shifts, which meant referral loss and patient complaints.

After restructuring our onboarding and retention approach, we dropped to about 6-7 departures yearly, mostly retirements or people moving away (unavoidable turnover).

That $80,000-$100,000 in recruitment and training costs? It dropped to maybe $30,000. The overtime budget cut in half. And—this matters—our patient satisfaction scores on imaging improved because we had consistent, experienced staff.

The investment in better onboarding paid for itself in under a year.

What to Do Right Now

If you're a hiring manager or department leader reading this, here's what you can implement immediately:

Fix week one. Paperwork in afternoon if you have to, but spend the first day actually immersing new people in your department and your team.

Be intentional about mentorship. Don't just assign a senior tech. Actually select people who want to mentor, train them, and release them from other duties so they can do it well.

Schedule a 90-day check-in. Don't wait to see if new techs work out. Check in and actually listen.

Identify what actually matters for someone to be successful in your specific department, and build your onboarding around that—not around generic checklist items.

Look at your culture. New people are extremely sensitive to dysfunction. If your department is toxic, no amount of good onboarding saves people.

The rad tech shortage is real. But here's what's also real: many departments are losing people they could keep. The difference is intentionality. The departments retaining people are the ones doing this work deliberately.

Your new hires are an investment. Treat them like one.