Our approach

A Packet, Not Just a Letter: What a Complete Appeal Actually Needs

By the AppealAngle Research Team · Published July 11, 2026

Here is our view, and it shapes how we built AppealAngle: the single most common mistake people make when appealing a health insurance denial is treating the appeal as a letter-writing problem. Write something persuasive, sign it, send it, hope. We think that's backwards. A well-worded letter with nothing behind it is easy for a reviewer to uphold. What actually moves a decision is a complete, organized packet — where every claim you make is backed by a specific document and tied to the plan's own language.

This is our perspective, not a rule handed down by regulators. But it's grounded in how the process actually works. Insurers are required to tell you the reason for a denial and how to dispute it, and you have the right to a full and fair review that considers the evidence you submit (HealthCare.gov). "Full and fair" is the tell: the review is about evidence and criteria, not eloquence. So this article walks through what a complete packet contains, why each part matters to the human reviewing your file, and how you could assemble one yourself — even if you never use our tool.

Why "just a letter" leaves value on the table

Picture the person on the other end. They're a reviewer working through a queue, holding your file against the plan document and a set of clinical criteria. Their job is to decide whether to uphold or overturn. A bare letter asks them to do the work of finding the relevant plan clause, matching it to your situation, and locating the evidence — or, more likely, to uphold because nothing in front of them compels a reversal.

A packet flips that burden. It hands the reviewer the exact clause, the exact evidence, and the exact contradiction, already lined up. You're not asking them to trust your prose; you're showing your work. That matters because the appeal you actually submit has a real chance: in Medicare Advantage, more than 80% (83.2% in 2022) of appealed prior-authorization denials were partially or fully overturned, yet only about one in ten denials were appealed at all (American Medical Association, 2024). And appeals remain rare overall — in ACA Marketplace plans, consumers appealed fewer than 1% of denied in-network claims in 2024 (KFF, 2026). When so few people push back, the person who submits an organized, evidence-backed packet stands out.

What a complete packet contains

Below is the full anatomy of the packet we think an appeal deserves — thirteen elements, and what each one does for the person reading it. You can build every one of these yourself with a folder, your denial letter, and your plan documents.

1. Case summary. One page at the front: who you are, the service denied, the stated reason, the deadline, and what you're asking for. It orients the reviewer in thirty seconds so nothing that follows is a surprise.
2. Document manifest. A numbered list of everything in the packet. It signals completeness and lets the reviewer confirm nothing is missing — and lets you confirm the same before you file.
3. The denial reason, decoded. The insurer's stated reason translated into plain language and pinned to a category — medical necessity, no prior authorization, out of network, not a covered benefit, experimental, or a coding/administrative error. The fix is different for each, so naming the category correctly is the whole game.
4. The appeal deadline. Stated explicitly, calculated from the date on the denial notice. Deadlines are where good appeals die; putting the date on the page keeps it from slipping.
5. A policy-language map. The heart of the packet: the denial reason set directly beside the plan's exact clause that governs it. If the denial says "not medically necessary," this maps it to the plan's own definition of medical necessity, quoted verbatim. You are arguing on the insurer's turf, in the insurer's words.
6. A contradiction log. Every place the insurer's rationale conflicts with the plan language or with your evidence. If the letter cites a criterion your records already satisfy, that's a logged contradiction. Reviewers respond to specific inconsistencies, not general disagreement.
7. A medical-necessity evidence checklist. The clinical proof, itemized: chart notes, test results, records of prior treatments tried and their outcomes, and — the centerpiece — a letter of medical necessity from your treating provider. Each item ties back to a criterion in the policy-language map.
8. A missing-evidence checklist. An honest list of what you don't yet have. This is not a weakness to hide; it's a to-do list that stops you from filing with a hole in your argument. Better to see the gap now than have the reviewer find it.
9. A source-cited issue list. Each argument you make, paired with the specific document and page that supports it. No claim floats free. If you assert a therapy failed, the citation points to the note that says so.
10. The draft appeal letter. Yes, there's still a letter — but it sits inside the packet as a summary of everything else, not as the whole case. In our tool it's marked DRAFT — NOT FOR SUBMISSION so you review, edit, and own it before anything is filed. It's the cover argument; the evidence is the substance.
11. Provider and expert questions. A short list of things to ask your doctor or a specialist — the specific statements or records that would strengthen the medical-necessity case. This turns a vague "get a letter from your doctor" into a targeted request.
12. An approval checklist. The final pass before you file: reason answered, IDs and claim numbers present, provider letter attached, criteria referenced, deadline confirmed, copy kept. It's the difference between a packet that's done and one that just feels done.
13. A receipt of sources used. A record of every document and citation the packet relied on, so you — and anyone helping you — can trace exactly where each claim came from. It keeps the whole thing honest and auditable.

What each element does for your appeal

Another way to see it: each part of the packet is doing a specific job for the reviewer. Here's the map.

Build one yourself: a starter framework

You don't need our tool to work this way. Here's a checklist you can run with a folder and your own documents:

• ☐ Write a one-page case summary: service, denial reason, deadline, your ask
• ☐ Number every document you have and list them in a manifest
• ☐ Name the denial category from the letter — and quote the exact wording
• ☐ Pull the matching clause from your Summary Plan Description or Evidence of Coverage and set it beside the denial reason
• ☐ Log every place the insurer's reasoning conflicts with that clause or your records
• ☐ Check off the clinical evidence you have; list what you still need
• ☐ Tie each argument to a specific document and page
• ☐ Write the draft letter last, as a summary of the packet — and mark it a draft
• ☐ Run a final approval pass; keep a dated copy of everything

To make the policy-language map possible, request your plan documents and the insurer's clinical criteria in writing. For employer (ERISA) plans especially, you generally have the right to receive, free of charge, the documents and criteria relevant to your claim — the same materials the insurer used to say no. That request is what lets you argue clause by clause instead of in generalities.

Where we land

A letter argues. A packet proves. When we designed AppealAngle, we chose the packet on purpose: a case summary, a policy-language map, a contradiction log, evidence and missing-evidence checklists, source-cited issues, and a draft letter that stays clearly marked DRAFT — NOT FOR SUBMISSION until you approve it. That's our approach, and we think it's the right default whether you build it by hand or let a tool assemble the first draft for you. The reviewer's job is to weigh evidence against the plan's own rules — so give them exactly that, organized, and make the strongest version of your case the easy one to say yes to.