Warehouse Workflow Lab
Plan how to handle warehouse problems
Published by Voodoo Robotics · workflows.voodoorobotics.com
01
Exception definition
What to do: Give each common problem a code and a clear meaning.
This section is a list.Use one row for each task, observation, test, person, field, or requirement. Add more rows when needed.
Exception codeEnter the short code used in the WMS, if one exists.
Plain-language nameGive the problem a short name a floor worker would immediately understand.
Detection signalExplain how a worker or system notices the problem.
Affected operationName the warehouse task where this problem occurs.
SeverityChoose how serious the effect is using the scale agreed for this worksheet.
ExampleGive one specific warehouse example that clearly fits this definition.
02
Containment and ownership
What to do: Use the Problem code to connect this response to the definition above.
This section is a list.Use one row for each task, observation, test, person, field, or requirement. Add more rows when needed.
Exception codeEnter the short code used in the WMS, if one exists.
Physical destinationState where the item, order, or container should be placed.
System statusEnter the exact status the software records at this point.
Immediate containmentFirst action that prevents the problem from spreading.
OwnerName the person responsible for this decision, task, or approval.
Response targetState how quickly the named owner should respond.
EscalationState who is contacted next, after how long, and by what method.
03
Resolution
What to do: Use the Problem code to show what closes each problem.
This section is a list.Use one row for each task, observation, test, person, field, or requirement. Add more rows when needed.
Exception codeEnter the short code used in the WMS, if one exists.
Permitted resolutionsWrite a visible action with a named owner and finish condition.
AuthorityName the person responsible for this decision, task, or approval.
Required evidenceName the photo, report, scan, system record, or observation that proves the answer.
Inventory / order correctionState the exact inventory and order records that must be corrected before closure.
Closure eventState the action or record that proves the problem is closed.
04
Learning loop
What to do: Use the Problem code to track how often the problem returns and what prevents it.
This section is a list.Use one row for each task, observation, test, person, field, or requirement. Add more rows when needed.
Exception codeEnter the short code used in the WMS, if one exists.
FrequencyUse a count divided by a clearly named opportunity and include the time period.
Median ageUse a number and unit, and state the start and stop points when needed.
Repeat causeName the verified reason the same problem keeps returning.
Corrective actionWrite a visible action with a named owner and finish condition.
Action ownerName the person responsible for this decision, task, or approval.