Good WMS training is organized by role, not by menu. Each receiver, picker, inventory controller and supervisor learns only the tasks they will do. They practice on the handhelds and labels they will use, in a training environment loaded with your own items and locations. Choose super users from every shift before anyone else is trained, give them protected time, and let them co-teach their own crew. Sign each person off with a practical check on the task, not an attendance sheet, and keep a super user on the floor of every shift through the first weeks after go-live.
That answer holds for a new warehouse management system (WMS), a new tracking app on the dock, or an ERP module that changes how stock moves. This note covers the people side. It explains who the super users are, how much of their time to budget and what each role learns. It also covers training a night shift and a weekend crew, and proving that people can do the work. The written procedures that training teaches from are covered in writing warehouse SOPs that match the new system.
What a super user does on a warehouse system project
A super user is a floor employee who learns the new system first and in more depth than their coworkers, helps test it, helps teach their own shift, and becomes the first person their crew asks after go-live. The role is not IT support and not a replacement for a trainer. It is the link between the project team and the people who will run the system at 3 a.m.
ERP research has looked at the role, usually under the name “key user”. Maas, van Fenema and Soeters coded 58 interviews with key users, end users and managers about the period after an ERP system goes live (Journal of Knowledge Management, 2016). They found six mechanisms key users apply to share knowledge across structural, social or cognitive boundaries, and described three roles key users can play in that phase. Their practical advice is that key users’ tasks and responsibilities must be clear from the start, and that employees suited to the role should be selected with care.
A second study followed one ERP program at wind turbine maker Vestas and modeled super-user selection and training as a systematic process (Obwegeser and colleagues, 2019). The authors note that selecting and training super-users had received little academic attention. Their model highlights that different skills matter at different phases of selection and training. The authors also compared what management expected of super users with the skills the super users actually had.
Super-user work by project phase
The role changes as the project moves. Write this table into the super-user role description, so the person and their manager know what they are agreeing to.
| Project phase | What the super user does | What it produces |
|---|---|---|
| Process walk and requirements | Describes how work is really done, including the bad days | Exception list in floor language |
| Build demos | Tries the screens on a handheld at each demo | Issues logged in the words the floor uses |
| User acceptance testing | Runs the test scripts for their area | Signed test results |
| Documentation | Tests draft SOPs and reference cards by doing the task | Marked-up drafts |
| End-user training | Co-teaches their own shift and runs practical checks | Sign-off records |
| Go-live and hypercare | Supports the floor, triages problems, logs issues | Issue log entries |
| After hypercare | Trains new hires, spots process drift, flags changes | New-hire sign-offs, change requests |
Super users do much of their best work during user acceptance testing. Someone who has run the receiving scripts twice, and watched three of them fail, can explain the screens with authority that a slide deck never has.
Who teaches what: trainers and super users
Split the teaching between two people. A project trainer, from the implementation team or your own training function, owns the curriculum, the scenario scripts and the practical checks. Super users co-teach the sessions for their own shift and run most of the checks.
That split keeps the material identical across shifts, while the voice in the room belongs to someone the crew already knows. It also means that when the project trainer leaves, the people who can train the next new hire are already on the payroll. Plan the handover of the trainer pack (session plans, scenario scripts, checks) as a named step, not an assumption.
What super users are not
Super users are not the project’s unpaid help desk. If they spend go-live resetting passwords and chasing printer tickets, nobody is coaching receivers. Route account and hardware problems to IT from day one.
They are also not a way around your controls. A helpful super user does not need supervisor overrides, adjustment approval rights or administrator access. Give them the permissions of their own role, plus read access where it helps them diagnose. Inventory adjustments still go through the person who owns them.
How to choose super users
Choose people their coworkers already go to with questions, from every shift and every area whose work will change, and confirm in writing that their manager can release them. Speed on the old system is a weak signal. Patience, knowledge of the exceptions and the trust of the crew matter more.
The study of the Vestas program treated selection as a deliberate step with defined skills, not a show of hands (Obwegeser and colleagues, 2019). In a warehouse, these are the criteria we would score:
| Criterion | What to look for | Warning sign |
|---|---|---|
| Peer trust | Coworkers already ask this person how to handle odd cases | Named because they are the manager’s favorite |
| Exception knowledge | Knows what happens with short shipments, damaged pallets and missing labels | Knows only the normal flow |
| Teaching temperament | Explains without grabbing the scanner out of someone’s hand | Does the task for the trainee to save time |
| Shift fit | Works the shift they will support and expects to stay on it | About to transfer, rotate or leave |
| Availability | Manager agrees to release the hours, in writing | “They can do it in their spare time” |
| Candor | Reports problems with the new system plainly | Defends the old system, or the new one, no matter what |
How many super users you need
There is no published ratio worth quoting, so count from your own operation. List every shift, then every functional area on that shift whose screens or scans will change: receiving, put-away, picking, packing and shipping, inventory control. Each cell in that grid needs a named super user. In our engagements we plan at least one super user per shift at each site, and more where areas are large or far apart.
Then add backups. Shifts lose people to vacation, sickness and turnover, and a cell with one name in it is a single point of failure. Where one person covers two areas, check that both areas are not at their busiest in the same hours on that shift.
Common selection mistakes
- Choosing supervisors. Supervisors are needed to run the shift during go-live. They should be trained early and in depth, but they are rarely free to coach at a station for hours.
- Choosing only office staff. An inventory analyst who works days may know the system well but has never seen how the night crew handles a trailer that arrives without an ASN.
- Choosing temporary or agency staff. The knowledge leaves when the assignment ends.
- Not asking. Tell candidates what the role involves, how long it lasts and what changes for them before they agree. Decide up front whether the role carries a title, a pay differential or neither, and say so in writing.
How much time super users need, and how to protect it
Budget super-user time in hours per week for each project phase, put those hours on the labor plan, and agree backfill with each manager before training starts. The hours are real work, and they are paid. If they are not planned, operations will reclaim them the first busy week.
A useful planning fact: under the federal wage-and-hour rules, training is not working time only if four conditions are all met. Attendance must be outside regular hours, actually voluntary, not directly related to the job, and free of productive work (29 CFR 785.27). Attendance required by the employer is not voluntary (29 CFR 785.28), and training that helps an employee do their current job more effectively is directly related to it (29 CFR 785.29). Training on the new WMS fits that description, so a night-shift receiver who comes in at 2 p.m. for a session is on the clock. Ask HR how that interacts with overtime and your pay rules before you schedule.
Example (fictional). A distribution center runs three shifts and names seven super users. It budgets each super user’s hours by phase, following the plan in the chart above:
| Phase | Weeks | Hours per week | Hours |
|---|---|---|---|
| Super-user training | 3 | 8 | 24 |
| User acceptance testing | 3 | 12 | 36 |
| End-user sessions and practical checks | 3 | 16 | 48 |
| Floor support, first two weeks after go-live | 2 | 40 | 80 |
| Floor support, next two weeks | 2 | 20 | 40 |
| Total per super user | 13 | 228 |
For seven super users that is 1,596 hours. At 40 hours a week, the site needs roughly 40 person-weeks of backfill, which goes into the labor plan as temporary labor and approved overtime.
Four ways to protect the hours
- Put the hours in the labor plan. If the site plans labor by engineered standards or pick rates, the super users’ targets drop for the weeks they are released, and so does everyone’s target in the first weeks after go-live.
- Agree backfill per person. Name the temp, the overtime or the cross-trained colleague who covers each super user’s normal work.
- Fix the schedule. Super-user hours sit on the same days and times each week. “When it’s quiet” never comes.
- Give the role an escalation path. If a manager pulls a super user back to the line, the project lead and the sponsor hear about it that day.
Building a role-based WMS training curriculum
Start from each role’s task list, taken from the requirements and the SOPs, and teach each person only the tasks they will perform, in the order they meet them on a shift, including the exceptions. A menu-by-menu tour of the system teaches people where things are, not how to do their job.
The task list should already exist. If the requirements were written as testable statements, each task maps to one or more acceptance tests and one SOP. Our page on onboarding and training describes the same matrix: each role, its tasks and the session that covers them.
| Role | Core tasks | Exceptions they must handle | Practical check |
|---|---|---|---|
| Receiver | Receive against an ASN, receive without one, apply license plate labels | Short or over shipment, pallet without a label, wrong item | Receive three test shipments, one with an exception, without help |
| Put-away and replenishment | Directed put-away, location confirmation scans, replenishment tasks | Location full, location label damaged, override request | Put away five pallets with every location confirmed by scan |
| Picker | Pick tasks, pick to tote or pallet, short pick | Empty location, damaged item, item in the wrong slot | Complete a test wave that includes a short pick |
| Pack and ship | Pack, print carton labels, close and load the shipment | Label printer failure, weight outside tolerance | Ship a three-carton order with correct labels and load scan |
| Inventory control | Cycle counts, recounts, holds, adjustments | Variance over tolerance, negative on-hand | Take a count with a variance through to an approved adjustment |
| Supervisor | Task queues, exception queues, approvals, shift handover | Stuck tasks, an interface message that failed | Clear a seeded exception queue and explain each reason code |
| Customer service | Order and shipment status lookups | Carrier exception, partial shipment | Answer a “where is my order” call from the screen alone |
How a session runs
Each session covers a handful of tasks and follows the same pattern: show, do, check. The trainer demonstrates the task once on a real handheld. Each trainee then performs it with coaching, and finally performs it alone while the trainer watches. Keep groups small enough that everyone has a device in hand for most of the session.
Supervisors and inventory controllers need one more layer: what each scan posts. When a receiver closes a receipt, what changes in the WMS, what goes to the ERP, and when? People who approve adjustments or clear exception queues make better decisions when they know which transaction created the number on the screen. This matters most in the days around cutover, when opening balances are fresh; the method for loading them is in WMS inventory cutover without losing the count.
Teach from the documents people will keep
Training should use the same SOPs and quick reference cards that will sit at the stations after go-live. If the trainer teaches one sequence and the card shows another, people follow whichever they saw last. Trainers and super users mark up the documents as they teach, and the documentation owner folds those notes into the next version before go-live.
Practice in a training environment that looks like your building
People should practice on the same handhelds, printers, label stock and location labels they will use, in a separate training environment loaded with your own items, locations and trading partners. Scripted scenarios should include the bad days, not just the clean receipt.
Never train in production. Practice receipts would post real inventory, and practice adjustments would reach the ERP. A training copy of the system, refreshed from a recent configuration, keeps the screens and settings identical without touching live stock.
What the training environment needs
- Your item master. Real item numbers, units of measure, case packs, lot and serial flags. If the item data is wrong in training, it is probably wrong in production too, which is worth finding now; item master data readiness covers how to check it.
- Your location scheme. The same aisle, bay, level and position format, so trainees learn to read the location IDs they will scan.
- A practice area with its own labels. A short mock aisle with printed location labels. Print them on a different color stock or mark them TRAINING, keep them in that area, and collect them afterward so nobody scans one in production.
- Your devices and label stock. The same handheld model and settings, the same printers and label sizes. Trainees should scan from real distances and angles, wearing gloves if the job requires them.
- Scenario data. Purchase orders, ASNs and orders built for each script, including the exceptions.
- One user ID per trainee. Practical checks are only evidence if each transaction can be traced to the person who did it.
- A reset routine. Restore the environment to a known state between sessions, so every class meets the same scenarios.
Example (fictional). Receiving scenario R-3 uses ASN EX-856-01 for four pallets of item EX-20118. In the training data, one pallet arrives with no license plate label, and one carton on another pallet is short. To pass, the trainee must receive the three labeled pallets by scan, print and apply a new label for the unlabeled pallet using the steps on the receiving card, record the short carton with the correct reason code, and close the receipt. The super user resets the scenario from a saved snapshot before the next trainee starts.
Why vendor demo data falls short
Demo data teaches the vendor’s warehouse. Item numbers, location formats and units of measure all differ from yours, so the first live morning is the first time people see their own codes on the screen. Loading your data into training costs a few days of work and exposes data problems while there is still time to fix them.
Training across shifts, languages and turnover
Run sessions on every shift, taught by that shift’s super user alongside a project trainer, and schedule the night and weekend crews first in the plan rather than last. Treat training as paid working time, and build a path for the people who will join after go-live.
Shift logistics
A predictable failure is a training calendar built around the project team’s working day. Day shift gets trained properly, second shift gets a rushed session, and the weekend crew gets a handout. Then go-live happens at 10 p.m. on a Sunday.
Build a grid of roles by shift before you book a single session. Hold sessions at the start of each shift or in that shift’s quiet hours, at the stations where the work happens. Move the trainer to the shift, not the shift to the trainer. Part-time and weekend staff need smaller groups and more sessions, so plan for them explicitly.
Agency and seasonal workers need the same practical check before they get a user ID. Agree with the staffing agency who delivers that training, and on whose time.
Example (fictional). A site runs a day shift, a swing shift, a night shift and a weekend crew. Its receiving sessions are booked like this, so that every crew is trained by its own super user in its own working hours:
| Crew | Session slot | Taught by | Group size |
|---|---|---|---|
| Day (6 a.m. to 2:30 p.m.) | 6:30 a.m., before the first trailers | Day super user and project trainer | 4 receivers |
| Swing (2 p.m. to 10:30 p.m.) | 2:30 p.m., after shift handover | Swing super user and project trainer | 4 receivers |
| Night (10 p.m. to 6:30 a.m.) | 11 p.m., the quietest hour on the dock | Night super user and project trainer | 3 receivers |
| Weekend (Fri to Sun, 12-hour shifts) | Saturday 7 a.m., repeated Sunday | Weekend super user | 2 receivers per session |
The project trainer works two night shifts and one weekend shift during the training weeks. Nobody is asked to attend outside their own shift.
Language and reading level
OSHA’s policy is that training required by its standards “must be presented in a manner that employees can understand” (OSHA Training Standards Policy Statement, April 28, 2010). The same memo says employers must use “a language and vocabulary that the employees can understand”, and that if employees are not literate, telling them to read training materials does not satisfy the obligation.
WMS training is not training required by an OSHA standard, so that policy does not govern it. The principle is still the right one. Run sessions in the language your crew works in, translate the quick reference cards, and rely on photos of the actual screens and labels rather than paragraphs of text.
If the handheld application can display more than one language, decide which language each user profile will use before training. The screen in the classroom must match the screen on the floor.
Turnover means training never ends
Warehouses replace people constantly, so a training plan that ends at go-live is already out of date. Bureau of Labor Statistics data for transportation, warehousing and utilities show an average monthly total separations rate of 4.0 percent in 2025, not seasonally adjusted (BLS JOLTS). The rate ran 6.7 percent in January and 6.5 percent in December, against 3.0 to 4.0 percent in the other months. The industry group is broader than warehousing, but the pattern is familiar to anyone who has staffed for peak.
For example, suppose a site of 150 people loses people at that average rate. That is about six people a month to recruit, train and sign off, long after go-live. Super users and a written new-hire path are what keep that training going without the project team.
Competence checks instead of attendance
Sign a person off when they have performed their role’s tasks in the training environment, including at least one exception, while a super user or trainer watches and records the result. An attendance sheet only proves that someone was in the room.
The forklift rule as a model (an analogy)
Federal workplace-safety rules already contain a practical model for this, in a different field. OSHA does not regulate WMS training, and nothing below is a legal requirement for it. We use OSHA’s powered industrial truck rule only as an analogy, because it describes competence-based training more precisely than most software training plans do.
Under 29 CFR 1910.178(l), the employer must ensure each forklift operator is competent “as demonstrated by the successful completion of the training and evaluation” in that paragraph. Training “shall consist of a combination of formal instruction”, practical training, and “evaluation of the operator’s performance in the workplace”. OSHA’s training eTool summarizes the same requirements for employers.
| What 29 CFR 1910.178(l) requires for forklift operators | The system-training practice it suggests |
|---|---|
| Competence "as demonstrated by the successful completion of the training and evaluation" ((l)(1)(i)) | Sign-off is earned by doing the task, not by attending |
| A combination of formal instruction, practical training, and evaluation of performance in the workplace ((l)(2)(ii)) | A short walkthrough, hands-on practice on real devices, then an observed check |
| Trainees operate only under direct supervision, and only where it does not endanger anyone ((l)(2)(i)) | Practice in the training environment, or in production only with a super user beside the trainee |
| Training and evaluation by people with the knowledge, training and experience to do it ((l)(2)(iii)) | Super users pass the checks themselves, and rehearse running them, before they evaluate anyone |
| Refresher training after unsafe operation, an accident or near miss, a failed evaluation, a different type of truck, or a workplace change that affects safe operation ((l)(4)(ii)) | Retraining after a traced error, a failed spot check, a new role, or a release that changes the screens |
| An evaluation of each operator at least once every three years ((l)(4)(iii)) | Periodic spot checks on an interval you set |
| Certification with the operator's name, the training date, the evaluation date and who trained or evaluated ((l)(6)) | A training record per person, task and system version |
Designing a practical check
A practical check is a short, scripted task with pass criteria written before anyone sits it. It should take minutes, not hours, and a super user should be able to run it without the project team.
| Element | What it looks like for a receiver |
|---|---|
| Task | Receive scenario R-3 in the training environment |
| Pass criteria | All pallets received by scan, unlabeled pallet relabeled, short carton recorded with the right reason code, receipt closed |
| Allowed help | The receiving reference card; no coaching from the evaluator |
| Evaluator | A super user or trainer who has passed the same check |
| Record | Name, role, task, date, evaluator, pass or retry, system version |
| If not passed | Coaching on the step that failed, then a second attempt on another day |
A failed check is information, not a verdict. If several people fail at the same step, the screen, the card or the session is at fault, and the fix belongs there.
Spot checks after go-live
A sign-off before go-live proves someone could do the task in training. A spot check after go-live shows whether they still do it that way on a busy floor. Each month, a super user picks a few people per role, watches one live task against the same pass criteria, and records the result. Fix the cards and the sessions first when spot checks fail, and coach individuals second.
Tie the sign-off to the user ID
The strongest control is simple: no sign-off, no production login. Accounts are created in advance but activated only when the person’s practical check is recorded. If a supervisor needs someone on a role before the check is done, that is a recorded exception with a super user assigned beside them.
The sign-off list, by person, role and shift, feeds the go or no-go decision. Training completion is one section of our go-live readiness checklist, next to data, interfaces and support.
A safety question to ask
A WMS project often changes more than screens. Go-live may come with re-slotting, new storage locations, new travel paths or terminals mounted on trucks. Ask your safety lead whether that counts as “a condition in the workplace” that “changes in a manner that could affect safe operation of the truck” under 1910.178(l)(4)(ii)(E). If it does, forklift refresher training belongs in the same plan.
Floor support after go-live
For the first weeks after go-live, keep super users off their normal production work and on the floor of every shift, easy to spot, with one issue log and a clear rule for what they fix themselves and what they escalate. Project teams often call this period hypercare.
Markus, Axline, Petrie and Tanis studied adopters’ experiences with ERP and found that problems arise in every phase, and that many problems seen in later phases “originated earlier but remained unnoticed or uncorrected” (Journal of Information Technology, 2000). On a warehouse floor, the early sign is the workaround: the receiver who keys a quantity because the label will not scan, or the picker who skips a short-pick step. Super users are there to see workarounds and log them, not only to answer questions.
The first shift on the new system
Place super users where the first transactions happen: at the receiving doors when the first trailer is opened, and at the start of the first pick wave. Stage spare charged handhelds, a spare printer and extra label stock in each area. Make sure every supervisor has the downtime procedure from the SOPs on paper, because the first time it is needed is the wrong time to look for it.
Keep the project team’s phone numbers on a card at each station for the first nights. Check the first receipts and picks against the paperwork before people go home, so a configuration error shows up on the first shift rather than at the first cycle count.
What super users fix and what they escalate
| Situation on the floor | Super user action | Escalate to |
|---|---|---|
| A user forgot a step | Coach at the station, then let them redo it | Nobody, but log it if it repeats |
| Label will not print or scan | Check printer, stock and ribbon; reprint | System administrator if the template is wrong |
| Location is full or does not exist | Follow the exception step on the card; log it | Inventory control |
| Screen quantity does not match the shelf | Stop; do not adjust; log the item and location | Inventory control |
| An expected ASN or order is missing | Log the reference number and time | IT or integration support |
| No procedure covers the situation | Get an interim instruction from the supervisor; log it | Process owner and documentation owner |
Daily rhythm
- Start of every shift. A short check-in where the super user hears what the previous shift logged and what has been fixed.
- During the shift. Super users walk the areas rather than wait to be called. People who are struggling often do not ask.
- End of every shift. Open issues are handed to the next shift’s super user by name, not left in a chat thread.
- Once a day. The project lead reviews the log with the operations manager and decides fixes, document changes and retraining.
Make super users visible. A colored vest or a lanyard costs almost nothing and saves a confused picker from walking the building looking for help.
When to stand down
Floor support ends against criteria agreed before go-live, not on a date chosen for convenience. Reasonable criteria include: the same “how do I” question no longer repeats on any shift, open issues are below a level the sponsor agreed, and everyone hired or moved since go-live has passed their check. Our go-live checklist asks for super users scheduled on every shift for the first two weeks; whether support stops then depends on those criteria.
Keeping training current after the project
Turn the project’s training into a standing program: a new-hire path, retraining triggers tied to releases and errors, an active super-user group, and records that show who is signed off on which tasks.
Retraining triggers
The forklift rule’s refresher list translates well, again as an analogy. Retrain a person on a task when:
- They are seen doing the task in a way that creates errors or risk.
- An inventory or shipping error is traced to how they performed the task.
- A spot check shows they no longer meet the pass criteria.
- They move to a role or area they were not signed off on.
- A system release, configuration change or new process changes the screens or steps they use.
The fifth trigger is the easiest to miss, because nobody on the floor made a mistake. When a release changes a receiving screen, the release notes should list the roles and SOPs affected, and the SOP owner should update the cards before the release goes live. Our note on warehouse SOPs that match the new system covers that version control.
Keep the super-user group alive
Without a reason to meet, super users drift back into their normal jobs and the network fades. Hold a short meeting every month where they bring the problems their shifts report, and review upcoming changes. Replace super users who leave before the gap shows, and train their replacements against the same practical checks.
Training records that answer real questions
Keep one record per person per task: name, role, task, training date, check date, evaluator, result and the system or SOP version. That record answers the questions that come up after an error: was this person trained on this task, on this version, and by whom? It also tells you, before a release, exactly who needs retraining.
A checklist for your training plan
Use this list to test a draft plan before you book any sessions. Each item should have an owner and a date.
- The role list is complete, and each role has a task list taken from the requirements and SOPs.
- A grid of shifts by functional areas exists, with a named super user and a backup in every cell.
- Each super user has a written role description, an agreed hours budget by phase and a named backfill.
- HR has confirmed how training hours are paid, including overtime for staff trained outside their shift.
- The training environment has your items, locations, devices, label stock and one user ID per trainee.
- Scenario scripts exist for every role, and each includes at least one exception.
- Sessions are scheduled on every shift, including nights, weekends and part-time crews.
- Reference cards are translated where needed and match the screens trainees will see.
- Every role has a written practical check, and accounts activate only after it is passed.
- Floor support is scheduled for every shift after go-live, with an issue log and stand-down criteria.
- A new-hire path and retraining triggers are written down for after the project.
- Your safety lead has reviewed whether layout or equipment changes trigger forklift refresher training.
If your plan has gaps in the shift grid or the practical checks, start there, because those gaps show up first, on the first night shift. To see how training fits into a full engagement, read how we work, and if you want help building the plan for your own sites, tell us about your rollout.
