Apr 28, 2026
Written By Elizabeth Cifers
There is a very specific kind of confidence that comes from reviewing your clinic schedule before the day begins. It’s quiet, reassuring, and, more often than not, slightly misleading. Everything appears balanced. New patients are spaced appropriately. Follow-ups and injections are layered in. There are no obvious red flags, no glaring overbooks, nothing that suggests the day will unravel.
And yet, by mid-morning, the clinic is running a little behind. Not dramatically so. Just… slower than it should be. A few minutes behind becomes ten, then fifteen. The clinic isn’t in chaos, but it’s no longer moving the way it looked like it would at 7:45 a.m.
The issue rarely starts with a single, identifiable problem. It’s usually a series of ordinary events unfolding exactly as real clinics do. A patient arrives late, but not late enough to require rescheduling. Another needs additional testing that wasn’t anticipated. A third requires a longer conversation because the family is with them today, and they have questions about mom’s treatment options. None of this is unusual. In fact, it would be more unusual if it didn’t happen.
But most schedules are built on the assumption that visits are predictable, with each patient type moving through the clinic in roughly the same amount of time. Unfortunately, retina clinics do not operate that way. They never have.
While we all know that every patient is different, when schedules are created, we work with “averages” in mind. At the center of this is a concept that works beautifully in theory and far less well in practice: the average visit. Schedules are often built around average times: average follow-up duration, average new patient slot, and average testing time. It sounds reasonable, and mathematically, it is.
But patients are not averages.
Some visits are straightforward and move quickly. Others require more attention, more testing, or more decision-making. Occasionally, what is labeled a “follow-up” behaves suspiciously like a new patient who was seen once two years ago.
Individually, these variations are manageable. Collectively, they begin to shift the entire day. When enough visits run just slightly longer than the “average,” the schedule doesn’t fail all at once. It quietly drifts.
Once the schedule begins to drift, even slightly, the entire clinic shifts into a more reactive mode. Adjustments happen in real time. Conversations become more compressed. Documentation quietly gets pushed to “later,” a polite way of saying the end of the day.
No one is doing anything wrong. In fact, everyone is working harder to keep things moving. But this is where efficiency starts to erode. Not because of effort, but because the system is no longer setting the pace. The day is.
The most deceptive schedules are not the ones that are obviously overloaded. Those tend to attract attention quickly. The more challenging version is the schedule that looks entirely reasonable yet still runs behind. It creates just enough friction to slow the clinic down, but not enough to prompt meaningful change. So the explanation becomes, “We’re just busy.”
And to be fair, it does feel that way.
A schedule is very good at showing structure. It shows time slots, patient types, and volume. What it doesn’t show is how the day actually unfolds. It doesn’t account for variability in patient needs, dependencies among staff and equipment, or the cumulative effect of small, predictable (and unpredictable) delays.
In other words, it tells you what the day is supposed to look like, not what it will actually be.
A schedule is not just a plan. It’s a prediction. And like most predictions, it’s only as accurate as the assumptions behind it. If those assumptions rely heavily on averages and ideal flow, the schedule will almost always seem reasonable until the clinic starts.
Which raises a slightly uncomfortable question: If the schedule looks appropriate and the volume feels manageable, yet the day consistently runs over, is the issue really how many patients you’re seeing? Or is it that the schedule is telling a different story than the one your clinic is following?
This isn’t the part where I tell you to rebuild your schedule, add buffers everywhere, or time every step of every visit. That would be a different article, and frankly, it’s not the point. The value here is simpler—and a little less traditional.
It’s recognizing that a schedule can be technically correct yet operationally misleading. What looks balanced in the system may not reflect how your clinic actually functions in real time. And that the friction you feel throughout the day is often not random; it’s structural.
Once you see that, it becomes much harder to default to “we’re just busy” as an explanation. Sometimes you are busy. And sometimes the schedule asks the day to behave in a way it never will.
At the end of clinic, most practices ask a version of: “How did today go?” A more useful question might be: “Where did the schedule stop aligning with reality?” Not in a dramatic, everything-fell-apart way, but in the small moments: the delays, the competition for an open lane or diagnostic testing, and the subtle slowdowns that seemed harmless on their own yet added up anyway.
And that’s where the insight lives. Not in fixing everything at once, but in noticing where the story the schedule is telling starts to drift from the one your clinic is actually living. Once you see that clearly, you don’t need a perfect schedule. You need one that matches how the day actually unfolds.
If this felt familiar, it’s not something that fixes itself by tweaking a few time slots. When the schedule and workflow aren’t aligned, the day will keep drifting—no matter how reasonable it looks in the system.
This is exactly the work I do.
If you want a clear, objective view of how your clinic actually functions—where flow breaks down and why—I can help you see it. Not in theory, but in your day-to-day reality.
Because at some point, it’s not about the schedule.
It’s about why it isn’t working the way you think it should.
.png)
.jpg)