Downgrades and frequencies: the two silent write-offs

If you had to guess where a well-run office loses production, you'd probably say cancellations, no-shows, or unfilled hygiene columns. Those are the losses everyone can see. The bigger loss is quieter, and it doesn't show up on the schedule at all: the difference between what your office quoted and what the payer actually paid, multiplied by every visit, every month, forever. Two rules cause most of it. They are called downgrades and frequencies.

Downgrades

A downgrade is a payer rule that pays a procedure at the fee of a less expensive procedure. The classic example is a posterior composite. The office bills a D2392, a two-surface composite on a molar. The plan carries a downgrade rule that pays at the amalgam fee — D2150 — because amalgam is, in the plan's words, the least costly method that would restore the tooth to function. The composite is still performed. The composite is still coded. The composite is still paid, but at the amalgam price.

The difference is not the plan's problem. It is the patient's problem, unless the office writes it off. Most offices write it off — because at the counter, the estimate said the plan would cover 80% of $215, and the patient wrote a check for the balance. When the EOB comes back at $128 allowed, the arithmetic no longer works, and the office is chasing a $70 balance from someone who thought they were paid up.

Downgrades apply to more than composites. Common downgrade pairs include:

• Porcelain-to-noble crown → base-metal crown fee (D2750 → D2790)
• White filling on posterior → amalgam fee (D2392 → D2150)
• Implant supported crown → traditional crown fee, on some plans
• Partial dentures with certain framework materials → basic acrylic partial
• Bone graft or membrane after extraction → often not covered at all, not just downgraded

A downgrade is not a percentage — it is a fee substitution. It has to be applied at estimate time, per code, not per category, or the number at the counter will not match the number on the EOB.

Frequencies

A frequency limit is the payer's rule about how often a specific service can be performed and still be covered. The most familiar example is bitewings: two per year. But 'per year' hides three different definitions:

• Calendar year — January 1 to December 31, resets on New Year's Day.
• Plan year — 12 months from the plan's effective date, which is different for every employer.
• Rolling 12 months — no reset date; a service performed today counts against the next 12 months.

A patient with a January cleaning and a July cleaning is fine on a calendar-year plan. On a rolling-12 plan, the same patient booked for a cleaning in December will be denied — the second one only cleared the six-month exam-and-cleaning cycle in mid-July.

Frequencies apply to more than prophies and exams. Watch for:

• Full-mouth x-rays or panoramic (once every 3 or 5 years, depending on plan)
• Sealants (once per tooth in a lifetime, on many plans)
• Perio maintenance (four per year, but on rolling-12, not calendar)
• Fluoride (per year, often with an age cap)
• Nightguards, occlusal adjustments, and CPAP appliances (once every N years, if at all)

Why this is a system problem, not a person problem

No front-desk person is going to remember every downgrade and every frequency on every plan in your patient base. The answer isn't a smarter team. The answer is that the plan facts should be verified once, in detail, and then read automatically at estimate time — so the person quoting sees the downgrade applied and the frequency window checked, without having to remember the plan they're looking at.

How Chartwright handles this

Chartwright Cloud captures downgrades at the code level and frequencies at the code-plus-window level. Chartwright OS applies both automatically when a visit is estimated. The number at the counter is the number the payer will honor — or, when the payer won't honor it, the office knows before the patient signs, not after. If that sounds like an obvious way for a system to work, that's because it is. Twenty minutes on demo will show you it working on your own plans.