Administrative cost is rarely one line item that a multi-location eye care group can simply cut. It is the accumulated cost of work that has no clear owner: calls that reach voicemail, eligibility checks completed twice, recalls handled only when a site has spare capacity, and local scheduling rules that require corporate staff to sort out exceptions after the fact.
That is why payroll percentage alone is a poor operating diagnosis. A group can spend less on administrative labor and still lose access opportunities, create more work for clinical teams, or leave site managers with no useful view of demand. The goal is not the smallest possible support team. The goal is a patient-access model that gives each recurring task a defined owner, a defined workflow, and a measurable outcome.
For an organization with three or more locations, this usually starts with a network-level view of administrative demand. Review call volume, booking requests, insurance work, recall activity, messages, and after-hours coverage by location and time of day. Then separate work that needs a person on-site from work that can be performed in a centralized or remote queue.
Table of Contents
- Where do administrative costs actually accumulate across locations?
- How should leaders establish a useful cost baseline?
- Which three levers reduce cost without weakening patient access?
- What work belongs in a centralized or remote team?
- How should a group control quality and HIPAA risk?
- Which metrics show whether the change is working?
- How should executives stage an administrative-cost program?
Where do administrative costs actually accumulate across locations?
The expensive part of administration is often variation. One office may have a receptionist answering every call, verifying benefits between interruptions, and calling overdue patients from a paper list. Another may use a different script, route the same question to a technician, and rely on voicemail callbacks. Neither site may look overstaffed in isolation. Across a group, however, the variation creates duplicated training, uneven coverage, and reporting that cannot tell leadership where work is truly going.
Staffing bloat also develops one sensible decision at a time. A site adds someone to catch up on billing work. That employee then cannot cover phones, so another hire fills phone coverage. Recalls become intermittent, so a manager asks the front desk to fit them in around arrivals. The group has added capacity without deciding which role owns each process from end to end.
Underutilization is a workflow issue before it is a people issue. A team member may spend part of the day on legitimate billing or scheduling work and the rest waiting for unpredictable interruptions. The answer is not to assume that person is unproductive. It is to measure the work arriving, the work completed, the work handed off, and the time required for each repeatable workflow. That evidence can reveal whether the issue is staffing level, poor queue design, inconsistent site rules, or a task that should not live at the front desk at all.
Supply costs deserve their own review, but they should not distract from the access layer. Leadership should examine purchasing discipline, inventory turns, and vendor terms through the appropriate finance and clinical governance process. Administrative cost reduction is most durable when it begins with work design, because that is where a multi-location group can standardize without reducing care capacity.
How should leaders establish a useful cost baseline?
Start with a baseline that links cost to work, not just a combined payroll number. For each location and for the group as a whole, document administrative labor, benefits, overtime, temporary coverage, vendor spend, and the management time spent repairing missed handoffs. Then pair those costs with workload: inbound calls, abandoned calls, booked appointments, reschedules, eligibility checks, recall attempts, billing follow-ups, portal messages, and after-hours contacts.
This view gives executives a way to compare locations without pretending they are identical. A high-volume location may need more on-site coordination. A site with a large amount of callback work may instead need better queue ownership. A newly acquired practice may need a transition period before its data is comparable. The point is to explain the differences, not to punish them.
MGMA’s work on healthcare call center efficiency and centralized scheduling is a useful prompt for this review: administrative workload should be studied as an operating system, including how requests arrive and where they are resolved.
Use the baseline to answer practical questions. Which locations are paying for duplicate coverage? Which call types generate the most transfers? How often does an in-office team stop patient-facing work to complete a task that could be queued? Which sites have a backlog of recall or insurance work because nobody owns it consistently? A spreadsheet that answers those questions is more valuable than a generic target percentage.
Which three levers reduce cost without weakening patient access?
Most groups need a mix of three levers: reduce avoidable work, standardize repeatable work, and place work with the right team. None of these is a one-time expense exercise. Together, they create a more manageable access operation.
First, reduce avoidable demand. Review the top reasons people call, message, or walk to the desk. Some demand is essential. Some comes from unclear confirmations, inconsistent reminder language, no self-service path for a simple request, or a process that asks patients to call back for information already available to the organization. The right intervention may be clearer communication, a better reminder sequence, or a defined digital route. It should not be a blanket attempt to push patients away from live help.
Second, standardize the repeatable work. Scheduling, confirmations, routine reschedules, recall outreach, insurance verification, and message intake need documented rules, disposition codes, and ownership. Standardization does not mean every location loses its legitimate scheduling constraints. It means the group distinguishes approved local exceptions from informal habits. For a practical comparison of operating models, see centralized versus distributed intake.
Third, use the right labor model for each task. In-office teams should remain focused on work that requires physical presence, immediate site judgment, or direct support during a patient visit. A centralized patient-access team, remote administrative team, or managed partner can handle defined recurring workflows where system access, training, quality review, and escalation rules are in place. That division protects the site team’s time while maintaining a clear path for exceptions.
What work belongs in a centralized or remote team?
The dividing line is not whether a task feels administrative. The question is whether it can be executed reliably through a documented workflow without requiring physical presence or clinical judgment. Routine inbound call handling, appointment requests, confirmations, basic reschedules, recall outreach, eligibility verification, billing follow-up, and structured message intake can often be centralized when the group has defined scripts and escalation rules.
That does not mean every call should be handled from one queue. Provider-specific scheduling restrictions, service-line differences, unresolved service recovery, and questions that require clinical assessment need a controlled handoff. Non-clinical staff should gather the approved information, follow the approved script, and route the request to the named owner. They should not make clinical decisions or improvise beyond the protocol.
For many organizations, front desk outsourcing is most useful when it operates as part of a governed patient-access layer instead of as overflow coverage. The same distinction applies when a group considers medical virtual assistants. A vendor or remote team can add capacity, but it cannot solve a missing process definition. The group must first decide who owns the queue, how outcomes are documented, and what happens when the task cannot be completed on the first interaction.
The operating model should also make after-hours coverage explicit. A general message, a scheduling question, and a time-sensitive clinical concern do not belong in the same response path. Define approved categories, escalation contacts, response expectations, and documentation rules before assigning coverage. This protects patients and staff while giving executives an auditable view of what the access team handled.
How should a group control quality and HIPAA risk?
Cost reduction should not introduce a black box. Any centralized or outsourced workflow needs documented access controls, training, quality assurance, escalation boundaries, and reporting. If a partner creates, receives, maintains, or transmits protected health information on the group’s behalf, compliance and counsel should review the arrangement and the applicable business associate requirements before it goes live.
Operational controls matter just as much as contract language. Give agents role-appropriate system access, keep scripts and knowledge articles under change control, and use structured outcomes rather than free-form notes whenever possible. Review a sample of interactions against the same rubric across locations. The rubric should test correct routing, documentation, scheduling logic, and escalation use, not just conversational tone.
The group should also decide how site feedback becomes a controlled update. When a location identifies a true exception, the central team needs a clear owner who can approve, document, and communicate the change. Otherwise, a legitimate local need becomes another undocumented variation. Healthcare call center outsourcing for multi-location groups explains why governance, not coverage alone, determines whether this model can scale.
Which metrics show whether the change is working?
Leadership needs a scorecard that connects administrative cost to access quality. Network averages are not enough. Report by location, call type, and queue so that a strong site does not conceal a weak handoff process elsewhere.
Track answered and abandoned calls, callback completion, appointment conversion from eligible requests, reschedule completion, recall activity, insurance verification completion, backlog age, transfer rate, and quality-review findings. Pair these operating measures with fully loaded administrative cost, overtime, outside coverage spend, and the amount of work that still returns to site teams for rework.
The right interpretation is important. A lower payroll percentage is not a win if callback completion falls or if clinical teams are absorbing administrative messages. Conversely, a temporary increase in centralized support can be worthwhile if it gives the group clean data, consistent workflow execution, and enough coverage to eliminate a recurring backlog. The executive question is whether the organization is getting a more controlled system for each dollar spent.
For a broader measurement framework, compare the scorecard with patient access center metrics for healthcare executives and the operational lens in enterprise healthcare staffing ratios and patient-access optimization.
How should executives stage an administrative-cost program?
Begin with one workflow that is common across locations and easy to observe, such as routine appointment calls, confirmation callbacks, or recall outreach. Map the current state, including volume, systems used, handoffs, local exceptions, and unresolved items. Set the future workflow, its owners, and the evidence that proves it worked. Then test the model with a limited group of locations using the governance and reporting design intended for wider rollout.
Do not call a pilot successful merely because a dedicated manager worked around every problem. A useful pilot proves that queues, scripts, integrations, escalation paths, QA, and reporting work without heroics. It should show what exceptions appear, how often they appear, and whether they belong in the standard workflow or a controlled site-specific path.
Once the workflow is stable, expand deliberately. Use the same definitions across sites, publish change decisions, and review location-level variance at a regular operating cadence. Groups planning a partner selection process can use the patient access center RFP vendor checklist to make requirements explicit before comparing proposals.
Reducing administrative cost is ultimately an exercise in making work visible. When leadership can see where demand enters, who owns it, when it is resolved, and where it returns for rework, it can improve the labor model without sacrificing access quality. That is a more reliable path than asking every site to spend less while leaving the operating design unchanged.
Managing administrative cost across 3+ locations? Request an Enterprise Assessment for your group.
