Reported, not repackaged

Claim Refused? The Five Checks That Come Before the Appeal, and the Order to Run Them

title:Claim Refused? The Five Checks That Come Before the Appeal, and the Order to Run Themauthor:Beatrix Stapletonpublished:2026-05-04section:Healthwords:1,016read:4 min
A denial letter and an explanation of benefits statement laid out on a kitchen table beside a handwritten log of phone calls and reference numbers
A denial letter and an explanation of benefits statement laid out on a kitchen table beside a handwritten log of phone calls and reference numbers

A denial letter is a document with a job to do. Read it in the right order and the appeal usually writes itself, often at a level below a formal hearing.

A refusal arrives as a short document with a code on it, and most people respond to the tone rather than the content. That is the expensive move. The letter is a procedural artifact: it was produced by someone with a queue, a rulebook, and a deadline, and it usually tells you which of those three failed. Read it that way and the appeal often turns out to be narrower, faster, and lower-stakes than it first looked.

Two things have shifted in the past few years that change where the leverage sits. Denial notices are increasingly required to name the specific rule or clinical criterion relied on, rather than gesturing at medical necessity in general. And payers are being pushed toward shorter decision windows on prior authorization, with electronic submission and status tracking replacing fax-and-wait. Both changes reward a reader who knows what to look for on the first page.

What changed, and why it matters before you appeal

The older generation of denial letters could survive on a phrase. "Not medically necessary." "Service not covered under the terms of your plan." That was hard to argue with because it did not commit to anything. The newer expectation, driven by federal rulemaking on prior authorization and by tighter standards for Medicare Advantage plans, is that a denial identifies the criterion applied and makes the basis for it available on request. When a plan relies on its own internal coverage rules rather than the terms of the benefit itself, that has become a harder position to hold.

The practical effect: a vague denial is now a defect you can point at, not just something to be frustrated by. If the letter does not say which criterion you failed, your first communication is a request for it, and the clock on your appeal deadline is worth protecting while that request is pending. The Department of Labor oversees claims and appeals procedures for employer-sponsored group health plans, and those procedures are written on the assumption that you are entitled to know the reason and to see the documents behind it.

Five things to check before you write a word

  1. Whether it is a denial or a rejection. These are different animals wearing the same coat. A rejection is administrative: the claim never entered adjudication because a member ID was mistyped, a taxonomy code was wrong, or the payer was billed as primary when it is secondary. Nobody made a coverage judgment. A denial means a decision was reached. Rejections are fixed by a clerk in the billing office resubmitting a corrected claim, and no appeal is needed or appropriate.
  2. The reason code, in its own words. Find the specific code and remark code on the explanation of benefits and read them literally. "Requires prior authorization" is a process failure and may be curable retroactively. "Non-covered benefit" points you at the plan document. "Not medically necessary" points you at clinical records. "Duplicate" and "included in another service" point you at coding. Each one sends the appeal to a different desk.
  3. Who actually decided. First-level reviews are often done against a checklist by staff who are not clinicians. A denial that turns on clinical judgment but was issued without clinical review is worth naming. So is a plan that applied an internal guideline when the benefit language is broader. Ask, in writing, for the credentials of the reviewer and the criteria used.
  4. Whether the coding matches what happened. A surprising share of refusals are coding disagreements dressed as coverage disputes: a modifier omitted, a diagnosis code that does not support the procedure code, a place-of-service mismatch. Your provider's billing staff can see this in a minute and often already know. Fixing a code is not an appeal, and it is much faster.
  5. Your deadlines, both of them. There is a deadline to file the internal appeal, commonly 180 days from the notice for group health plans, and a separate, shorter one to request external review after the plan's final decision. Write both on the folder. If the care is urgent, say so explicitly, because expedited timelines exist and are not applied automatically.

The order the appeal actually runs in

Skipping a rung usually costs weeks, because the higher body will send you back down. The sequence, in the order to attempt it:

StepWho decidesBest used when
Corrected claim or reconsiderationPayer claims staff, at your provider's requestCoding, eligibility, or authorization mechanics
Peer-to-peer reviewPlan medical director and your treating physicianMedical necessity, while the case is still recent
Internal appeal, first levelA plan reviewer not involved in the original decisionThe formal record starts here; attach the criteria you requested
Internal appeal, second levelPlan panel or committeeWhere the plan's own process requires it before external review
External reviewAn independent review organization, or your state insurance departmentAfter a final internal denial, on medical necessity and similar questions

Two side doors matter. If the dispute is a surprise out-of-network bill, the argument is between the provider and the plan under federal independent dispute resolution, and you should not be holding the balance at all. If the plan is a self-funded employer plan, the human resources benefits manager can sometimes resolve in a phone call what the appeals unit would take sixty days to process.

Building the judgment about when to escalate

The question worth answering early is which kind of disagreement you have. A factual dispute (what code, what date, what network status) is settled with a document and belongs at the lowest rung. An interpretive dispute (whether this treatment meets the plan's standard) needs a clinician's letter and eventually an outside reviewer. Spending an appeal level on the wrong kind wastes the only resource you control, which is time on the calendar.

Keep a single dated log: who you spoke with, the reference number, what they said they would do. Independent reviewers read that log, and so do state regulators. It is the cheapest thing in the file and it does more work than the letter you were tempted to write on day one.