The S&OP review meeting is where forecast translates into decisions. Production schedules get locked. Safety stock targets get confirmed. Commercial gets aligned on what's available to sell. The meeting is only as good as the data that comes into it — and in most mid-market CPG companies, that data is the weekly POS report and the ERP-generated statistical forecast.
If you've started incorporating external signals into your demand model, the meeting prep is where that work either gets acted on or gets ignored. A signal that shows up in your forecast tool but doesn't make it into the S&OP slide deck is a signal that won't drive a production decision. This article is about the practical mechanics of getting external signal data into the review in a format that's usable — not buried in a data appendix that nobody reads.
What Your S&OP Audience Needs to See
The people in your S&OP meeting have different orientations. Supply chain cares about production feasibility and inventory position. Commercial cares about what they can promise customers. Finance cares about inventory carrying cost and working capital. The VP chairing the meeting cares about which decisions need to be made today and what the risk exposure is on the forward forecast.
What they share: none of them want a deep-dive on your signal methodology. They want to know: is our current plan right, or does it need to change? If it needs to change, which SKUs, by how much, and why? What signal are we seeing that justifies a departure from the ERP baseline?
External signal data needs to be presented in that frame — not as a data science output, but as a forecast deviation recommendation with a clear driver and a specific action request. "Weather forecast indicates elevated cold beverage demand in weeks 4–6 for SKU [X], [Y], [Z]. Recommend increasing production run by 12% on the scheduled October 8 run." That's the format that gets a decision.
The Signal Deviation Summary: Structure
The practical vehicle for external signal data in a S&OP prep is what we call a Signal Deviation Summary — a single-page (or single slide) structured view of signal-driven departures from the ERP baseline. Here's the structure that works:
Section 1: Active Signal Flags (Top of Slide)
A simple table: which signals are currently active (above threshold) and which direction they're pushing demand. Three columns: Signal Type | Direction | Horizon. Limit to signals that are materially above their baseline — don't list every signal in the model, just the ones that are deviating enough to affect planning decisions.
| Signal Type | Status | Direction | Planning Horizon |
|---|---|---|---|
| Weather — Temp Anomaly | ACTIVE | +8°F above seasonal avg, Weeks 3–5 | 3–5 weeks out |
| Social Trend — Flavor X | ACTIVE | Velocity 2.4× baseline, accelerating | 4–7 weeks out |
| Macro — CPI-Food Index | MONITOR | +2.1% vs wages, approaching threshold | 6–10 weeks out |
Section 2: SKU-Level Deviation Table
For each active signal, list the affected SKUs with three numbers: ERP baseline, signal-adjusted forecast, and the delta. This is the decision table — it's specific enough for a production planner to act on.
| SKU | Signal Driver | ERP Baseline wks 3–5, cases/wk |
Adjusted Forecast wks 3–5, cases/wk |
Delta | Action |
|---|---|---|---|---|---|
| Sparkling Water 12oz (Cucumber Mint) | Social + Weather | 1,250 | 2,800–3,400 | +124–172% | Expedite 10/8 run |
| Sparkling Water 24oz (Lemon) | Weather only | 2,100 | 2,600–2,900 | +24–38% | Add to 10/15 run |
| Hot Tea Variety Pack | Weather (temp decline) | 3,400 | 3,200–3,500 | ±3–3% | No change |
Section 3: Recommended Actions and Decision Points
A bulleted list of the specific decisions the meeting needs to make. Each bullet should be a yes/no or choose-between-options decision, not an open-ended discussion point. The demand planner's job in meeting prep is to translate signal data into decision-ready framing.
- Decision 1: Approve 35% production volume increase on SKU [Cucumber Mint] for October 8 run? Current schedule: 4,200 cases. Recommended: 5,700 cases. Incremental cost: $[X]. Risk if we don't: potential stock-out in weeks 4–6 if social trend converts to retail velocity.
- Decision 2: Authorize safety stock elevation on social-trend watch-list SKUs (3 SKUs identified) through end of Q4? Estimated carrying cost increase: $[Y]/month.
- Decision 3: No action needed on remaining portfolio. ERP baseline within 10% of signal-adjusted forecast on 87% of active SKUs.
Building the Prep Into Your Weekly Rhythm
The signal deviation summary should be produced as part of routine meeting prep — not as a special analysis that happens only when someone notices a signal. Most S&OP cycles run monthly with weekly demand planning touchpoints. The rhythm that works:
- Weekly (Monday): refresh signal scores for all watch-list SKUs. Flag any that crossed alert threshold since last week. Review and update the signal flags table (Section 1).
- Weekly (Thursday): update SKU-level deviation table (Section 2) for any SKUs with active signals. Compare against current production schedule to identify conflicts or opportunities.
- Pre-S&OP (1–2 days before meeting): compile Signal Deviation Summary for the month's review. Include only SKUs where signal-adjusted forecast deviates from ERP baseline by more than 15% — below that threshold, the ERP plan is probably fine without adjustment.
The threshold matters. If every SKU shows up in the signal deviation summary because you included minor deviations, the meeting loses focus. The filter should produce a short list — ideally 3–8 SKUs per month that genuinely need a decision, not a catalog of 50 marginal adjustments that overwhelm the discussion and lead the commercial team to stop trusting the signal data.
Managing Push-Back From the Commercial Team
The first time you bring external signal data into an S&OP meeting, expect skepticism. "We've always used the ERP forecast. Why are we changing now?" is a reasonable question from a VP who has built their planning process around the existing model. The answer isn't "because AI said so" — it's a track record argument.
Build that track record starting with the first meeting. When you present a signal-adjusted forecast that departs from ERP, note it in the meeting minutes: "Signal-adjusted forecast for SKU [X] is 2,800 cases/wk for weeks 3–5; ERP baseline is 1,250." In 6 weeks, you'll know which was right. That comparison — did the signal call the actual demand, or did the ERP model? — is the only argument that matters to a commercial team. Two or three accurate signal calls and the credibility question answers itself.
We'd also note: this doesn't require your team to abandon ERP-based forecasting. The signal deviation summary sits alongside the ERP plan, not in replacement of it. Most SKUs in most months will show no material signal deviation — the ERP plan is fine and no change is needed. The signal data adds a layer on top of existing process, it doesn't replace it. That framing reduces change resistance significantly compared to presenting signal fusion as "a new forecasting system that replaces what you're currently doing."
Getting Signal Data Into the Meeting Without Manual Assembly
The practical obstacle to making this a routine: assembling signal data manually is time-consuming. If a demand planner has to pull weather forecasts from one source, social trend data from another, and macro indicators from a third — then reconcile all of that against the ERP forecast each week — the prep burden becomes unsustainable.
The signal deviation summary works as a repeatable process when the underlying signal data is pre-processed and delivered in a structured format — not when the planner is doing data wrangling every Monday morning. That's the operational case for a signal fusion platform: not the model sophistication (though that matters for accuracy), but the reduction in prep time that makes it possible to actually use external signals in your normal S&OP rhythm instead of treating them as a quarterly side project.