S&OP fails on calendars before it fails on concepts.
Ask any planning team to name the five steps of sales and operations planning and they’ll recite them without hesitation. Ask to see last month’s cycle calendar, with dates held, inputs delivered on time and decisions logged, and the conversation gets quieter. The five steps are commodity knowledge. The monthly discipline of running them, week by week, with a trustworthy baseline forecast entering at week one, is where the process either earns its meeting hours or wastes them.
That second condition deserves emphasis up front: the baseline forecast is the input that makes or breaks the entire cycle. Every review downstream (demand, supply, finance, executive) adjusts, constrains or approves numbers that started life as that baseline. A biased baseline wastes the meeting, because the room spends its time re-litigating the number instead of deciding what to do about it.
This guide covers the five steps, and then the two things most guides skip: the week-by-week calendar planners actually run, and who owns what at each step.
What is S&OP?
S&OP (sales and operations planning) is a monthly cross-functional process that aligns demand forecasts, supply plans and financial plans into a single agreed operating plan, approved by executive leadership. The process typically runs on a five-step cycle: data gathering, demand review, supply review, pre-S&OP reconciliation and the executive S&OP meeting. Its output is one set of numbers the whole business commits to executing, usually over a rolling 18- to 36-month horizon.
The 5 steps of the S&OP process
- Data gathering and baseline forecasting. Actuals are collected and cleansed, forecast accuracy from the prior cycle is scored, and a statistical baseline forecast is generated for the planning horizon.
- Demand review. Sales, marketing and demand planning enrich the baseline with market intelligence: promotions, new product activity, customer commitments. Output: an unconstrained consensus demand plan.
- Supply review. Operations tests the demand plan against capacity, materials, inventory targets and lead times. Output: a constrained supply plan plus a list of gaps and options.
- Pre-S&OP reconciliation. Demand, supply and finance meet to translate gaps into scenarios with financial consequences. Decisions that can be made at this level are made; genuine trade-offs are framed for executives.
- Executive S&OP. Leadership reviews performance, decides the escalated trade-offs and approves the plan. Output: one operating plan, with decisions and owners documented.
Step 1 in detail: data gathering and the baseline
Step one is scheduled as a data week and treated as an afterthought, which is backwards. Two things get built here: the scorecard (how accurate and how biased was last cycle’s forecast, measured at the granularity that drives supply decisions) and the baseline itself. Weak scorecards let bias persist for quarters. Weak baselines force every subsequent meeting to do statistical work by argument. Organizations that shortcut this week pay for it in weeks two through four.
Steps 2 and 3 in detail: the two reviews
The demand review’s job is enrichment, adding information the model cannot know, and its discipline is measurement: every adjustment should be tracked for the value it adds or destroys against the baseline. The supply review’s job is honesty, surfacing constraints early enough to act on them. The most common failure between these two steps is a demand plan that arrives late or pre-constrained, which quietly turns the supply review into guesswork.
Steps 4 and 5 in detail: reconciliation and decision
Pre-S&OP exists to keep the executive meeting short. If executives are seeing raw gaps for the first time in step five, step four failed. A functioning executive S&OP reviews a one-page scorecard, decides two or three framed trade-offs and adjourns. Anything longer is a symptom.
The monthly S&OP calendar
The five steps map onto a four-week operating rhythm. This is the table to pin to the planning wiki: inputs, outputs and an owner for every week.
| Week | Activity | Key inputs | Outputs | Owner |
| Week 1 | Data gathering and baseline forecast | Sales actuals, shipments, inventory, open orders, prior-cycle accuracy | Cleansed dataset, forecast accuracy scorecard, statistical baseline | Demand planner |
| Week 2 | Demand review | Baseline forecast, promotion calendar, NPI plans, sales intelligence | Unconstrained consensus demand plan, assumption log | Demand planning lead, with sales and marketing |
| Week 3 | Supply review | Consensus demand plan, capacity model, materials and lead time status, inventory targets | Constrained supply plan, gap and option list | Supply planning lead |
| Week 4 | Pre-S&OP and executive S&OP | Demand and supply plans, financial overlay, scenario analysis | Approved operating plan, decision log, actions with owners | S&OP process owner; executive sponsor chairs the final meeting |
Two rules keep the calendar alive. Dates are fixed for the year and attendance is delegated rather than postponed; a slipped demand review compresses everything downstream. And each week consumes the prior week’s output as its input, so a late or low-quality handoff is visible immediately rather than discovered in the executive meeting.
Who owns what in S&OP
Ownership ambiguity is the second-largest S&OP failure mode after calendar drift. A simple RACI settles it.
| Step | Demand planner | Supply planner | Finance | Sales | Executive sponsor |
| Data gathering and baseline | R/A | C | C | I | I |
| Demand review | R/A | I | C | R | I |
| Supply review | C | R/A | C | I | I |
| Pre-S&OP | R | R | R/A | C | I |
| Executive S&OP | C | C | C | C | R/A |
R = responsible, A = accountable, C = consulted, I = informed.
The pattern worth noting: accountability moves through the cycle. The demand planner owns the front, supply the middle, finance the reconciliation, the executive sponsor the decision. Processes where one function claims accountability end to end tend to produce plans the other functions treat as someone else’s numbers.
Demand planning process: where forecasting fits
Inside week two sits the demand planning process, the sequence that turns a statistical baseline into a consensus demand plan: score last cycle’s accuracy, generate the baseline, enrich with market intelligence, document assumptions, and publish. The ordering matters. Enrichment before scoring means nobody knows whether last month’s judgment calls helped; a solid grounding in demand forecasting methods is what separates enrichment from decoration.
The demand review process that follows is a decision meeting, and it works when three conditions hold: the baseline arrives on time and pre-validated, every override is logged with an owner and a rationale, and forecast value added is reported so the room can see whether its own adjustments have been improving the plan. Where those conditions hold, the meeting shortens and the plan sharpens. Where they don’t, the meeting becomes a negotiation about whose number wins.
S&OP vs IBP: what changed
Integrated business planning (IBP) is best understood as S&OP grown up rather than a different process. Three things distinguish a genuine IBP implementation: financial integration (plans expressed in dollars and margin, with a live bridge to the annual operating plan), horizon (24 to 36 months, long enough to move capacity and portfolio decisions rather than just inventory), and scenario discipline (decisions made by comparing modeled alternatives, with product and portfolio review folded into the cycle).
In practice, many organizations that renamed S&OP to IBP changed the calendar invites and little else. The label matters less than whether finance owns a seat, whether the horizon is long enough to change supply decisions, and whether scenarios are modeled or merely discussed.
How mature is your S&OP?
A four-level self-assessment. Locate your organization honestly.
- Level 1: reactive spreadsheets. Forecasting lives in disconnected workbooks, the monthly cycle exists on paper but slips routinely, and accuracy is either unmeasured or measured inconsistently. Meetings re-create the numbers each month.
- Level 2: standardized process. The five steps run on a fixed calendar with defined owners. Accuracy and bias are scored monthly. The baseline is statistical but requires heavy manual maintenance, and planners spend most of their week producing numbers rather than reviewing them.
- Level 3: integrated IBP. Financial integration is real, horizons extend past 24 months and scenario analysis informs decisions. The constraint shifts to throughput: the planning team’s capacity to generate, maintain and explain forecasts across the full portfolio.
- Level 4: AI-assisted. Machine-generated baseline forecasts arrive scored and explainable, planners direct their attention to exceptions and enrichment, and forecast value added governs which human touches survive. The cycle compresses because week one stops being a bottleneck.
The jump from level 3 to level 4 is a change in where human hours go. Kenvue reduced forecast error (MAPE) by 37% by combining its planning organization with AI-generated baselines: the machine produces the starting number, the planners contribute the judgment. The reallocation can be quantified. One global food and consumer packaged goods manufacturer, planning thousands of SKUs across many customers and distribution centers, found that roughly 75% of its forecast volume was suitable for touchless planning, leaving planner attention concentrated on the quarter of the portfolio where human context genuinely changes the number. In week one specifically, automation compounds; one large, publicly traded automotive aftermarket manufacturer running more than 100,000 SKUs cut manual data cleansing work by roughly 70%, converting most of a data-preparation week into review time. A deeper treatment of what this looks like architecturally is in our piece on AI-powered supply chain operations.
Wherever you land on the maturity scale, the pressure point is the same: the quality of the baseline entering week one determines the quality of the decision leaving week four. If your cycle is disciplined but the baseline still consumes the calendar, evaluating demand forecasting software is the logical next step. Request a demo to see how DemandForecast.ai fits into an existing S&OP cadence.