The 5 reports a warehouse manager should open every Monday morning

I used to open twelve reports every Monday morning. Inventory accuracy, throughput, labour hours, dock-door utilisation, cycle-count compliance, returns ageing, carrier mix, vehicle fill, top-10 movers, bottom-10 movers, exception ageing, near-miss safety log. By the time I'd skimmed all twelve it was 10:30 and the only thing I'd actually decided was what coffee to get next. The week had started without me.

Now I open five. Same warehouse. Same volumes. Better decisions, made faster, and the back half of Monday is mine for the things that actually move the floor.

Here's what those five are, in the order I open them, and what I do with each.

Why the Monday morning ritual matters

Monday morning is the only thirty minutes in your week where last week is finished and this week hasn't started kicking the door in yet. By 09:30 a customer is going to ring about a missing pallet. By 10:00 there will be a driver issue. By 11:00 someone has called in sick and you're three pickers down on a peak day. From that point on, you are reactive until Friday.

The Monday ritual is the only chance you get to be the other thing — proactive. To look at last week as a finished artefact, not as a thing in motion, and ask: what did that week tell me that I should do differently this week? If you skip it, every week looks the same. The same zones miss accuracy. The same client breaches SLA. The same exceptions get filed and never closed. You're running a warehouse that has no memory longer than five days.

The discipline isn't about the reports. It's about giving last week a vote in this week's plan. Most warehouse managers I've worked with don't have a vote-counting mechanism — they just have a "things felt rough on Wednesday" feeling, and that feeling decides nothing. Five reports, thirty minutes, no laptop open for email. That's the mechanism.

A second thing: the ritual signals to your team that you care about last week, not just next week. Once people know the Monday review is real, the people running cycle counts, the people closing exceptions, the people chasing PODs — they start to treat last week's work as something that gets read. That alone is worth the half-hour.

Report 1: Last week's inventory accuracy

What it shows: weekly variance percentage broken down three ways — by zone, by client (if you're a 3PL), and by velocity tier (A/B/C). Not a single warehouse-wide number. Three slices.

What I do with it: I pick the worst-performing zone and book a daily count on it for this week. Not "schedule extra counts when we get time" — actually carved into the count plan that goes out at 06:30 each day. The point isn't to fix the variance through counting; the point is that counting daily for a week tells me whether the variance is a counting problem, a putaway problem, or a pick-error problem. Each of those has a different fix, and I can't tell which without the daily pattern.

The metric I'm driving down: weekly net variance percentage at the zone level. Not warehouse-wide. The warehouse number is almost always fine — that's how averaging works. The zone number is where the work is.

Common pitfall: averaging across zones masks the bad ones. If you've got 99.2% accuracy across the warehouse, that can mean one zone is at 94% and three are at 100%, and you'd never know. The 94% zone is the one bleeding margin and credibility. Always look at the breakdown, never the average. Same goes for clients: a 3PL with eight customers and a 0.4% variance is hiding the one customer whose variance is 2%, and that customer is going to leave in six months.

I've written before about why most warehouses plateau at 97% accuracy and what it takes to get past it. The Monday review is where you decide whether you're going to do that work this week or not.

Report 2: Pick-pack throughput vs forecast

What it shows: actual orders shipped last week against the forecast or commitment for the week. Daily breakdown, with a running cumulative line. If you operate to client-specific volume commitments, slice it by client too.

What I do with it: if I'm behind cumulative forecast, I make a labour decision before lunch — either bring in agency on Tuesday and Wednesday, or have a conversation with the commercial team about pushing back on this week's commitments. If I'm ahead, I redeploy. Spare pickers go to slotting, to count support, to clearing the exception backlog. Nothing burns morale faster than visibly under-utilised people on a busy floor.

The metric I'm driving up: percentage of weeks finishing within ±10% of forecast. That's the real number. If you're consistently outside that band, the problem isn't the warehouse — it's the forecast, or the commercial team's commitments. Either way it's a conversation, and you can't have it without the weekly trend.

Common pitfall: looking at the daily number and missing the trend. A Tuesday that's 200 orders behind isn't a problem on its own — you might catch up by Thursday. A Tuesday that's 200 behind for the fourth week running is the problem, and you'd never spot it if you only look at the day. Daily ops boards are for the floor leads. Monday's report is for the trend.

Report 3: Inbound-to-putaway latency

What it shows: for every inbound consignment that landed last week, the time from goods-received scan to "inventory available to pick". Reported as both median and p95. Ideally broken down by supplier or client so you can see the patterns.

What I do with it: latency is the most diagnostic single number in a warehouse. If it's high, the question is which kind of high. High median with a low spread tells me staffing is wrong on inbound — there's a steady backlog. High p95 with a normal median tells me something specific is going wrong with a subset of consignments — usually ASN quality (the paperwork doesn't match the truck) or slotting (we don't have a home for it, so it sits on the floor). High both tells me I have a structural problem and need to look at the dock plan.

The metric I'm driving down: p95 latency, not median. Median tells you about the good days. P95 tells you about the days a customer is waiting for stock that's physically on your site but not yet bookable on the system. Those are the days that cost you orders.

Common pitfall: only watching the median. The long tail is what kills you, and the long tail is exactly what a median hides. A median of 4 hours sounds fine. A p95 of 36 hours on the same data means one in twenty consignments takes a day and a half to become available, and that one in twenty is almost certainly the consignment your biggest customer is waiting on. Always look at both numbers, and run them by supplier — the bad ASNs cluster.

Report 4: SLA breaches by client / customer

What it shows: every breach last week — missed order cut-off, missed delivery window, late POD upload, missed pick-up slot. Named, with cause coded against each one. Grouped by client.

What I do with it: this is the credibility report. Every breach is a conversation I am going to have, or should have, with that client this week. Some I will get ahead of by calling them on Monday before they call me on Tuesday. Others I will roll into the monthly review with context. The point is that I know about every one of them before anyone outside the building does. Surprised customers are the ones who leave.

The metric I'm driving down: total weekly breaches, with a secondary cut on "breaches caused by us" versus "breaches caused by the client or the carrier". The first number is the one I own. The second is the one I need ammunition on for the commercial conversation.

Common pitfall: not naming the cause. A breach with no cause attached is useless — it tells you there's a problem but not where to push. Was it the carrier missing the pick-up window? Our pickers not closing the wave in time? The client sending the order after cut-off and expecting heroics? Each of those leads somewhere different. If your WMS doesn't make it easy to tag a cause against a breach, that's the first config job. Without it you'll spend every Monday looking at the same list and never moving it. (Loaditude's transport reporting does this on the TMS side; the WMS side should do the same.)

Report 5: Open exceptions older than 7 days

What it shows: every exception still open seven days after it was raised — damaged inventory not yet resolved, supplier claims pending, putaway discrepancies untouched, returns sitting in the quarantine bay with no decision against them.

What I do with it: assign every single one a name and a date by end of Monday. Not "look into it" — a named owner and a target close date. Exceptions don't get more solvable with age, they get less. The supplier you can claim against in week one will not take the call in week six. The customer who would have accepted a credit note for a damaged pallet in week one wants a full refund and a written apology in week eight. Stale exceptions become disputes, and disputes become churn.

The metric I'm driving down: count of open exceptions older than seven days. Nothing fancier. If that number is going up week on week, your warehouse has a hidden liability building, and you will find out about it eventually — usually at month-end when finance asks why the stock adjustment account is moving.

Common pitfall: filing exceptions but never closing them. Most WMS implementations are good at opening exceptions and bad at closing them — the workflow stops once the ticket is raised, and the ticket lives forever. The fix is procedural, not technical: every exception gets a target close date when it's opened, and the Monday report shows the ones that have blown past it. If you can't see the agers, you can't act on them.

The reports that don't deserve Monday morning

Three reports I deliberately don't look at on a Monday, even though most dashboards push them to the top:

Per-picker leaderboards. They look useful and they create the wrong culture. The top picker is almost always the one cherry-picking the easy waves, and a leaderboard rewards that. If you want pick-rate visibility, look at the team average and the bottom-quartile pattern — the bottom quartile is where coaching pays back. The top of the leaderboard takes care of itself, usually by gaming the metric.

Real-time location utilisation. It's a vanity dashboard. A heatmap showing 78% of bays occupied at 09:14 on a Monday tells you nothing you can act on — what's the alternative, dispose of a third of your racking? Utilisation is a quarterly conversation about footprint and capex, not a weekly review item. Looking at it on Monday makes you feel like you're managing, and that's the trap.

Daily activity heatmaps. Granular hour-by-hour pick-and-pack heatmaps for last week. Interesting if you're tuning shift patterns, useless on a weekly cadence. By the time you've absorbed the pattern, the week is over and you can't change Tuesday's labour because Tuesday already happened. These belong in a quarterly shift-plan review, not on Monday.

The test for a Monday report is simple: can I act on this, this week? If the answer is "no, but it's nice to know", it doesn't go in the ritual.

The ritual itself

Thirty minutes. Email closed. Phone face-down. One coffee. In this order:

1. Accuracy — pick the worst zone, book the daily counts.
2. Throughput — decide on labour for the week, redeploy if you're ahead.
3. Latency — flag any p95 spikes to inbound and ASN owners.
4. SLA — list the client calls you need to make today.
5. Exceptions — assign owners and target dates to anything over seven days old.

By 09:30 the week has a shape. You've made five decisions about last week that change what this week looks like. The reactive part of the day can begin, and it begins from a position of having decided things, not just having had things happen to you.

The reports themselves matter less than the discipline of the ritual. If your WMS surfaces these five cleanly — broken down the way I've described, not collapsed into warehouse-wide averages — Monday morning is thirty minutes. If it doesn't, the ritual takes ninety minutes of pivot tables and you'll skip it within a fortnight.

That's the bit operators underestimate when they choose a WMS. It isn't the feature list. It's whether the system makes the weekly review possible, or whether it buries it under thirty equally-weighted dashboards. The platforms that respect operator time put the right five at the top, and the other twenty-five one click away for when you need them.

If you're rebuilding your reporting around the way you actually run the floor — by zone, by client, by velocity tier, with p95s and ageing buckets that match how decisions actually get made — that's most of what Loaditude's warehouse reporting is designed for. Whether you build it there or somewhere else, build it. Then sit down with it for thirty minutes every Monday morning, and watch how different the week feels by Friday.