In brief
- A project team without completion forecasting experience reports dates it cannot support, so cost exposure surfaces late, often when the cash call is already due.
- Clients can test the team by asking for the method behind a date, not the date itself, and by checking progress records against a walk of the site.
- The fix is a written forecast updated on a fixed cycle, with the assumptions, quantities and remaining work listed so a third party can audit them.
Contents
Completion forecasting experience gaps in Bosaso show up as finish dates and final cost figures that a team cannot support. The gap rarely looks like a missing skill on a CV. It looks like a date produced from memory, without quantities, without remaining work measured on site, and without the assumptions written down where a client or quantity surveyor can test them.
What goes wrong when nobody has forecast completion before?
The first honest finish date arrives late, and it usually arrives after a cash call.
Forecasting completion means counting what is left, not what is done. On a Bosaso build this includes blockwork still to lay, screed and finishes still to start, joinery and sanitary fittings not yet on site, external works, and the connections and tests that follow. A team without that habit tends to read progress from activity. Workers are present, material is moving, so the job looks close. The remaining quantities stay unmeasured.
The cost side fails in the same way. Late finishes hold plant, supervision and site overheads for longer. Those costs belong to the project, not to the calendar. When nobody re-forecasts, the client sees them first in a request for more money, after the money is needed.
Ask for the remaining quantities behind any date, in the units of the work: square metres of blockwork, linear metres of pipe, cubic metres of concrete. If the team cannot produce them, the date is an opinion.
How does the gap create late recognition of cost exposure?
Cost exposure stays hidden until the work that drives it is priced, and that pricing happens late by default.
A forecast built from the programme alone misses the second-order items. A delayed roof changes when the internal trades can start, which changes supervision weeks, scaffolding time and the order in which materials are bought. Each shift carries cost, and a team without forecasting experience does not map those shifts to money.
Shortages matter too. If the date is wrong, procurement is planned against it. Reinforcement, cement or tiles ordered late may need sourcing outside Bosaso, which changes both delivery time and haulage. Ask the procurement lead to show the order dates tied to the current programme. If the dates were never set, the cost exposure is not being tracked.
There is a specific trap for projects funded under a World Bank programme. Where disbursement and reporting follow the agreed schedule, the programme tends to hold long after the physical date has moved. Read the reporting calendar against the site date. Where they diverge, late recognition of cost exposure is already happening.
How can a client or quantity surveyor detect the gap before it bites?
Detection is a test of method, not a test of confidence. The wrong question is whether the team believes the date. The right question is how the date was built.
Practically, work through four checks:
- Ask for the basis of the date: remaining quantities, productivity assumed, resources assigned and the list of assumptions.
- Walk the site and compare visible progress with the progress claims in the last report.
- Ask who prepared the forecast and what that person forecast before. Do not accept a role title as proof.
- Ask what could move the date and by how much. A team that names only weather is not forecasting.
If the answers are unavailable, ask the project manager to produce a written forecast with its assumptions before the next payment cycle, and check what the contract allows on reporting.
What to do next
Ask the project manager for a written completion forecast with remaining quantities, productivity assumptions and procurement dates, and request the same forecast again two weeks later. Compare the two. If nothing moves while the site changes, the gap is live. On the next visit, walk the site against the progress report before agreeing anything.
Frequently asked questions
How often should a completion forecast be updated on a Bosaso project?
General practice is to re-forecast at every reporting cycle and whenever the sequence changes, not only when the date slips. Agree the cycle in writing with the project manager and check what the contract requires.
Can a contractor with experience elsewhere forecast a Puntland project?
Not automatically. Ask what they forecast before, on what kind of work and with which supply chain, and ask for the assumptions they would use in Bosaso. Site conditions, procurement routes and supervision arrangements all change the numbers.
Does a late forecast delay payment?
Payment rules sit in the contract. Read what your contract allows on reporting and certification before holding or releasing anything, and take advice if the wording is unclear.
Local reporting: this article is written for building work in Bosaso and Puntland. Ground conditions, prices and rules differ between places; confirm the details for your own site.