Growth is supposed to be the good problem. More referrals, more admissions, more census. But for a lot of agencies, growth quietly turns into a coding capacity problem long before it turns into a revenue win, because the coding team that worked fine at last year's volume starts falling behind the moment census picks up.

Here's why hiring your way out of that isn't always the answer, and what agencies are doing instead.

The coder shortage is real, and it's not going away

The American Academy of Professional Coders puts the current national shortage of certified medical coders at around 12 percent with the shortage even more pronounced in home health, where coding and QR requires specialized expertise, which means the coders you'd need to hire to keep pace with growth are competing for a smaller pool than the industry actually needs. That shortage shows up as longer time to fill open coding roles, upward pressure on coder salaries, and a real risk of losing experienced coders to agencies willing to pay more for the same scarce talent.

For a growing home health or hospice agency, that math doesn't work in your favor. You need more coding capacity right when it's hardest and most expensive to hire for it.

Why hiring ahead of growth doesn't actually solve the problem

The instinct is to hire ahead of the curve, bring on coders before volume actually justifies it, so you're not scrambling later. In practice, that's expensive in a different way. You're carrying salary and overhead for capacity you might not need for months, and if growth slows or shifts, you're stuck with headcount sized for a census that didn't materialize.

Hiring behind the curve has the opposite problem. By the time you've posted the role, gotten through the coder shortage competing for the same candidates, and onboarded someone new, you've usually been running short-staffed for months. Coding backlogs build, turnaround slows, and the same overworked team that was already stretched thin absorbs the gap in the meantime, which is exactly the kind of pressure that [pulls a DON's time into chart questions and escalations](insert DON time audit blog URL) instead of the clinical leadership work only they can do.

What scaling without headcount actually looks like

The alternative a lot of growing agencies are turning to is pairing their existing team with a coding and QA partner that scales with volume automatically, without a hiring cycle attached to every census increase. When referrals spike, the reviewing capacity spikes with it. When things level off, you're not carrying excess capacity you have to justify.

This isn't about replacing your coding team. It's about giving them a way to absorb growth without the lag time, the recruiting cost, or the risk of a bad hire made under time pressure. Your existing coders keep doing what they do well, and the capacity gap that used to mean overtime, backlogs, or a rushed new hire gets covered by a partner built to flex with your volume instead.

Why this matters beyond the coding team itself

A coding bottleneck doesn't stay contained to coding. Backlogs delay claims. Delayed claims delay cash flow. And a stretched coding team under growth pressure is more likely to produce the kind of scoring inconsistencies that show up in an ADR letter months later, at the worst possible time to discover them.

Scaling capacity ahead of that pressure, rather than reacting to it after backlogs have already built, is what actually lets growth stay the good problem it's supposed to be.

See what this could look like for your growth plans

We offer a 30-day, low-risk pilot, opt out any time, and we're happy to walk through pilot pricing specifically built around what scaling with your census would actually look like.