Denial management: work the cause, not the queue.
Most practices work denials in the order they arrive, which guarantees the same denials keep arriving. Denial management that actually changes the numbers sorts by root cause, fixes the process that produced each category, and treats the appeal as the secondary activity rather than the main one.
Key takeaways
- Categorise by root cause before working anything. Date order tells you nothing; cause order tells you what to fix.
- Appeal deadlines are shorter than filing deadlines. A denial sitting for a month may already be unappealable.
- Not every denial is worth appealing. Some cost more to rework than they return; decide deliberately rather than by default.
- A denial category that recurs is a process defect. Feed the finding back to the front end or it repeats indefinitely.
Sort by cause, then decide what to do with each group
The first act of denial management is classification. Group every denial by why it happened rather than when it arrived: eligibility, authorisation, coding, documentation, bundling, timely filing, coordination of benefits, or contractual. Once grouped, each category has a different answer. Eligibility and authorisation denials are front-end failures and largely preventable. Coding and bundling denials need a coder and often a corrected claim. Documentation denials need the clinical record. Timely filing denials are usually lost, and their only value is as evidence that a process is broken.
This ordering also reveals scale. A practice discovering that a third of its denials share one cause has found a project rather than a queue, and fixing that upstream is worth more than appealing every instance individually. Working denials without categorising them is the reason many practices rework diligently for years without their denial rate improving.
| Category | Typical remark | Fix | Where prevention lives |
|---|---|---|---|
| Eligibility | CO-27, CO-31 | Rebill correct payer, or bill patient where the agreement supports it | Batch verification the night before |
| Authorisation | CO-197 | Retro-authorisation where permitted; often unbillable to the patient | Authorisation confirmed before scheduling |
| Coding | CO-11, CO-16 | Corrected claim with the supported code or missing element | Scrubber edits plus periodic coding audit |
| Bundling | CO-97 | Withdraw, or unbundle with the correct modifier and documentation | Edit-pair checks pre-submission |
| Medical necessity | CO-50 | Appeal with the clinical record meeting the coverage policy | Coverage criteria surfaced at order entry |
| Timely filing | CO-29 | Appeal only with proof of timely submission; otherwise written off | Charge lag measurement and a fixed denial work schedule |
| Coordination of benefits | CO-22 | Rebill correct primary; update COB on file | Coverage change question at every registration |
Work denials on a schedule, inside the appeal window
Appeal deadlines are frequently much shorter than original filing deadlines, and they run from the remittance date rather than the service date. A denial that sits in a queue for six weeks may be beyond appeal before anyone opens it, which converts a recoverable claim into a write-off through inaction alone.
The operational answer is a fixed cadence with ownership: denials worked within a defined number of days, categories assigned to the people equipped to handle them, and an escalation path for anything approaching a deadline. Practices that work denials "when there is time" systematically lose the ones with the shortest windows, which are often the most valuable.
Report denials as a percentage of claims by category each month and show the trend, not just the total. A flat overall denial rate can conceal one category collapsing while another grows. The categories that persist month after month are the ones where the prevention was never implemented, and the trend line makes that visible in a way a monthly total never does.
Do and don't
- Categorise every denial by root cause before working it.
- Work denials on a fixed schedule inside the appeal window.
- Feed recurring categories back to the front end as process changes.
- Track appeal outcomes by category so effort follows what actually wins.
- Decide deliberately which low-value denials are not worth reworking.
- Don't work the queue in date order.
- Don't resubmit the same claim unchanged and expect a different outcome.
- Don't let denials age past the appeal deadline.
- Don't appeal everything reflexively; some cost more than they return.
- Don't treat a recurring denial category as a cost of doing business.
Frequently asked questions
What denial rate should we be aiming for?
Low single digits at first submission is a reasonable target for most outpatient practices, though the achievable figure varies with payer mix and specialty. More useful than the headline number is the category breakdown: a practice at five per cent with denials spread evenly across many causes is in a very different position from one at five per cent where a single preventable category dominates. Fix the concentration first.
How quickly must denials be worked?
Inside the payer's appeal window, which is often considerably shorter than the original filing deadline and runs from the remittance date. A practical standard is working every denial within a couple of days of receipt, which keeps you comfortably inside even short windows. The risk is not that any single denial is urgent; it is that a queue worked irregularly systematically loses the ones with the tightest deadlines.
Is it worth appealing small-balance denials?
Not always, and pretending otherwise wastes staff time. Compare the expected recovery against the cost of the rework. Low-value denials with poor appeal odds are often better written off deliberately, with the effort redirected to preventing that category. What matters is that the decision is explicit and reviewed, rather than an unspoken habit of ignoring anything small.
How do we stop the same denials recurring?
Route the finding to wherever the cause lives. Eligibility denials go to the front desk process, authorisation denials to scheduling, coding denials to the scrubber and to coder education, medical necessity denials to order entry. A denial worked but not fed back is a claim recovered and a process unchanged, which is why practices can rework diligently for years while their denial rate stays flat.
Do you work denials as part of your service?
Yes, and we categorise by root cause before working anything, so the monthly report shows which categories are shrinking and which are not. Every denial is worked within a defined window, and recurring causes are raised as process changes rather than simply reworked each month. The measure we hold ourselves to is whether the category stops appearing, not how many appeals we filed.