Process Design

The hidden cost of a handoff

Every handoff costs more than the work on either side of it. Here is how to price one, and why most process maps hide the number.

14 September 2026 · 7 min read

Ask an operations leader where their process is slow and you will usually hear about a system, a team, or a person. Almost never a handoff. Yet in the last forty process diagnostics we have run, handoffs accounted for a median 61% of total elapsed cycle time and roughly 24% of labour cost.

The reason is structural: a process map draws the steps, and a step is visible. A handoff is the white space between two boxes, and white space does not appear on a Gantt chart. It appears as elapsed time, which most organisations do not measure at that granularity.

What a handoff actually costs

A handoff has four cost components, and only the first one is usually counted.

Transfer time. The act of moving work — writing the note, attaching the file, selecting the queue. Small, but it compounds across a long chain.

Wait time. The interval between the work being ready and the next person starting it. This is usually the dominant cost and almost always invisible, because it is nobody's task.

Context loss. The receiving person reconstructs what the sender already knew. In knowledge work this is often fifteen to forty minutes per handoff, and it is the single largest driver of rework.

Rejection loops. Work sent back because an input condition was not met. Each loop re-incurs all three costs above.

How to price it in a week

You do not need process mining software to start. Take one end-to-end process, list every handoff, and for each one record three numbers: how many instances per month, the median wait in hours, and the median rework rate. Multiply instances by wait to get the wait-hours; multiply instances by rework rate by the average handling time to get the rework-hours.

In a mid-market operation, a single process typically produces between 400 and 1,200 wait-hours per month. Priced at fully loaded cost, that is usually the largest single line item in the process — larger than the labour of any team involved.

The most expensive thing in your process is not the work. It is the work waiting for someone to notice it.

Three fixes that pay back immediately

Name the owner of the gap. Not the owner of the step before, or after. The handoff itself needs an accountable role whose job includes noticing when work is stuck. In practice this is often a queue owner rather than a manager.

Define the input contract. State exactly what condition the work must be in to be accepted. Most rejection loops exist because acceptance criteria were never written down, only assumed.

Instrument the wait, not the work. System dashboards measure throughput at the end. Track the age of the oldest item in each queue instead — it moves a day earlier and it is the number that predicts your cycle time.

None of this requires a platform. It requires a decision that handoffs are part of the process, and a habit of measuring them.

NEXT STEP

Ready to find the 20% your process is hiding?

A two-week diagnostic will show you where the waste sits, what it costs, and which five moves pay back first.