Digital First Dentistry › Monitoring tooth wear with intraoral scans

Blog · 14 November 2026

Monitoring tooth wear with intraoral scans

Tooth wear usually progresses slowly, which makes it hard to judge at a single visit. Clinicians and patients alike struggle to say whether a worn edge is getting worse or has been stable for years. Routine scans change that, because they turn memory into a record.

Why wear is hard to judge

  • Change between visits is small and easy to miss by eye.
  • Photographs vary with angle and lighting.
  • Notes describe wear but rarely measure it.

What scans add

A full-arch scan with a bite record, taken at routine check-ups, gives a three-dimensional baseline. Later scans can be overlaid on it so that areas of change stand out. Many scanner platforms include comparison tools; others allow scans to be exported for comparison in separate software.

Practical points

  • Scan the full arch and record the bite, so occlusal surfaces and contacts are captured.
  • Be consistent: similar scan strategy, similar conditions, every time.
  • Grade and record each finding as stable, to discuss or at risk.
  • Look for the cause as well as the change: attrition, erosion and abrasion are managed differently.
  • Treat monitoring as an outcome. Where wear is stable, recording it may be all that is needed.

Talking to the patient

Showing a patient two scans side by side, months apart, is often the clearest way to explain why prevention, a splint or restoration is being discussed, or why nothing needs doing yet.

Definitions: tooth wear, attrition, erosion, superimposition.

Get the white paper, starter guide and checklist

Free. Enter your email and we will email all three to you.

Tell us more (optional)

We use your email to send these resources, and updates only if you tick the box. Never shared unless you ask for introductions. Unsubscribe any time.

Written by Dr Bhavin Bhatt BDS MFGDP RCS (Eng), GDC 76358 with AI drafting assistance · Facts checked 16 November 2026 · Editorial policy · Independence · Report an error