How Many Hands Does One Request Pass Through?

A patient calls asking whether a procedure is covered and when it can be scheduled. Follow the request rather than the patient.

The front desk cannot answer the coverage question, so it goes to the billing team as a message. Billing checks the plan and determines an authorization is required, so it goes back to clinical staff for documentation. Clinical staff send what they have, billing submits, and the payer requests more information. That comes back to clinical, then out to the payer again. Approval arrives four days later in a shared inbox. Somebody eventually notices and passes it to scheduling, who calls the patient. The patient does not answer.

Nine transfers. Roughly 11 minutes of actual work spread across four people, and eight elapsed days. Nobody was slow. Nobody dropped anything. The request simply spent almost all of its life sitting in the space between people.

That space is the subject here. Administrative handoffs are the least examined unit in healthcare operations, and they are where most of the elapsed time in your organization actually lives. Your team is not the problem: the count of transfers is a property of how the work is organized, not of how hard anyone is working.

Healthcare Already Solved This, in One Domain

Here is the part that should be uncomfortable.

Healthcare has studied handoffs seriously for twenty years, built structured protocols for them, trained staff on them, and generated real evidence that structure works. All of it in the clinical domain.

The I-PASS framework is the best-known example. It structures a clinical handoff into illness severity, patient summary, action list, situation awareness with contingency planning, and synthesis by the receiver. That final element matters most and is the one administrative work never borrows: the person receiving the handoff reads the key points back to confirm they received them correctly.

The results are documented. AHRQ's Patient Safety Network describes an implementation of a family-centered adaptation of the framework across seven pediatric units in which harmful errors fell by 38 percent, from 20.7 to 12.9 per 1,000 patient days. AHRQ also notes that communication failures are a common root cause of sentinel events, the most serious category of harmful error.

One detail in that write-up deserves particular attention from an operations perspective. The reduction in harmful events happened without significantly increasing how long the process took. The structure did not cost time. It replaced informal, variable communication with consistent communication, and the consistency was the benefit.

Now compare that with administrative handoffs in the same building. No framework. No mandatory content. No confirmation of receipt. No read-back. No record that a transfer occurred, and frequently no way to tell afterward who was holding the request when it stopped moving.

The asymmetry is the opportunity. Healthcare already knows that structured handoffs outperform informal ones, because it proved it clinically. It has simply never applied the finding to administrative work.

What an Administrative Handoff Actually Costs

Four costs attach to every one of your administrative handoffs, and only one of them shows up in anybody's reporting.

‍Sender time. Writing the message, finding the right recipient, summarizing what happened. Usually one to three minutes, and it is the only cost most organizations would recognize.

‍Receiver time. Reading, reconstructing context, frequently going back to the source because something is missing. Often longer than the sender's time, because the receiver is rebuilding understanding the sender already had.

‍Latency. The elapsed time between transfer and pickup. This is the largest cost by a wide margin and is almost never measured. In the example above, eleven minutes of labor produced eight days of elapsed time. Latency, not effort, is what patients experience as slowness.

‍Rework probability. The chance that the handoff was incomplete and the whole exchange has to happen again. MGMA's March 2026 poll describes intake calls in exactly these terms, as a multi-step data chase where the time sink lies both in the original contact and in the rework that follows when a policy number, a spelling, or a medication list turns out to be missing.

Two effects make administrative handoffs worse the more of them there are. Context decays, since each transfer passes a summary rather than the original, and by the third handoff somebody is acting on a summary of a summary. The patient said something specific in the first thirty seconds that nobody currently working the request has seen.

Ownership diffuses. After a transfer, the sender believes it is handled, and the receiver may not have registered it as theirs. This is why requests stall silently: a stalled item is nobody's overdue task, because nobody holds it.

The Six Kinds That Matter

Not all administrative handoffs behave the same way, and lumping them together produces vague improvement plans.

Within a Team

The cheapest administrative handoffs happen here: one scheduler passes to another, or a task moves across a shared queue. Context loss is low because the vocabulary is shared. Latency is usually low too. These are the cheapest transfers and rarely worth engineering away.

Between Departments

Front desk to clinical, clinical to billing, billing to scheduling. This is where the cost of administrative handoffs concentrates. Vocabulary differs, priorities differ, and neither side sees the other's queue.

The MGMA-published Valley View analysis found that the front desk's highest transfer rates involved matters outside its scope, including prescription refills, clinical questions, billing, and medical records. Those are not failures of the front desk. They are requests arriving at a door that was never able to resolve them, which is the definition of a structurally guaranteed handoff.

Across Shifts and Time

The end-of-day transfer, the weekend, the vacation coverage. Anything unresolved at close becomes an administrative handoff to a future person, sometimes a future self, with whatever context survives in a note.

To and From the Patient

Every time you ask a patient to call back, bring a document, or check a portal, you have handed work to them. These transfers are invisible in internal reporting because the labor moved outside the organization, which does not make it cheaper. It makes it unmeasured.

To and From Payers

Authorization submissions, status checks, documentation requests, appeals. Latency in these administrative handoffs is measured in days, and the receiving side operates on its own timetable entirely. Our guide to insurance verification and prior authorizations covers these in depth.

Between People and Systems

A person reads from one screen and types into another. These are the administrative handoffs nobody calls handoffs, and they are often the most frequent in the building. Each carries the same costs as any other transfer plus a transcription error rate.

A Simple Way to Price a Handoff

Here is a rough model for pricing administrative handoffs using your own data. It is deliberately crude, because a crude number that exists beats a precise one that does not.

For a given workflow, estimate: sender minutes, receiver minutes, average elapsed hours between transfer and pickup, and the share of transfers that require a follow-up exchange.

Then count how many times per month those administrative handoffs occur.

Labor cost is simple to compute: sender plus receiver minutes, multiplied by volume, multiplied by loaded hourly rate. Most organizations find this number smaller than expected, which is precisely why handoffs survive scrutiny.

The number that matters is the latency figure. Multiply average elapsed hours by monthly volume and you have the total time requests spend in transit rather than in progress. Express it in days. For most organizations running any payer-facing workflow, this is where the answer stops being comfortable.

Then apply the rework rate. If one in four transfers requires a repeat exchange, your effective handoff count is not what your process document says. It is twenty-five percent higher.

Three things usually become apparent. Latency dominates labor by an order of magnitude. Between-department handoffs cost several times what within-team handoffs cost. And the workflows with the most administrative handoffs are almost always the ones patients complain about, which is not a coincidence.

Two Strategies: Fewer Handoffs, or Better Ones

There are exactly two ways to reduce the cost of administrative handoffs, and they are not alternatives.

‍Reduce the count. The most effective handoff improvement is the handoff that no longer needs to happen. If the point of first contact can resolve the coverage question, check the authorization requirement, and book the appointment, seven transfers disappear rather than getting faster. This is where AI Agents create most of their value: not by moving requests between queues more efficiently, but by completing work at the point of contact so it never enters a queue.

Realistically, some transfers are structural. A refill needing clinical sign-off will always involve a clinician. The goal is removing the ones that exist only because the receiving point lacked information or authority.

‍Improve the quality of what remains. For handoffs that must happen, borrow from the clinical playbook. The administrative handoffs that remain should each carry a structured payload: what was requested, what has been done, what is outstanding, what the receiver is expected to do, and by when. It should confirm receipt, which is the read-back principle. It should be recorded, so the chain is reconstructable. And it should have an owner at every moment, never a queue that everybody can see and nobody holds.

Notice that none of this is exotic. It is the I-PASS structure applied to a refill request instead of a patient in a bed. The clinical world has established that this works and costs little additional time. Our overview of front office operations covers how the boundary between these functions is shifting.

The Handoffs Worth Keeping

An article arguing against all administrative handoffs would be wrong. Some transfers exist for good reasons, and the aim should be to do them well.

Clinical escalation should always be a handoff. When symptoms are described or a situation sounds urgent, the request should move to a clinician quickly, and the objective is speed and completeness of context rather than avoidance.

Emotional situations should reach a person. A frightened or grieving patient should be transferred, warmly, with context, so they do not have to repeat themselves.

Financial hardship should reach someone with discretion, since these conversations need judgment that no rule set should replace.

Anything requiring accountable professional judgment belongs with the professional who holds it. Automating the transfer is appropriate. Automating the decision is not.

The useful test is whether the receiving party will do something the sender could not. If yes, engineer the handoff to be excellent. If the answer is that the receiver merely has access the sender lacked, the handoff is an artifact of your system design and a candidate for removal.

Here's How Confido Health Can Help

This article argued that administrative handoffs carry costs almost nobody measures, and that the largest of those costs is elapsed time between people. Confido Health's AI Agents address both halves of the problem: they resolve requests at the point of contact, so fewer transfers occur, and they make the remaining transfers structured, contextual, and recorded.

Here is what Confido Health delivers:

• Resolution at first contact across scheduling and rescheduling, eligibility and benefits verification, prior authorization submission and follow-up, referral and fax intake, refill coordination, payment collection, and waitlist backfill, so requests are completed rather than routed
• Structured escalation with full context, warm transferring to the right person or routing a task carrying the entire conversation, so nobody restarts from a blank screen
• Integration-first approach with 40+ EHR and PMS systems including Epic, Athenahealth, and eClinicalWorks, which removes the person-to-system handoff of reading from one screen and typing into another
• A complete record of every transfer, with transcripts, actions, and write-backs logged, so a stalled request has an owner and a history rather than disappearing into a shared inbox
• Empathetic, natural conversations with 97 percent patient satisfaction, in more than 20 languages, answering every call on the first ring so patients are not handed work in the form of a callback
• Proven ROI, with up to 70 percent reduction in staff call burden, 60 percent reduction in cancellations, 80 percent reduction in manual administrative work, 75 percent faster prior authorization processing, and a 15 to 20 percent increase in revenue collections
• Live in under 30 days using expert-approved templates co-built with practicing physicians and operations leaders

Confido Health is more than a tool. It is the layer that closes the gaps between your people, so requests spend their time being worked rather than waiting to be picked up.

Want to know how many transfers sit inside your most common request types? Let's get started today.

Still in research mode? Start with our explainer on what an AI voice agent is, then see the front desk KPIs worth tracking.

Frequently Asked Questions

What is an administrative handoff in healthcare?

An administrative handoff is any transfer of a nonclinical task between people, teams, or systems: front desk to billing, staff to payer, or person to software. Unlike clinical handoffs, administrative handoffs typically have no standard structure, no confirmation of receipt, and no record.

Why do administrative handoffs cost so much?

Four costs attach to each one: sender time, receiver time, elapsed latency between transfer and pickup, and the probability of rework when information was incomplete. Latency usually exceeds labor by a wide margin, which is why requests feel slow even when everyone works quickly.

How are clinical and administrative handoffs different?

Clinical handoffs have structured frameworks, mnemonics, training, and an evidence base showing that structure reduces harm. Administrative handoffs have none of this despite involving the same organizations and often the same people. The asymmetry is a design gap rather than a difference in importance.

What is context decay in a handoff?

Context decay is the loss of detail at each transfer, since every handoff passes a summary rather than the original. By the third transfer, someone is acting on a summary of a summary, and specifics the patient gave in the first conversation are no longer visible to whoever holds the request.

Why do requests stall without anyone noticing?

Ownership diffuses at each transfer. The sender assumes the task is handled, and the receiver may not have registered it as theirs. A stalled request sitting in a shared queue is nobody's overdue item, so it generates no alert and surfaces only when a patient calls to chase it.

How do you measure the cost of a handoff?

Estimate sender minutes, receiver minutes, average elapsed hours before pickup, and the share requiring a repeat exchange, then multiply by monthly volume. Report the latency figure in days. Most organizations find elapsed transit time dominates labor cost by a substantial margin.

Can AI eliminate handoffs entirely?

No, and it should not try. Clinical escalation, emotionally difficult conversations, and financial hardship discussions should reach people. The goal is removing transfers that exist only because the first point of contact lacked information or authority, then making the remaining ones structured and traceable.

What makes a good handoff when one is necessary?

It carries a structured payload: what was requested, what has been done, what remains outstanding, what the receiver should do, and by when. It confirms receipt, is recorded so the chain can be reconstructed, and has a named owner at every moment rather than sitting in a shared queue.

Which handoffs are most expensive?

Between-department transfers, because vocabulary and priorities differ and neither side sees the other's queue, and payer-facing transfers, where latency runs into days rather than minutes. Within-team administrative handoffs are comparatively cheap, carry little context loss, and are rarely worth engineering away first.

Does asking a patient to call back count as a handoff?

Yes, and it is one of the most overlooked. Asking a patient to call back, bring a document, or check a portal transfers work outside the organization. It disappears from internal reporting without becoming cheaper, and it carries a high risk of the request never resuming.