A six-physician orthopedic practice showed us its denial report in March. There were 1,140 open denials. The two billers who worked them opened the list every morning sorted by date received, oldest first, and worked down. That morning's first hour went to nine denials from January, all CO-45 adjustments under $20 that were never going to pay anything. Further down the same list sat 12 CO-197 denials for MRI and injection claims, each worth $900 to $2,400, that had come in six weeks earlier. The payer's appeal window was 60 days from the remittance. Four of them had already expired.
Nobody on that team was lazy. They were doing exactly what the software made easy, and the software made "oldest first" easy. The denial work queue, meaning the list of denied claim lines a biller works from and the order in which they appear, is the single biggest driver of how much denied revenue a practice recovers. Sorting it by date received treats a $14 balance and a $2,400 balance as equally urgent and ignores the fact that some denials expire.
This article is how we build the queue instead: sorted by expected payment, days remaining to the appeal deadline and fix type, batched so a biller works twenty similar problems in one sitting. For readers new to remittance vocabulary: a CARC is the claim adjustment reason code on the electronic remittance (the 835) that says why a line was denied, such as CO-197 for a missing precertification, and a RARC is the remark code that adds detail.
Key takeaways
- Sort the denial work queue by a priority score built from expected payment and days remaining to the appeal deadline, never by date received.
- Every denial needs three fields the 835 does not give you: expected allowed amount, appeal deadline date (from a payer table) and fix type.
- Fix type determines who works the denial and lets you batch: corrected claims to a biller, medical necessity appeals to a coder, authorization denials to the authorization coordinator, registration denials back to the front desk.
- The numbers that tell you the queue is working are days from remit to first touch, overturn rate by CARC, and the count of denials that expired unworked, which should be zero.
- A queue only pays if every touch ends in a resolution code; "called payer, waiting" is not a resolution.
Why date received is the wrong sort
First in, first out feels fair and it is how most practice management systems default. It fails for three reasons. Denials are not equal in value: in a typical primary care practice a third of denied lines are under $30 and a tenth carry more than half the denied dollars. Denials are not equal in urgency: Medicare gives 120 days from the initial determination to request a redetermination, most commercial contracts give 180 days for an appeal, some give 60, and a corrected claim often has to meet the original timely filing limit rather than the appeal window. And denials are not equal in effort: a CO-16 for a missing referring NPI is a two-minute corrected claim; a CO-50 medical necessity denial is a records pull, a letter and a 45-day wait.
When you sort by age, the biller spends the morning on the oldest items, which are disproportionately the low-value ones nobody wanted to touch, and reaches the high-value recent items last. Meanwhile the clock on those items runs. In our experience the single largest category of avoidable write-off in a practice with a backlog is "appeal deadline passed," and it is almost entirely a sorting problem.
How to build the denial work queue in your billing system
Start with the fields. The 835 gives you payer, claim and line, date of service, CARC, RARC, billed amount and paid amount. You add four: expected allowed (from your loaded fee schedule, or the payer's historical average for that code if you have not loaded contracts), deadline date, fix type and owner. Deadline date is calculated, not typed: the remittance date plus the appeal window from a payer table you maintain, with the corrected claim limit stored separately. Fix type is assigned by a rule on the CARC and RARC, with a human override.
| CARC | What it usually means | Fix type | Owner | Typical effort |
|---|---|---|---|---|
| CO-16 with an N-series RARC | Claim lacks information (NPI, referring provider, modifier, dates) | Corrected claim | Biller | 2 to 5 minutes |
| CO-4 | Procedure code inconsistent with modifier | Coding review, corrected claim | Coder | 10 minutes |
| CO-11 | Diagnosis inconsistent with procedure | Coding review; corrected claim or appeal | Coder | 10 to 20 minutes |
| CO-22 | Coordination of benefits; another payer is primary | Registration fix, rebill to correct payer | Front desk or biller | 10 minutes plus patient call |
| CO-29 | Timely filing | Appeal with proof of timely submission, or write off | Biller | 15 minutes |
| CO-50 | Not medically necessary per payer policy | Appeal with records and policy citation | Coder or clinician | 30 to 60 minutes |
| CO-97 | Bundled into another service | NCCI check; modifier appeal or write off | Coder | 10 minutes |
| CO-197 | Precertification or authorization absent | Retro authorization request or appeal | Authorization coordinator | 20 to 40 minutes |
| CO-109 | Not covered by this payer | Eligibility recheck, rebill | Biller | 5 to 10 minutes |
| PR-1, PR-2, PR-3 | Deductible, coinsurance, copay | Not a denial; transfer to patient balance | Automated | None |
With those fields loaded, the sort is a formula. We use priority score = expected allowed × urgency, where urgency is 3 when fewer than 15 days remain to the deadline, 2 when 15 to 45 days remain, and 1 otherwise. Lines with expected allowed under a floor you choose (many practices use $25) and a fix type of "write off" drop into a separate weekly batch so they never compete with real money. PR lines never enter the queue at all.
A worked example: five denials, one morning
Here are five denials from the orthopedic practice's list, with the date-received order they were in and the order the score produces.
- CO-45 on a 99213, expected allowed $0 (contractual adjustment posted as a denial by an old rule), received 71 days ago. Date order: first. Score: 0. Correct action: fix the posting rule so it stops appearing.
- CO-16 with RARC N290 (missing rendering provider NPI) on a 20610, expected allowed $62, received 40 days ago, deadline in 140 days. Date order: second. Score: 62 × 1 = 62.
- CO-197 on a 73721 (MRI knee), expected allowed $410, received 47 days ago, payer window 60 days, deadline in 13 days. Date order: third. Score: 410 × 3 = 1,230.
- CO-50 on a 27447 assist-at-surgery line, expected allowed $1,150, received 20 days ago, deadline in 160 days. Date order: fourth. Score: 1,150 × 1 = 1,150.
- CO-197 on a 20611 with J7325, expected allowed $980, received 44 days ago, deadline in 16 days. Date order: fifth. Score: 980 × 2 = 1,960.
The scored order is 5, 3, 4, 2, 1. The two authorization denials that were about to expire come first, the large medical necessity appeal comes next because it will take an hour and can be started today, the quick corrected claim follows, and the phantom denial is removed from the queue permanently. The biller's morning now protects roughly $2,500 of recoverable revenue instead of clearing $62 and a zero.
Batching by fix type
The score decides what matters. Fix type decides how the work is organized. A biller who alternates between a corrected claim, an appeal letter, a payer phone call and a registration fix loses several minutes on every switch, and the appeals get rushed. We set the queue up as views: the authorization coordinator opens only CO-197 and CO-15 lines sorted by score, the coder opens CO-4, CO-11, CO-50 and CO-97, the front desk lead gets a weekly CO-22 and CO-109 list because those are registration and eligibility failures that will recur until someone upstream changes a habit, and the biller takes everything that ends in a corrected claim. Each view is still sorted by score inside itself, so the deadline logic survives.
Batching also produces the feedback loop that prevention depends on. When the front desk lead sees 31 CO-22 denials in a month from one payer, that is a registration script problem, not 31 individual problems. When the coder sees 18 CO-97 denials on 99213 with 96372, that is a modifier 25 training problem. We write one sentence per batch in a monthly denial notes file and bring those to the denial management review; the queue is where the pattern shows up first.
The numbers to watch
Four measures tell you whether the queue is working, and they belong on a weekly one-page report. Days from remittance to first touch, by fix type, with a target under seven for anything scored above the floor. Overturn rate by CARC, meaning the share of appealed or corrected lines that later paid; in our experience CO-16 corrected claims should pay above 90 percent of the time, CO-197 retro authorizations vary enormously by payer, and a CO-50 overturn rate below 40 percent usually means the appeals are form letters. Dollars recovered against dollars denied for the month, using expected allowed rather than charges so the number means something. And the one that matters most: count of denials that reached their deadline without a resolution code. That number should be zero every week, and when it is not, the report should name the payer and the fix type so the cause is visible.
Resolution codes are the discipline that makes the numbers true. Every touch ends in one of a short list: corrected claim sent, appeal sent, retro authorization requested, rebilled to other payer, transferred to patient, written off with reason, or closed as paid. "Called payer, pending" is a status, not a resolution, and a line can sit in that status for a defined number of days before the queue surfaces it again. Practices that let billers log a touch without a resolution end up with a "worked" backlog that is not actually moving, and the days-to-first-touch metric looks fine while the deadline count climbs.
Questions we hear
Our practice management system only sorts by date or payer. Can we still do this?
Yes, with a spreadsheet as the queue and the system as the record. Export open denials weekly with the CARC, RARC, remit date and billed amount, add the expected allowed from your fee schedule with a lookup, add the deadline from a payer table, compute the score and hand each person their filtered tab. It is clumsy, and it still recovers more than working the native list oldest first. Most modern systems and clearinghouses can hold custom fields and saved views; ask your vendor before assuming the answer is no.
Where do we get the appeal deadlines for the payer table?
From the provider manual or the contract for each payer, and for Medicare from the redetermination rules (120 days from the date of the initial determination). Record both the appeal window and the corrected claim window, because they differ, and note whether the clock starts at the remittance date or the date of service. Review the table once a year; payers change these terms with a bulletin and rarely with a phone call.
Should small balances ever be worked?
In batches, yes, and individually, almost never. A weekly 30-minute pass through the under-$25 list, sorted by fix type, lets a biller send 20 corrected claims in one sitting when the fix is the same. Anything below that floor that needs an appeal should follow your written small balance policy, which in most practices means a documented write-off.
What to do this week
- Export every open denial and add three columns: expected allowed, deadline date and fix type. Count how many are already past deadline; that is the cost of the current sort.
- Build the payer table with appeal and corrected claim windows for your top ten payers and store it where the billing team can see it.
- Set the priority score and the small balance floor, sort the list, and have each person work the top of their fix-type view for one week.
- Add the resolution code list to the system or the spreadsheet and require one on every touch.
- Run the four numbers next Friday and compare them to the week before.
