Denials & reviews

How to read a denial letter without missing the real issue

A denial is easier to respond to when you split it into the decision, stated reason, rule or term relied on, evidence considered, missing evidence, deadline and review path.

Reviewed 27 August 2026

A denial letter can feel like one long rejection, but most useful information is scattered across several parts of the document. The first job is not to argue with it. The first job is to turn it into a structured record you can check.

Make a seven-line decision summary

On a clean page, write seven headings: decision, reason, rule or term, evidence mentioned, evidence missing or disputed, deadline, and review route. Fill them only with information you can point to in the letter. If the letter is silent, write “not stated”. That simple phrase is useful because it distinguishes an actual gap from something you may have overlooked.

For example, a fictional warranty denial might say a repair is excluded because the damage is considered accidental. Your summary should not become “they think I misused it” unless the letter actually says that. Record the exact exclusion wording or policy section, then separately note your question: “What evidence was used to classify the damage as accidental?”

Separate reasons from supporting detail

Some letters give one reason and several supporting observations. Others list several independent reasons. Number them. A response that addresses only the easiest point can fail to deal with another reason that is sufficient on its own.

Look for signal words such as “because”, “based on”, “under section”, “not provided”, “insufficient”, “excluded”, “ineligible”, “outside the period”, “unable to verify”, or “does not meet”. Do not let the heading of the letter replace the actual reason paragraph.

Build a reason-to-evidence table

Create one row for each stated reason. In the second column write the fact that would need to be clarified or proved. In the third column list evidence you already have. In the fourth, list evidence you may need to obtain. This converts a vague urge to “send everything” into a reviewable file.

Stated reason	Question to resolve	Evidence already held	Possible gap
Example: required document not received	Was it submitted, and can submission be proved?	Upload confirmation, sent email	Copy of the exact file submitted
Example: event excluded by policy term	What event classification was used?	Photos, invoice, contemporaneous notes	Written reasons or relevant report

Treat dates as a separate workstream

Write down the issue date, the date you received the letter, any date the decision takes effect, the date a review must be requested and any rule about how time is counted. Do not assume “30 days” always means the same thing. Some processes count calendar days, some business days, some start from a service date, and some have special rules for weekends or delivery. A generic calculator can help you plan, but the official rule controls.

Ask for what you need, not for everything

If the reasons are unclear, a focused request can be more useful than an emotional response. Ask for the decision reasons, the clause or rule relied on, the evidence considered, and the available review process if those are not already clear. Keep a copy of your request and proof of when it was sent.

Before you respond

• Read the whole letter including attachments and footnotes.
• Copy reference numbers exactly.
• List every independent reason.
• Match evidence to each reason.
• Verify the current review route and deadline at the official source.
• Keep the original denial unchanged in your records.

---

Finish with a verification check

• Have you preserved the original notice, form or transaction record?
• Can every important factual statement be traced to a document or dated note?
• Have you distinguished official deadlines from your own planning dates?
• Have you checked the current official route before submitting?
• Have you saved proof of what you sent and when?