Preventive work often competes for money with projects that promise an obvious increase in output. A new line can be described in units per hour. Better maintenance, stronger monitoring or more capable technical support may chiefly prevent interruptions that have not yet occurred. If the investment case counts only additional production, prevention starts the comparison at a disadvantage.
That does not mean every preventive proposal should be approved. Managers need a comparison that shows what the organisation spends and experiences under its current arrangements, what the proposed change would alter, and which consequences remain uncertain. A credible case makes those distinctions visible to the people who control resources. It gives them grounds for judgement without presenting a speculative cost estimate as a fact.
Compare prevention with the work it would replace
The starting point is the work the organisation currently performs to maintain control and recover when that control is disrupted. A proposal for preventive maintenance, for example, may be compared with a pattern of reactive repairs, lost production time, extra cleaning, repeated checks and delayed dispatch. The comparison concerns two feasible ways of operating over the same period. It is misleading to treat the proposed maintenance spend as a new cost while leaving the effort and disruption in the existing arrangement at zero.
Define the present baseline carefully. How often has the problem occurred, how long did it interrupt work, and what was required to restore normal operation? Maintenance records may describe repair time; production records may show lost line availability; corrective-action records may show investigation and follow-up. These records describe different parts of the same experience. They need to be linked by event and time before costs are added, otherwise the case can count the same lost hour more than once. A period that includes an unusual incident may also need comparison with a longer trend so it does not stand for an ordinary year without justification.
The alternative is more than the purchase price of a machine, service or extra person. Implementation may require installation time, training, planned downtime, monitoring, upkeep and management attention. It may also shift work between departments. If Engineering gains a planned inspection task and Operations loses some emergency stoppages, the case should show both effects. An apparent saving in one budget can otherwise be a transfer to another team.
Managers should describe at least the realistic alternatives they can choose among. Continuing as now may be viable for a time, but it has continuing burdens and exposure. A smaller intervention may address a well-understood cause without the cost of a full redesign. A staged trial may buy evidence before a larger commitment. The choice depends on the problem, available authority and the consequences of delay. Technical requirements set the minimum acceptable control; an investment case can compare how that control is achieved, not assume it can be abandoned to improve the return.
Count the value that does not increase output
Preventive investment can create value by reducing work that should not have been necessary. Recurrent corrective actions consume time to contain a problem, investigate it, agree actions, change the work and check that the change holds. A repeated equipment fault may also create waste, overtime, delayed production and administrative effort. Reducing that burden can release scarce capacity even when the factory does not produce one additional unit.
The distinction between money saved and capacity released matters. If a maintenance change saves a supervisor several hours each month, the saving may allow that person to complete planned work rather than reduce payroll. Calling those hours a cash saving would overstate the case. Calling them valueless would be equally unhelpful if the team is already postponing inspections or improvement work. The business case can show the time, explain the work it would enable and state whether any expenditure would actually fall.
Consider a site that repeatedly loses time to the same type of equipment fault. Engineering repairs the fault, Production rearranges its schedule and Technical checks whether the interruption has affected product or control evidence. Management is considering more systematic condition checks and planned replacement of a vulnerable component. The historical repair and interruption records could support a range for recurrent labour and lost operating time. They could also show whether the same fault is genuinely recurring, rather than several different failures being grouped under a convenient label.
Engineering needs to assess whether the proposed checks can detect the fault early enough, and Technical may need to assess what controls are affected by any equipment change. If the proposed work reduces emergency repairs, the site may gain more predictable access to the line and less disruption to other planned tasks. Those benefits should be described in terms the receiving managers can test: which interruptions might be avoided, what work would be released, and what assumptions must hold for the result to follow.
Opportunity cost belongs in the same discussion. Funding preventive work may delay another improvement or use maintenance time that could be spent elsewhere. That does not make the preventive proposal weak; it makes the comparison honest. A resource decision is stronger when the manager explains what will be displaced and why the expected benefit justifies that choice.
Keep uncertain consequences visible without pricing them falsely
Some parts of a preventive case are supported by reasonably direct records. A site can count repairs, investigation hours, wasted material or periods of downtime, subject to the quality of those records. Other consequences are possible but much harder to price. A severe low-frequency event may have major operational or customer consequences, yet the site may have no sound basis for assigning it an annual probability to several decimal places. Customer confidence and organisational capability can matter even when no credible currency value exists.
Forcing every consequence into a single financial total can hide that difference in evidence. A spreadsheet may produce a precise return on investment because its cells contain precise numbers, even when the crucial inputs are guesses. The decision-maker then sees apparent certainty where the case actually depends on judgement. A better presentation separates observed burden, estimated effects under stated assumptions and material consequences that are not responsibly monetised.
Scenario ranges can help when the uncertainties are intelligible. Management might examine what happens if the intervention reduces recurrent failures modestly, substantially or not at all. The purpose is to test whether the decision remains reasonable across plausible outcomes, not to invent a probability distribution. If a case is attractive only when every optimistic assumption is true, the managers considering it may need a smaller trial or better evidence first. If even a conservative effect would release valuable capacity, they can say so without pretending the severe-event risk has been priced.
The unpriced consequences still need explanation. Regulatory exposure, customer trust or loss of specialist knowledge should not appear as vague reasons to approve any expenditure. Identify the mechanism: what failure or weakness could arise, how the proposed investment might reduce it, and what remains outside the proposal's reach. A manager may conclude that a risk deserves action despite weak financial quantification. That is an accountable judgement when the basis and uncertainty are visible, not a failure of commercial discipline.
Turn the case into an accountable decision
A useful business case ends with a decision that someone can actually make. It should identify the proposed option, the alternative being rejected or deferred, the resource required, the technical conditions that cannot be weakened, and the evidence that will be reviewed later. The person preparing the analysis may be a technical or operational specialist; the person authorised to release the money may be elsewhere. The case needs to travel across that boundary without losing the assumptions that make its conclusion credible.
The level of commitment can reflect the evidence. A reversible, limited trial may be sensible when the mechanism is plausible but the size of the benefit is uncertain. A wider investment may need clearer evidence about implementation, capacity and dependencies. Where a significant requirement is already unmet, a financial comparison cannot substitute for the necessary control decision. Management still has to choose an executable response and allocate the resources it requires.
Approval is the start of a further test. The organisation should know who will implement the change, what normal work will need to alter, and what evidence will show whether the intended burden has fallen. A new inspection schedule may be installed and recorded while breakdowns remain unchanged. In that case, completion of the scheduled activity has been shown, but the investment's intended effect has not. Conversely, an early fall in faults may be encouraging without proving sustained benefit if the period is short or operating conditions have changed.
Review should therefore revisit both the operational outcome and the original assumptions. Did recurrent repairs, investigations or downtime change? Was capacity actually released for the work the case named? Did the change create new work or difficulty elsewhere? The answers may justify sustaining the intervention, refining it or changing course. Recording the reasoning at approval makes that later review more useful because managers can compare the result with the decision they actually made, rather than with a simplified story told afterwards.
A credible preventive investment case does not need to prove that every avoided problem has a precise price. It needs to show the real comparison, distinguish what can be measured from what must be judged, and make the decision and its later test explicit. That is how preventive spending can be considered on its merits alongside more visible claims on scarce resources.
