Writing Clinical Narratives That Actually Get Approved

A payer reviewer never sees your patient. They see your submission. The clinical narrative — the few sentences you attach to explain why a procedure is necessary — is often the single thing that decides whether a pre-determination is approved, denied, or bounced back for more information. And most narratives get it wrong in the same predictable ways. A strong narrative isn't longer or more clinical; it's one that answers the exact questions the reviewer is required to check.

Why the narrative carries so much weight

Payers approve based on evidence, and for anything beyond routine diagnostic and preventive care, the narrative is where the clinical justification lives. Radiographs and charts show what is happening; the narrative explains why it requires this specific treatment now. When a reviewer can't connect the diagnosis to the procedure from what's in front of them, the safe default is to deny or request more information — not because your clinical judgment was wrong, but because it wasn't on the page.

This is the core mental shift: the reviewer is not evaluating your treatment. They're evaluating your documentation of your treatment. A perfectly justified procedure with a vague narrative loses to a well-documented one every time.

The anatomy of a narrative that gets approved

A strong narrative answers five questions, briefly and specifically:

What's the diagnosis? Name the condition, not just the tooth. "Tooth #30 with a fractured MODL cusp and recurrent decay under an existing restoration."
What are the objective findings? The measurable evidence — pocket depths, bone loss percentage, caries extent, mobility, symptoms and their duration. Numbers beat adjectives.
Why is this procedure necessary? Tie the diagnosis directly to the treatment. Why a crown and not a filling; why extraction and not endo.
What has been tried or ruled out? Prior treatment, why a more conservative option won't work, relevant history.
What evidence supports it? Point to the attached radiographs, charts, or photos by name so the reviewer connects your words to the images.

Specificity is the whole game. "Patient needs a crown" tells the reviewer nothing. "Tooth #30 has a fractured mesiolingual cusp with recurrent caries extending subgingivally; remaining tooth structure is insufficient to retain a direct restoration; see attached PA and bitewing" gives them everything they need to approve.

Procedure-specific essentials

Different procedures trigger different review criteria. The narrative should speak to the ones that matter:

Crowns: extent of decay or fracture, cusp involvement, why the remaining structure can't hold a filling, whether there's a crack or prior endodontic treatment.
Scaling and root planing (D4341/D4342): pocket depths by quadrant, radiographic bone loss, bleeding on probing, presence of calculus — the objective perio picture that distinguishes therapy from a routine cleaning.
Extractions: the reason (non-restorable caries, fracture, severe perio, impaction), and why it can't be saved.
Implants and grafts: the missing tooth, ridge or bone condition, why this restorative path, and — critically for grafts — why the graft is separately necessary rather than incidental to the placement.
Occlusal guards, buildups, perio surgery: each has its own necessity threshold the narrative should hit head-on.

The mistakes that get narratives denied

Most denied narratives fail in one of a handful of ways:

Restating the code. "D2740, crown, porcelain" is not a narrative — it repeats what the reviewer already sees.
Vagueness. "Tooth is bad," "patient in pain," "needs treatment." No diagnosis, no findings, nothing to approve against.
No necessity link. Describing the condition but never connecting it to why this procedure.
Contradicting the evidence. A narrative that claims severe bone loss when the attached film shows none gets flagged fast.
Missing the evidence entirely. Asserting findings without attaching the radiographs or charts that back them.

A simple structure you can reuse

You don't need a template for every code — you need a habit. For any procedure that requires justification, write two or three sentences that move from diagnosis → objective findings → why this treatment → see attached evidence. That order maps directly onto how a reviewer reads, and it forces you to include the necessity link that vague narratives skip.

Where Accord fits

Accord Dental checks whether each procedure's documentation actually supports what you're submitting — flagging when a narrative is missing, thin, or unsupported by the attached evidence before the pre-determination goes out. It knows which procedures need a necessity narrative and what a reviewer will look for, and it ties every flag back to the specific payer rule or ADA guideline behind the requirement. Instead of a denial that says "insufficient documentation" three weeks later, you fix the gap while the patient is still in the chair.

The reviewer decides from what's on the page. Put the diagnosis, the findings, and the necessity there — specifically — and approvals stop being a gamble.