Operational go-live test checklist

Warehouse Workflow Lab

Operational go-live test checklist

Published by Voodoo Robotics · workflows.voodoorobotics.com

Person responsible for this worksheetDateVersion

Test control

What to do: Define the exact equipment, software, test area, data, and people approving the result.

System / versionRecord the software name and exact version tested.Example: Acme WMS 2026.4Hardware / configurationRecord the exact equipment model, quantity, settings, and connections used in the test.Example: Eight VDR-24 displays, firmware 4.2, brightness 70%Test areaUse the real warehouse name or location code.Example: Zone A, locations A-01 through A-48Test data setName the photo, report, scan, system record, or observation that proves the answer.Example: Event log 14:32 and photo IMG-10482WitnessesName the person responsible for this decision, task, or approval.Example: A. Rivera — Operations ManagerAcceptance authorityName the person responsible for this decision, task, or approval.Example: A. Rivera — Operations Manager

Normal-flow tests

What to do: Use one row for each normal task that must work.

This section is a list.Use one row for each task, observation, test, person, field, or requirement. Add more rows when needed.

Exception and failure tests

What to do: Use one row for each shortage, wrong item, no-read, delayed or repeated message, outage, power failure, backup method, and record-repair test.

This section is a list.Use one row for each task, observation, test, person, field, or requirement. Add more rows when needed.

Test IDGive each test a short unique code so failed tests can be tracked through retesting.

Failure scenarioDescribe the exact shortage, wrong item, no-read, delay, outage, or other problem being tested.

Expected responseState what the worker, equipment, and software should do when this problem occurs.

Actual responseRecord what really happened during the test, including any delay or workaround.

Pass / fail evidenceRecord both the result and the proof used to judge it.

Owner / next stepName the person responsible for this decision, task, or approval.

Performance and usability

What to do: Test a safe pace that workers can repeat, not a short best-case burst.

Median and p95 responseRecord typical delay and the slow-end delay that 95% of responses finished within.Example: Median 0.8 sec; P95 2.6 secPeak task rateEnter the highest safe, repeatable task rate demonstrated during the test.Example: 720 order lines/hour for a full 60-minute periodAccuracyEnter correct opportunities divided by all checked opportunities.Example: 999 correct lines out of 1,000 = 99.9%Training timeRecord the time from first instruction until the worker passes the independent-work check.Example: 2.5 hours across two shiftsErgonomic observationRecord repeated reaches, bends, lifts, grip, posture, or fatigue concerns during the test.Example: Three workers reported shoulder strain at the top two cubby rowsWorker feedbackSummarize specific worker comments about clarity, effort, pace, and common problems.Example: 4 of 5 workers preferred the prompts; two could not hear alerts at packing

Disposition

What to do: Use one row for each failed test until it is fixed, retested, and accepted.

This section is a list.Use one row for each task, observation, test, person, field, or requirement. Add more rows when needed.

Related on voodoorobotics.com: pick-to-light Starter Kit — What a Starter Kit pilot includes and how it scales.