Budget season has a way of turning coding and QA spend into a single line item that's easy to either overlook or cut without much scrutiny. That's a mistake in either direction. Underfunding this part of the operation tends to cost more than it saves once missed reimbursement and audit exposure are factored in, and overspending on the wrong kind of support doesn't actually reduce risk the way agencies hope it will.
Here's how to think through this budget line more deliberately heading into the new year.
Start with what your current setup is actually costing you, fully
A lot of agencies budget for coding and QA based on the invoice they're used to seeing, without factoring in the full cost of the current setup. That means accounting for internal staff time spent on chart review and coding questions, not just a vendor fee, and factoring in the cost of any missed reimbursement or comorbidity adjustments that a stronger coding process would likely have caught. The real cost of your current approach is often higher than the number on the invoice suggests.
It helps to actually write this out rather than estimate it in your head. List the vendor fee, then add a rough estimate of internal hours spent per month on coding questions and chart escalations, valued at what that time is actually worth. The total is often a more honest number to budget around than the invoice alone.
Think about capacity, not just cost per chart
A coding shortage doesn't ease up just because your agency's budget cycle is calm. If growth is part of your plan for the year ahead, it's worth budgeting for coding and QA capacity that can actually scale with census, rather than assuming you'll simply add headcount as volume increases. Hiring ahead of growth ties up budget for capacity you might not need yet. Hiring behind it means months of strain before a new hire is fully up to speed. A model that scales with volume avoids both problems.
Factor compliance risk into the number, not just efficiency
Coding and QA spend often gets evaluated purely on efficiency, faster turnaround, lower cost per chart, without much thought given to how it affects audit and compliance exposure. That's a narrow way to look at a budget line that has real downside risk attached to it. A cheaper coding process that produces less consistent documentation isn't actually cheaper once you factor in the cost of a real ADR response, a recouped payment, or a downgraded case mix that traces back to a documentation gap nobody caught in time.
Building compliance risk into how you evaluate this budget line, not as an afterthought but as part of the actual cost comparison, tends to produce a more honest picture of what different options actually cost an agency over a full year.
Weigh vendor claims against verified numbers, not marketing copy
If you're evaluating a new coding or QA partner as part of this year's budget planning, ask for real, verified accuracy data rather than a single headline stat. We publish our own numbers every quarter specifically so agencies evaluating us have something concrete to check against, not just a claim to take on faith. Olli publishes our accuracy report every quarter because we take pride in our accuracy and believe in transparency. If your current coding vendor doesn’t publish their accuracy scores, it’s worth asking why.
Whichever vendor you're considering, the same standard applies: a number you can't see the methodology behind isn't a number worth budgeting around.
Build in room to actually test before committing for the year
A full annual budget commitment based on a sales pitch alone is a real risk. Building in a low-risk pilot period before locking in a full year's spend lets you see real performance on your own charts before the number becomes a fixed line item you're stuck with regardless of how it actually performs.
See what this could look like for your budget
We offer a 30-day, low-risk pilot, opt out any time, so you can see our actual pricing, speed, accuracy, and support firsthand before it becomes part of your budget for the year ahead.