## Precision is not completeness
The equipment quotation was ₹9.8 crore. It was specific enough to give the proposal a sense of completeness, and I supported that framing as head of planning in 2019. The project also needed ₹1.4 crore for civil work, ₹1.1 crore for grid connection and ₹0.7 crore of startup cash. Together the requirement was ₹13 crore. The missing ₹3.2 crore needed additional approval, and the project was delayed nine weeks. The equipment amount had not become less precise. Our use of it as the project's funding account had been incomplete.
I find that distinction more useful than a general statement that budgets should contain everything. The supplier was describing a particular scope. The enterprise needed to describe the cash necessary to make the project usable. Those are related accounts, but they are not automatically the same account. The problem arose when a number assembled for the first purpose acquired the authority of the second. Finance should have made the boundary visible before the proposal reached approval, rather than let colleagues infer that an exact quotation meant the wider requirement had been reconciled.
Operating colleagues had identified work outside the equipment scope. I had not brought it into one funding explanation with enough care. That is an important part of the story because otherwise the omitted items can be described as if they appeared unexpectedly after approval. Some project needs do change as work develops, but that description should not be used to conceal requirements that were already relevant to making the proposal usable. In this case, my review needed to connect the operating account with the cash account before presenting the headline amount.
The corrected total also needed restraint. Calling the requirement ₹13 crore did not determine how every component should be treated in the accounts. Civil work, connection and startup needs were included here to explain project cash. Their accounting classification required its own professional assessment. I did not want the correction to one incomplete statement to create a different overstatement about capitalisation. A useful finance account can answer the funding question clearly while acknowledging that another question requires a separate analysis under the applicable requirements.
## Operating readiness has a cash sequence
The project needed more than ownership of the quoted equipment. It needed the surrounding work and resources that allowed the enterprise to use it in the intended setting. Those needs also had a sequence. An approval conversation that treats them as unrelated details can miss how one unresolved requirement delays the value expected from another. The nine weeks mattered because the company had organised expectations around a proposal that did not yet describe the complete cash commitment. The later approval repaired that account, but did not return the lost time.
I learned to ask operating colleagues to explain what must exist before the proposed equipment can perform its intended role. The purpose is not for finance to certify engineering readiness or make technical release decisions. It is to understand enough of the sequence to identify the resources and timing the funding proposal must carry. Specialists retain their authority, while finance makes their requirements intelligible in the decision account. That collaboration is more useful than asking the teams to produce separate lists and assuming the headline total already represents their combined meaning.
The mistake also changed how I viewed a contingency discussion. A general allowance is not a substitute for identifying known requirements. An unexplained extra percentage might make the total larger without making its scope clearer. Conversely, a precise list of known work does not eliminate every future uncertainty. I wanted the proposal to distinguish what had been identified from what remained uncertain, so the decision makers could understand both. This case does not prescribe a contingency rate or claim that a complete cash account can predict every development during a project.
There is a commercial consequence to that clarity. When the funding account is incomplete, colleagues may commit to dates or other plans that depend on work not yet supported. The delay then appears to belong solely to execution, although part of its cause lies in the proposal management approved. A better account does not make every schedule dependable, but it gives the enterprise a more honest basis for deciding what it is prepared to promise. Finance has a role in that promise because cash requirements and operating conditions meet before delivery begins.
## The finance sponsor belongs in the correction
I did not want the revised proposal to remove my original endorsement from view. As head of planning, I had helped give the incomplete figure its standing. The additional approval and delay therefore belonged in my account of judgement, even though several teams had responsibilities within the project. This is not an argument for assigning every project problem to finance. It is an argument for retaining the part finance actually played, so the organisation can improve the review rather than explain the failure entirely through work that happened after approval.
The correction itself needed a modest description. We obtained approval for the additional ₹3.2 crore and made the cash requirement clearer. That did not create a saving, prove the project would achieve its intended return or make the original proposal successful. Those outcomes would need their own evidence. I wanted colleagues to see the value of correcting the account without requiring the correction to become a larger commercial achievement. Otherwise a leadership narrative can reward the discovery of an error while quietly losing the consequence of having supported it.
For a board, the case suggests asking what the amount in an investment paper actually covers. Is it a supplier's quotation, the company's project cash requirement, an accounting asset amount or something else? The question is useful because each can be legitimate within its purpose. Directors should be able to understand the relationship without rebuilding the project model themselves. Management and specialists should explain the known requirements, timing and uncertainty, while finance makes clear which conclusion the presented total supports and which separate assessments remain necessary.
I now want a proposal to remain readable when its most memorable number is removed. If the account can still explain what must be done, who owns the requirements and how cash supports the sequence, the number has a stronger context. If the whole proposal depends on the authority of a single quotation, there may be work missing from the decision rather than merely from the appendix. My kiln project taught me that lesson through additional funding and delay. The quotation was useful evidence; it was never the whole obligation the enterprise had accepted.