Warehouse Labor / Productivity
How Do You Measure Warehouse Crew Productivity?
Units per crew hour, compared only against the same kind of work. The arithmetic is one division — the discipline is in what you divide by and what you compare.
October 2, 2026 · 5 min read
Divide the quantity handled on a job by the crew hours it took, and compare the result only against jobs of the same kind. That is units per crew hour, and it is the one productivity number in warehouse labor that survives being questioned.
The arithmetic is trivial. Everything that goes wrong goes wrong in the two phrases: crew hours and the same kind.
Units per crew hour, compared like for like. Everything else is a footnote to that.
The calculation
Crew hours is the sum of each person's time on the job, from their own clock-in to their own clock-out. Four people for three hours is twelve crew hours, not three. Here is one floor-loaded container worked by four people, one of whom left half an hour early.
Illustrative example with simulated data. The figures show how the calculation works, not a measured customer result — put your own numbers in their place.
LD-3118 · Floor-loaded container devan
- Cases recorded
- 2,400
- Three crew at 3h 15m each
- 9h 45m
- One crew member at 2h 45m
- 2h 45m
- Total crew hours
- 12h 30m
- Cases per crew hour
- 192
Why elapsed time lies
The tempting shortcut is to divide by how long the job ran. Put three jobs of the same work type, for the same customer at the same site, side by side and the shortcut ranks them backwards:
| Job | Per elapsed hour | Per crew hour |
|---|---|---|
| LD-3104 · 4 crew, 2,160 cases | 720 | 180 |
| LD-3111 · 6 crew, 1,890 cases | 840 | 140 |
| LD-3118 · 4 crew, 2,400 cases | 738 | 192 |
LD-3111 finished fastest because six people were put on it. Per crew hour it was the least productive of the three. Elapsed time rewards adding people; crew hours rewards working well.
Nothing in the 140 says why. It says where to look. The job's own record — its notes, its crew changes, its photos — is where the reason will be: a delay at the door, extra hands added halfway through, freight that was harder than usual. A productivity number that cannot be traced back to the job it came from can only be argued about.
Compare like with like
- Same work type. Palletized unloads and floor-loaded devans are different jobs. Averaging them produces a number that describes neither.
- Same unit. Cases per hour and pallets per hour cannot be added together, and weight-based work needs its own line.
- Same customer's freight, where you can. A single-SKU container and a mixed-SKU one of the same case count are not the same day's work.
- Enough jobs. One slow load is an event. A slow month for one work type at one site is a pattern.
The same rule governs cost. Blended across work types, a productivity figure hides the job that is quietly slow in exactly the way a blended cost per unit hides the job that loses money.
What load data can't tell you
It cannot tell you who on the crew was fastest. When four people work a container together, the 2,400 cases belong to the crew. Splitting production pay equally or by time worked is a pay rule; it is not a measurement of who handled what, and ranking individuals off it is ranking them off a formula.
What the record does show per person is real and useful: how many loads each crew member worked and their total hours. FOREMAN's Crew Report gives both, one row per crew member.
Where the numbers come from in FOREMAN
Every load carries the quantities recorded on it — cases, sorts, weight, pallets, pieces — and every crew member's own clock-in and clock-out. Those are the two halves of the division, and they are captured on the dock, not reconstructed afterwards. Tying crew time to the job is covered in knowing where your labor hours are going.
The Load Report lists completed loads with Cases, Weight and Labor Hours side by side. Filter it to one customer, one location and one work type, and you have the like-for-like set; export it to CSV — where sorts, pallet and piece counts can be added as columns — and the division is one more column.
FOREMAN does not compute a productivity score for you, on purpose. Which unit, which work types and which period count is a judgment about your operation, and it should stay yours.
Measure the crew to find the job worth looking at. Then look at the job.
Common questions
What is the best measure of warehouse crew productivity?
Units handled per crew hour — cases, pallets, pieces or weight divided by the total time every crew member spent on the job. It is only meaningful when compared against the same kind of work: the same work type, unit of measure and, ideally, the same customer's freight.
Should productivity use crew hours or the job's elapsed time?
Crew hours. Elapsed time ignores how many people worked, so a job that finished quickly because six people were put on it looks better than one that four people did more efficiently. Crew hours is the sum of each person's clock-in to clock-out on that job.
Can you measure an individual worker's productivity on a shared load?
Not from the load record. When a crew works a container together, the recorded quantity belongs to the crew, not to any one person. Splitting production pay between them is a pay rule, not a measurement of who handled what.
Does FOREMAN calculate a productivity score?
No. It records the quantity on every load and every crew member's clock times, and its Load Report puts cases, weight and labor hours side by side for completed loads, filterable by customer, location and work type and exportable to CSV. The division is yours, which keeps the definition yours too.
Put quantity and crew time on the same record
FOREMAN records what was handled and who handled it, for how long, on the job itself — so productivity is a report you read rather than a reconciliation you build.