Executive summary: Sales and operations planning is the monthly process that reconciles what the business intends to sell with what it can actually produce, over a horizon long enough to do something about the gap. Most S&OP processes fail not because the mechanics are wrong but because no decision ever gets made in them: the meeting reviews a forecast, notes a shortfall, and adjourns. This guide covers the monthly cycle, forecast accuracy versus bias, capacity reconciliation, and how to run a meeting that actually resolves conflicts.
- What is sales and operations planning?
- Why do most S&OP processes fail?
- Where does S&OP sit against scheduling and execution?
- What are the steps of the monthly cycle?
- How do you measure forecast accuracy properly?
- Why does bias matter more than accuracy?
- How do you reconcile demand against real capacity?
- Can you shape demand instead of chasing it?
- How do you set inventory targets in S&OP?
- How do you run the executive meeting?
- How do you resolve sales and operations conflict?
- What changes in high-mix, low-volume businesses?
- What metrics track S&OP maturity?
- What are the most common S&OP mistakes?
- S&OP: operator FAQ
- About the Stagnation Assassin
What is sales and operations planning?
Sales and operations planning is a monthly cycle that reconciles the demand plan with available supply capacity over a rolling horizon of roughly three to eighteen months, and resolves the gap through explicit decisions. It sits above scheduling and below strategy, and its purpose is making imbalances visible early enough to act on them.
The defining characteristic is the horizon. Execution deals with today and this week, where your options are limited to expediting and overtime. S&OP deals with the window where you can still add a shift, qualify a supplier, shift a product between plants, shape demand, or decline business. That window is where the useful decisions live, and most companies do not have a process that operates in it.
I have led operations at Berkshire Hathaway, Illinois Tool Works, Whirlpool, and JBT Marel, and the distinction I would draw is between companies that run S&OP as a decision forum and companies that run it as a reporting cycle. The mechanics look nearly identical from outside. The difference is whether anything is ever decided that would not have happened anyway.
The test is simple and uncomfortable. Look at the last six months of S&OP meetings and count the decisions that changed what the company did. If the answer is zero, you have a monthly review of numbers, and the considerable effort going into it is producing a report rather than a plan.
Why do most S&OP processes fail?
Because the meeting has no authority to resolve the gap. Demand exceeds supply, everyone acknowledges it, and the meeting ends without anyone deciding which orders will not be filled or what capacity will be added. An S&OP process that cannot make a binding decision is a status review with a planning label.
Four failure patterns account for most of it.
No decision rights in the room. The meeting is attended by planners and analysts who can describe the imbalance and cannot resolve it. Resolution requires someone who can commit capital, decline revenue, or change priorities, and if that person is not present the gap simply carries into next month.
One number nobody believes. The forecast is a negotiated artifact rather than an estimate. Sales submits a number shaped by quota pressure, operations applies a private discount, and both parties plan against different figures while nominally agreeing. Everything downstream inherits this fiction.
Capacity stated rather than measured. The supply side of the reconciliation uses theoretical capacity from a routing system rather than demonstrated output. The plan balances on paper and fails in execution, which teaches the organization that the plan is not real.
The horizon is too short to act. Many processes described as S&OP are actually reviewing the next four to six weeks, where no meaningful option exists. By the time an imbalance is visible, the only remaining levers are overtime and disappointing customers.
Where does S&OP sit against scheduling and execution?
S&OP operates monthly over three to eighteen months and balances aggregate demand against aggregate capacity. Master scheduling operates weekly over four to twelve weeks and commits specific orders to specific periods. Execution operates daily and sequences work at the constraint. Confusing these layers is the most common structural error.
Each layer answers a different question and requires a different level of detail. S&OP asks whether we can serve the demand we expect, at the product family level, with capacity we could still change. Master scheduling asks which orders go in which week given the capacity we now have. Execution asks what runs next on the machine that governs our output.
The practical consequence is that S&OP should not be attempting to sequence orders and execution should not be attempting to resolve capacity shortfalls. When a plant tries to solve a structural capacity gap through daily expediting, it is answering an S&OP question at the execution layer, where the only available tools are overtime and disappointment.
One documented failure illustrates the layer confusion neatly. A plant printed its schedule every Monday while customer orders changed continuously through the week. By Thursday roughly 40 percent of the schedule was obsolete while the floor was still running Monday’s plan. That is not an S&OP problem and no amount of better forecasting fixes it. It is a master scheduling cadence mismatched to demand volatility, and the fix belongs at that layer.
What are the steps of the monthly cycle?
Five steps run in sequence: gather and cleanse demand data, produce an unconstrained demand plan, test it against real supply capacity, resolve the gaps at a pre-meeting, then take the remaining conflicts to an executive meeting with decision authority. Each step must complete before the next begins or the cycle collapses into a single crowded meeting.
Step 1: data gathering
Assemble actual demand history, current orders, pipeline, and known events such as promotions, launches, and customer changes. Cleanse for anomalies. A forecast built on unadjusted history that includes a one-time bulk order will project that order forward indefinitely.
Step 2: unconstrained demand plan
Produce what the business genuinely expects to sell, independent of whether you can supply it. Constraining the demand plan at this stage is a common and damaging error, because it hides the size of the gap and removes the information the whole process exists to produce.
Step 3: supply review
Test the demand plan against demonstrated capacity, not theoretical capacity. Identify where the plan exceeds what the limiting resources can produce, by period and by product family. This is where the real content of S&OP lives.
Step 4: reconciliation pre-meeting
Planners and functional leaders resolve everything resolvable and prepare the remainder as explicit choices with options and consequences. The purpose is to ensure the executive meeting handles only genuine decisions, not analysis.
Step 5: executive meeting
Decide the unresolved items. Approve the plan. Commit to capacity changes, demand shaping actions, or explicit choices about which demand will not be served. The output is a decision record, not minutes.
The discipline that makes this work is the pre-meeting. Executive meetings that receive raw analysis spend their time understanding the situation and run out of time before deciding. Executive meetings that receive two or three framed choices with quantified consequences decide in twenty minutes and adjourn.
How do you measure forecast accuracy properly?
Measure at the level you plan at, not at the level you sell at, and measure at the lag that matters for your decisions. Item-level accuracy is always poor and largely irrelevant to capacity planning, because aggregation cancels error. Family-level accuracy at a three-month lag is what determines whether your capacity plan works.
Two technical points carry most of the value here.
Aggregation improves accuracy, mathematically. Individual item errors are partly independent, so they offset when summed. A portfolio forecast is always more accurate than the average of its item forecasts. This means item-level accuracy is a poor measure of forecasting quality and a poor basis for judging the demand team, while also meaning you should plan capacity at the aggregate level where your forecast is actually good.
Lag determines relevance. A forecast for next month made last week is more accurate than one made six months ago, and far less useful, because six months ago you could have done something about it. Measure accuracy at the lag corresponding to your decision lead times: if adding capacity takes four months, four-month-lag accuracy is what matters.
On method, mean absolute percentage error is the common measure and it has a known weakness: it behaves badly on low-volume and intermittent items, where a small absolute error produces an enormous percentage. For portfolios with a long tail, weight the error by volume or value so the measure reflects business impact rather than being dominated by items nobody plans capacity around.
Why does bias matter more than accuracy?
Because bias is systematic and therefore correctable at no cost, while random error requires buffer inventory or capacity to absorb. A forecast that is consistently 15 percent high can be corrected by adjusting it down 15 percent. A forecast that is randomly wrong by 15 percent in either direction cannot be corrected at all, only buffered against.
This distinction is routinely missed, and missing it wastes a great deal of effort. Teams pursue accuracy improvement broadly when the fastest available gain is usually removing a systematic bias that everyone has quietly been compensating for privately.
Bias almost always has an organizational cause rather than a statistical one. Sales forecasts high because forecasts function as commitments and ambition is rewarded. Or sales forecasts low because the forecast becomes the target and sandbagging is safer. Operations privately discounts whatever it receives, which means the official number and the planning number differ, and nobody says so.
A forecast that is consistently 15 percent high costs nothing to fix: adjust it down 15 percent. A forecast that is randomly wrong by 15 percent in either direction cannot be corrected at all, only buffered with inventory or capacity. Measure bias separately from accuracy, because one is free to remove and the other has to be paid for.
The practical move is to measure and publish bias by forecasting owner, separately from accuracy. Not punitively. Bias is nearly always a rational response to an incentive structure, and making it visible surfaces the incentive rather than the individual. Once visible, it is usually removed within two cycles, which is a substantial planning improvement for almost no effort.
How do you reconcile demand against real capacity?
Convert the demand plan into load on your limiting resources using demonstrated rates, then compare period by period. Aggregate capacity is nearly meaningless, because a plan can balance overall while being impossible in specific months and on specific constrained resources. Reconcile where the limits actually bind.
Three requirements make this work.
Use demonstrated rates, not routing standards. Routing standards are frequently optimistic by wide margins, and a capacity plan built on them balances on paper while failing in practice. Use what the resource has actually produced, measured, including its real availability.
Reconcile against the limiting resources specifically. Every operation has a small number of resources that govern output. Testing the plan against total plant hours tells you almost nothing. Testing it against the specific constrained resources tells you whether the plan is achievable.
Reconcile period by period. A plan that balances across a year can be badly infeasible in individual months. Seasonality, launches, and customer patterns all concentrate load, and annual averages conceal exactly the problem S&OP exists to find.
When the reconciliation shows a gap, the options are limited and should be stated explicitly: add capacity, shift the work elsewhere, move the demand in time, or decline it. Every S&OP cycle that identifies a gap and picks none of those four has deferred the decision to the execution layer, where it will be resolved by whoever shouts loudest.
Can you shape demand instead of chasing it?
Yes, and it is the most underused lever in S&OP. Demand timing is frequently more negotiable than anyone assumes. Delivery windows, order patterns, promotional timing, and lead time commitments can often be adjusted to smooth load, and doing so can release throughput without any capital investment at all.
This deserves emphasis because most S&OP practice treats demand as given and supply as the only variable. That framing is a habit rather than a fact.
The clearest example from my own work involved a refrigeration division losing 175 million dollars annually. The consensus was that we needed more equipment, more people, and more space. The actual constraint turned out not to be any machine. It was customer delivery commitments that forced specific lines to run at specific times regardless of efficiency, which created artificial limits across the whole system. By renegotiating delivery windows with key customers and smoothing demand across true capacity, we unlocked throughput that had been invisible to management, and cut annual losses by more than half without adding a single machine or a dollar of capital.
A refrigeration division losing $175M annually was convinced it needed more equipment. The real constraint was customer delivery commitments forcing lines to run at specific times regardless of efficiency. Renegotiating delivery windows and smoothing demand halved the annual losses without a single new machine or a dollar of capital.
Practical demand shaping levers worth testing before accepting a capacity gap: negotiating delivery windows with major accounts, differential lead times by product family, pricing or terms incentives to shift order timing, promotional calendar alignment with capacity, and minimum order quantities that reduce transaction load. Each is cheaper than capacity and faster than capital.
How do you set inventory targets in S&OP?
Set targets by product family based on demand variability, supply lead time, and required service level, then hold S&OP accountable for the aggregate rather than for individual items. Inventory in this process is a planning buffer against uncertainty, and its correct size is a decision about how much uncertainty you are absorbing.
The framing that helps is treating inventory as the price of uncertainty. Higher demand variability, longer supply lead times, or higher required service levels each raise the buffer needed. Reducing any of those three reduces the inventory requirement structurally, which is a far better outcome than pressuring the number directly.
That gives you a clear hierarchy of action when inventory is too high. First, reduce demand variability, through demand shaping and better forecasting at the family level. Second, reduce supply lead time and its variability, which is usually a supplier and changeover question. Third, and only third, accept a lower service level, which is a genuine commercial trade and should be decided commercially rather than by a working capital target imposed from finance.
The common failure is inverting this. A working capital target arrives, inventory is cut without addressing variability or lead time, service deteriorates, expediting increases, and total cost rises while the balance sheet improves temporarily. S&OP is the right forum to make this trade visible, because it is the only forum that sees demand, supply, and service simultaneously.
How do you run the executive meeting?
Present two or three framed decisions with quantified consequences, not a data review. Attendance requires people who can commit capital, decline revenue, and change priorities. The output is a decision record with owners and dates. A meeting that ends with actions to investigate has failed.
A workable agenda structure, kept deliberately short:
- Performance against last cycle’s plan. Five minutes. What did we commit to, what happened, and what did we learn about our planning accuracy. Not a discussion, a statement.
- The demand plan and what changed. Ten minutes, focused on material changes and their causes rather than a walkthrough of every family.
- The gaps. The heart of the meeting. Where does the plan exceed capacity, by how much, in which periods, at which resources.
- The decisions. Two or three framed choices, each with options, consequences, and a recommendation. This is where the time should go.
- Commitments. What was decided, who owns it, by when.
The single most effective discipline is that no item reaches this meeting without a recommendation attached. Requiring the pre-meeting to produce a recommended course for every gap transforms the executive discussion from analysis into decision, and it forces the planning team to think through consequences rather than presenting a problem and waiting.
On authority, the meeting needs someone who can say no to revenue. If nobody present can decline demand, then the only available answer to every gap is to promise it and fail later, which is how S&OP processes lose credibility with the operations organization that has to absorb the consequences.
How do you resolve sales and operations conflict?
Make the trade explicit and quantified rather than arguing about who is being unreasonable. Sales wants responsiveness and operations wants stability, and both positions are rational. The resolution is deciding what responsiveness is worth and pricing or planning for it, rather than treating the tension as a relationship problem.
The conflict is structural and permanent, which is why it recurs regardless of the individuals involved. Sales is measured on revenue and customer satisfaction, which rewards flexibility and short lead times. Operations is measured on cost and efficiency, which rewards stability and long runs. Both are doing their jobs correctly and their optima genuinely differ.
Three mechanisms convert this from a recurring argument into a managed trade.
Quantify the cost of responsiveness. What does a rush order actually cost in disrupted schedule, lost constraint capacity, and expediting? Once that number exists, the discussion becomes commercial: is this customer worth that cost, and should they be paying for it. Frequently the answer is that some should and are not.
Segment service levels deliberately. Not every customer needs the same lead time, and offering uniform responsiveness to all means overserving many and underpricing the rest. Differentiated lead times by segment resolve a large share of the conflict structurally.
Align the metrics. As long as sales is compensated on revenue and operations on cost, the incentive conflict persists underneath any process fix. Shared accountability for contribution rather than for volume and cost separately is the durable resolution, and it is harder than any process change.
What changes in high-mix, low-volume businesses?
Plan at a higher level of aggregation and in units of constrained capacity rather than in product units. Item-level forecasting is genuinely impossible below a certain volume, so plan capacity in hours at the limiting resources and let the master schedule handle the mix. Forecasting harder is not the answer.
This is the situation where standard S&OP guidance breaks down, and where a great deal of wasted effort accumulates. A business running hundreds of configurations against variable order patterns cannot forecast items accurately, and organizations respond by investing heavily in forecasting sophistication that cannot overcome the underlying statistics.
What works instead:
Plan in capacity units. Forecast total hours required at each constrained resource rather than units of each product. Total load is far more forecastable than its composition, and total load is what capacity planning actually needs.
Use families that share constrained resources. Group products by how they consume your limiting capacity rather than by commercial or engineering similarity. This makes the aggregation meaningful for planning purposes.
Plan flexibility rather than volume. In high-mix environments the useful capacity question is not how much but how quickly you can switch. Changeover reduction at the constraint and cross-trained labour do more for service than a more accurate forecast ever will.
Push mix decisions to the master schedule. Let S&OP resolve aggregate feasibility and leave the specific sequencing to the layer with current information. Attempting mix decisions at a monthly cadence in a business with weekly volatility guarantees the plan is wrong before it is published.
What metrics track S&OP maturity?
Track forecast bias separately from accuracy, plan attainment at the family level, the number of decisions actually made per cycle, and how far ahead capacity gaps are identified. That last one is the clearest maturity signal, because the whole purpose of the process is seeing problems while options still exist.
Forecast bias and accuracy, reported separately
Bias by owner, accuracy at the planning level and at the decision-relevant lag. Reporting them together conceals the correctable component inside the uncorrectable one.
Plan attainment
Did the business produce what the plan committed to, at the family level. Consistently low attainment means the plan is not being built against real capacity, which invalidates everything downstream.
Decisions per cycle
Count them. A process producing zero decisions per month is a reporting cycle. This metric is unusual and it is the most honest measure of whether the process is working.
Gap identification lead time
How far in advance are capacity shortfalls being identified. A mature process sees them with enough runway to add capacity or shape demand. An immature one discovers them at the master schedule, where the only options left are expediting and disappointing customers.
What are the most common S&OP mistakes?
Five recur: constraining the demand plan before the supply review, planning against theoretical capacity, holding the meeting without decision authority present, measuring forecast accuracy at item level, and treating demand as fixed when timing is frequently negotiable.
Mistake 1: constraining demand too early
Planners reduce the demand plan to what they believe is producible before the supply review happens. The gap disappears from view, and with it the entire reason for the process. Produce the unconstrained plan first, always, even when everyone knows it cannot be met.
Mistake 2: theoretical capacity
Reconciling against routing standards and nameplate rates produces a plan that balances on paper and fails on the floor. Use demonstrated output at the limiting resources, including real availability, or the reconciliation is arithmetic rather than planning.
Mistake 3: no authority in the room
A meeting of people who can describe problems but not resolve them will describe the same problem every month. Someone present must be able to commit capital and decline revenue, or the process cannot close a gap.
Mistake 4: item-level accuracy obsession
Chasing item-level forecast accuracy in a business with a long tail consumes enormous effort against a statistical limit. Measure and plan at the level where aggregation makes the forecast reliable, and handle mix at the scheduling layer.
Mistake 5: treating demand as fixed
Accepting the demand plan as immovable and treating supply as the only variable eliminates the cheapest lever available. Delivery windows, order timing, and lead time commitments are frequently negotiable, and shaping them costs far less than capacity.
The mistake I made personally was allowing the process to become a presentation. I built a genuinely rigorous cycle with clean data, honest capacity, and well-framed gaps, and then let the executive meeting fill with material designed to demonstrate that the planning team had done thorough work. It had. But an hour spent proving the analysis is an hour not spent deciding, and the meeting produced fewer decisions as the analysis got better. Cut the presentation to the gaps and the choices, and accept that the quality of the underlying work will be invisible.
S&OP: operator FAQ
What is S&OP?
A monthly cycle that reconciles the demand plan against available supply capacity over a rolling three to eighteen month horizon and resolves the gap through explicit decisions. It sits above master scheduling and below strategy, operating in the window where capacity, sourcing, and demand timing can still be changed.
Why do most S&OP processes fail?
Because the meeting lacks authority to resolve the gap. Demand exceeds supply, everyone agrees, and nobody decides which orders will go unfilled or what capacity will be added. Other common causes are constraining the demand plan too early, planning against theoretical rather than demonstrated capacity, and a horizon too short to act on.
What is the difference between forecast bias and forecast accuracy?
Bias is systematic error in one direction and costs nothing to correct, since a consistently high forecast can simply be adjusted down. Accuracy error is random and cannot be corrected, only buffered with inventory or capacity. Measure them separately, because one is free to fix and the other must be paid for.
How should high-mix businesses run S&OP?
Plan in hours of constrained capacity rather than in product units, group families by how they consume limiting resources, and push mix decisions down to the master schedule. Item-level forecasting below a certain volume is statistically impossible, so planning flexibility and changeover capability matters more than forecasting harder.
About the Stagnation Assassin
Todd Hagopian is a Fortune 500 transformation executive who has generated $3B+ in shareholder value across Berkshire Hathaway, Illinois Tool Works, Whirlpool, and JBT Marel, where he serves as VP of Global Product Strategy. Known as The Stagnation Assassin, he is the author of two published books: The Unfair Advantage: Weaponizing the Hypomanic Toolbox and Stagnation Assassin: The Anti-Consultant Manifesto. His blog is published in 15+ languages and read by operators worldwide. Bring him to your stage via the speaking page or connect with him on LinkedIn.
Next step: count your decisions
Look at your last six S&OP meetings and count the decisions that changed what the company actually did. If the answer is zero, you have a monthly reporting cycle wearing a planning label. Book a 20 minute review and I will help you turn it into a forum that resolves gaps while you still have options. Start the review here.