Map the process · 3 pages

Map how the process works today

List each step, who performs it, what the system does, and where work waits or goes wrong.

Fill it in online · Print or save as PDF · Your entries are not uploadedNot sure about a term? Open the plain-English glossary
How to use this worksheet
  1. Fill it out with workers who do the job.
  2. Use actual observations or system records.
  3. If an answer is uncertain, write what still needs to be checked.

Your answers stay only in this open page. Print or save a PDF before closing or reloading it.

Use this when

A process has unclear ownership, hidden waits, or undocumented system/physical mismatch.

See a filled-example scenario

You map an order from release through picking and packing, including the three places where a tote can wait or leave the normal path.

The gray examples inside the fields show the level of detail expected. They are examples only and are not saved as answers.
Warehouse Workflow Lab

Map how the process works today

Published by Voodoo Robotics · workflows.voodoorobotics.com

01

Scope

What to do: Choose one bounded value stream.

02

Process steps

What to do: Record both physical and information flow.

This section is a list.Use one row for each task, observation, test, person, field, or requirement. Add more rows when needed.
StepUse one specific, observable piece of work.
Actor / systemName the person, team, device, or software responsible for this step.
InputList the item, information, container, or approval needed before the step can begin.
ActionWrite a visible action with a named owner and finish condition.
Output / stateWrite what is true after the step is complete.
Cycle timeUse a number and unit, and state the start and stop points when needed.
Queue / waitRecord what waits before this step and the typical or slow-end wait time.
03

Decision and exception points

What to do: Show where the happy path splits.

This section is a list.Use one row for each task, observation, test, person, field, or requirement. Add more rows when needed.
Signal / conditionState what causes the process to take a different path.
Decision ownerName the person responsible for this decision, task, or approval.
Normal branchDescribe the next action when the condition is normal.
Exception branchDescribe what went wrong, where it was noticed, and the practical effect.
Escalation clockState how long workers wait before contacting the next level.
System statusEnter the exact status the software records at this point.
04

Constraint summary

What to do: Name evidence, not opinions.

Keep related photos, drawings, reports, and system records with the saved PDF. This worksheet does not replace site-specific safety, quality, regulatory, or engineering review.

Reviewed byDate
← All practical worksheets