What this worksheet resolves
In the procurement savings working file, compare baseline purchasing cost with negotiated cost after implementation expense and demand change. A dated result gives the procurement manager a baseline that can be compared with a later operating period.
Once the procurement savings cutoff is fixed, if the source cutoff changes, create a new case and explain the timing difference before comparing the results.
Compare like populations
If procurement savings is annualized or based on averages, state that plainly because seasonality and concentration can alter interpretation.
When procurement savings enters a decision, a dated Supplier Concentration Calculator can test supplier concentration without rewriting the present baseline.
In the procurement savings working file, outliers should remain unless an approved rule excludes them; show the output both ways when the decision is material.
Use the example as a control total
A reproducible example is supplied as Baseline comparable quantity = 42000 units; Baseline price per unit = $12.80; Current quantity = 45000 units; Current price per unit = $11.95; Implementation and transition cost = $18,000. The operating file should preserve full source precision even if the page rounds the display.
A comparison involving procurement savings requires that use the reset control to recover the test case after exploring alternatives, then begin a clean documented run.
Reperform the calculation independently
In a reconciled procurement savings result, to reconstruct the output, preserve source precision and apply: Net procurement savings subtract current purchase cost and implementation expense from the comparable baseline cost. Round only the final presentation value.
Preserve the evidence status of Baseline comparable quantity and Implementation and transition cost; actual, committed, forecast, and target values are not interchangeable.
Against the recorded procurement savings population, where make or buy affects the discussion, reconcile shared fields with the Make or Buy Calculator.
Assemble a defensible field set
Supplier performance file: Document Baseline comparable quantity again when a separate scenario changes Baseline comparable quantity. Mark baseline comparable quantity as estimated, not actual. A later Baseline comparable quantity correction should state its Baseline price per unit effect.
Supplier performance file: Reconcile Baseline price per unit before the displayed relationship uses Baseline price per unit. Identify the report column supplying baseline price per unit. Never mix partial-period Baseline price per unit with complete-period Current quantity.
Supplier performance file: Keep raw Current quantity precision in the saved Current quantity case. Save the current quantity source timestamp with the result. Keep Current quantity treatment stable while stress-testing Current price per unit.
Supplier performance file: Identify Current price per unit as observed or approved; mark Current price per unit committed or estimated when applicable. Keep a manual-adjustment note beside current price per unit. Check whether Current price per unit and Implementation and transition cost describe compatible populations.
Supplier performance file: Give every Implementation and transition cost adjustment an owner; note the Implementation and transition cost reason. Confirm the manager responsible for implementation and transition cost agrees with its definition. If Implementation and transition cost changes definition, rerun before interpreting Baseline comparable quantity.
Quality checks for the saved case
Keep excluded effects visible when comparing alternatives. procurement savings leaves supplier enforceability unresolved beside Baseline comparable quantity. Evidence beyond Baseline comparable quantity is required. Conclusions about Implementation and transition cost remain separate from procurement savings. The model relates Baseline comparable quantity to Implementation and transition cost; future events affecting procurement savings are not predicted.
The review trail for procurement savings supports this point: document conversion rates, allocations, and partial-period treatment in the same folder as the saved result.
Use the result in a management discussion
Circulate procurement savings with the source cutoff and boundary statement visible; a number alone invites overinterpretation.
Against the recorded procurement savings population, reconcile common inputs before comparing linked outputs, especially where period length or population can differ.
Answers for the working file
How should reversals appear?
A repeatable procurement savings process assumes that follow the source policy and explain any reversal that materially changes the procurement savings result.
Can fields come from different systems?
The source case for procurement savings shows that yes, after their cutoffs, units, identifiers, and population are reconciled.
What if the operating population changes?
Save a new procurement savings case and distinguish population movement from metric movement.