Managing the Revenue Cycle Through Staff Turnover

There is a fine balance between confidence and panic after someone in the business office resigns. Some people remain calm, convinced that a replacement is readily at hand—they just need to hire them. Post the ad, and in a week you will have a new employee. That is the equivalent of waving a magic wand and having a replacement appear. It is a lovely thought, but, sadly, it is not how things work.

Others become anxious, knowing how much knowledge is walking out the door, how many candidates were interviewed to find “the one,” and now “the one” is leaving. Yes, you will hire someone new, but even though the role is well defined, the system will be challenged to keep everything together until that replacement arrives.

Why? Well, in most retina practices, the revenue cycle is not simply a clean, predictable sequence of tasks. It is also a series of decisions, institutional knowledge, habits, and workarounds for payer quirks that have been built over time by the people doing the work. When one of those people leaves, they do not just take their login credentials and a few passwords. They take the “how” with them, including how A/R is prioritized, how certain payers are handled, and how errors are caught before claim submission rather than afterward.

This is where the disruption begins.

The Illusion That Everyone Can Be Replaced

In theory, revenue cycle roles are interchangeable. Charge entry is charge entry. Payment posting is payment posting. A/R is A/R. Denials are worked, payments are posted, and prior authorizations are obtained. There are job descriptions for everything, and in most practices, policies and procedures describe how each task should be performed.

In reality, most practices are not run by policies and procedures. They are run by people.

Over time, billing staff develop a rhythm. One person knows which claims to prioritize because they know which payers are slow to process claims. Another has a mental checklist before releasing a claim, but it has never been written down. Someone else knows exactly when to follow up—not because it is documented anywhere, but because they have learned the difference between “too soon to check” and “too late to appeal.” None of these procedures appears in a job description.

When turnover occurs, what leaves is not just a person. It is consistency. And consistency, as it turns out, is what keeps the revenue cycle from slowly becoming a mess.

Turnover rarely creates immediate chaos. The clinic still runs. Claims still go out. Payments still come in. No alarms sound. No one announces that the revenue cycle is having issues. Instead, things slowly shift. Claims sit a little longer before someone touches them. Follow-up still happens, but not as often or with the same urgency. Errors that once were caught upstream quietly make their way downstream, where they are more expensive—and far more frustrating—to address.

Although nothing in particular seems urgent, the cumulative effect reshapes the financial picture. A/R and adjustments rise. Cash flow becomes less predictable. Eventually, someone asks, “We’re busy, so why are we collecting less?” That question usually arrives after the underlying problem has already settled in.

Hiring Faster Is Not Always the Answer

When turnover starts to hurt, the instinct is to move quickly. Post the job. Fill the role. Get someone—anyone—back in the seat so the work keeps moving. And yes, leaving a position open indefinitely is not a viable option. But hiring faster does not necessarily solve the problem. It may only compound it.

Every new hire brings a different interpretation of how the role should be performed. Without a consistent framework, each transition subtly reshapes the revenue cycle. Over time, the system begins to change—not because claim volume has increased or payer policies have shifted, but because the execution of the work is no longer consistent.

From the physician’s perspective, this is when things become especially frustrating. Clinic volume is normal. The number of injections, laser procedures, and office visits has not changed. Yet financial performance begins to wobble in ways that are difficult to explain.

That is because the question is not, “Did we replace the person?” The question is, “Did we preserve the process?”

Standardization (Without Making Everyone Miserable)

At some point, someone will suggest standardization, and at least one person in the room will immediately assume it means creating a rigid, joyless checklist that strips the process of all critical thinking. That is not the goal. The goal is clarity about what cannot change.

There should be a shared understanding of what constitutes a clean claim before it leaves the practice. There should be consistency in how often A/R is worked, what follow-up looks like, when issues are escalated, and—this is a favorite—where claim follow-up information is documented so it can be found by someone other than the person who wrote it. (If the answer is “on a spreadsheet saved somewhere on someone’s desktop,” we should talk.)

This type of process standardization does not eliminate judgment. It protects judgment. It ensures that judgment is applied within a structure that keeps the rest of the system stable.

The solution is not a 50-page manual—whether on paper or online—that no one reads. It is making expectations visible, workflows repeatable, and outcomes measurable. When that happens, new staff are not guessing. They are stepping into a role that already has structure.

Most practices monitor the revenue cycle at a high level, tracking collections, days in A/R, and perhaps denial rates if someone is especially detail oriented that week. Although those metrics are useful, they are also lagging indicators. By the time they reveal a problem, the problem already exists.

Build a System That Survives Staff Turnover

If there is one strategy that consistently works, it is this: build a system that does not depend on any one person. That means using the practice management system as intended rather than relying on external notes, side spreadsheets, or “I’ll remember to follow up on that.” It also means creating workflows that are visible and transferable so work can be picked up, continued, and completed without starting from scratch.

When the revenue cycle is built on standardized processes, the impact of turnover changes. It becomes inconvenient rather than disruptive. It becomes manageable rather than expensive. Most importantly, it stops resetting the revenue cycle every time someone leaves.

The Goal Isn’t Stability. It’s Resilience.

It would be ideal if staffing remained stable and the revenue cycle ran like a well-oiled machine in the background, performing exactly as it should. That is not the environment in which most practices operate. The goal is resilience.

A revenue cycle that continues to function as people change. A system that maintains consistency even as roles turn over. A process that does not need to be rebuilt every time someone new logs in.