Skip to main content

Practice Operations

Well-Child Visit Recall and the School-Year Calendar

Pediatric demand is not spread evenly across the year. How well-child visit recall works when the calendar, not the chart, decides when families will book.

9 min read

Well-child visit recall fails less because families forget and more because everyone remembers at the same time, in the same three weeks of August.

A pediatric practice knows exactly which patients are due. What it cannot control is when families act on it. Demand collapses into the weeks before school starts, the schedule cannot absorb it, and the patients who were due in February get seen in September along with everyone else, if they get seen at all.

The chart says when. The calendar says when they will call.

Recall in most specialties is a question of who is overdue. In pediatrics there is a second variable that outweighs it.

Well-child visits are anchored to a child’s age, which spreads them evenly across the year. Families book them against the school calendar, which does not. A visit that came due in March gets deferred until the form is needed, and the form is needed in August.

That mismatch produces two problems at once. August is oversubscribed, with families calling for appointments that cannot be accommodated before the first day of school, and the rest of the year is under-filled with capacity that was available when the visit was actually due.

Practices feel the August half acutely because it generates angry calls. The February half is invisible, which is why it rarely gets addressed. Both are the same problem, and the lever for both is the timing of the outreach rather than its volume.

Recall built as a campaign will always arrive late

The common approach is a recall campaign: pull a list of overdue patients, send a batch of messages, work the responses.

It underperforms for a structural reason. A campaign runs when someone has time to run it, which means outreach clusters rather than tracking the underlying due dates. Families receive a message about a visit that came due four months ago, at a moment they were not thinking about it, and a good share of them defer again.

What works better is a rolling list rather than a campaign. Read each patient’s appointment history through GET /patients/{patientid}/appointments, compare it against the interval the practice uses for that age, and generate the small daily set of children entering their due window. Contact those families then, while the window is opening rather than after it closed.

Run that way, the same total outreach spreads across the year, which is exactly the shape the schedule needs. It also converts better, because a family contacted at the right moment is being offered something useful rather than reminded of something they are behind on.

The automation is doing date arithmetic and outreach. It is not deciding what any individual child needs. The intervals come from the practice’s own protocol and the exceptions are flagged for staff.

The complication: the slot exists but converts by 9:30

Pediatric templates carry rules that no static scheduling system can express, and recall outreach runs straight into them.

One pediatric practice holds an 11:45am newborn slot every day and converts it into two sick visits if it has not filled by around 9:30. That is a real and operationally important rule. It exists because newborn demand is unpredictable and same-day sick demand is not, and the practice would rather run the slot twice than leave it empty.

An outreach automation that reads open availability and offers whatever it finds will offer that slot at 10am, after it has already been reallocated. The family accepts, the practice has two bookings on the same time, and someone has to call back and undo one.

Getting this right means the outreach has to know the practice’s conversion rules and the times they take effect, not just the current state of the slot table. In practice that means protected slots are excluded from recall outreach entirely, or offered only inside the window where they are genuinely available.

The wider version of this is worth stating: recall outreach should never be pointed at the same capacity the practice is holding for acute demand. A well-child visit is the definition of a schedulable appointment, which makes it the right thing to place in planned capacity and the wrong thing to place in the buffer.

Forms are the real reason families finally call

Understanding the trigger changes what the outreach should say.

Most deferred well-child visits are eventually prompted by a requirement rather than by the visit itself. A school needs a completed physical form. A sports program needs a signature. A camp needs immunization records by a date. The visit is the means; the paperwork is the motivation.

Outreach that leads with the paperwork therefore lands better than outreach that leads with being overdue, and it lands earlier. A family told in May that the school form will need a visit and that appointments are open now will frequently book in May. The same family told in May that their child is due for a checkup often will not.

This also gives the practice a way to smooth the August peak deliberately rather than hoping. Work the outreach list in the spring for children whose forms will be needed in the fall, and a meaningful share of that demand moves into months with open capacity.

The handoff points stay clear throughout. The automation books the visit and can note which form is expected so the practice is prepared. It does not complete the form, does not confirm to a parent that a child is up to date on anything, and does not answer questions about immunization status. Those go to clinical staff, and a parent asking one is transferred rather than reassured.

The phone burden this competes with

Every outbound recall call happens in a practice whose inbound lines are already loaded, and pediatrics is a high-contact specialty.

In a March 10, 2026, MGMA Stat poll of practice leaders, the most time-intensive phone tasks were eligibility and prior authorization at 45%, scheduling at 31%, intake at 9%, prescription refills at 6%, and an other category at 9%. The poll had 294 applicable responses.

Recall outreach is discretionary work in a practice where nothing else is. When the front desk is underwater, the recall list is the first thing dropped, which is precisely why it tends to run as an occasional campaign rather than a continuous process. The work is genuinely valuable and it is always the least urgent thing on the list.

That is the strongest argument for automating this particular workflow rather than a busier one. Recall is not competing with clinical work for attention. It is competing with the phone, and it loses every time. Moving it off the phone is the only way it gets done consistently.

Measure how the visits spread across the year

Completion rate is the metric practices track and it hides the entire problem. A practice can see every child eventually and still have an unworkable August.

The measure that matches the goal is the distribution of well-child visits across the year. Specifically, the share of visits happening within a defined window of when they came due, rather than the share happening at all. That number tells you whether outreach timing is working.

Two more are worth watching. Track August and early September booking density against the rest of the year, because that ratio is the thing families experience as whether the practice has availability. And track the share of recall contacts that result in a booking on the same contact, which is the honest read on whether the outreach is reaching families at a moment when they can act rather than adding to a list they will get to later.

Key Takeaways

  • Recall timing matters more than recall volume in pediatrics. The chart says when a visit is due; the school calendar decides when the family will actually book it.
  • Replace the campaign with a rolling daily list of children entering their due window. Campaigns cluster outreach by staff availability, not by due date.
  • Compare appointment history against the practice’s own age intervals. The automation does date arithmetic and outreach, never a judgment about what a child needs.
  • Exclude protected and convertible slots from recall outreach. A slot that converts to two sick visits at 9:30 is not availability a recall call should be offering at 10.
  • Point recall at planned capacity, never at the buffer the practice holds for acute demand. A well-child visit is the most schedulable thing on the calendar.
  • Lead the outreach with the form the family will need rather than with being overdue. The paperwork is the trigger, and naming it moves bookings earlier in the year.
  • Work fall form requirements in the spring. That is the deliberate version of smoothing the August peak instead of absorbing it.
  • Measure the share of visits happening close to when they came due, plus August density against the rest of the year. Completion rate will look fine and tell you nothing.

Pediatric recall is unusual in that the practice already has the entire answer. It knows which children are due, when they came due, and roughly what will finally prompt the family to call. What it lacks is a way to act on that every day rather than in the weeks when someone finds the time, and by then the calendar has made the decision instead. An AI team working inside athenaOne can read appointment history against the practice’s own intervals and produce the small daily list of families entering their window. It leads with the form that will actually motivate the booking and keeps protected slots out of the offer set. Every question about a child’s health goes to the clinical staff who should be answering it.

Sources

Ready to See It in Action?

See how PGA works pediatric recall inside athenaOne against the calendar families actually book on

Schedule a Demo →

Written by Kevin Henrikson