222 no-showed appointments in one month, at one location. That figure came out of a prospect's own schedule export during a demo, and it stopped the conversation cold.
What made it worse was where the number had been living. This was a multi-site group, and their board deck reported one network attendance rate. That rate looked fine. The 222 were inside it, averaged against 30 other sites that were doing better.
Averaging is how five-figure revenue leakage from missed appointments survives quarter after quarter in an operations report. Nobody hid anything. The math did it automatically.
Our claim for this no-show reduction playbook: at network scale, no-show variance is an operations metric. Publish it by location every week, or nothing else you do will hold. Standardize the reminder, sure.
But the standardization only sticks when a ranked list arrives Monday morning showing which sites kept it.
Below: the sequence itself, the per-location cost math to run first, the weekly cadence that keeps sites on the standard, and what changes for a central scheduling team once patients start answering.
Network leadership sees one attendance number, and it usually sits in a range nobody escalates.
Underneath that number, spread is normal and large. Two clinics in the same specialty, 15 miles apart, on the same athenaOne contract, can differ by 10 points. The strong site pulls the mean up. The weak one gets carried.
Ask for the same report sorted worst to best, and it stops being a summary. There's a top three now, and those three have names, addresses, and practice managers.
Individual practices lose $20,000 to $30,000 monthly to no-shows, based on figures we see in prospect schedule reviews. That's the no-show cost per location an enterprise finance team almost never sees broken out.
Run the arithmetic on your own network before you buy anything. Take one weak site, its monthly missed visits, and your average revenue per visit. Multiply those. Then repeat across every site in the bottom quartile and add the results.
The total usually covers the fix several times over inside the first quarter. Bring that figure to the meeting instead of a rate.
Somewhere in your network, one site is already good at this.
Maybe her front desk calls every Tuesday afternoon for Thursday and Friday visits. Maybe she moved reminders from one day out to three, and it stuck. Whatever it is, it works. Nobody else knows it exists, because no report names her as the winner, so nobody thinks to ask.
Local fixes stay local. Twelve sites solve the same problem twelve times, badly, and the network pays for all twelve attempts.
Calling patients does work. It also stops scaling around the second hour of the day.
A front desk running confirmation calls reaches maybe 40% of a day's list. Then the phones, the check-ins, and the walk-ins take the afternoon back. Voicemails confirm nothing.
Wrong numbers eat the time that's left. And the patients who most need to move an appointment are the ones hardest to reach by phone during business hours.
Schedule utilization across a multi-site network can't rest on how much phone time each front desk happens to have that week.
The fix for local wins that never travel is to stop relying on travel.
Curogram sets the sequence at the center, and every location runs it whether or not anyone briefed them. Your best-performing site's timing becomes the network timing. A clinic joining in November inherits it fully set up, including reply handling and opt-out rules.
The practical effect shows up in onboarding. An acquired practice used to spend its first two quarters discovering reminder settings by trial; now it opens at the benchmark, and its first ranked report tells you whether anything local is fighting the standard.
Adoption stops depending on a change management project. Day one at a new site already matches the network standard.
Patients answer reminders in the same thread the reminder arrived in. Three outcomes matter operationally.
A confirm marks the appointment and removes it from anyone's call list. A cancel frees the slot immediately, with days of notice instead of an empty chair discovered at 9:05. A reschedule request routes to whoever owns rebooking, with the patient's appointment and history already attached.
That third path is the confirmation workflow for centralized scheduling teams. Requests land in a queue as ready work, with the reason already typed by the patient.
Standardization holds when somebody looks. Regional operations can run the whole loop weekly:
|
Step |
Owner |
When |
What it produces |
|---|---|---|---|
|
Rank |
Ops analyst |
Monday AM |
Sites sorted worst to best on no-show % |
|
Investigate |
Regional admin |
Monday–Tuesday |
Confirm rate and reply rate for the bottom 3 |
|
Coach |
Regional admin |
Wednesday |
One specific change per flagged site |
|
Verify |
Ops analyst |
Next Monday |
Movement, or escalation |
Four steps, under two hours of anyone's week. A practice manager who knows she'll appear on Monday's ranked report acts before Monday. One waiting on a quarterly summary has nine weeks of cover.
Two-Way Confirmation Logic turns each reminder into a decision point the patient can act on. They confirm, cancel, or ask to rebook by replying in plain words. No portal, no callback, no phone tree.
Every reply writes to the athenahealth schedule as it lands, so the front desk and your central schedulers work the same live calendar. Freed slots surface in time to refill from a waitlist rather than after the fact.
Reporting is the piece that turns a feature into a policy. Per-location no-show and confirm rates sit side by side, refreshed weekly. A regional administrator can rank, investigate, coach, and verify without pulling a custom export.
Curogram is HIPAA-compliant and SOC 2 Type II certified, and consent and opt-outs are handled for you at every site.
Take a nine-site region running at a 13% network no-show rate, with a bottom site at 19% and a top site at 8%.
Week 1. The governed sequence goes live at all nine sites at once. Nobody schedules a rollout call. The first ranked report publishes Monday of week two.
Week 2. Confirm rates move first, ahead of any change in the no-show number. The bottom site shows 61% confirmed against 82% at the top site. The gap is the diagnosis: patients at the bottom site aren't answering, and the reply rate says why before anyone visits.
Week 3. Investigation traces it to stale mobile numbers on roughly one in six records at that site. That's an intake habit at the front desk, upstream of any reminder setting. Coaching is one specific change: verify mobile number at every check-in.
Week 4–6. Confirm rate at the bottom site climbs into the seventies. Freed slots start reaching the central rebooking queue with two to four days of notice, which is enough time to fill them.
Figures in this walkthrough are illustrative, drawn from the shape of engagements we run rather than one named client.
Every site's leak gets a number and an owner. Most of the improvement that follows comes from that visibility, before anyone changes a setting.
Atlas Medical Center cut no-shows from 14.20% to 4.91% in three months on a two-way confirmation sequence, based on our internal case data.
A network inheriting that sequence starts each new site near that benchmark instead of at whatever its front desk improvises.
Variance narrows from the bottom up, since the sites furthest from the standard have the most ground to gain by adopting it.
Recovered appointments lift revenue 10–20% for practices on the sequence, from our internal data, and the mechanism is refills rather than fewer cancellations.
A patient who texts back Tuesday about a Thursday slot hands your central team 48 hours of notice. A patient who says nothing hands them an empty room. Same cancellation either way, and the only variable is whether answering took effort.
Provider utilization climbs alongside it, which is the number your medical group leadership actually watches.
Averages are why this problem is old. One rate on a board slide, 40 different realities under it, and no way to tell which site needs help.
Pull no-show rates ranked by location, worst first, for the last full quarter. The three sites at the top are your fastest revenue recovery this year. The gap between them and your best site is the part standardization closes.
Schedule a consultation, and we'll compute the per-location leak from your own utilization data, then model what recovery looks like site by site.