In brief
- A bidder who has never coded costs on a comparable package cannot show where money actually goes, so the gap sits hidden inside the lump sum.
- Ask for a coded bill of quantities and past cost reports; the absence of these records is the warning sign, not a low price on its own.
- Fix it by requiring a simple code structure in the contract and checking coded drawdowns against measured progress each month.
Contents
Cost coding experience gaps in Hargeisa show up when a bidder cannot break a lump sum into the work packages that will actually consume it. The price looks complete. The coding behind it does not exist. When spending starts, nobody can tell which package is running over until the money is gone and the work is unfinished.
Why does weak cost coding hide package overruns?
Cost coding links every purchase, wage and plant hour to a package such as foundations, blockwork or roof, so overruns surface while there is still time to act. A team without that habit records expenses as one running total. One package can absorb the budget of another and the accounts still balance at the top. On a Hargeisa build, where imported materials and hired plant move quickly, the distortion can run for weeks before anyone notices. The mechanism is simple: without coded entries, the first reliable signal of trouble is a stalled site, not a report. Ask the bidder to show how a previous job split its cost records by package. If no such records exist, the bidder is pricing from memory. Confirm what the contract requires for cost reporting by checking the tender documents and asking the client's quantity surveyor what format is accepted.
Who detects a project experience mismatch, and how?
The client's quantity surveyor or project manager detects it by testing the bidder's records against the packages in this project, not by comparing headline totals. Useful checks are quick. Ask for a coded bill of quantities. Ask for one recent cost report showing budget against actual by package. Walk a recent site the bidder completed and ask the supervisor how variations were coded. A bid that cannot be split into packages is a package mismatch, even when the total looks reasonable. The same test applies to supervision. If the site team cannot say which cost code pays for a delivery, no one is tracking package spend. Ask the municipal engineer's office what records it holds on completed works in the area, and use those finished projects as a comparison set rather than relying on a single reference.
How do you close the gap before work starts?
Close it by writing the code structure into the contract and checking coded spend against measured progress each month. A short list of cost codes, one per package, agreed before mobilisation, gives both sides the same vocabulary. Then require a monthly statement that shows drawdown by code next to measured quantities. When a code runs ahead of its measured work, the client and the surveyor can ask why while the package still has room. General practice is to keep retention and payment terms aligned with verified coded progress, but confirm the exact provisions in the contract and against the project specification. If the bidder has never worked this way, agree a simple structure, not a complex one, and check it for the first two months.
What to do next
Before awarding the next Hargeisa package, ask each bidder for one coded cost report from a similar job and a proposed code list for this one. Score the answers with your quantity surveyor. Require monthly coded drawdowns against measured quantities in the contract, and review the first two statements closely.
Frequently asked questions
Is a low bid always a sign of a cost coding gap?
No. The warning sign is the missing coded backup, not the number. Ask for a package-by-package breakdown and a past cost report. If the bidder can show both, the price may simply be competitive.
Can a small contractor build cost coding experience?
Yes. A short code list, one per work package, plus a monthly spend statement is enough to start. Keep the structure simple and check it against measured quantities for the first two months.
Who should hold the coded records?
The contractor keeps the working records, and the client's quantity surveyor should receive the monthly coded statement. Check what your contract requires and agree the format before mobilisation.
Local reporting: this article is written for building work in Hargeisa and Somaliland. Ground conditions, prices and rules differ between places; confirm the details for your own site.