Your periodontal practice management software is probably sitting on hundreds of reports you have never run. Legacy perio systems brag about having 300-plus reports, and that number is meant to impress you. It should worry you instead. A report you have to remember to pull, build, and interpret is a report that does not get run on a busy Tuesday. The reports that actually protect your revenue and your patient base are the ones the software generates on its own, drops in front of the right person, and ties to an action. Everything else is a filing cabinet.
So here are the four reports your system should produce without you asking, why each one maps to how a perio practice actually makes and loses money, and the contrarian reason report quantity is a vanity metric.
The short answer
Good periodontal practice management software automatically generates four reports and pushes each to the person who can act on it: a perio maintenance recall report that flags lapsing supportive-therapy patients, an unscheduled treatment report that surfaces accepted cases sitting idle, a referral source report that shows which dentists are sending or slowing, and an AR and cross-coding report that catches denials before they age out. The test is not whether your software can produce these. It is whether it produces them on a schedule and turns each into a queued task. DSN was built for periodontal workflows specifically, so recall, referrals, and cross-coding run as automated workflows rather than reports you have to hunt down.
Why periodontal practice management software needs different reports than general dentistry
A general dental office runs on recall for cleanings. A periodontal practice runs on something more fragile: converting active treatment into lifelong supportive care, and keeping a referral pipeline warm. The money is not in the first SRP. It is in whether that patient shows up every three months for the next decade, and whether the dentist who referred them sends the next fifteen cases.
That means your reporting cannot be generic. It has to watch the specific seams where perio practices leak: patients who finish scaling and root planing and quietly disappear, treatment plans that get accepted and never scheduled, referrers who go dormant, and claims that fall into the gap between dental and medical coding. General dental software does not watch those seams because a general office does not have them in the same way. Purpose-built periodontal practice management software does.
Report 1: The perio maintenance recall report
This is the report that decides whether your practice compounds or churns. After active therapy, periodontal patients need supportive maintenance every three to four months. Miss that cycle and you lose the recurring revenue and, worse, the patient’s periodontal health backslides.
The report you need answers three questions automatically: who completed active treatment but never booked their first maintenance visit, who is overdue for their next supportive-therapy appointment, and how many patients have gone dark entirely. The version most legacy systems offer makes you build a query and read a list. The version that works generates the list on a schedule and hands your coordinator the recall queue with reminders already teed up.
DSN automates recall scheduling and reminders so maintenance patients stay on track without your team living inside a spreadsheet of phone calls. That is the difference between a report that tells you 40 patients lapsed and a system that already started winning them back. A list is a guilt trip. A queued workflow is revenue recovery.
Report 2: The unscheduled treatment report
Here is money most perio practices cannot see: treatment that was presented, accepted, and then never scheduled. A patient agrees to a graft or an implant case in the chair, walks out to reschedule, and falls through a crack. That accepted-but-unscheduled treatment is real dollars sitting frozen in your system, and almost nobody reports on it.
Your periodontal practice management software should generate an unscheduled treatment report on its own, showing the total dollar value of accepted treatment not yet on the books, sorted by how long it has been sitting. It should also break down acceptance rate by provider, because that number tells you whether a soft close is a training problem or a scheduling-handoff problem.
The distinction matters. If Dr. A presents ten implant cases and closes eight, and Dr. B closes three, that is a coaching conversation. If both close well but half the accepted cases never get scheduled, that is a front-desk workflow gap. One report, generated automatically, tells you which lever to pull. Without it, you are guessing at where your production is stalling.
Report 3: The referral source performance report
Periodontics depends on referrals more than almost any specialty. Your practice management software should treat the referral pipeline as a monitored asset, not a stack of fax paperwork.
The referral source report you want shows three things without prompting: which referring dentists sent cases this period, how that compares to their usual volume, and which referrers have gone quiet. That last one is the signal nobody catches in time. A GP who sent you three cases a month for two years and sends zero this month has either retired, gotten unhappy, or started referring elsewhere. You want to know inside 30 days, not at your year-end review.
DSN integrates referral tracking directly into scheduling and surfaces your referrer relationships so you can see the pipeline instead of guessing at it. When the software flags a top referrer going dormant, that is a lunch you should be scheduling this week. The report is not the point. The prompt to act on it is.
Report 4: The AR and cross-coding report
Perio billing is its own animal. Many periodontal procedures cross into medical necessity, especially when tied to systemic conditions like diabetes or cardiovascular disease, which means you are billing both dental and medical insurance on the same case. The gap between CDT and CPT codes is where perio claims die.
Your periodontal practice management software should generate an AR report that does more than list outstanding balances. It should show claims aging by payer, denials grouped by reason, and the specific coding failures that keep recurring. It should know the difference between D4341 and D4342 and flag when medical billing might apply. Most importantly, it should audit claims before they go out, not report on the wreckage after.
DSN automates cross-coding between dental and medical claims and validates them before submission, which means fewer rejections and faster payment on exactly the high-value, medically nuanced procedures where perio practices lose the most. An AR report that only tells you what already got denied is a coroner’s report. The one you want prevents the death.
The four reports at a glance
Here is what separates a report you have to chase from one that works for you.
| Report | What it should answer | The action it should trigger on its own |
|---|---|---|
| Perio maintenance recall | Who lapsed or never converted to maintenance | Auto-build the recall queue with reminders |
| Unscheduled treatment | What accepted treatment is not booked, by provider | Flag idle cases and route to the front desk |
| Referral source performance | Which referrers are up, flat, or going quiet | Alert you when a top referrer drops off |
| AR and cross-coding | Which claims are aging and why they deny | Audit and cross-code before submission |
Notice the pattern in the last column. In every row, the bar is not producing a document. It is triggering the next move automatically. That is what “without you asking” actually means.
The contrarian take: report count is a vanity metric
Vendors love to advertise how many reports their system has. Three hundred reports. Five hundred. All Excel-exportable. It sounds like power. In practice, it is the software equivalent of a menu so long you cannot decide what to order, so you order nothing.
Here is the uncomfortable truth: a report nobody runs is worse than not having it, because it creates false confidence. You believe the data is being watched simply because the capability exists somewhere in a menu. It is not being watched. Nobody has time to run 300 reports, and the four that matter get lost in the pile with the 296 that do not.
The right question to ask any periodontal practice management software vendor is not how many reports it has. It is which reports it runs automatically, who they go to, and what action each one kicks off. A system that pushes four reports on a schedule and turns each into a task beats a system with three hundred reports gathering dust. Depth of automation, not breadth of catalog. If a demo answers “how many reports” with a big number instead of a workflow, that is the wrong answer to the wrong question.
How to pressure-test this in a demo
If you want to separate real reporting automation from a long feature list, run this sequence.
- Ask them to show the maintenance recall report generating on a schedule, then ask what happens next. If the answer stops at “you get a list,” keep looking.
- Ask to see the dollar value of accepted-but-unscheduled treatment. Many systems cannot produce this at all.
- Ask how the software alerts you when a top referrer’s volume drops, not just how it stores referral data.
- Give them a perio case that should cross-code to medical and watch whether the system catches it before submission.
- Ask who each report goes to by default, and whether that routing is automatic or manual.
- Ask how many of these four your current system runs without someone remembering to pull them.
Run that and the difference between a reporting catalog and a reporting engine becomes obvious fast.
Frequently asked questions
Which report tells me why perio maintenance patients are falling out of the recall cycle?
The maintenance recall report, if it is built right. It should separate patients who finished active treatment but never booked their first supportive visit from those who came for a while and then lapsed, because those are two different problems with two different fixes. DSN automates the recall scheduling and reminders around that report, so the gap gets closed instead of just measured.
How do I know if my treatment plan acceptance problem is a provider issue or a scheduling issue?
Look at acceptance rate and unscheduled treatment side by side. If acceptance is low, that is a case-presentation or provider issue. If acceptance is high but a chunk of accepted treatment never gets scheduled, that is a front-desk handoff issue. Good periodontal practice management software shows both numbers automatically so you are not guessing which lever to pull.
Can periodontal practice management software flag referring dentists who have stopped sending cases?
The good systems can, and it is one of the most valuable things they do. Referral volume trends tell you when a reliable referrer goes quiet, usually before you would notice on your own. DSN builds referral tracking into scheduling and surfaces those relationships so a dormant top referrer becomes a prompt to reach out, not a surprise at year end.
How should an AR report handle claims that cross between dental and medical insurance?
It should treat cross-coding as a first-class function, not an afterthought. Perio procedures tied to systemic conditions often qualify for medical billing, and the report should flag those cases and audit the coding before the claim goes out. DSN automates cross-coding between CDT and CPT and validates claims pre-submission, which is where the rejections get prevented rather than counted.
How often should these four reports run to actually change behavior?
Frequency depends on the report, and the software should handle the cadence for you. Recall and unscheduled treatment reward weekly attention because the window to act is short. Referral trends and AR aging work well monthly. The point is that the system schedules them, so behavior changes without anyone remembering to check.
Do I really need 300 reports, or just a few that matter?
A few that matter, run automatically, beat a giant catalog every time. The value is not in the size of the report library. It is in whether the handful that drive perio revenue get produced on a schedule and turned into action. Ask a vendor what runs automatically, not how many reports exist.
The bottom line
Your periodontal practice management software should not make you remember to look. It should watch the four seams where perio practices leak money: lapsing maintenance patients, unscheduled treatment, cooling referrers, and claims stuck between dental and medical coding. Then it should hand the right person the next action, on a schedule, without being asked. If your current system only produces these when you go dig for them, you are doing the software’s job for it.
Want to see this in your workflow? Let’s set up a walkthrough.