Set the planning baseline.
Create the horizon and product-customer lines with baseline quantity, proposed quantity, and explicit planner assumptions.
Consensus demand plan
Balance demand and supply without erasing the argument.
Turn a versioned forecast, commercial signals, capacity response, and cross-functional review into one approved quantity with its rationale intact.
Five movements into one plan.
The process makes disagreement useful by recording each source of evidence before the decision is published.
Add independent demand evidence.
Quantify customer expansion, schedule changes, promotions, and other signals with confidence and date.
Model the supply response.
Compare proposed quantity with available capacity, feasibility, and incremental cost at product level.
Bring functions to the same case.
Demand, sales, supply, and executive participants review the exact forecast version and supply scenario together.
Record consensus and rationale.
Approve the quantity and whether the decision accepts forecast, shapes demand, or expands supply.
The decision keeps its sources.
What matters is not only the number, but why the organization chose it and which trade-offs were accepted.
| Evidence | Question answered | Recorded context |
|---|---|---|
| Forecast version | What was the controlled starting point? | Horizon, line quantities, planner assumptions |
| Demand signal | What changed outside the baseline? | Type, impact, confidence, product, customer |
| Supply scenario | What can operations support? | Availability, feasibility, incremental cost |
| Consensus decision | What will the organization operate? | Quantity, decision type, approver, rationale |