How to map handoffs and rework in a business process

01

Trace a small set of real items

Pick a process with an agreed start and finish, then select recent completed items and some still in progress. Include routine work and exceptions. Walk through each with the people who handled it, using records to check the sequence and timing.

Draw the steps in order and mark the owner, input, output and decision at each handoff. Add queues and approvals. Show returns and alternate routes too. Note where the record is incomplete rather than filling gaps with assumptions.

02

Inspect each handoff

For every transfer, ask what the receiving person needs, how they accept responsibility and what happens when the information is incomplete. Compare that agreement with actual samples. A forwarded message may leave a request without an accepted owner.

Mark where work waits and where it returns for correction. Record the reason and originating step when known. If several corrections share a cause, trace that cause to the point where it could be prevented rather than counting each return as a separate root cause.

03

Try a bounded change

Choose one recurring failure with the team, such as missing information at intake. Define the minimum required information, identify who checks it and agree what happens for urgent or unusual requests. Keep a path to correct mistakes and escalate disputes.

Compare the same kind of work before and during a limited trial. Record return reasons, elapsed time, completed items and any customer or quality problems. Review the results with both sides of the handoff before extending the change.

For example, if requests often return because an address is incomplete, agree which address fields the receiving team needs and who checks them. Let the sender resolve a missing field before transfer, while giving urgent requests an exception route. Review both returned requests and the time spent collecting information; a lower return count alone may hide extra delay at intake.

Keep the original map with the changed version and mark who approved the trial. If a required approval protects quality or a legal obligation, involve its owner before changing it. When the sample is small or the work mix changes, treat the result as a reason for further observation rather than proof of a lasting improvement.

04

Record handoff ownership

Make the handoff record usable: add four fields to each arrow on the map—sender, receiving owner, required input and acceptance event. For example, “sent by email” is a transmission event, while “accepted by an assigned reviewer” confirms ownership. Check disputed handoffs against the actual record before changing the process.