Send Them Home, or Spend the Hours: The October Call That Lands in December

The shift where there isn't enough work

You did the hard part. The requisitions cleared, the job fairs ran, orientation moved to Saturdays, and by the first week of October you had the headcount you asked for. Three hundred people badged and on the floor.

And there isn't enough work for them.

Volume does not arrive on the day the staffing plan says it should. It arrives in a wave that starts somewhere in the first half of November and does not care what your peak season labor planning assumed in July. So you get a stretch — two weeks, sometimes four — where the building is fully staffed and running at sixty percent of what it will run in a month.

Everybody sees it. The supervisors see people standing around. The associates see it too, and start asking each other whether the hours are going to hold. Finance sees a labor line running against volume that hasn't shown up, which is the version that generates the phone call.

The phone call always asks the same thing. Can we send some of them home until it picks up.

What sending them home actually costs

The saving is real. It is also small, and you can calculate it in about four minutes.

The cost is larger, arrives six weeks later, and almost never enters the conversation.

Here is the mechanism. A seasonal hire is not evaluating you on culture. They took the job because it pays and because the hours were described as steady. Send them home twice in the first month and you have told them, clearly, that the hours are not steady. They are not offended. They just start looking, and in October there is somewhere else to look.

The ones who leave first are the ones with options, which is to say the better ones.

Then you replace them in late November. That means a requisition, a background check, an orientation, and a person starting at zero on the learning curve during the week you need everyone at full rate. The hours you saved in October come back as training hours in the worst week of the year, and they come back with a multiplier.

The asymmetry is the whole problem. The October saving shows up on the labor line where everyone can see it. The December cost shows up as a throughput miss that gets blamed on volume. One of those numbers has your name on it. The other one does not.

There is no second window

Every building plans to train during peak. Almost none of them do.

Not because anyone is lazy. Because of arithmetic. The person qualified to teach is, by definition, one of your better producers, and the moment volume lands you cannot afford to have them anywhere but on the line. "We'll train them as we go" is a sentence that is true in October and false by the second week of November, and nobody notices the moment it flips.

The same arithmetic runs on mistakes. A new picker putting a pallet in the wrong location today costs you one correction. The identical error in week eight does not stay one error. It becomes a short pick, a cycle count, a replenishment that doesn't fire, and somebody walking the aisle at ten at night looking for inventory the system says is there. Errors are cheap when the building is slow and they compound when it is not.

So the lull is not the gap before the work starts. It is a window, and it closes on its own schedule regardless of what you did with it.

The only question is whether you spent it.

Where the hours go

Not to busywork. People know the difference immediately, and assigning it costs more credibility than the hours are worth.

Put new people on real tasks at low volume. This is the only stretch of the season where someone can work at half rate for a week without it mattering, and the only stretch where the person beside them has time to answer a question. A picker who gets to be slow in October is at rate in November. A picker who first touches the job in November is slow in December.

Re-time what you are measuring them against. Most buildings run a labor standard that was set on people who had done the job for two years, then apply it to someone in week three and call the gap a performance problem. It is not a performance problem. It is a measurement problem, and this is when you have the slack to find out what the real curve looks like.

Then there is the backlog everybody carries into peak and nobody schedules. Slotting that drifted since spring. Putaway accuracy. Cycle counts on the locations that always seem to be wrong. Travel paths that got longer one SKU at a time. None of it is urgent in October, all of it is load-bearing in December, and these are the only hours you will have to do it in.

And the part that is not a task at all. Somebody has to learn the names. Somebody has to explain what the building does and why the box matters. Week one is physically brutal for people who have not done this work, and whether they come back for week three is decided largely by whether anyone said that out loud.

The November bill

The labor line in October makes the lull look like waste. It is not. It is the cheapest labor you will buy all season, because it is the only labor you can spend on something other than getting orders out the door.

The bill comes either way. You can pay it now, in hours you planned, on work you chose — a slow picker learning the job, a standard re-timed, a slotting pass nobody has run since April. Or you can pay it in November, in hours you did not plan, on problems that chose themselves.

The second version always costs more. It costs more because it happens at volume, because the people who could have taught are needed producing, and because by then the options have narrowed to overtime and apology.

Nobody gets a quiet October twice.