The position was open for five months. You interviewed eight candidates. Three of them had no inpatient experience. Two ghosted after the second interview. One accepted a counteroffer from their current employer. And now, finally, you have a new hire starting Monday.
Your team is relieved. You are relieved. And you are also completely unprepared, because you have been so busy covering the workload of that empty seat that you have not had time to build an onboarding plan. You do not have a training schedule. You do not have a mentor assigned. You barely have a working login ready.
This is where most frontline leaders lose the hire they just spent months finding.
The Onboarding Problem No One Talks About
The national coder shortage is real. AAPC reported a 12% shortage of certified medical coders this year. Facilities are competing for the same talent, offering sign-on bonuses and remote flexibility and every perk they can think of to get someone in the door.
But getting someone in the door is not the hard part. Keeping them past the first 90 days is.
New coders, especially those coming from certification programs with limited real-world exposure, walk into their first inpatient position and hit a wall. The volume is higher than they expected. The documentation is messier than the textbook examples. The systems are unfamiliar. And if the team is already stretched thin, the new hire picks up on that tension immediately. They start wondering if they made the right choice before they have even finished their first week.
You cannot control the shortage. You cannot control how many qualified candidates apply. But you can control what happens once they walk in.
What "Good Enough" Onboarding Looks Like When You Are Short-Staffed
Perfect onboarding is a luxury most frontline leaders do not have right now. You do not have a dedicated trainer. You do not have weeks of protected time to shadow. You do not have the time to build a curriculum from scratch.
So here is what good enough looks like, and good enough is the difference between keeping a coder for two years and losing them in two months.
Give them one person. Not the whole team. One person who is their go-to for questions, for context, for the unwritten rules of how things work in your department. That person does not need to be the best coder on the team. They need to be patient, approachable, and willing to say "I do not know, let me find out" without making the new hire feel like they are a burden.
Sequence the complexity. Do not hand a new coder a sepsis chart on day three. Start with lower-acuity cases and build up. Let them feel what it is like to code a straightforward case accurately before you introduce the complicated ones. Confidence is not built by throwing someone into the deep end. It is built by letting them succeed at something manageable first.
Check in on day 3, day 10, day 20 and day 30. Not "how is it going" check-ins. Specific ones. What is confusing? What do you wish you had more of? Is there anything you are stuck on that you have not asked about yet? New hires will not tell you they are struggling unless you create the space for it. And by the time they tell you on their own, they have usually already decided to leave.
Write down the things everyone on your team already knows. Where to find the query templates. How the worklist is sorted. What the escalation process is when a chart is incomplete. The small operational details that feel obvious to your experienced coders are invisible to someone new.
The Hidden Cost of "Figure It Out"
Getting it written down saves hours of confusion — but it's not enough.
Handing a new coder a cheat sheet or a shared drive full of documents and expecting them to self-onboard adds to their confusion and frustration. It doesn't demonstrate support — it signals that nobody has time for them. And that feeling is exactly what drives a new hire out the door before the 60-day mark.
A document is not a training program. It puts the burden on them to train themselves.
The Mentorship You Wish You Had
Most frontline leaders got promoted because they were good coders. Not because someone taught them how to lead. And onboarding is one of the first places that gap shows up, because building someone else's competence requires a different skill set than building your own.
You need a formal onboarding and mentorship program. You need a consistent, intentional habit of checking on the person you hired. Not their productivity numbers. Them.
Are they asking questions? Good. Are they quiet and never flagging anything? That is not a sign they are fine. That is a sign they are afraid to look like they do not know what they are doing.
The coders who stay are the ones who feel like someone noticed them. Someone answered the question without making them feel stupid. Someone said, "This chart is hard. Here is how I would approach it," instead of "You should know this by now."
You Cannot Afford to Lose This One
The math is simple and painful. Every month that position was empty, your team absorbed the extra work. Their accuracy may have dipped. Their morale definitely did. You spent time and energy recruiting. You finally found someone.
If that person leaves in 60 days because the onboarding was chaos, you are back to square one with a team that is now even more exhausted and less willing to believe the next hire will stick.
The investment is not big. It is intentional. One mentor. Sequenced cases. Weekly check-ins. And someone in your corner who has done this before.
Your team needs you to protect the first 60 days of every new hire like it is the most important retention tool you have. Because it is.
Questions Worth Sitting With
- What does your onboarding process look like right now?
- Do you have enough coders to justify lost production time while someone mentors a new hire?
- Do you have a plan to clear any backlog this creates?
- And do you have a plan to prevent fatigue and resentment in the experienced coders who keep covering additional workloads?
There Is a Better Way
Your team shouldn't have to carry this alone.
Reilly Coding Strategies specializes in exactly this 60-day window. We provide structured onboarding support, mentorship scaffolding, and interim coding coverage so your team maintains output while the new hire actually gets trained — not just handed a stack of PDFs and a login.
Talk to Us About Your Team arrow_forwardShare this article