Peak season labour planning for Indian warehouses
Festive volume is forecast in units and staffed in guesses. The gap between the two is why orders ship late in the week that matters most.
- Convert the order forecast into pick, pack and dispatch hours before deciding headcount. Units alone tell you nothing.
- New hires are not productive on day one. Hire early enough that the learning curve finishes before the peak starts.
- Peak attrition is real and predictable. Plan for it rather than being surprised in week two.
- The bottleneck is usually one station, not the whole floor. Staff the constraint, not the average.
Every festive plan has a volume forecast. Far fewer have a labour plan derived from it. Headcount tends to be decided by reference to last year, adjusted by a feeling about growth, and finalised late.
Then the peak arrives, dispatch slips, and the conclusion is that the forecast was wrong. Usually the forecast was fine and the conversion from orders to hours never happened.
Start with rates, not headcount
The bridge between a volume forecast and a staffing plan is your own throughput rates, and most operations have never measured them properly.
Three numbers, measured on your floor rather than borrowed from a benchmark: units picked per person hour, orders packed per person hour, and how many orders can be staged and handed to a courier within the pickup window.
Measure them by category if your mix varies, because a bulky item and a small sachet are not the same work. Then divide forecast volume by the rate to get required hours, and divide those by usable hours per shift after breaks, briefings and handover. What comes out is a defensible headcount.
The value is not just the number. It is that when somebody challenges it, you have arithmetic rather than an assertion.
Hire before you need them, not when
The most common and most expensive scheduling error is hiring temporary staff to start when volume starts.
A new picker does not work at full rate on their first shift. They are learning your layout, your scanning process, your packaging standards and where things are. That learning happens on the floor and takes real days.
If they begin on the first heavy day, you have your least productive workforce during your highest volume period, and every error they make becomes a return or a complaint precisely when your service metrics are most visible.
Bring them in before the ramp, let them learn on ordinary volume, and enter the peak with a team already at rate. The extra days of wages are cheap compared with a week of late dispatch.
Plan for attrition rather than hoping
During festive season every warehouse in the area is hiring. Temporary staff have options, and some will take them.
Baseline attrition rises, and the planning failure is assuming it will not. If your plan needs a certain number on the floor and you hired exactly that number, you are short by the second week.
Look at what actually happened last season if you have the record. Build the expected loss into the hiring target explicitly, and keep a live relationship with your labour supplier through the period rather than treating recruitment as finished once the plan is filled.
Staff the constraint, not the average
Adding people evenly across the floor feels fair and usually wastes most of them, because throughput is set by the slowest station.
Walk the floor during a busy hour and find where work is queuing. It is often packing when items are awkward to box, quality check in a high return category, or dispatch when the courier window is tight and everything has to be staged at once.
Adding pickers to a floor constrained by packing produces a larger pile in front of the packing bench and no additional shipments. Find the constraint, staff it properly, and re-check after, because relieving one bottleneck simply moves it somewhere else.
Overtime has a limit worth respecting
Overtime is the flexible tool for genuine spikes and a poor substitute for headcount over a sustained peak.
Output per hour falls as hours extend, and error rates rise. During festive weeks a picking error is not just a rework, it is a wrong item shipped to a customer who is already anxious about a gift arriving, which becomes a return, a complaint and often a rating.
Use overtime for the unexpected day. Use people for the expected fortnight.
Write the plan down before the season
Required hours by week, headcount derived from them, start dates that account for training, expected attrition and the buffer that covers it, and the constraint station identified in advance.
That document takes an afternoon and it is the difference between a peak that is busy and one that is chaotic. The teams that struggle are rarely the ones that forecast wrong. They are the ones that never converted the forecast into hours.