How do supervision gaps show up in Qardho completion forecasts?

A completion forecast in Qardho drifts when supervision gaps let unverified work count as finished. The forecast is only as good as the progress it is built from. If a supervisor records a pour, a blockwork run or a service trench as complete without checking it against the drawing, the test record and the site itself, the schedule keeps moving while the work does not.

Where does weak supervision break completion forecasting in Qardho?

Supervision breaks forecasting when nobody compares the reported progress to the physical work. A foreman reports a slab complete because formwork is stripped. The supervisor writes it into the weekly return without checking level, cover to reinforcement or curing. The forecast then absorbs an activity that may still need rework, and the cost of that rework surfaces weeks later as a variation or a delay.

The same happens with inspections. On building work in Puntland, a pour or a backfilled trench can be scheduled so tightly that the inspector arrives after the work is buried. Ask the project's engineer what hold points the specification sets, and confirm them against the project's specification or engineer, because these are general practice, not a fixed local rule. A hold point that nobody enforces is a line in a document, not a control.

Watch the forecast's shape as well. A completion forecast that barely moves for months and then drops sharply near the end usually means progress was overstated earlier, not that the team suddenly accelerated.

How do you detect late recognition of cost exposure on a Qardho build?

Late recognition of cost exposure shows up when the first warning is a rework bill, not a site note. Compare the latest forecast against the last three monthly returns. If an activity moved from planned to complete without a matching inspection record, a test result or a photograph with a date, treat that progress as unverified. Then ask what it would cost to redo that item, and put the figure in the forecast.

Follow the materials as well. Ask for delivery notes and check that they match the volume the forecast assumes is built in. A site that claims high blockwork progress with little cement or block delivered on site has a gap between the paperwork and the wall.

Test records matter most where the work hides. Concrete cube results, compaction checks on fills and pipe pressure tests are the evidence a forecast needs before it can close an activity. If the laboratory has no record, the activity is not finished, whatever the site diary says.

How do you close the supervision gap?

Close it by making progress claims carry evidence. Set a simple rule with the contractor: no activity counts as complete until the inspection record exists and the supervisor has walked that part of the site in the same reporting period. Write that rule into the reporting format so the monthly return has a column for the record reference, not just a percentage.

Then walk the site yourself on a fixed day each month, with the drawing and the last return in hand. Pick three activities marked complete and check them. Note what you find, not what you were told.

Agree the hold points in writing before the next pour, and confirm the sequence against the project's specification and engineer. If a step needs a third party, such as a laboratory or a municipal inspection, book it in advance so the work waits for the check rather than the check chasing the work.

What to do next

Ask the contractor for the last three monthly progress returns and the inspection records behind them. Pick the three activities with the largest claimed progress since the previous return, then walk those parts of the site with the drawing and note what is actually built. Put any unverified item back into the forecast as open work.