Skip to main content

Pre-Auth

The Dental Pre-Authorization Checklist: Stop Getting Denied Before Treatment Starts

March 25, 2026 · 7 min read

Waiting three weeks for a pre-auth that should take three days is a common problem. You submit the crown claim. Two weeks later, denied. Why? No pre-auth. Or worse — you submitted one when the carrier didn't even require it, and now you've wasted everyone's time for nothing.

The rules change depending on the carrier, the procedure, and sometimes even the specific plan type within the same carrier. Cigna wants pre-auth on premolar crowns but not molars. Delta requires it for implants but not surgical extractions. There's no universal standard, and carriers don't publish clear guides.

This guide covers which procedures need pre-auth by carrier, what documentation to include, and how software can handle most of this automatically.

Which CDT Codes Require Pre-Authorization?

Not everything needs pre-auth — that's part of the problem. Offices either over-submit (wasting days on approvals they didn't need) or under-submit (eating a denial they could've prevented). Here are the CDT codes that most commonly trigger pre-auth requirements across the five major carriers:

ProcedureCDT CodeDeltaCignaMetLifeAetnaBCBS
Crown (porcelain)D2740VariesYes*NoVariesVaries
Implant bodyD6010YesYesYesYesYes
Surgical extractionD7210NoVariesNoNoVaries
SRP (4+ teeth)D4341NoNoNoNoNo
Osseous surgeryD4260YesYesVariesYesYes

*Cigna requires pre-auth specifically for premolar crowns. Molar and anterior crowns may not require it.

The Pre-Authorization Documentation Checklist

Getting a pre-auth approved isn't just about submitting it. It's about submitting the right stuff with it. Miss one attachment and you're looking at another 2-4 weeks of back-and-forth while the patient sits in limbo.

Here's what you need every time:

  • Completed ADA claim form with accurate CDT codes and tooth numbers — double-check these, because a typo here snowballs into a denial later
  • A clinical narrative that actually explains why the procedure is necessary (not just "tooth is broken" — tell the story: existing restoration failed, recurrent decay undermining the remaining structure, crown is the least invasive option)
  • Radiographs — periapical or pano depending on the procedure, and they can't be older than six months. Carriers will reject stale images without telling you that's the reason.
  • Periodontal charting — for any perio procedure, include probing depths, bleeding on probing, and bone loss measurements. If you don't attach it, they'll ask for it, and that's another two weeks gone.
  • Intraoral photos — especially for crowns. Show the fracture, the decay, the failing restoration. A picture is worth a thousand words in a narrative, and reviewers appreciate not having to guess.
  • Treatment history — any previous work on the same tooth, particularly if frequency limitations are in play

Common Pre-Auth Mistakes That Cause Dental Claim Denials

  1. Not knowing the carrier requires it in the first place. This is the most common mistake. Cigna wants pre-auth for premolar crowns. MetLife doesn't. If you're juggling 200+ patients across five carriers, you can't keep all of that in your head.
  2. Letting the pre-auth expire. Most are good for 90 days. Sounds like plenty of time until the patient reschedules twice, and suddenly you're at day 95. Claim denied. You have to start the whole process over, and the patient is frustrated.
  3. Mismatched codes between pre-auth and claim. You pre-authorized D2740 but submitted D2750 on the final claim. To you, it's the same crown. To the carrier's system, it's a completely different procedure. Denied. This one's surprisingly common and completely preventable.
  4. A weak narrative. "Patient needs crown" isn't a narrative. It's a sentence. The reviewer wants clinical findings, the rationale for this specific treatment, and why alternatives won't work. Same standards apply whether it's a pre-auth request or a final claim — don't phone it in on the pre-auth just because it feels like a formality.

How AI Automates Dental Pre-Authorization

Memorizing pre-auth rules across 13 carriers and 180 procedure codes isn't realistic. This is the kind of rules-based work that AI billing software handles well. You enter a claim, and the system already knows whether that carrier requires pre-auth for that specific code. No Googling, no calling the carrier's provider line, no guessing.

Here's what a good AI billing platform handles automatically:

  • Flags when pre-auth is required for a specific carrier + procedure combo before you submit
  • Generates a carrier-specific clinical narrative tailored for pre-auth approval — not a generic template, but language that matches what each carrier's reviewers actually want to see
  • Builds the attachment checklist so you know exactly which documents to include
  • Estimates approval probability and turnaround time, so you can set patient expectations
  • Tracks expiration dates and alerts you before a pre-auth goes stale

What used to be a 30-minute research-and-paperwork task becomes a 60-second automated check. If you're running complex treatment plans with crowns, implants, and perio surgery across multiple carriers, that time adds up fast. That's hours per week saved on administrative work.

Never miss a pre-auth requirement again.

AIDentalClaims knows which of the 180 CDT codes require pre-authorization for each of 13 carriers. Automated dental claim scrubbing catches it before you submit.

Try It Free