Right — monthly S&OP, usual shape. Amanda takes us through demand, Luca through supply, and we leave with one number that everybody plans to. Sales, factory, finance — one number. And a request up front: I don't want to spend the hour on this month's firefighting. The decisions that matter today are week five onwards.
Helen names the purpose in the first breath: the meeting exists because every function quietly keeps its own forecast — sales has an ambitious one, finance a cautious one, the factory plans to a third. S&OP is where those collapse into ONE number everyone commits to. Her second move is horizon discipline: "the decisions that matter today are week five onwards" — a common S&OP failure is spending the whole hour on this month's fires, where nothing can be changed anyway.
No promises on the firefighting. But agreed — the real conversation today is later in the quarter.
It is. And I'll say it now so nobody relaxes: the real conversation is a problem. A solvable one — but only because we're catching it five weeks out.
"I'll say it now so nobody relaxes" — Amanda signals early that a problem is coming, before walking through the routine numbers. This is a kindness to the room: people listen differently when they know a punchline is on its way. And "solvable... because we're catching it five weeks out" frames it as early warning, not crisis — which changes the whole temperature of what follows.
Baseline first, quickly — the core range is steady, forecast accuracy last month was fine, nothing scary there. The story is the launch. The oat bar starts selling in week five, and on the current forecast it needs nine days of production time on Line Two between now and quarter end.
Amanda spends one breath confirming the baseline is healthy before raising the alarm. It's a small move with a big effect: it tells the room she's looked at everything, not just the scary part — so when she says "the story is the launch," the number that follows is trusted. Also notice her unit: days of line time, not tonnes or cases. She's translated demand into the factory's currency before the meeting.
And Line Two has five free days. So before any promotion, before any upside surprise — we are four days of production short. That's not a rounding error. That's close to half the launch volume with nowhere to be made.
Nine days needed, five available, four short, "close to half the launch volume." No "we have a serious capacity issue" — the gap is stated in units both sides understand and can act on. This is the same discipline Series 1's sponsor demanded ("a number, not an adjective"), and it's what separates a planning conversation from a panic.
I'll stand behind those five days — but understand what they assume. Nothing breaks, and no allergen clean-downs beyond the ones already in the plan. It's an honest number. It is not a comfortable one.
Luca confirms Amanda's figure but names its assumptions out loud — no breakdowns, no extra clean-downs. This is calibrated honesty: he's telling the room how much weight the number can carry before it bends. A supply planner who says "it's fine" and one who says "it's honest but not comfortable" are giving you two very different plans.
Four days short on our own launch. Wonderful. Go on — I assume it gets worse before it gets better.
It gets worse. Harlow's have moved our feature slot. The gondola end we'd agreed for November is now week six — their category reset shuffled the whole calendar, and it's take it or leave it until spring. I found out Friday afternoon.
A hard FMCG reality lands here: the promotional calendar belongs to the retailer, not the supplier. Harlow's reshuffles, and Edmund gets a take-it-or-leave-it with a deadline. "I found out Friday afternoon" — he's also quietly establishing that this wasn't sat on. When you bring disruptive news, the timeline of when you knew is part of your credibility.
Week six is inside the frozen period, Edmund. We freeze eight weeks out precisely so the plan I give the factory on Monday is still true on Friday.
The "frozen period" is the window (here, eight weeks) where the production plan is locked — because materials are ordered, shifts are rostered, and changes ripple through everything. Luca isn't being rigid for its own sake; he explains the rule's purpose in one sentence. When you defend a process, defend it by its function, not its existence.
I know exactly where week six sits, and I took the slot anyway. That feature is our launch, on an end, in our biggest customer, in launch month. Turning it down to protect a planning rule would have been the wrong call — but I own the mess it makes in this room.
Edmund doesn't apologise and doesn't pretend he didn't know. He states the judgement call — the commercial value outweighed the planning rule — and then the crucial sentence: "I own the mess it makes in this room." Breaking a rule with a reason and taking the consequences is a legitimate professional move; breaking it and hoping nobody notices is not. The difference is whether you bring it to the meeting yourself.
How deep is the mechanic? Because if it's the usual feature price, my model says roughly four hundred cases a week of uplift for three weeks — landing exactly when the launch is already eating the line.
Amanda's first response to disruptive news is a sizing question, not a complaint. "How deep is the mechanic?" — meaning how big is the discount, because depth drives uplift. She already has a model number ready (four hundred cases a week) and just needs Edmund to confirm the input. Reacting to news with a question that sizes it is one of the most professional moves in any meeting.
That's about right — maybe a touch higher. It's the launch, Harlow's will merchandise it properly. And before anyone asks: yes, some of that uplift cannibalises the core bars, so the net extra load on the line is about two days, not three.
A feature on the oat bar doesn't just add demand — it steals some from the company's other bars sitting on the same shelf. Edmund nets this off himself before anyone challenges him: gross uplift, minus cannibalisation, equals two extra days of line load. Doing the honest maths on your own promotion, out loud, is how a commercial person keeps the room's trust.
So the four-day gap is a six-day gap. I want that number on the table before we argue about anything else — because it defines what kind of problem this is.
And Edmund — one more thing before we solve it, because it decides what we're solving. The launch sell-in you gave me and the number you presented at the commercial review are eight percent apart. Which one am I planning to?
This is the most important exchange in the pack. Sales functions often run two forecasts: an ambitious one for management, and a safer one for planning — or the reverse, inflating the planning number to guarantee stock. Either way, supply signals blur and someone plans to the wrong future. Amanda names the split precisely (eight percent) and asks the only question that matters: "which one am I planning to?"
The review number is the ambition — what happens if Harlow's really gets behind it. Yours is what I'd bet on. And saying that out loud, I can hear the problem.
I can't buy raw materials to an ambition. If I plan your safe number and you sell your brave one, the launch goes out of stock in launch month — and a gap on a feature is worse than no feature at all. Harlow's will remember the empty shelf, not the ambition.
A sentence worth memorising. Amanda doesn't attack the ambition — she names what a forecast is FOR: it drives real purchases, real shifts, real pallets. And she spells out the failure mode in the customer's memory: "Harlow's will remember the empty shelf, not the ambition." An out-of-stock during your own promotion is the most expensive kind, because the retailer paid for the space.
One number, Edmund. Pick it in this room, and everything downstream plans to it. That is what this meeting is for.
Helen doesn't debate the two numbers or ask for a compromise between them — she enforces the process: pick one, here, now, and it becomes everyone's plan. This is the S&OP contract, and it only works if the most senior person in the room refuses to let two numbers leave the meeting alive.
Plan the commercial number. All of it. If that means something else in the portfolio goes short, I'd rather short a slow seller than the launch — but I want a say in which one.
Edmund picks the ambitious number — and immediately accepts the consequence: if the line can't make everything, something else gives. "I'd rather short a slow seller than the launch" is him doing the trade honestly. And "I want a say in which one" is fair — the person who owns the customer should be in the room when the shortage is chosen. He's about to get his wish.
So — the shape of it. We need six days of Line Two that we do not have. Three ways to find them, and I've fully costed none of them yet, so these are shapes, not quotes. One: weekend shifts — money, plus the crew's goodwill, which is not infinite. Two: a co-packer — twelve weeks of lead time and a technical transfer, so that's a spring answer to an autumn question. Three: we make room from inside the plan.
Luca presents three routes with their real character: cost, lead time, disruption. "Shapes, not quotes" flags his own precision level — he won't pretend to numbers he hasn't run. And "a spring answer to an autumn question" kills the co-packer option in six words: right idea, wrong timeline. Naming WHY an option dies is as useful as naming the options.
Define "from inside".
The two smallest bar SKUs — the 200 gram and the caramel multipack. Together they're under four percent of quarter volume. But they are eleven changeovers, and the caramel takes a full allergen clean-down every single run. Pause both for eight weeks and I hand you six and a half days.
Four percent of volume, but eleven changeovers and repeated allergen clean-downs — small SKUs cost far more line time than their sales suggest, because every switch stops the line for cleaning and setup. This cost is invisible in a sales report and enormous on a factory floor. It's why "just keep everything running" is never the neutral option it appears to be.
And there it is. Luca, you're asking me to deliberately gap two products Harlow's ranges. Shelf gaps are how listings die — and we walk into annual terms in three months. I am not handing Richard's team a grievance to open the negotiation with.
Edmund pushes back hard, but look at what the push-back is made of: a listing risk (retailers delist products that gap) and a negotiation risk (a grievance three months before annual terms). These are arguments the room can weigh — not "my products are off limits." When you resist a proposal, give the room your actual reasons; territorial resistance gets overruled, reasoned resistance gets negotiated with.
Then let the data pick. Sell-out on the 200 gram has been declining for over a year — and the last time it gapped, shoppers traded up to the 400 gram. Ours, not a competitor's. The multipack is different — that one's sticky. If we pause anything, pause the 200 and protect the multipack.
The fight was heading for opinion versus opinion; Amanda replaces it with evidence: a year of decline, and proof from a previous gap that shoppers substitute within the company's own range. "Ours, not a competitor's" answers Edmund's real fear before he voices it. The proposal also shrinks — pause one SKU, not two — which makes it much easier to accept.
The 200 alone gives me four days. Add one weekend shift and we're covered — with a thin buffer, but covered.
Edmund?
If Harlow's hears it from me before a single shelf gaps — framed as us protecting availability on their feature, not as a quiet delist — then I can live with the 200. I'm not thrilled. But I'd rather explain a pause than an empty gondola end in week six.
Edmund moves — but attaches the condition that protects his side of the business: the customer hears it from him, first, with the right framing. "Protecting availability on their feature" is the same fact as "we're pausing a SKU," told in the customer's interest. Controlling how a story reaches your customer isn't spin; it's the difference between a partner managing supply and a supplier quietly failing.
Then that's our base case, and it goes to the exec meeting as numbers, not vibes. Amanda — one page: cost of the weekend shift against the margin on the feature, plus the stockout risk if we did nothing. Luca — re-run the schedule and confirm those four days are real once the pause is in. Edmund — Harlow's hears it this week, from you, with the availability framing. Thursday, all of it.
Helen converts the argument into an exec-ready package: one scenario, three owners, one deadline. Each task is specific enough to check on Thursday. Notice she doesn't decide the trade-off herself — the weekend-shift cost versus feature margin goes UP as a costed case. Knowing which decisions belong in this room and which go to the exec meeting is part of chairing well.
One flag for that page. If the launch sells through faster than plan, the next constraint is week nine, not week six. I'd rather we say that out loud now than rediscover it in a crisis meeting.
The room has solved week six; Luca is already looking at week nine. Planning one constraint ahead — and saying it in the meeting where it can be written down — is what separates supply planning from supply firefighting. "Success is also a scenario" is a surprisingly easy thing for a room to forget.
Put it on the page — good problem, but on the page. And one more thing, for all of us. We caught this five weeks out, which is the only reason we're choosing instead of firefighting. Next launch, capacity sits in this room from day one. I don't want to be trading SKUs on the back foot again.
Helen closes the loop at the system level: this went well only because it was caught early, so the fix is structural — capacity joins launch planning from day one. Good chairs do this move at the end of a hard meeting: extract the rule that stops the same meeting happening again.
For what it's worth — the reason I could see the 200's decline store by store was the sell-out feed from the new reporting platform. A year ago that argument would have been two opinions and whoever spoke loudest.
A quiet observation with a big point: the argument in scene six was settled by data that simply didn't exist in the company a year ago. Better information doesn't just improve decisions — it changes the social dynamics of the room, replacing "whoever speaks loudest" with "whoever brings the sell-out numbers."
Then take the win. Right — we have one number, one base case, and three owners. Same time next month — and with any luck, a duller agenda.
I'll take dull. Dull means the feature worked.
A closing worth noticing: in planning meetings, boring is success. A dull S&OP means the forecast held, the line coped, and the promotion did what the model said. Teams that celebrate quiet months build the credibility that gets them heard in the loud ones.