These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- SCM with Demand Forecasting
- Features
- S&OP review
S&OP review
Carry the demand position through meetings, decisions and a published cycle version.
OverviewS&OP meeting schedule×
SCM with Demand Forecasting · S&OP review
New
S&OP meeting schedule
SOP meetings
Demand review2
SPC-74132SPM-94610
12 Oct
SPC-90508SPM-40390
04 Oct
Add
Supply review2
SPC-10130SPM-32697
26 Oct
SPC-66501SPM-95168
16 Oct
Add
Reconcile1
SPC-33225SPM-66360
11 Oct
Add
Executive SOP1
SPC-27753SPM-57260
26 Oct
Add
What you can do
Keep the meeting tied to the plan
An S&OP cycle carries its month, fiscal year, kickoff date, owner and status. Its meetings identify the demand, supply, reconciliation and executive stages. Each meeting has a facilitator, scheduled date and status. Attendee records identify each person’s role at the meeting and attendance outcome, including a delegate when relevant. The Demand Planning Manager can use those records to make the review cadence explicit.
Decisions have a type, description, decision maker, date, status and optional quantity or revenue impact. They also connect to affected planning entities. A decision to accept an adjustment can therefore be read next to the period forecast and the meeting where it was made. Forecast versions preserve the statistical, marketing-adjusted, sales-consensus and final-approved positions as dated snapshots.
How the work is organized
- Set the cycle. Demand Planning Manager reviews the month and meeting schedule.
- Record discussion. Facilitator gathers attendees and puts exceptions, contributions and forecast versions on the agenda.
- Capture the decision. Executive and the planning manager review the final position; decisions retain their affected entities and impact.
What to agree during setup
Agree who facilitates each meeting, who is required to attend and when a delegate may speak for an absent member. Define the cutoff for forecast version snapshots. A version taken before commercial input should remain distinct from one taken after consensus; changing a label later would make the sequence hard to audit. Decide who records the decision and when its status can move from recorded to applied.
The cycle status should represent the current review stage. A published cycle should have a final snapshot and the relevant decision trail available to the people who will use it. The demand planning function should agree how new information discovered after publication enters the next cycle or a documented correction, rather than being folded into a prior version without explanation.
Check the handoff on an actual case
A demand review identifies a large variance for a product in the Central wholesale channel. The facilitator puts the exception and affected forecast version on the meeting agenda. Operations Lead brings a capacity concern to supply review. At reconciliation, Demand Planning Manager reviews the chosen adjustment and its affected planning entity. Executive reviews the final version and recorded impact in the executive meeting before the cycle is published.
After publication, compare the final forecast with the next actual quantity and error metrics. This closes the learning loop: a meeting decision becomes a traceable plan, and the next cycle has evidence for a better judgment.
What your team sees
- S&OP meeting schedule — Upcoming demand, supply, reconciliation and executive sessions with facilitators.
- Consensus plan board — The position moving through review stages toward publication.
- Open exceptions — Issues that need a decision before the plan is settled.
Follow the work through
Follow consensus to publication and exception to decision.
What it keeps track of
Data model- SOP cycles
- The monthly S&OP cycle header.
- SOP meetings
- The four meetings that drive a cycle.
- SOP meeting attendees
- Per-meeting attendee list.
- SOP decisions
- Recorded decisions per meeting.
- SOP decision entities
- Per-decision affected Planning Entity list.
- Forecast versions
- Snapshot of all Forecasts rows at each S&OP cycle stage.
- Forecast error metrics
- Per-cycle, per-Planning Entity error metrics rolled up across model runs.
- Consensus plans
- The collaborative plan that walks the S&OP cycle.
Who uses it
Permissions- Demand Planning Manager
- Owns the cycle.
- Operations Lead
- Contributes to supply review.
- Executive
- Reviews the final position.
- Sales Rep
- And Marketing Manager explain their inputs where relevant.
Set up SCM with Demand Forecasting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.