Onboarding Your New Rad Tech: A 90-Day Plan That Prevents Early Turnover

You've finally hired your new radiology technologist. The interview process was exhausting, the background check is clean, and they're starting Monday. Everything should feel like a win.

Then why do so many of them leave before 90 days?

I've been on both sides of this equation. Early in my career, I was the new hire standing in the imaging department at 7:45 AM, confused about where to clock in, where the break room was, and what I was supposed to be doing first. My manager had hired me but seemed surprised I'd actually shown up. No tour. No buddy assigned. Just a vague directive to "shadow whoever's here" before I was thrown into unsupervised patient care within two weeks.

I left after five months.

Years later, as an MRI technologist and career coach, I've helped dozens of managers fix their onboarding disasters. The pattern is always the same: they hire talented people, fail to set them up for success, and then express genuine shock when those people start job hunting again.

Here's the truth: A bad onboarding experience doesn't just lose you one employee. It damages your reputation in a close-knit professional community. Rad techs talk. A new hire who felt neglected or unprepared will tell everyone in their network, and suddenly, your next job posting gets fewer applications.

The good news? Turnover in the first 90 days is almost entirely preventable. It takes planning, structure, and genuine investment from leadership. But the payoff—in retention, productivity, and department morale—makes it worth every minute.

The Pre-Arrival Phase: Your First Impression Happens Before Day One

Your onboarding process should start before your new rad tech ever walks through your door. Most departments skip this entirely, which is mistake number one.

Two weeks before their start date, send a welcome package. It should include:

• A personalized welcome letter from the department director (not a form letter)
• Your imaging department's handbook and specific protocols they'll need to review
• Parking information and campus map
• IT setup instructions—username, email setup, any required passwords they need to create
• The name, photo, and a brief bio of their assigned buddy/mentor
• A schedule for their first week, so they know exactly what time to arrive and what to expect
• A friendly note from that buddy introducing themselves

This single step transforms the narrative from "I hope this place isn't disorganized" to "They're actually prepared for me."

Schedule HR and IT appointments before they arrive. Nothing derails day one like sitting in a waiting room for three hours while IT creates your account. Have a point person responsible for these pre-arrival logistics. This isn't glamorous work, but it's foundational.

Assign one primary mentor at least a week in advance. This person should be:

• Technically skilled and current with your protocols
• Patient and able to communicate clearly
• Not drowning in their own workload (this is a problem with most buddy systems)
• Someone who remembers what it felt like to be new

Tell your mentor explicitly that mentoring is part of their job for the next 12 weeks, and acknowledge the time commitment. Many departments assign mentors but never give them credit or adjustment to their schedule, which guarantees they'll provide surface-level supervision while secretly resenting the burden.

Week One: Orientation and Integration

Week one should feel intentionally structured. Your new technologist is experiencing information overload and anxiety—structure makes that manageable.

Day One: Orientation and welcome. Block out at least four hours that morning with HR, IT, and your department director. Your new tech should:

• Meet their mentor in person before 9 AM
• Complete IT setup and credential access
• Review your department safety protocols and emergency procedures
• Get a thorough, unhurried tour of your imaging suite (not the five-minute version where nobody points out where the water fountain is)
• Meet at least 3-4 key team members by name
• Understand the schedule, break room protocols, call-in procedures, and basic department culture

By the end of day one, they should feel welcomed, oriented, and clear on expectations.

Days Two through Five: Clinical observation and shadowing. Your new rad tech should:

• Shadow the same mentor all week (consistency matters)
• Observe at least 2-3 different modalities or procedure types relevant to their role
• Review your specific protocols for those modalities
• Ask questions without pressure to produce
• Have a quiet 30-minute debrief with their mentor each afternoon

At the end of week one, have a brief check-in meeting (15 minutes) with your new tech and mentor. Ask: "How are you feeling? What was confusing? What do you need next week?" Document this conversation. You're gathering baseline data on how the first week landed.

Weeks Two Through Four: Supervised Clinical Work and Rapid Skill Building

This is where most departments go wrong. They treat "supervised" loosely, which often means "I'm in the department, but I'm not actually watching you."

Define what "supervised" actually means for each task. Initially, your new rad tech should not perform patient care independently. Every scan should be performed with direct supervision:

• The mentor (or another qualified tech) should be physically present, observing the entire procedure
• Patient positioning, protocol selection, imaging parameters, and communication should all be reviewed in real time
• Constructive feedback should happen immediately, while the skill is fresh
• Documentation and exam completion should be co-reviewed before moving to the next patient

This is time-intensive. Acknowledge it. Your department may run slightly slower for four weeks. That's the cost of preventing six months of poor performance followed by turnover.

Institute a structured protocol familiarization schedule. Don't expect your new technologist to absorb every protocol by osmosis. Instead:

• Create a written list of 8-12 core protocols they need to master
• Assign specific days for training on specific protocols
• Pair protocol training with hands-on supervised practice that day
• Have them demonstrate competency before moving to the next one

Schedule weekly check-ins with the mentor. Fifteen minutes, same time each week. The mentor should address:

• What protocols are they mastering?
• What's causing confusion?
• Are there specific knowledge gaps?
• How's the personality fit with the team?

These aren't performance reviews; they're early intervention opportunities.

Weeks Five Through Eight: Building Independence and Maintaining Momentum

By week five, your new technologist should be performing supervised clinical work on their own, with the mentor available but not physically present for every scan.

Create a graduated independence schedule. Define specific points where they earn more autonomy:

• Week 5: They can perform routine protocols independently, with mentor review of images and documentation
• Week 6: They can perform two or three specific protocols completely independently
• Week 7: They can handle higher-volume days with mentor spot-checks
• Week 8: They should be functioning near baseline with mentor backup for complex cases

This gradation is crucial. It builds confidence while maintaining safety.

Continue frequent feedback. Weekly check-ins should now include:

• A review of specific cases they handled well
• One area where they're progressing
• One area needing continued focus
• Any concerns the mentor has noticed

Watch for early warning signs of disengagement. If your new tech is:

• Arriving just before start time (they were early the first three weeks)
• Asking fewer questions
• Seeming withdrawn or frustrated
• Having conflict with team members

...address it immediately. Don't wait for week 12. Early intervention during week 6 or 7 prevents week 12 resignations.

Weeks Nine Through Twelve: Full Integration and Retention Conversation

By week nine, your new technologist should be functioning independently on standard cases, with appropriate escalation protocols for complex situations.

Transition from onboarding to regular performance. Your mentor's intensive role should decrease, but don't abruptly disappear. Instead:

• Transition from daily check-ins to weekly
• Have the mentor remain available for questions, but your new tech should be increasingly self-directed
• Include them in team meetings and normal department operations
• Assign them to regular schedule rotations

Conduct a 90-day formal review. This is not a performance evaluation in the traditional sense. Instead, have a structured conversation with your new technologist and their mentor that covers:

• Their experience during the first 90 days
• What they feel confident doing
• What areas they want to continue improving
• Their feedback on the onboarding process itself
• Their vision for growing in your department

Have an explicit retention conversation. This is the step most departments skip, and it's crucial. During this meeting, explicitly tell them:

• You want them here long-term
• You've invested in their success
• You see potential in them
• What their next opportunities for growth look like in your department

Many new hires leave not because they're unhappy but because they've never been explicitly told their future matters. This conversation changes that.

Common Onboarding Mistakes That Cost You Technologists

Mistake #1: Insufficient buddy support. Your mentor is drowning in their own work and gives your new tech surface-level supervision. Solution: Adjust the mentor's schedule or workload during the first 12 weeks.

Mistake #2: No written structure. Everyone assumes the new tech should learn the same way they did. Solution: Create a documented onboarding protocol that applies to all new hires consistently.

Mistake #3: Expecting too much too soon. Your new technologist is thrown into independent clinical work within two weeks. Solution: Plan for four weeks of supervised work minimum.

Mistake #4: Poor communication about expectations. Your new hire doesn't know if they're succeeding or struggling. Solution: Weekly feedback every week for the first 12 weeks.

Mistake #5: No retention focus. You bring them in, get them up to speed, then check them off your list. Solution: Make explicit retention conversations part of your 90-day plan.

Why Structured Onboarding Pays for Itself

A new technologist costs 6-12 months to reach full productivity. Every dollar you invest in structured onboarding in weeks one through twelve is paid back tenfold when that technologist is still with you 12, 24, even 36 months later.

Beyond retention: structured onboarding reduces your patient safety risks, speeds time to productivity, improves your reputation in the professional community, and strengthens your team culture. New technologists who feel genuinely welcomed and prepared become your strongest employees and your best recruiters.

Your new rad tech's first 90 days aren't an onboarding period you squeeze in around your busy schedule. They're the foundation of years of stable staffing, quality imaging, and a department culture people actually want to be part of.

Start your plan before they arrive. Stick to it during those first three months. And watch what happens to your retention rates.

---

Ready to implement a 90-day onboarding plan in your department? Start by mapping out your current process. Where are the gaps? Where are technologists struggling in their first month? Where could a mentor role make a difference? Take 30 minutes this week to create a basic onboarding checklist tailored to your facility. Your next new hire will thank you—and more importantly, they'll still be there in year two.