A claim appeal is not a longer version of “please reconsider.” It is a structured argument that connects the payer’s stated reason for denial to the rule, documentation, and claim facts that support a different outcome. Before writing anything, verify that an appeal is actually the right vehicle. Correctable claim data may belong in a corrected-claim workflow; a missing attachment may have a specific reopening or documentation path; a true adverse coverage determination may require a formal appeal. Sending every problem as an appeal slows the queue and can waste a limited filing window.
Build the packet before drafting the letter
Appeal packet checklist
- Claim number, patient/member identifier, dates of service, billed service lines and amounts
- The exact denial reason from the ERA/EOB, including CARC/RARC or payer message
- The payer policy, Medicare NCD/LCD, contract provision, authorization record, or other controlling source
- Relevant clinical documentation—not the entire chart by default
- Proof of prior submission or authorization when timing/status is disputed
- The appeal level, filing deadline, submission method, and address/portal destination
- A dated cover letter that states the requested action and lists the enclosures
The best argument is usually one page long before attachments. Start with what was denied, why the payer says it was denied, and what you are asking the payer to change. Then explain the factual mismatch. If the payer says authorization was absent and you have a valid authorization number covering the date and service, lead with that. If the denial concerns medical necessity, identify the policy that applies and point to the specific note elements that satisfy it. Do not overwhelm the reviewer with unrelated chart pages or generic statements about the patient needing care.
Use policy precisely: national, local, or payer-specific
For Original Medicare, the Medicare Coverage Database can show whether an NCD applies nationally and whether a MAC has an LCD or related Billing & Coding Article for the service. An LCD is jurisdiction-specific, so the contractor and service location matter. Commercial plans may publish medical policies with their own effective dates and criteria. Quote only the portion that matters and record the version/effective date you relied on. If the policy changed after the date of service, a current page may not describe the rule that controlled the original claim.
Deadlines belong on the tracker, not in memory
Appeal windows vary by payer and level. For Medicare fee-for-service, CMS currently states that a first-level redetermination request generally must be filed within 120 days from receipt of the initial determination. Later appeal levels have different windows and procedural requirements. Commercial and Medicaid plans have their own rules. Capture the deadline as soon as the denial enters the queue, along with proof of submission. A beautiful appeal sent one day late may never reach the merits.
First level, second level, and external review are not interchangeable
A first-level appeal often asks the original payer or contractor to reconsider with supporting information. A second level may go to a different review unit or entity and can have stricter requirements about evidence. External review applies only in certain benefit and dispute contexts and should not be treated as a universal third step for provider claims. Read the denial notice and payer manual for the actual ladder. When a first appeal fails, compare the new decision with the original packet; do not resend the same letter automatically if the reviewer identified a different gap.
Close the loop after the decision
Record the outcome, decision date, payment or adjustment, next deadline, and root cause. If a denial was overturned because a valid authorization was omitted from the claim, fix the workflow that failed to carry the authorization number. If multiple denials cite the same policy, notify coding or clinical teams where appropriate. Appeals are expensive touches. The best appeal program uses overturned and upheld cases to reduce the number that should never have been denied—or appealed—in the first place.
Make every assertion traceable to an exhibit
A reviewer should be able to move from each important sentence in the letter to a specific piece of evidence. Use a simple exhibit index when the packet is more than a few pages: Exhibit A = denial/remittance, Exhibit B = authorization, Exhibit C = relevant note pages, Exhibit D = policy version in effect for the date of service. In the letter, point to the exact exhibit and page rather than saying ‘see attached records.’ This is especially useful when one chart contains dozens of pages but only two findings matter to the dispute. It also makes internal QA easier because a second employee can verify whether the argument actually matches the evidence before submission.
Control the transmission as carefully as the argument. Record the appeal level, destination, method, date sent, confirmation or portal receipt, packet version, and the employee who submitted it. If the payer later says the packet was incomplete or never received, a copy of the final file plus transmission evidence is more useful than a note that says ‘appealed.’ When a decision returns, link it to the same record and classify the result—overturned, upheld, partially paid, returned for missing information, or redirected to another workflow. That history turns one appeal into training data for the denial team instead of leaving the outcome buried in account notes.