Routine Foot Care Recalls and the Every-Nine-Weeks Grid

Routine foot care recalls are the most predictable revenue a podiatry practice has, which is exactly why nobody watches them. A large share of the panel comes back on a fixed interval set by the clinical team. The visits are short, the coding is familiar, and the schedule was built to hold them. Then one week slips, and it keeps slipping, and six months later the practice is running at eighty percent of a schedule it thinks is full.

Most scheduling advice treats a recall as a task. Somebody should call this patient. That framing is wrong for podiatry, and it is why the problem never gets fixed.

A fixed-interval recall population is a capacity commitment. If four hundred patients are on a nine-week cycle, the practice has committed to roughly forty-four visits a week, every week, forever. That is not a call list. It is a standing block of the calendar that either holds its shape or quietly deforms.

When it deforms, it does so invisibly. A patient pushes a visit by ten days. The next one lands eleven days late. Two cycles later that patient has drifted a full interval out of position, and the slot they used to occupy is now sitting empty on a Tuesday while Thursday is triple-booked.

No one notices because every individual reschedule was reasonable. The damage is in the aggregate, and the aggregate is not on anybody’s screen.

The interval is a coverage rule before it is a preference

Podiatry is unusual in how tightly its recurring work is bounded by coverage rules, and the front office needs to understand the shape of those rules even though it never applies them.

Medicare generally excludes routine foot care, listing the cutting or removal of corns or calluses, the trimming of nails, and routine hygienic care as services furnished in the absence of localized illness, injury, or symptoms involving the feet. Payment may be made under exceptions, and the local coverage determination governing routine foot care and nail debridement spells out when those exceptions apply.

One of its limitations is directly operational. Where the patient’s condition is designated by a code carrying an asterisk, routine foot care is reimbursable only if the patient has been under the active care of a doctor of medicine or osteopathy for the complicating condition during the six month period before the service.

Read that as a scheduling constraint and it changes what the front office is tracking. There is the visit interval the clinical team set, and there is a separate rolling window tied to another provider’s care. Both have to be true on the day of the appointment. A practice that only tracks the first will book visits that are perfectly timed clinically and unpayable administratively.

The grid lives in appointment types, and appointment types lie

The second problem is that the schedule where all this is supposed to live does not describe itself accurately.

Practices build calendars out of generic slot types, the fifteen and thirty minute containers that a template hands back. Search the schedule for a specific appointment type and the system will happily return a generic one. Whether that generic fifteen minute opening can actually hold this particular visit, with this provider, in this department, is a mapping question that exists in somebody’s head rather than in the calendar.

When the catalog changes it gets worse. A practice consolidated a whole set of specific procedure types into one shorter follow-up type overnight, and the surviving type could not hold the longer services that had been folded into it. Nothing broke visibly. The schedule simply started accepting bookings it could not honor.

For a recall grid this matters more than it does elsewhere, because the grid is the same shape every week. An error in the mapping does not produce one bad appointment. It reproduces itself forty times a week until somebody notices the providers are running behind on the same day every cycle.

GET /appointmenttypes and GET /appointments/open are how an automated front office reads the real shape of the calendar rather than the intended one. The gap between those two is usually where the lost capacity is hiding.

One slip is a cascade, not an exception

The single most valuable thing automation does for a fixed-interval practice has nothing to do with answering the phone. It is holding the chain together when a link moves.

When a patient reschedules, the correct behavior is not just to find them another slot. It is to re-anchor the rest of their series so the interval stays honest, and to put the vacated slot back into circulation before it ages out. PUT /appointments/{appointmentid}/reschedule moves the visit. Deciding what else has to move is the part practices do badly, because doing it by hand for every change is not realistic with two people at the desk.

Backfilling the hole is the other half. A nine-week grid always has someone who would happily come in earlier, and they are trivially identifiable, because they are already on the same grid. This is the cheapest form of schedule recovery available and most practices do not run it, since it requires reaching people the moment a cancellation happens rather than during the evening cleanup pass.

No-shows keep this from being theoretical. An August 2025 MGMA Stat poll found 73% of medical practices reported no-show rates that stayed the same or decreased in 2025, while 27% said no-shows increased. In a practice whose revenue is a repeating grid, the increase is not the real cost. The un-refilled hole is.

What the automation actually holds

Described concretely, the work is unglamorous and completely rule-bound, which is why it runs well without a person.

It tracks every patient on a recurring interval and knows when their next visit is due. It calls or texts inside the booking window rather than when someone gets to it. It offers times that fit the correct appointment type for that patient with a provider who can see them. It re-anchors the series when a visit moves. It puts a cancelled slot back in front of the patients most likely to take it. It checks that coverage is still active before the day arrives, because coverage changes between visits and nobody tells the practice.

It also does the thing a person will never do consistently, which is watch the grid in aggregate. Which intervals have drifted, which providers are carrying more of the recurring load than the template assumed, how many recall patients are past due, and how much of next month is already committed. Practice leaders describe wanting reports the calendar does not surface well, and this is the clearest example of one.

None of that requires judgment about anyone’s feet.

Where staff still own the work

The boundary is easy to state. The clinical team sets who is on a recurring interval and how long that interval is. Nothing in the front office changes that, proposes changing it, or infers it from the pattern of past visits.

The automation books, moves, backfills, confirms, chases coverage, and reports. When a patient says something is wrong, when they want to move a visit for a reason that needs a clinician to weigh in, or when the coverage exception looks like it may not hold, that goes to a person the same day.

The practical result for a practice administrator is a schedule that keeps its shape without anybody defending it. The grid was always the asset. It just never had anyone watching it between the hours of eight and five, when the desk is busy with the people standing in front of it.

Key Takeaways

Treat a fixed-interval recall population as a standing capacity commitment, not a call list, because that is how it behaves on the calendar.
Track the rolling active-care window separately from the visit interval, since both have to be true on the day for the visit to be payable.
Verify what a generic slot type can actually hold, because a mapping error in a repeating grid reproduces itself every week.
Re-anchor the rest of a patient’s series when one visit moves, or the interval drifts a full cycle within a few months.
Backfill a cancelled slot from the same recall population immediately, since those patients are the easiest fill available.
Watch the grid in aggregate, including drift, past-due counts and committed capacity, because no individual reschedule looks like a problem.

A podiatry practice does not lose its recurring revenue in one bad month. It loses it a week at a time, to reschedules nobody re-anchored and holes nobody refilled. Holding the grid is the whole job, and it is work a front office should not be doing by hand.

Sources