# Handoff Map worksheet: the 30-minute method

Source: https://dutygraph.com/resources/handoff-map/
Companion file: handoff-worksheet.csv

A handoff is the moment work changes hands. Most operating friction that leaders
describe as "a people problem" or "a systems problem" is a handoff with no agreed
acceptance rule. This worksheet records those moments so your team can fix the
rule instead of arguing about the symptom.

Use it for one workflow at a time. Thirty minutes is enough for a first pass.

## What you need

- One workflow with a clear first and last step, such as quote to order.
- The `handoff-worksheet.csv` file, opened in any spreadsheet tool.
- 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 in the first column. Agree out loud where it starts
(the trigger) and where it ends (the accepted result). 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. For each row, fill in:

- **sending_role** and **receiving_role**: who hands over, who picks up.
- **trigger**: what causes the handover.
- **required_information**: what the receiver needs before they can start.
- **work_product**: what is actually handed over.

Do not describe how the work should happen. Describe what happened the last time.

## 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**. A row with no
acceptance rule is where work waits.

Then record the **exception** that breaks the rule most often, and the
**decision_owner** who may resolve it. If nobody can name the decision owner,
write "Named owner to confirm" and keep going.

## Minutes 25 to 30: record what you do not know

Fill in **system_of_record** (where the agreed version lives),
**evidence_reference** (the example or document you used) and
**open_question** for anything the group could not settle. Set a
**review_date** so the sheet does not quietly go stale.

Leave the open questions visible. 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 is a likely delay.
- A row where two people describe the required information differently is a
  definition problem, not an effort problem.
- A row whose decision owner is unknown is the reason exceptions reach the owner
  of the business.
- A row that one person alone can complete is a single point of failure.

A reported delay is not yet a measured delay. Before you change anything, agree
what you will measure and when you will check it.

## What to do next

Fix the two rows with the weakest acceptance rules first, name an owner for each
exception, then re-check the sheet in 30 days.

If the workflow crosses several departments, or the same question keeps coming
back to leadership, a business operations audit maps the whole picture from the
team's own answers: https://dutygraph.com/audit/

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