In brief
- A contingency is only real if the priced clause, the contract terms and funded work items match, so a low bid can look complete while carrying no money for the unknown.
- Site supervision is where a missing contingency surfaces, because the first sign is a stalled instruction, missing test or repeated rework that nobody has a priced line for.
- Close the gap by reading the tender line by line against the contract and the site record, and by putting the response time for unforeseen ground or weather into a written agreement before work starts.
Contents
A tender contingency in Garowe fails in a quiet way. The bid looks complete, the priced items add up, and the award is signed. The gap appears later, when something the drawings did not show has to be paid for and no clause, allowance or funded line exists to cover it. Weak site supervision then decides what happens, usually by doing nothing.
What a bundled contingency hides in a Garowe tender
A contingency disappears from a bid when the estimator folds it into another rate.
Ask for the priced bill of quantities and read it as a list of things to buy, not a total. A rate for excavation that already includes rock removal, dewatering and disposal leaves nothing visible for an unexpected boulder or a softer layer than the trial pit showed. The clause may mention the ground in a general way, so the bid passes review, but the mechanism is gone: there is no separate line to trigger, measure and pay.
On a Garowe building site, check three things in the contract before award. Is the contingency a lump sum or a measured item? What event releases it? Who certifies that event? General practice is that a genuine provisional sum needs a defined trigger and a named certifier, so confirm how this project's specification treats it with the consultant or engineer. If the tender says only that the contractor carries the risk, treat the missing allowance as a supervision question, not a costing one.
How weak supervision lets the gap widen
Supervision fails at the point where nobody converts an unforeseen event into a written instruction, and the work stops or the wrong fix gets built.
Watch for the small signals. A supervisor receives a verbal request to dig deeper and does not log it. A test result is asked for by phone and never filed. Concrete is placed in a footing whose level nobody recorded. Each of those is a contingency becoming unbudgeted work, and the site diary is the only place it can be caught early.
Supervision also misses the difference between rework and new work. If a wall is rebuilt because a setting-out error was never checked, that cost sits with whoever the contract assigns it to, and the claim may fail if no inspection record exists. Ask to see the last month of inspection requests, the test register and the instruction log. A register with gaps points to a site where unforeseen items are being absorbed silently.
How to close the gap before work starts
Close it by making the trigger, the evidence and the response time explicit in the contract and on the site, then checking both.
Four checks work together. Read the tender clause against the contract clause, because the second one governs. Walk a recent site with the same scope and ask the site team how rainy-season days were recorded and valued on that project, and how unforeseen ground was handled. Ask the municipal engineer's office what records it holds for the plot, and request soil or test records from the client if they exist. Then agree, before mobilisation, how many days the contractor has to notify an unforeseen event and who signs the instruction. General practice is a notice measured in days, not weeks, so confirm the period this contract sets.
If the client will not fund a separate contingency line, the supervision plan has to carry the risk instead: named inspections at defined stages, a running instruction log and a test register signed off each week. Ask the site team how rainy-season days were recorded and valued on previous projects in the area, and whether the programme already shows them. A schedule with no float and no weather allowance is the same gap in a different file.
What to do next
Before the next award in Garowe, take the priced bill of quantities and the contract conditions to the project engineer in one sitting. Mark every item that could hide an unforeseen event, and write down its trigger, its certifier and its notice period. Send that list to the client for written confirmation, or ask for the contingency to be repriced as a separate measured item.
Frequently asked questions
Does a low bid always mean no contingency?
No. A low bid can carry a real allowance that is simply not shown as a separate line. Ask for the build-up of the rates that cover excavation, ground risk and weather, then compare it with the contract terms before deciding.
Who should keep the contingency record on site?
The supervisor keeps the day-to-day record of instructions, tests and delays, and the project manager reconciles it against the contract each month. Agree both roles in writing before mobilisation.
Local reporting: this article is written for building work in Garowe and Puntland. Ground conditions, prices and rules differ between places; confirm the details for your own site.