An inventory can be precise and still leave a maintenance planner with an unanswered question. The item exists, the purchase is recorded and its location is known. None of those facts necessarily establishes that the assembly supports the application now proposed. I have learned to treat that distinction as an operating responsibility. It is not an accusation against procurement, nor a reason for a COO to make an engineering judgement from the stock report.
The temptation to collapse the distinction is understandable. A business has paid for material and wants the expenditure to mean preparedness. A team under pressure to confirm a maintenance date wants to know that a difficult requirement has been covered. An inventory figure can appear to satisfy both needs. The problem arises when a statement about possession quietly becomes a statement about suitability without the evidence and authority needed for that change.
## Begin with the intended work
In our fictional 2016 review, twelve high-value spare assemblies were being considered against four planned applications. Engineering colleagues asked for the application evidence to be examined rather than relying on the stock position alone. The review found nine compatible assemblies and three requiring modification or replacement. I retain that distinction because it is the point of the case. Twelve held and nine confirmed describe different aspects of preparedness, even though both numbers can be accurately reported.
The result does not mean the unresolved three had never been useful or had necessarily been purchased carelessly. An application may have changed, the operating plan may have developed or the available evidence may not support the use being proposed. The actual reason must be established in the specific assessment. I would not want an executive narrative to turn a focused review into a sweeping judgement about every earlier procurement decision. The account should be as limited and as clear as its evidence permits.
Starting with intended work also changes the conversation between teams. Instead of asking procurement to defend the existence of an item, the planner can explain the application and the question that must be resolved. Engineering can state the finding and the conditions relevant to it. Commercial colleagues can then examine the supplier response and expense implications. Those responsibilities are connected, but the fact that they meet in one discussion does not make them interchangeable.
My contribution is to organise that discussion and ensure its consequences reach the programme. If the finding is inconvenient, I should not encourage the team to replace it with a more comfortable description. If the evidence is incomplete, I should not call the item unsuitable merely to make the uncertainty easier to classify. An honest preparation account can include an unresolved question, provided the responsible people and the effect on the intended work are understood.
## The uncomfortable result is useful before the window
The nine-and-three finding made our apparent preparedness less straightforward. Procurement colleagues had invested effort in the original purchase and reasonably wanted a specific explanation for reopening it. The maintenance team wanted the issue resolved before the planned use. I supported the review because discovering the distinction earlier gave the organisation a more credible basis for its next decision. That did not make the review painless or establish that every later difficulty could be avoided.
We incurred ₹1.6 Cr in verification and rework expense. The programme had to reflect the applications that remained unresolved until the proper decisions were made. A summary showing the original stock quantity without the qualification would have allowed the maintenance commitment to rest on an assumption we now knew required attention. I preferred the less flattering account because it described what the available material could actually support.
There is a danger, however, in turning this lesson into a ritual of repeated checking. A review should answer a defined question, use appropriate expertise and produce evidence relevant to the planned application. It should not become an open-ended exercise in seeking a level of certainty that no practical decision can have. The purpose is to improve the basis of the operating commitment, not to delay it indefinitely through a vague demand for more assurance.
The timing of a question also matters to how dissent is received. When a concern appears after a programme has been publicly celebrated as ready, colleagues may experience it as a challenge to their competence or commitment. Raising the application question while the programme is still being developed gives it a better chance of being treated as part of the work. That is a leadership choice about the conditions for an honest discussion, not a promise that every disagreement will disappear.
I also want to know what happens to the unresolved items in the next account. A finding can be accurately recorded and then lose visibility when the report returns to its usual format. The programme should retain the consequence until the responsible decision has been made. That does not require broadcasting every technical detail to every audience. It requires enough continuity that a senior reader does not infer closure merely because the original stock total has reappeared without qualification.
## Do not turn a review cost into an invented saving
The ₹1.6 Cr in the case is verification and rework expense. It is not the inventory value of all twelve assemblies, the price of replacing every unresolved item or a calculated loss that the review prevented. Each of those would require different evidence. I am careful about this because preparation work is often defended through a dramatic counterfactual: what might have happened if we had not done it. A plausible concern does not by itself establish the monetary value of an avoided event.
The business still needs to assess whether the expense was justified. That assessment can consider the application requirement, the alternatives available and the consequence of leaving the issue unresolved. It does not need an invented saving to make the decision discussable. Where an estimate is used, its assumptions should be visible. Where the outcome cannot be quantified reliably, the report should say what was established rather than reach for a larger number that appears more impressive.
This discipline also protects the technical finding. If the review is presented mainly as the source of a headline financial benefit, there may be pressure to make its conclusion more comprehensive than the evidence supports. I would rather report a narrower, defensible result and preserve the distinction between engineering assessment and the commercial decision built around it. That gives both disciplines a clearer basis for challenge and prevents the executive summary from becoming a substitute for either.
At fleet level, the broader question is what we mean when we say a maintenance programme is prepared. Material holdings, qualified people, supplier commitments, technical findings and the relevant operating window all contribute to the answer. A strong number in one category cannot settle every other category. The COO’s role is to understand the dependencies well enough to explain the commitment and its remaining conditions.
I therefore see a spare assembly as part of a proposed application, not simply an asset on a reassuring list. The physical item and its accounting record matter, but the operating claim needs its own support. When I ask that the distinction remain visible, I am asking for a more useful account of preparedness. It may be less comfortable at first reading, yet it gives the people responsible for the next decision something they can actually use.