The Revenue You Lose to Undercoding
Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
Most practices worry about overcoding — the audit, the clawback, the reputational risk. That fear is real, and it's right to respect it. But it quietly pushes many practices into the opposite failure, one that never triggers an audit and never shows up on a report: coding below the work that was actually done and documented. The visit was a level higher than what got billed. The chronic condition managed alongside the acute complaint never made it onto the claim. The revenue was earned and then left on the table.
This isn't about gaming codes or pushing every visit upward. The money you lose to undercoding is money you already earned — the work happened, the risk was managed, the note could support it, and the claim simply didn't reflect it. Closing that gap is an operational discipline, not a billing trick, and for most practices it's the most reachable revenue they have.
THE ENCOUNTER-TO-CLAIM GAP
work actually done ▇▇▇▇▇▇▇▇▇▇ (full visit + managed conditions)
documented in note ▇▇▇▇▇▇▇░░░ (some detail never captured)
coded on the claim ▇▇▇▇▇░░░░░ (defaulted low, safe, incomplete)
└──────┘
revenue earned, never billedOwner symptoms
Your visit levels cluster suspiciously — nearly everything billed at the same middle code, regardless of complexity.
Providers default to the "safe" lower level because it feels less risky than defending a higher one.
Chronic conditions you actively manage rarely show up on the claim, even when the note describes the work.
Why this happens
Undercoding is usually a fear response, not a knowledge gap. Providers hear the horror stories about overcoding and quietly conclude that the safest number is a low one. On top of that, most practices never build a shared standard for what supports each level, so coding drifts to whatever each provider feels comfortable defending in a hypothetical audit. Add rushed documentation — a note written at the end of a long day that captures the diagnosis but not the full decision-making — and the claim gets built from an incomplete record. Nobody decided to give away revenue; the system just quietly does it.
Common mistakes
Defaulting to the safe middle level on every visit, so complexity never shows.
Documenting the outcome but not the work — the thinking, the reviewed data, the managed comorbidities — so the note can't support what actually happened.
Dropping managed chronic conditions that were addressed during the visit but never coded.
Treating coding as a back-office task disconnected from what the provider actually did in the room.
Never sampling your own coding patterns, so the leak stays invisible.
Business consequences
Undercoding doesn't announce itself. There's no denial, no rejection, no angry payer letter — just a slow, silent discount applied to work you genuinely performed. Spread across thousands of encounters a year, a fraction of a level per visit compounds into real money that never funds a hire, a piece of equipment, or the owner's own pay. The practice that tightens this doesn't earn more by working more; it collects for the work it's already doing. The contrast is stark: two identical practices, seeing identical patients, can diverge substantially in revenue purely on how faithfully the claim reflects the encounter.
How experienced operators think about it
They frame accurate coding as telling the truth completely, not aiming high or low. The goal isn't the biggest number or the safest one — it's the number the documented work actually supports. That reframe removes the fear: if the note fully reflects the complexity and decision-making, the correct level isn't aggressive, it's just accurate, and it's defensible precisely because it's true. Experienced operators also treat this as a documentation problem first and a coding problem second. Fix the note — make it capture the real work — and the coding follows honestly. They build a shared standard so it doesn't ride on each provider's private risk tolerance.
Practical actions
Sample your own visit-level distribution. If nearly everything lands on one code, that's a signal to investigate, not proof of anything — real complexity varies.
Tighten documentation at the point of care, so the note captures decision-making and managed conditions while they're fresh, not reconstructed later.
Build a shared, written standard for what supports each level, so coding doesn't swing by provider comfort.
Capture managed chronic conditions that were genuinely addressed in the encounter, not just the presenting complaint.
Review a small sample of encounters regularly — comparing note, work done, and code billed — to catch drift in both directions.
This is general business information, not medical/clinical or professional advice. Consult a qualified professional for your situation.
Questions every owner should ask
If I looked at my visit-level distribution today, would it reflect the real range of complexity we see — or would it cluster on one safe number?
Do our notes capture the full work done, or just enough to name the diagnosis?
Is our coding standard written down and shared, or does it live in each provider's head?
Frequently asked questions
Isn't coding higher exactly what gets practices audited?
Overcoding — billing above what the record supports — is what creates audit risk, and that risk is real. But accurate coding isn't the same thing as high coding. The target is the level the documented work actually supports: no higher, no lower. When your note fully reflects the complexity and decision-making, the correct level is simply the true one, and being true is what makes it defensible. Undercoding trades a phantom safety for a real, ongoing loss.
Where should we start if we suspect we're leaving money on the table?
Start with documentation, not coding. Sample a handful of your own recent encounters and compare three things: what the provider actually did, what the note captured, and what got billed. The gaps between those three are your leak. Most of the time you'll find the work was real and the note was thin — which means the fix is capturing the work better at the point of care, not changing how anyone codes.
Related articles
Running a Profitable Medical Practice — the pillar.
Managing Prior Authorizations Without Delaying Care — another revenue-cycle discipline.
Verifying Coverage Before the Visit, Not After — stopping loss at the front end.
Inconsistent Quality and Rework: Why It Happens — the universal pattern behind coding drift.
The True Cost of Rework — what inconsistency really costs.
Every business has more decisions than time
Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.
Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.