Correct, Reconsider, or Appeal: A Denial Routing Decision Tree
A printable decision tree that sends each behavioral-health denial down the right path the day it arrives, so appeal effort goes where appeals are the answer.
On this page: Direct answer
Direct answer
Denial routing decision tree: what operators need to know
A printable decision tree that sends each behavioral-health denial down the right path the day it arrives, so appeal effort goes where appeals are the answer. Four destinations, not two: correct and resubmit, reconsider with documentation, appeal, or write off with a recorded cause.
The expensive mistake in denial management is not failing to appeal. It is appealing things that should have been corrected, and correcting things that should have been appealed. An appeal of a transposed authorization number wastes weeks and a reviewer's patience; a corrected resubmission of a medical-necessity downgrade quietly forfeits the argument and often the appeal window with it.
Routing is a decision that should take under a minute and should not depend on who opens the mail. The tree below makes it a rule: read the group code, read the reason code, read the paired remark code, then follow the branch. It sends most denials somewhere other than the appeals desk, which is the point.
Key takeaways
The short version
- Four destinations, not two: correct and resubmit, reconsider with documentation, appeal, or write off with a recorded cause.
- Read the group code first. CO, PR, and OA carry different liability consequences before you look at the reason.
- A generic reason code is not a reason. Its content is in the paired remark code, and routing without reading it is guesswork.
- Route by the field that failed, not by the denial's severity: units go to utilisation review, provider eligibility goes to credentialing.
- Never correct-and-resubmit a medical-necessity determination. That is an appeal, and resubmission can cost the window.
- Record the route taken and the outcome. Route accuracy is itself a measurable thing, and it is usually the biggest available win.
Take the template with you
Free to copy · no email required
Printable denial routing tree
The eight-step tree in a form you can pin above a desk, with the four destinations and the day-one actions that apply regardless of route.
Saves as denial-routing-decision-tree.txt
Denial routing log
One row per denial with the route chosen, the field that failed, whether the route changed, and the outcome — the fields route accuracy is computed from.
denial_ref,received_date,payer,plan_type,level_of_care,group_code,reason_code,remark_codes,amount,dates_of_service,is_rejection,determination_type,failed_field,route_chosen,appeal_deadline,claim_file_requested,route_changed_to,days_lost_to_reroute,resolution_date,outcome,amount_recovered,preventable,upstream_owner,owner,next_action,next_action_due DEN-0001,2026-10-06,[payer],Medicaid MC,IOP,CO,197,N54,4820.00,2026-09-14 to 2026-09-30,no,matching_failure,units,correct_and_resubmit,2026-12-05,no,,0,,pending,,yes,utilisation review,[name],recompute units net of prior claims,2026-10-08
Saves as denial-routing-log.csv
1. Four destinations, defined before you start
Most teams operate with two buckets — fix it or fight it — and the ambiguity in between is where work stalls. Four destinations remove the ambiguity, because each has a different owner, a different artifact, and a different clock.
| Destination | When | Owner | Clock that applies |
|---|---|---|---|
| Correct and resubmit | A data or claim-construction error; the payer never evaluated the merits | Billing | Timely filing limit |
| Reconsider with documentation | The payer evaluated but lacked something; an informal review or records submission resolves it | Authorization or utilisation review | Payer's reconsideration window; appeal deadline still runs |
| Appeal | A determination on coverage, medical necessity, or level of care | Appeals | Appeal deadline by plan type |
| Write off, with a recorded cause | Not recoverable, or recovery costs more than the balance | Revenue-cycle lead | None, but the cause must be recorded |
2. The tree
- 01
Step 1 — Is it a rejection or a denial?
A rejection never entered adjudication: it failed a front-end or clearinghouse edit and there is no determination to appeal. Correct and resubmit, and watch the timely filing clock. If it adjudicated, continue.
- 02
Step 2 — Read the group code
CO means a contractual adjustment you generally cannot bill the patient for. PR assigns responsibility to the patient. OA means the paired remark and the contract decide. This changes the financial consequence before any clinical question, and it changes who needs to be told.
- 03
Step 3 — Read the reason code and its paired remark
Generic reason codes carry no content on their own; the remark code names the field. If there is no remark code on a generic reason, that is itself a defect worth raising rather than a puzzle to solve.
- 04
Step 4 — Is this a determination about necessity, coverage, or level of care?
If yes, route to appeal. Do not correct and resubmit. Calendar the appeal deadline the same day and request the claim file.
- 05
Step 5 — Is it a matching failure between the authorization and the claim?
Code, modifiers, units, dates, place of service, rendering provider, facility, or authorization number. Route to the owner of that field and correct, then resubmit. Log which field failed.
- 06
Step 6 — Is it an eligibility, enrolment, or coordination-of-benefits issue?
Route to the function that owns the data: front-office for eligibility, credentialing for enrolment and effective dates, billing for coordination of benefits. These are corrections, not appeals.
- 07
Step 7 — Is something merely missing?
Records, a treatment plan, a form. This is reconsideration with documentation. Send what was asked for, but calendar the appeal deadline anyway, because a reconsideration that fails leaves you inside the appeal window only if you tracked it.
- 08
Step 8 — Still unclear?
Request clarification in writing, and record it as pending clarification rather than as any of the four destinations. Do not guess, and do not let it sit in an untracked state.
3. Routing by what the remittance says
The table below maps denial categories to destinations. It is organised by what the remittance tells you rather than by code number, because the same operational problem shows up under different codes across payers. Where a code page exists on this site, the codes section on this page links to it.
| What the remittance indicates | Destination | First action |
|---|---|---|
| Authorization absent or not obtained | Appeal or reconsider | Check whether one exists; if it does, this is a matching failure, not a missing authorization |
| Authorization exceeded — units or days | Appeal | Compare billed to approved net of prior claims; if billing erred, correct; if treatment exceeded, appeal |
| Service date outside the authorization period | Correct or appeal | If dates were miskeyed, correct; if treatment genuinely fell outside, seek retroactive authorization or appeal |
| Level of service not supported by documentation | Appeal | This is a necessity determination; request the criteria and the claim file |
| Experimental, investigational, or unproven | Appeal | Coverage determination; build the evidence and criteria argument |
| Rendering provider not eligible on the date of service | Correct, via credentialing | Check enrolment effective dates; this is rarely an appeal |
| Records requested and not received | Reconsider with documentation | Send what was asked; confirm receipt; check whether an audit pathway is running |
| Revenue and procedure code mismatch on a facility claim | Correct and resubmit | Facility coding; common on per diem IOP, PHP, and residential claims |
| Add-on code billed without its primary service | Correct and resubmit | Claim construction; check the primary service is present and payable |
| Generic denial with a remark code attached | Read the remark, then route | Do not route on the reason code alone |
| Duplicate claim | Correct or write off | Confirm whether it is a true duplicate or a legitimate repeat service needing a modifier |
| Coordination of benefits — other insurance primary | Correct and resubmit | Update the payer order and rebill; not an appeal |
| Timely filing exceeded | Write off or appeal on proof of timely submission | Pull submission evidence before conceding |
4. What has to happen on day one regardless of route
- Record the denial as structured data: payer, plan type, group code, reason code, remark codes, dates, amount, level of care.
- Calculate and calendar the appeal deadline, even if the chosen route is correction. A failed correction that ran out the clock is a write-off nobody decided on.
- Assign one owner and one dated next action. A denial without an owner has a route and no motion.
- For anything heading to appeal, send the claim file or criteria request the same day.
- Record the route chosen, so route accuracy can be measured later against outcome.
- Flag high-balance or whole-episode denials for same-day human review rather than letting them queue by date received.
5. Measure routing, not just recovery
Most denial dashboards measure recovery rate and days to resolution, which tells you how the desk performed but not whether the work was sent to the right place. Route accuracy is the measure that improves the system rather than the effort.
| Measure | Definition | What it tells you |
|---|---|---|
| Route accuracy | Denials resolved by their first route ÷ all denials | Whether the tree is being applied, and where it is wrong |
| Mis-route cost | Days lost on denials that changed route ÷ denials that changed route | The price of ambiguity, in days |
| Appeals that should have been corrections | Count, by failed field | Points at an upstream control, usually reconciliation |
| Corrections that should have been appeals | Count, by denial category | The most expensive error class; should trend to zero |
| Deadline misses | Denials that aged past an appeal deadline | A process failure, not a staffing one |
| Preventable share | Denials whose cause was a matching or data failure ÷ all denials | How much of your denial volume should not exist |
Common questions
Answers before you build.
Why not just appeal everything and let the payer sort it out?+
Because appeals are the slowest and most expensive route, and most denials are not determinations. Appealing a transposed authorization number takes weeks to achieve what a corrected resubmission achieves in days, and it spends credibility you want available for the determinations that matter.
What is the difference between a reconsideration and an appeal?+
A reconsideration is typically an informal review, often resolved by supplying what was missing, and payers use the term inconsistently. An appeal is the formal process with a regulated deadline and defined rights. The practical rule is to pursue the reconsideration if it is faster, while calendaring the appeal deadline as though it were the only option.
Our denials arrive as paper remittances. Does this still work?+
Yes, but the structured capture step becomes the bottleneck rather than the routing. Key the group code, reason code, remark codes, dates, and amount into a single log as they arrive. Without structured capture you can route individual denials but you can never see the pattern.
Who should own the tree?+
One revenue-cycle lead owns the tree and reviews route accuracy monthly. Individual denials have individual owners, but a tree owned by committee drifts, and the branches that get fuzzy are exactly the ones that cost the most.
How do we handle a denial that belongs to an audit rather than a claim?+
Route it out of the denial workflow entirely. Records requests, prepayment review, and overpayment demands are retrospective payer reviews with their own timelines and escalation paths, and treating one as a denial is how response windows are missed.
Practical closeout
Use this operator checklist.
- Four destinations, not two: correct and resubmit, reconsider with documentation, appeal, or write off with a recorded cause.
- Read the group code first. CO, PR, and OA carry different liability consequences before you look at the reason.
- A generic reason code is not a reason. Its content is in the paired remark code, and routing without reading it is guesswork.
- Route by the field that failed, not by the denial's severity: units go to utilisation review, provider eligibility goes to credentialing.
- Never correct-and-resubmit a medical-necessity determination. That is an appeal, and resubmission can cost the window.
- Record the route taken and the outcome. Route accuracy is itself a measurable thing, and it is usually the biggest available win.
Continue through the cluster
Verified customer case studies are added only with customer permission and supporting evidence; none is implied by these operational examples.
Codes on this topic
Look up the code on the remittance
- CO-16Something is missing or wrong on the claim itself, and the remark code on the line says what.Denial code · Coding & billing
- CO-A1A generic denial. X12 requires a remark code alongside it, and that remark code carries the actual reason.Denial code · Coding & billing
Sources & methodology
Trace the operational claims.
Marsa Health Editorial reviewed the primary and research sources below on October 18, 2026. We translate them into workflow controls, distinguish proposals from final rules, and flag where plan, program, state, contract, or clinical requirements vary.
- 01Health care payment and remittance advice Centers for Medicare & Medicaid ServicesHow the 835 carries claim adjustment reason codes and remittance advice remark codes, which is what a reconciliation step actually reads.Accessed or rechecked October 18, 2026
- 02Appealing health plan decisions Centers for Medicare & Medicaid ServicesCMS guidance on internal claims and appeals rights, notice contents, and the relationship between internal appeals and external review.Accessed or rechecked October 18, 2026
- 0329 CFR 2560.503-1: Claims procedure Electronic Code of Federal RegulationsParagraph (h)(3)(i) gives group health claimants 180 days to appeal; (h)(2)(iii) requires reasonable access to and free copies of all documents relevant to the claim; (m)(8) defines what counts as relevant.Accessed or rechecked October 18, 2026
- 0442 CFR 438.402: The State's grievance and appeal system Electronic Code of Federal RegulationsParagraph (c)(2)(ii) allows 60 calendar days from the adverse benefit determination notice to request a plan appeal, and sets when a provider may file on the enrollee's behalf.Accessed or rechecked October 18, 2026
- 0542 CFR 422.582: Request for a standard reconsideration Electronic Code of Federal RegulationsGives 60 calendar days from the organization determination notice to request reconsideration, and describes who may file.Accessed or rechecked October 18, 2026
- 06External Appeals Centers for Medicare & Medicaid ServicesFederal external-review process and consumer protections.Accessed or rechecked October 18, 2026
- 07CMS Interoperability and Prior Authorization Final Rule CMS-0057-F Centers for Medicare & Medicaid ServicesCurrent implementation dates, decision timeframes, denial-reason requirements, metrics, and API provisions for impacted payers.Accessed or rechecked October 18, 2026
Organizational author. Editorial review covers source accuracy, search intent, workflow boundaries, and human-oversight requirements. This material is educational and does not provide clinical, legal, coding, or coverage advice.
No named clinical or legal expert reviewer is attributed to this version. Marsa Health does not invent reviewer credentials.
Read our editorial methodRevision history
What changed and when
October 18, 2026
Initial publication, source review, and operational editing.