← Back to Insights

Operations

Scoring an unscheduled treatment report in multi-office dental groups

By Better Software · Fri Sep 18 2026 · 10 min read

Scoring an unscheduled treatment report in multi-office dental groups

The unscheduled treatment report in a single dental office is usually manageable. In a group, it stops being a list and becomes a portfolio. The useful question is no longer “how many dollars are unscheduled?” It is “which lines are worth a phone call this week, after we remove duplicates, stale plans, and patients who are already handled somewhere else?”

The answer is to treat the report as a scoring problem. Before anyone calls, run four passes: dedupe the patient, re-price the treatment, age the plan, and exclude what should not be on a call list at all. Once you do that, the headline dollar total usually shrinks, but the remaining number is far closer to work you can actually schedule.

What the unscheduled treatment report actually contains

Most practice-management systems can print some version of an unscheduled treatment report. The details vary, but the output usually includes the patient name, phone number, planned procedures, diagnosing provider, carrier, benefit renewal date, remaining benefits, and a plan amount or batch total.

That sounds more complete than it is. In Dentrix, for example, offices often use the report flags marked “S” and “U” to sort scheduled and unscheduled items, but those flags only tell you whether the procedure is currently in one of those states inside that database. They do not prove the diagnosis is still current, the fee is current, or the patient is still a valid call target.

The report also omits the things a group operator needs most:

  • No reliable diagnosis-quality signal.
  • No cross-location view of the same patient.
  • No current-fee re-pricing if the fee schedule changed after diagnosis.
  • No freshness check on eligibility or remaining benefits.
  • No clear provider attribution beyond where the plan was entered.
  • No useful distinction between a plan created yesterday and one created two years ago.

That is why the report can be useful in a single location but misleading across ten, twenty, or forty-five offices. The more systems you have, the more likely the same patient appears in more than one place, and the more likely the dollar figure on the screen is a mix of real opportunity and stale bookkeeping.

Why the same list behaves differently at 3 offices and at 30

At small scale, the front desk already knows which patients are worth reaching. At group scale, that local knowledge disappears. A central team sees a large number, a sorted list, and not much else. If that team works top-down by dollar amount, it often starts with the least closeable work first: large cases that are old, poorly aged, duplicated, or no longer clinically relevant.

Group dentistry makes this worse for three reasons. First, acquisitions bring in years of inherited charts. Second, mixed practice-management systems do not reconcile cleanly with one another, so a patient may appear in Dentrix at one office and in Open Dental or Eaglesoft at another. Third, diagnosis and pricing drift over time. A treatment plan entered before a fee update may show a dollar figure that no longer matches what the practice would collect today.

That is why a multi-office unscheduled treatment report should be treated like a reconciliation problem, not a calling report. You are not trying to work every line. You are trying to build a smaller, cleaner queue with a higher chance of becoming scheduled care.

A scoring model for diagnosed-but-unscheduled treatment

The simplest useful model is not complicated. It asks two questions about every line: should this patient be excluded outright, and if not, how likely is this plan to convert this quarter?

Start with exclusion rules

Before scoring anything, remove records that should not be called at all. A practical exclusion list looks like this:

  • The patient is already scheduled for the same treatment.
  • The patient was treated elsewhere in the group.
  • The plan is already in an active recall or hygiene follow-up sequence.
  • The plan is so old that it should be re-diagnosed rather than re-sold.
  • The patient has no usable contact path.
  • The remaining benefit data has not been verified and is too stale to trust for a call.

These exclusions matter because they prevent a call team from spending time on records that are not actionable. They also keep the score from being polluted by patients who only look unscheduled because the database has not been reconciled.

Then score the plans that remain

After exclusions, assign points or weighted values to the fields that change the odds of scheduling. The exact weights should fit your group, but the signals are usually consistent.

  • Diagnosis age. The older the diagnosis, the more likely the patient’s condition, finances, or insurance have changed.
  • Diagnosing provider still employed. Patients are often easier to schedule when the original doctor is still in the group and available to re-engage the case.
  • Procedure category. Some treatment is symptom-driven and easier to move than elective or cosmetic work.
  • Benefit remaining verified within a recent window. Fresh eligibility data is more useful than a cached balance from last year.
  • Benefit year-end proximity. Patients with remaining annual benefits may be more actionable near year-end.
  • Prior no-show or cancellation history. This lowers the score because the phone call is less likely to convert quickly.
  • Distance to the nearest group location. The more convenient the office, the better the chance of scheduling.
  • Last hygiene visit. Recent contact usually improves the odds that the patient is still active.
  • Partial course already started. A case that began but did not finish is often more reachable than a brand-new elective plan.
  • Outstanding patient balance. A large unpaid balance can slow scheduling even when the treatment is clinically important.

An illustrative example helps. Suppose two unscheduled crown cases both show $2,400 on the report. One was diagnosed three weeks ago, the provider is still in the practice, eligibility was checked last week, and the patient lives near the nearest office. The other was diagnosed 19 months ago at a location that has since changed fee schedules, the patient had two cancellations, and the chart still shows an old benefits figure. They are not equal opportunities, even though the report prints the same dollar amount.

That is the core mistake with a gross unscheduled treatment total. The number looks precise, but it is not a ranked pipeline. The score is what turns the list into a queue.

Re-price before you rank

The diagnosed amount and the collectible amount often diverge. A fee schedule may have changed. A payer contract may have changed. The patient may have moved to a different plan. Any of those changes can make the original figure unreliable.

For that reason, the score should use today’s fee schedule and today’s contracted rate whenever possible, not the amount saved at diagnosis. If you cannot re-price automatically, flag the line as “price unverified” and push it down the queue. A line with an outdated dollar figure should not outrank a line with a verified collectible amount.

This is one place where an analytics layer or internal data layer is useful. A PMS report can show what the office entered. A better queue can show what the group is likely to collect now.

Which tool is enough: PMS report, analytics layer, or your own data layer

The right answer depends on how many systems you operate and how much control you need over the queue.

OptionWhat it can doWhere it breaks down
PMS report onlyShows local unscheduled treatment in one system.Weak across mixed systems, no cross-location dedupe, limited control over ranking.
Bolt-on analytics productCan aggregate data across offices and add some filtering.May still inherit stale diagnosis logic and vendor-defined views of the data.
Internal data layer over all PMS instancesCan dedupe patients, re-price plans, apply scoring, and change rules as the group changes.More setup and governance. Requires someone to own the logic.

If you have one PMS, a handful of locations, and no near-term acquisition plan, a bolt-on analytics tool may be enough. It gives you a better view without forcing a bigger data project.

Once you have multiple PMS vendors, a central scheduling team, or comp plans tied to unscheduled production, the bolt-on often stops short. At that point you need the queue to be ordered, not just populated. You also need the logic to survive the next acquisition, because every new office imports more stale data and more report formats.

That is the same basic problem Better helped solve for Apex Dental Partners, where a group that grew past 45 practices needed reporting, payroll, time management, and day-to-day operations to work across locations rather than inside one office. The broader point is simple: in a multi-office dental group, reporting is usually a reconciliation problem first. If you need the operational context behind that kind of work, see Better’s healthcare page.

What to measure after you change the list

Do not measure success by the gross unscheduled dollar total on the dashboard. That number may go up or down for reasons that have nothing to do with conversion. Measure whether the list became more actionable.

  • Contact-to-schedule rate by cohort. Compare new plans, plans 3 to 12 months old, and plans older than a year.
  • Schedule-to-chair-time rate. Some calls create appointments that never turn into completed care.
  • Re-diagnosis rate on older plans. If many plans older than 12 months are being re-diagnosed, your aging rule is working.
  • Close rate by location and provider. Normalize for case mix so one office is not blamed for a harder patient mix.
  • Dollars actually collected versus dollars ranked. This tells you whether your scoring model predicts real revenue or just produces a prettier list.

If these measures improve, the model is doing its job. If they do not, the problem is usually one of three things: the exclusions are too loose, the re-pricing is stale, or the call team is still working the list in the wrong order.

The practical next step

If you are running a group with mixed systems, start with a simple test on one month of data. Pull the unscheduled treatment report from each PMS, dedupe patients across offices, re-price the lines against today’s fees, exclude anything already scheduled or clearly stale, and then rank what remains by diagnosis age, eligibility freshness, provider availability, and patient accessibility.

If that exercise turns a big dashboard number into a much smaller queue with obvious priorities, you have your answer. The report was never the problem. The problem was asking it to do the work of a scoring model.

FAQ

How do I run the unscheduled treatment report in Dentrix, Open Dental, or Eaglesoft?

Run the vendor report for unscheduled treatment or unscheduled treatment plans in the system where the patient was diagnosed. The exact clicks differ by product and version, so use the vendor help documentation for the mechanical steps. For a group operator, the hard part is not pulling the report. It is reconciling and ranking what comes out of multiple systems.

What can you filter unscheduled treatment plans by?

Usually by provider, office, date range, treatment category, and sometimes patient or family. Those filters are useful, but they do not solve cross-location duplication, stale pricing, or diagnosis aging. Treat them as input filters, not a complete ranking method.

How often should the report be run?

For a single office, weekly may be enough. For a central team working a live queue, daily or near-daily is better because eligibility, appointments, and cancellations change quickly. The right cadence depends on how fast your call team can work through the list and how often your data changes.

Should we outsource the calling?

Only if the list is already clean enough to work. Outsourcing a noisy, duplicated, stale report usually shifts the problem rather than solving it. A third party can make calls, but it cannot fix broken dedupe, stale fee data, or weak eligibility data for you.

Why does our group total not match the sum of the offices?

Because each office may be counting a different version of the truth. One office may include older plans, another may exclude inactive patients, and a third may be using a different fee schedule or eligibility snapshot. Mixed PMS systems make this more common, not less. Before you compare totals, define the rules for inclusion, re-pricing, and aging.