How do low bid explanations gaps affect Hargeisa builds?

A low bid explanations experience gap in Hargeisa means the bidder has priced the work but cannot write down how the price will be delivered. The number looks competitive, yet no method statement, crew list, plant list or programme logic explains it. The client then awards on price alone and carries assumptions that were never tested.

Why does a missing explanation matter more than the price?

A bid price is an output; the explanation is the input that shows whether the output can be delivered. When the written explanation is thin, the assumptions stay hidden: which plant will be on site, who supervises the concrete, how materials reach the plot through Hargeisa traffic, and what happens if the Gu or Deyr rains interrupt the programme.

A low number with no explanation can mean the bidder has not costed temporary works, testing, water, curing or supervision. Ask each bidder to submit a method statement, a plant and labour schedule, and a programme that names the sequence of trades. Ask them to list two projects of similar scope and give the client reference for each. Then walk one of those recent sites and look at what was actually built. The municipal engineer's office can say what records it holds on the plot; a laboratory can confirm what testing it can perform.

What delivery assumptions hide inside a low number?

Delivery assumptions are the promises a bidder makes without writing them down. Common ones include assuming the client will supply water or power, that access is clear, that the ground needs no treatment, or that one supervisor can run two sites at once.

In Hargeisa the checks are practical. Ask the bidder to state the water source and how it will be stored and cured. Ask where the plant comes from and whether it is owned or hired, with a hire letter if hired. Ask how many supervisors will be on site each day and what else they are running. Ask for the programme logic, not just dates: which activity follows which, and how long each curing or testing period takes.

Set these as general practice, and confirm the specifics against the project's specification or engineer. If the bidder cannot explain a line, the number behind it is a guess. That guess becomes a variation, a delay or a defect later, and the client pays for it either way.

How do you test explanations before award?

Test explanations through a structured clarification round, in writing, with the same questions to every bidder. Ask for the method statement, plant and labour schedule, programme logic, and the two project references. Ask what the bidder will do if the water source fails or the rains arrive early, and ask who signs off each completed stage.

Then verify. Call the references and ask whether the works were completed and whether the same crew and plant turned up. Walk a recent site and look at the workmanship, the temporary works and the site records. Check the programme against the quantities. Ask the bidder to price the assumptions as a separate schedule, so extras are visible before signing.

Where the explanation stays weak, the client can ask the bidder to attend a clarification meeting and resubmit. Check what the tender documents and your contract allow before you change anything, and never instruct work or adjust payment outside the agreed terms.

What to do next

Take the lowest two or three bids and send each bidder one written clarification request: method statement, plant and labour schedule, programme logic, two project references, and a priced schedule of assumptions. Set a deadline. Walk at least one referenced site before award. If a bidder cannot answer in writing, treat the explanation gap as a risk to price into the evaluation, not a discount to accept.