What do bid program reviews miss in Garowe supervision?

A bid program review can approve a completion date that no crew working in Garowe can actually hold. The review usually reads the programme document, not the site. When site supervision is thin, nobody compares the promised durations against the pours, deliveries and inspections that follow. The promise stays on paper, the work slips behind it, and the client only sees the gap near handover.

How does a weak bid program review in Garowe let an unrealistic promise through?

A review that only reads the document cannot test the durations against the site. Bar charts and milestone tables look orderly on paper, whatever the crew can deliver. In a hot, dry inland climate, external works and concrete pours depend on water supply, shade and curing, and those needs are easy to leave out of a programme.

A bidder who knows the review is document-based can promise an early completion to win the tender. That promise is not a lie at the moment of bidding; it is an assumption about labour, materials and weather that nobody has checked.

The review should ask what evidence sits behind each duration. Ask the bidder for the crew numbers, the plant list and the water source per activity, then ask the municipal engineer's office what it knows about working seasons and access on similar plots. Record the answers in the evaluation file so the approved programme has a stated basis. Check the project specification and the engineer's instructions for what the programme must contain, and confirm that list before scoring.

How does the gap show up on site?

It shows up as a schedule that stays on the wall while the work moves at its own pace. Early activities look acceptable because groundworks absorb slack. The delay appears later: blockwork, roof, screed and finishes compress into too few weeks, and curing and drying times get squeezed.

Weak supervision misses the mechanism because it checks progress rather than the plan behind it. A monthly percentage tells nobody whether the approved duration still fits what remains. Ask for dated records: concrete pour dates, cube test requests, reinforcement inspection sign-offs and delivery notes. Walk a recent site with the same supervisor and compare its records with its programme.

How do you close the gap in the review and on site?

Tie the approved programme to records the supervisor must produce. Make progress measurement a condition of the contract and the programme, so the comparison happens on a fixed day each month, not when someone remembers.

The reviewer checks the bid programme against the specification and the engineer's comments. The supervisor then checks the site against the approved programme and reports the variance in writing. Where a delay appears, the report should name the activity, the lost days and the reason, and it should reach the client before the next progress meeting.

Ask what your contract allows before you act on a slipping programme. It may set notice periods for delay, extension claims or resequencing. The engineer's office can confirm what records it expects to see and whether any submission is required. Where two versions of a programme exist, keep the approved one as the baseline.

What to do next

Take the winning bid programme for your Garowe project and ask the site supervisor for dated records for every completed activity. Mark them on the baseline and count the days between plan and execution. Where the variance keeps growing, write to the contractor asking for a revised programme, and check with the municipal engineer's office and your contract what the next step allows.