Go-live readiness checklist for warehouse software
A 19-item go-live readiness checklist for WMS, inventory and tracking software covering the decision, testing, data, people, support and rollback.
Plan cutover and training
Checklist
Go-live is a decision, not a date on the plan. This checklist holds 19 items in five sections that should be true before a warehouse, inventory or tracking system goes live: who decides, what was tested, whether the data is right, whether the people on the floor are ready, and how you get back if it goes wrong.
How to use the checklist
- Start two to four weeks before the planned date. Every unticked item gets an owner and a due date.
- Tick only what can be shown: a test report, a reconciliation, a training sign-in sheet, a rehearsal log.
- Run it again in the go or no-go meeting. An item that still cannot be ticked is either a no, an accepted risk with a written workaround, or a reason to move the date. Record which.
- Download the CSV and attach it to the decision record. Ticks are not saved on the page.
What good looks like
Go or no-go decision
One named person makes the call, usually the operations sponsor. The criteria for go, delay and rollback are written before the meeting, for example: “Go if all critical acceptance tests pass, opening balances reconcile within the agreed tolerance and every shift has a trained super-user.” The meeting has a time limit, so it ends in a decision.
Testing
All critical tests in the UAT test plan pass. Open defects are reviewed, and each has an owner and a workaround the floor has seen. A full day of volume has been processed in test. Interfaces have been tested with each trading partner, not only with sample files.
Data
Opening balances are counted or validated, not just loaded. Master data is spot-checked on the floor by scanning real items and labels. Open orders and shipments in transit are converted. A reconciliation report compares the old and new systems, and someone has signed it.
People and floor
Every user has an account and has logged in at least once. Floor staff have trained hands-on with real devices and labels. Quick reference cards are at each station. Super-users are scheduled on every shift for the first two weeks.
Support and rollback
A support channel and an escalation path are published. Vendor and integration contacts are on call for cutover. The rollback plan has been rehearsed, so the team knows how long it takes and what data has to be re-keyed. Daily check-in meetings are booked for the first two weeks.
Choosing the date
Avoid going live just before a peak season, a month-end or quarter-end close, or a scheduled physical inventory. Pick a lower-volume day with full staffing, plan extra labor for the first week, and keep inbound appointments light for the first few days so receiving problems do not stack up.
Who should fill it in
- The project manager owns the checklist and the meeting.
- The testing lead confirms the testing section.
- Inventory control or the data owner confirms balances, master data and the reconciliation.
- The operations manager and training lead confirm accounts, training and super-user coverage.
- IT confirms support, on-call contacts and the rollback rehearsal.
- The sponsor makes the call.
Common mistakes
- Going because the date was announced. A delayed go-live costs less than a failed one.
- Treating attendance as readiness. People who sat through a demonstration have not used the scanner.
- A rollback plan that was written but never rehearsed.
- No reconciliation, so the first sign of a data problem is a pick from an empty location.
- Super-users pulled back to their own work after day two.
Go-live sits between stage 5, test and cut over, and stage 6, document and onboard, in how we work. Onboarding and training prepares the floor, documentation produces the quick reference cards and runbooks, and project planning sets the criteria early enough to be useful.
Scope your project.
Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.