Two Clinicians, One Tuesday
Same practice, same Tuesday, two nearly identical sessions. The first clinician codes hers conservatively, the way she’s coded everything since a former employer got audited years ago and the fear outlived the job. The second codes what the documentation supports, no more, no less. Neither one is wrong on any single claim. Stretch the difference across a year of identical work and they’re thousands of dollars apart, and the practice has no idea, because nobody has ever put the two patterns on one chart.
The Silent Failure and the Loud One
Coding fails in two directions, and owners only ever hear about one. Undercoding is the silent version: work delivered, documented, and billed below what the documentation supports, out of caution, haste, or old scar tissue. That’s finished work, partially donated, visit after visit, year after year. Overcoding is the loud version: billing past what the documentation supports, which is money held on strings. A payer can pull it back later with interest, and bring extra attention to whatever you submit next.
Both fears point away from the actual target: complete and accurate. Everything that happened, nothing that didn’t, with documentation that proves it in both directions. And unlike either fear, that target is measurable.
The Spread Is the Tell
Put the same visit in front of three clinicians and you’ll often get three codes, each defensible to its author. That’s human variability working directly on your revenue, and it bills you twice. The conservative coders donate steadily. And the spread itself forms a pattern, visible to payer analytics across your entire claim history long before it’s visible to you. A practice that has never charted its own code distribution is being read by someone who has.
Chart It. One Hour.
Pull your top visit types and chart the code distribution by clinician for one quarter. What the chart shows is rarely a villain. It shows a cluster: most of the group inside a band, and one or two names sitting far outside it, in either direction. When you sit down with an outlier, there’s always a story: the audit at the old job, the template that defaults to the middle code, the onboarding that never mentioned thresholds existed. The chart locates the conversations worth having and arms them with data instead of vibes, and the data was in your system the whole time.
Four Guardrails
Written thresholds for the recurring judgment calls, so the common cases stop being personal style. Documentation templates built to capture the elements that support the code, so the note and the bill can’t drift apart. A review trigger for outliers in both directions, because under and over are the same defect with opposite signs. And per-clinician feedback, delivered with context and care: each person sees their own pattern against the group, framed as patterns, never as accusations about individual claims. The same structure appears as factory four in the denial prevention guide, because payers meet your coding long before you review it.
What Changes
The conservative clinician gets something she didn’t know she was owed: permission. Her documentation was supporting more than she billed all along, and coding what happened simply invoices work she already did and already wrote down. The high outlier gets a safety net before a payer supplies one, which is by far the better way to receive that news. And the owner stops flinching away from the whole topic, because two vague fears just became one chart, refreshed quarterly, mostly showing a band.
Where to Start
Run the distribution this week; it costs an hour and it names its own priorities. Then grab 30 minutes with us. Prep nothing. We’ll show you coding-pattern views from real practices, both directions on one screen, and you’ll see what a healthy band looks like and exactly how outliers announce themselves.