Workflow Mapping Sheet
Map triggers, people, steps, systems and handoffs so recurring work can be reviewed before it is automated.
Working record
| Check | What to do | Evidence to retain |
|---|---|---|
| Trigger | State the event that starts the workflow and the input it supplies. | The trigger record, its source and the person responsible for resolving missing evidence. |
| Owner | Name the person who can approve the decision and the person who carries out the next action. A team name alone can leave the handoff unclear. | Named decision owner, action owner and review date. |
| Steps | Write the actions in execution order with their inputs and expected outputs. Test the instructions with a representative case. | The steps record, its source and the person responsible for resolving missing evidence. |
| Handoffs | Identify what passes between people or systems and what confirms successful receipt or completion. | The handoffs record, its source and the person responsible for resolving missing evidence. |
| Output | Show a concrete example of the result the receiving person or system needs. Check fields, format and next action. | Expected output fixture and receiving owner. |
Review the decision
Map triggers, people, steps, systems and handoffs so recurring work can be reviewed before it is automated. Keep trigger, owner, steps attached to the conclusion so the next owner can challenge the assumptions. Resolve missing evidence before treating this record as approval.
Continue the decision
The Real Cost of Adding Another SaaS Tool · Cash Runway: How to Calculate It and What to Watch.
Calculation and source notes
Keep the displayed formula, input units and model scope with the result. Corrections or questions can be sent through the request section on this page.
Content updated: October 11, 2026