Write a sensitivity note a project team can act on
The useful question is which assumption changes the decision.
Start from the base case
Save the agreed inputs and label their sources before trying alternatives. Choose assumptions that are both uncertain and material, such as operating hours, maintenance frequency or replacement timing. Do not change every input at once and then attribute the result to a single cause.
Use clear scenarios
Create a low, base and high case with a short explanation of why each value was chosen. These labels are scenarios, not probabilities. Use consistent assumptions across comparable options. If a supplier provides a range, record its scope and whether it depends on maintenance conditions.
Look for a decision threshold
If an energy-price assumption changes the preferred option, identify the approximate point where the totals cross. That threshold helps the team decide what further evidence is worth collecting. Keep the calculation method and unrounded inputs available; a polished chart alone is not an audit trail.
Assign the next action
Turn each material sensitivity into an action: obtain a revised quotation, check operating logs, or seek an independent service-life estimate. Record the owner and the deadline before procurement. If the ranking is stable across the chosen scenarios, describe that result only within those ranges; do not call the option universally optimal.
References provide background. The working methods and fictional examples here are our editorial guidance, not an endorsement by the referenced organisations.
Put this into practice: open the worksheet →