Construction Contingency: How Much to Keep and When You Are Allowed to Use It

A contractor in Pune secured a Rs 5.8 crore commercial office fit-out and added a standard five percent contingency to the project budget. That put Rs 29 lakh in the contingency fund. In month three, the client’s interior designer revised the ceiling layout without issuing a formal variation. The rework cost Rs 7 lakh. The project manager pulled it from contingency because there was no other bucket to charge it to. In month five, the civil subcontractor walked off site over a payment dispute with the previous contractor on the same project. Emergency replacement cost Rs 15 lakh above the original work order rate. Contingency balance: Rs 4 lakh. Ahead still: a flooring material price increase and a pending MEP scope addition. The project closed Rs 13 lakh over budget. The contingency fund was not undersized. It was spent on the first two problems that appeared, with nothing left for the ones that mattered most. Construction contingency managed deliberately protects margin. Treated as a general expense account, it only delays the moment when an overrun becomes impossible to ignore.
What Construction Contingency Is and What It Is Not?
Construction contingency is a separate budget allocation saved to cover risk events that are highly probable of occurring, but that particular amount cannot be accurately decided. Contingency sits within the cost line and represents a financial buffer for things that go wrong. However, when contingency is decided, the project cost may rise and profit compress. When this contingency is used, the project is an outer edge of its cost budget. Anything out of this contingency amount can cost your profit.
There are many Indian contractors that merge contingency and profit into a single margin percentage added to the cost estimate. This results in unawareness of the fact that contingency is being consumed fully. There is no awareness about that. And by the time the contingency is consumed and the amount has been taken from the profit, the overrun has already taken place. It takes away the profit margin.
A cost allowance is not the same as a contingency. For a known item whose ultimate specification or price is still up in the air, a cost allowance is set aside. For instance, stone cladding that is included in the budget prior to the client choosing the finish is an allowance. If the final choice turns out to be more expensive, it is a budget overrun rather than a risk event.
Uncertain occurrences that might or might not happen are the purpose of contingency. It is not intended to pay for anticipated expenses, the precise amount of which is still being determined.
How to Size Construction Contingency by Risk Category?
One of the most common approaches of Indian construction projects are applying flat 5% to total contract value. This contingency approach is the least accurate one because since every project is different, every project has a different risk profile. And a reliable method is way deeper than that. It works when you identify events that could increase project costs, when you estimate how often each can occur, and finally estimating the financial impact that it can do on a project. Multiplying probability by impact gives an expected value for each risk.
For a mid-size Indian building project, four risk categories consistently require contingency allocation:
- Design risk: It is evident to have variation in execution when drawings are incomplete. In cases like these, it is a smart choice to keep aside about 2 to 4% of the contract value for any risk related to drawing. Any revision that leads to rework after work has started draws from its allocation.
- Subcontractor and supply chain risk: This covers subcontractor failure mid-scope, supplier delivery delays, and specialist re-sourcing under deadline pressure. Any project that has more than three subcontractors must allocate at least 1 to 2% of contract value in subcontractor and supply chain risk. Even a single default with or in subcontractor on an ongoing project can cost more than the entire subcontract value when replacement premium and delay impact are included.
- Site condition risk: Unexpected site conditions such as hidden utilities, unforeseen structural issues, or access constraints often lead to costs beyond the original estimate. Projects that begin without proper geotechnical investigation carry a higher level of risk compared to those with complete site data available before tender.
- Regulatory and approval risk: Delays in municipal inspection, compliance hold points, and late approvals for material or drawing can lead to time wastage and can cause rescheduling. The risk is higher in any government project compared to privately managed projects.
A contingency built from these four categories, sized to match the specific risk profile of the project, gives the project manager a fund with a clear purpose. A flat percentage gives a fund with no defined purpose and no defensible basis for any individual draw.
When Drawing on Construction Contingency Is and Is Not Justified?
Deciding the construction contingency coverage is mainly the 50% of the work. There is still 50% left, which is applying consistent criteria to every draw request. This helps in avoiding erosion in funds, which helps in better execution or planning.
A draw is justified when all three of the following conditions apply:
- The event that generated the cost was identified as a risk at project start, or falls clearly within an identified risk category
- The project team took reasonable steps to prevent the risk from materializing or to limit the cost impact once it did
- The cost was not caused by a project team error, a planning failure, or a foreseeable cost that should have been in the original estimate
Events that meet this test and typically justify a draw:
- A client-issued variation order for scope not in the original contract
- A site condition discovery that differs materially from what the tender documents described
- A subcontractor failure requiring emergency replacement at a rate above the original work order
- A material price escalation above the ceiling specified in the supply agreement
Events that do not meet this test and should not be recovered from contingency:
- Rework caused by the contractor’s own workmanship failures
- Idle crew time caused by poor sequencing decisions by the site team
- Material wastage above the estimate because cutting plans were not followed
- Procurement delays caused by the contractor ordering materials too late
- Any cost that a more disciplined execution approach would have prevented
When a project manager is aware of the fact that every drawer request is going to be closely assessed against preconditioned tests, they pay more attention to it before submitting. In result, the contingency fund lasts longer and covers what it was designed to cover.
How to Track Contingency Throughout Execution?
Most Indian contractors track contingency as a single budget line: allocation minus draws equals balance. That balance figure is accurate as a number but useless as a management signal, because it says nothing about whether what remains is enough to cover the risks still ahead.
A more useful tracking approach runs two records simultaneously.
The first is the standard balance: total contingency minus total approved draws to date. This number should update in the project accounts every time a draw is approved, not at the end of the month.
The second is a residual risk log: a running list of identified risks that have not yet materialized, updated fortnightly as the project progresses. Each open risk carries a probability and an estimated cost impact. The sum of expected values across all open risks is the residual risk exposure at that point in the project.
The project manager receives a clear indication when the remaining contingency is compared to the present risk exposure. The project is underfunded and requires action before those hazards materialize if the balance is ₹11 lakh and the remaining risk is ₹18 lakh.
At project completion, the excess can be converted back into profit if the balance is ₹11 lakh and the remaining risk is ₹5 lakh.
What helps?
It gets hard to manually track budget category balances in real time against actual and committed costs. Construction management platforms like Onsite can automate that for you. With the help of this, the current balance is always visible even after every draw is marked to the contingency line at the point of approval. The project manager and the finance team have been brought in together with the help of Onsite so that same current figure seems visible rather than from records that diverge between reporting cycles. Platforms like Onsite connect contingency tracking to the broader project budget view so both signals are always visible together.
Construction Contingency Is a Risk Tool, Not a Cost Buffer
The Pune contractor’s Rs 13 lakh overrun was not a contingency sizing problem. Rs 29 lakh on a Rs 5.8 crore project is a reasonable allocation. The overrun happened because the first two cost events consumed the fund before the risks it was designed for arrived. When contingency is treated as a general buffer for any unexpected cost, it gets spent on whatever appears first. The risks that required careful financial protection arrive later to find the fund empty.
When contingency is sized by risk category and drawn on only for genuine risk events that meet a defined three-condition test, it functions as the management tool it is designed to be. The balance at any point reflects real financial protection against real residual risk, not just a number that counts down as problems accumulate.
FAQs
Construction contingency is a budget allocation within the project cost that covers risk events likely to occur but impossible to price exactly at tender. Project profit sits above the cost line and represents the contractor’s expected return for delivering the project. When contingency is drawn on, project cost increases and profit margin compresses. When contingency is fully consumed without a margin overrun, the project finishes at budget. Any additional cost after contingency is exhausted directly reduces profit. Most Indian contractors combine the two into a single margin percentage, which removes the signal that contingency consumption provides during execution.
The right level depends on the project’s specific risk profile rather than on a standard percentage. Projects with complete drawings at award, experienced subcontractors, well-investigated site conditions, and a stable supply chain may need two to three percent. Projects with incomplete design at award, new subcontractors, limited geotechnical data, or volatile material markets may need six to ten percent. A risk identification exercise at kickoff that assigns probability and financial impact to each identified risk produces a defensible figure. A flat percentage applied to the contract total produces a figure that is easy to calculate and frequently disconnected from the project’s actual risk exposure.
A draw request should satisfy three conditions before it is approved. First, the event that generated the cost must have been identified as a risk at project start or must fall clearly within an identified risk category. Second, the project team must have taken reasonable steps to prevent the risk from occurring or to limit the financial damage once it materialized. Third, the cost must not have resulted from a project team error, a planning failure, or a foreseeable cost that belonged in the original estimate. Any draw request that cannot satisfy all three conditions is not a risk event. It is a cost control failure that contingency was not designed to cover.
Several cost types are commonly charged to contingency in practice but should not be. Rework caused by the contractor’s own workmanship failures is a direct project cost, not a risk event. Idle crew time from poor sequencing decisions reflects a scheduling failure, not an external risk. Material wastage above the estimate indicates that cutting plans or consumption controls were not followed. Late material deliveries caused by the contractor’s own procurement timing are avoidable. Any cost that disciplined execution, better planning, or tighter site management would have prevented does not qualify as a risk event and should not erode a fund allocated specifically to cover genuine external risk.
Effective tracking runs two records simultaneously. The first is the standard balance: total contingency minus total draws approved to date, updated every time a draw is approved. The second is a residual risk log: a list of identified risks still open, each carrying a probability and an estimated cost impact, updated fortnightly as the project moves forward. The sum of expected values on the residual risk log is the financial exposure still ahead. Comparing the contingency balance against that exposure tells the project manager whether the fund is adequate for what remains or whether additional provisioning is needed before the next risk materializes.
Yes. Contingency that is not drawn on by the time a project closes can be recognized as additional project profit in the final accounts. This is the financial reward for accurate risk sizing and disciplined draw management. Contractors who over-allocate contingency as a precaution lock up margin unnecessarily and understate project profitability throughout execution. Contractors who size it accurately and apply consistent draw criteria typically finish projects with a small residual balance that flows directly to the bottom line, with a clear project record showing which risks materialized, which did not, and why each draw was approved.
A project allowance is a budget provision for a known scope item whose exact specification or final cost is not yet confirmed at the time of budgeting. Stone cladding budgeted before the client selects the finish is a typical allowance. If the selected finish costs more than the allowance, that is an overrun on a planned cost, not a risk event. Construction contingency, by contrast, covers events that have not yet happened and may not happen at all. The two should sit on separate lines in the project budget. When they are combined, the project manager cannot tell how much of the available fund is covering planned uncertainty versus genuine risk, and both get managed poorly as a result.