Consensus and supply handoff

Bring one dated baseline and an adjustment register. Northstar baseline forty-five plus six genuinely incremental new-store units gives fifty-one. An existing order of ten already inside baseline adds zero. A sales target of sixty-five is a goal, not evidence that customers will request sixty-five. Keep the gap visible without forcing the forecast upward. Each adjustment needs an owner, evidence date, affected product and period, incremental quantity, and expiry condition. An adjustment should not persist forever because its origin was forgotten. Preserve baseline and final versions so future review can evaluate whether judgment helped on the same frozen target and lead time. An optional event adds twelve only if it occurs, making event-on demand sixty-three from a base of fifty-one. A downside loss of eight gives forty-three. These cases help prepare responses; they are not calibrated intervals and carry no probability unless evidence supports one. Do not call their average expected demand without probabilities. Avoid stacking adjustments that represent the same cause. More stores and more display exposure may overlap. Explain which assumptions move together and which are separate choices. Timing matters as much as a total: shifting an event between weeks can preserve monthly volume while moving the operational peak beyond available capacity. Consensus is a working assumption with accountable owners, not certainty. Record disagreements and evidence that would resolve them. Sales can verify the store opening, the analyst can preserve the baseline, and a review chair can approve the published version. End with actions, dates, and triggers rather than a vague request to revisit the forecast. When outcomes arrive, compare baseline and adjusted errors and record whether the planned event happened. A reasonable forecast can still be wrong; a lucky forecast can rest on weak evidence. Learning requires keeping the original reasoning and distinguishing changed execution from a poor estimate of the demand effect. State product, location, unit, bucket dates, issue time, horizon, and scenario. Include baseline, approved adjustments, consumed orders, separate old backlog, and quality limitations. The demand owner describes expected customer wants; the supply owner evaluates feasible fulfillment. These are linked decisions with different responsibilities, not interchangeable versions of one number. Fresh demand fifty-one plus backlog six gives fifty-seven obligations. Stock eighteen and on-time receipts ten leave twenty-nine to obtain. Quarantined or reserved stock is not usable. A receipt after the need date cannot offset an earlier requirement without accepting delay. Document timing and eligibility rather than relying on a period-total shortcut. Supplier availability twenty-four, manufacturing thirty-two, and shipping thirty mean twenty-four additional usable units if they are sequential limits on the same flow and period. Do not add capacities. Against requirement twenty-nine, the gap is five. Do not reduce the demand forecast to hide that gap; retain a separate feasible fulfillment view. Recovery may involve earlier supply, approved substitution, increased capacity, or customer rescheduling. Each option needs an owner, lead time, and effect on the gap. Deferring five units does not erase demand. Keep original due dates and revised promises so later service and backlog reports reflect what actually happened. Fresh low divided by base divided by high demand forty-three, fifty-one, sixty-three gives net requirements twenty-one, twenty-nine, forty-one with the same backlog, stock, and receipt. Against twenty-four usable additional units, low has three headroom and base divided by high gaps five, seventeen. These cases let the supply team tie actions to observable demand triggers. A separate production check for twenty-nine good units at expected yield ninety seven percent suggests thirty starts, with expected output twenty nine point one, never a guarantee. Thirty starts at twelve minutes plus one thirty-minute changeover use three hundred ninety of four hundred eighty usable minutes, leaving ninety. This hypothetical calculation does not resolve the supplier constraint; assumptions must stay distinct. At the end of the lab, give the next team a plan they can use. Name the week, the unit, the owner, and the cut off. Show what is new, what is old, what is in stock, and what is due to arrive. Show the gap before you choose a fix. Then name a low case and a high case with a clear cause for each. A plan is not a vow that the world will stay still. It is a way to see what must change when new facts arrive, and who must act on those facts.

1. Begin with a common baseline

   Original flat diagram with separate labeled input and output boxes, using Northstar bottle icons.

   • Begin with a common baseline
   • Base 51, downside 43, event-on 63; target 65 remains a goal.
   • Check units and timing
2. Tie scenarios to conditions

   Original calculation card with aligned quantities and an arrow showing one change.

   • Tie scenarios to conditions
   • Base 51, downside 43, event-on 63; target 65 remains a goal.
   • Check units and timing
3. End with a decision record

   Original comparison chart with clearly labeled cases and a small assumption note.

   • End with a decision record
   • Base 51, downside 43, event-on 63; target 65 remains a goal.
   • Keep assumptions visible
4. Publish a demand contract

   Original flat diagram with separate labeled input and output boxes, using Northstar bottle icons.

   • Publish a demand contract
   • Publish a versioned forecast, net requirement, constraint gap, and recovery choices.
   • Check units and timing
5. Expose the limiting capability

   Original calculation card with aligned quantities and an arrow showing one change.

   • Expose the limiting capability
   • Publish a versioned forecast, net requirement, constraint gap, and recovery choices.
   • Check units and timing
6. Handoff scenarios and checks

   Original comparison chart with clearly labeled cases and a small assumption note.

   • Handoff scenarios and checks
   • Publish a versioned forecast, net requirement, constraint gap, and recovery choices.
   • Keep assumptions visible