Why your warehouse overtime won't clear (and what actually fixes it).

If you've added headcount in the last six months and overtime is still running at 12–18%, your problem isn't a labour shortage. It's almost always one of three structural causes — and adding people makes none of them better.

Most operations directors I've worked with have the same instinct when overtime climbs. More volume must mean more people. The maths feels obvious — divide the extra hours by the cost-per-hour, work out how many heads it would take to cover it, hire them, and the problem goes away.

It doesn't go away. Three months later, you're staring at the same overtime number, two new starters who are still finding their feet, and a finance director who's lost patience with the labour line.

What's happening is that the original assumption — that overtime is being driven by genuine work volume — was never properly tested. And without testing it, the structural cause stayed exactly where it was. The new starters absorb capacity for the first six to eight weeks before they're properly productive. The structural inefficiency keeps running underneath them. The overtime drifts back to its previous level inside a quarter.

This post is a diagnostic. It covers the three structural causes that produce sustained, unclearing overtime in UK warehouse operations — what each one looks like, how to spot it on your floor, and what to actually do about it. None of this is theoretical. These are the patterns we see again and again in PainKiller audits, across retail distribution, e-commerce fulfilment, manufacturing, and FMCG.

First, a question worth asking: is your overtime actually a labour problem?

Before we get to the three causes, there's a quick diagnostic worth running. If you can't answer "yes" confidently to all three of these, your overtime is almost certainly not a labour-shortage problem:

• Has work volume genuinely increased by more than 10% in the last 12 months, with no operational changes to absorb it?
• Are the same individuals consistently working the overtime, week after week — and is the distribution roughly even across the team?
• If you removed overtime entirely, would you have a measurable, immediate shortfall in output that couldn't be recovered through process change alone?

If you've answered "no" to any of those, what looks like a people problem is almost certainly a process problem. The rest of this post tells you what kind.

Cause 01 · Planning lag — volume hits the floor before it's been scheduled for

Planning lag is the most invisible of the three structural causes because it presents itself as a labour problem. The team is working flat out. They're not slow, they're not idle. They're just always slightly behind, in a way that compounds across the day.

What's actually happening is that your forecast and your floor are out of sync. Volume is arriving at the operation before the operation knows it's coming. The shift starts and there are 30 extra picks in the queue that weren't in this morning's plan. Or the goods-in volume that was forecast for tomorrow has actually arrived today. Or yesterday's late orders have rolled into today's morning shift and nobody adjusted the staffing.

The cumulative effect is that every shift starts behind. The team catches up by working harder, and "harder" eventually becomes "longer," and "longer" eventually becomes "overtime." Add headcount and the same pattern repeats with more people in it.

What planning lag looks like on the floor

• The first hour of each shift is consistently spent catching up rather than starting on the day's plan
• "Late orders" or "urgent intake" feels like the norm rather than the exception
• Shift supervisors spend more time re-planning the day in the morning than they do supervising it
• Volume forecasts exist but are rarely matched against actual against forecast week-on-week
• If you ask the floor team "when did you find out about the volume change?", the answer is usually "today"

What actually fixes it

The fix is not more granular forecasting — most warehouses already over-engineer their forecasts. The fix is closing the loop between forecast and floor. Specifically: making the variance between forecast and actual visible to operations leadership within 24 hours, and creating a standing mechanism for the floor to flag volume mismatches as they happen. When the planning team finds out about the mismatch a week later, the overtime has already happened.

In practice, this is a short daily forecast-vs-actual review (10 minutes, one supervisor, one number), and a flagging mechanism that doesn't require an email chain. Most operations are surprised at how much variance has been quietly absorbed.

Cause 02 · Handover failure — every shift inherits problems from the previous one

This is the single most common cause of sustained overtime that I see across PainKiller audits. It's also the most expensive, because the loss compounds across every shift transition, every day, every week, indefinitely.

Most multi-shift warehouse operations lose 25 to 35 minutes per shift handover to undocumented informal processes — outgoing shift workers waiting to brief the incoming team, incoming workers piecing together what happened the day before, equipment that was left in inconsistent states, tasks that were left partly complete with no documentation of where they stopped.

What makes handover failure particularly insidious is that it doesn't feel like a problem. Each individual handover looks fine. The 30 minutes lost feels normal. The cost only becomes visible when you add it up across a week, or when you ask why the late shift always inherits a backlog and the morning shift always finishes their day fully and then runs into a handover problem the next morning.

What handover failure looks like on the floor

• Incoming shift workers spend the first 20–40 minutes catching up on what happened previously, before starting productive work
• There is no standard handover log, or there is one that nobody uses
• Late shifts consistently absorb backlogs created earlier in the day, even when work volume was even
• Equipment is left in inconsistent states between shifts (scanners flat, trolleys missing, returns pending)
• If you ask the late shift "what would make your shift easier?", the answer is "knowing what happened in the morning"

What actually fixes it

The fix is one of the simplest and highest-ROI interventions in warehouse operations: a standardised shift handover log, used consistently, with a structured five-minute handover meeting between outgoing and incoming shift supervisors. It's not technology. It's not training. It's a document and a process discipline. Most operations recover the 25-35 minutes per transition within two to four weeks of consistent use.

This is exactly what our Operations Toolkit includes a template for — a field-tested handover log that's been adapted across multiple operations.

Cause 03 · Flow design — your operation creates artificial bottlenecks

The third cause is the deepest and the hardest to spot from inside the operation. It's also the one that adding headcount makes worse rather than just neutral, which is why it's the most painful when discovered late.

What's happening is that your operation's process flow — the sequence and pacing of how work moves through the building — has been designed (or, more commonly, has evolved) in a way that creates artificial bottlenecks. These aren't capacity bottlenecks. The team has the capacity. The flow is just forcing them to wait, or to queue, or to backtrack, or to handle the same item multiple times when once would do.

When you add more people to an operation with bad flow design, you don't relieve the bottleneck — you create more people queueing at the bottleneck. The flow becomes more congested, not less. Overtime worsens because the bottleneck constraint stays in place and the new starters now compete with the existing team for time at the constraint.

What bad flow design looks like on the floor

• Operatives regularly waiting at a specific point in the process — typically goods-out, putaway authorisation, or QC sign-off
• The same bottleneck moving between two or three stages predictably, never disappearing
• Pickers backtracking through congested zones to complete an order
• Multiple handlings of the same item (e.g. moved into a staging area, then moved again to dispatch)
• "Hot" tasks that always need expediting and always interrupt the planned flow

What actually fixes it

Fixing flow design is the highest-impact and most demanding of the three interventions, because it requires changing how the operation is structured, not just how a single process is run. In practice, this usually means: identifying the actual constraint point (which is rarely the obvious one), reorganising the flow to either eliminate the queue at that point or pace work so that the queue never forms, and re-sequencing shift allocation so that capacity matches the actual work volume mix rather than a historical assumption.

This is the kind of work that a proper operational audit identifies — not because it's exotic, but because it requires someone standing on the floor watching the operation run, who isn't inside the operation every day. The people closest to the flow are usually too close to see what's wrong with it.

So how do you know which cause is yours?

In practice, most operations running sustained overtime have at least two of the three causes operating at once. Planning lag and handover failure together are the most common pairing — they reinforce each other, because the handover doesn't carry the planning information that would let the next shift correct course.

The diagnostic question that tells you most cheaply is this: "Where in the day does the overtime actually accumulate?"

• If it accumulates in the first two hours of each shift, your problem is most likely handover failure or planning lag
• If it accumulates in the last two hours of the late shift, your problem is most likely flow design (the constraint has fully expressed itself by then)
• If it accumulates evenly across the day, you almost certainly have all three operating together — which is the typical pattern in operations that have grown without re-designing the flow

The honest comparison: adding people vs fixing the cause

Operations directors sometimes resist this framing because adding headcount feels safer and faster than process change. It's neither. It's just more visible.

The maths is brutal once you do it. Adding three people at £24k each loaded comes to roughly £75k a year. The structural interventions described above — standardised handover, forecast-vs-actual loop, flow redesign — typically cost a fraction of that and reduce the overtime requirement directly, which usually saves more than the new headcount would have absorbed.

And the structural fixes don't depreciate. Once the handover process is in place, it keeps working. Once the flow is redesigned, the operation runs at the new pace permanently. The new starters, by contrast, will absorb capacity for six to eight weeks before they're productive, and the underlying inefficiency they were hired to compensate for is still running underneath them.

If you recognise this in your operation

If sustained, unclearing overtime is the pattern you're living with — and you've already added headcount or are considering doing so — the most important thing is to test the assumption before you act on it.

Three structured ways to do that, depending on how you want to approach it:

1. The £99 Scorecard — 25 questions across six operational health domains. 10 minutes. Instant 10-page PDF report identifying your top three risk areas. The fastest way to see whether overtime is symptomatic of something structural.
2. The Operations Toolkit (£49) — five templates including the shift handover log mentioned above. If you want to start with the handover fix yourself, this is the lowest-friction entry point.
3. The On-Site Audit (from £950) — for operations where the overtime has been running for months, internal fixes haven't worked, and you want an independent diagnostic before committing to any further headcount or capital spend.