FREE WORKSHEET

The Handoff Map worksheet

A handoff is the moment work changes hands. This worksheet records every handoff in one workflow, with the rule each receiver uses to accept it, so you can see where work waits. One workflow, about 30 minutes.

Why map handoffs first?

Most operating friction that leaders describe as a people problem or a systems problem is a handoff with no agreed acceptance rule. Sales says an order is ready when the quote is accepted. Operations cannot begin until the delivery details arrive. Everyone completed their own step, and the work still waits.

You do not need a full process map to find that. You need the list of moments the work changes hands, and one sentence per moment about what the receiver needs.

The 30-minute method

Use it for one workflow with a clear first and last step, such as quote to order or supplier onboarding. Bring two or three people who send, perform, review or receive the work.

Minutes 0 to 5 · Name the workflow and its edges

Write the workflow name, then agree out loud where it starts and where it ends. Write both down. If the group cannot agree on the edges, that disagreement is your first finding.

Minutes 5 to 15 · List every change of hands

Add one row for each moment the work moves to a different person, team or system: who hands over, who picks up, what triggers it, what the receiver needs and what is actually handed over. Describe what happened last time, not what should happen.

Minutes 15 to 25 · Write the acceptance rule

For each row, answer one question: how does the receiver know the handover is complete enough to start? That sentence is the acceptance rule. Then record the exception that breaks it most often and the person who may resolve that exception.

Minutes 25 to 30 · Record what you do not know

Fill in the system of record, the example you used, and an open question for anything the group could not settle. Set a review date. A map that hides its gaps is less useful than one that marks them.

How to read the result

A row with no acceptance rule
This is where work waits.
Two people describing the required information differently
This is a definition problem, not an effort problem.
A row whose decision owner is unknown
This is why exceptions reach the owner of the business.
A row only one person can complete
This is a single point of failure if that person leaves.

A reported delay is not yet a measured delay. Before you change anything, agree what you will measure and when you will check it. Fix the two rows with the weakest acceptance rules first, name an owner for each exception, then re-check the sheet in 30 days.

The example rows in the file are fictional. The worksheet is a planning aid, not a compliance record, an approval or a guarantee of a saving.

Get the worksheet

Give us a work email and the files appear right here. Every field except the email and the agreement is optional.

Please do not include confidential company or employee information. See Privacy.

Questions about the worksheet

What is in the download?

Two files: a CSV worksheet with the columns to fill in and three fictional example rows, and a Markdown guide with the 30-minute method. Both are plain files you can open in any spreadsheet or text editor.

Do I have to give my email to get it?

Yes. We ask for a work email so we can send the follow-up you agree to, and the files appear on this page as soon as the form is accepted. Nothing is emailed before you ask for it.

Will this put me in a sales sequence?

No. You agree only that we may contact you about this worksheet and DutyGraph. The newsletter is a separate, optional choice on the same form, and we never sell or share your address.

How is a handoff map different from a process map?

A process map shows the whole path from trigger to result. A handoff map records only the moments work changes hands, and the rule each receiver uses to accept it. It is the fastest way to find where work waits.

What if our team cannot agree on the acceptance rule?

Write both versions in the row and mark it as an open question. A disagreement about what counts as complete is a finding, not an error to tidy away.

Related reading

RACI matrix: roles and responsibilities · Cross-functional handoffs · Process mapping services · How pricing works