Skip to content
Projects Advisors

Stage 02 · The Lifecycle

Delivery & Controls

Heavy reporting, and less clarity than the reporting suggests.

The stage

What happens at this stage

Delivery is heavily instrumented. There are schedules, cost reports, risk registers, change logs, dashboards and steering committees. That volume of reporting can still leave an organisation surprised later by what the reports did not show.

The reason is that project reporting measures conformance to a plan, not the health of the thing being produced. A programme can be green on every metric and still be accumulating problems that will not surface until it is operated.

Flyvbjerg’s dataset is the uncomfortable backdrop: nine in ten megaprojects exceed budget, the pattern holds across 104 countries and six continents, and it has not improved over the ninety years for which comparable records exist. This publication reads that persistence as a sign that the cause is structural rather than local.

What goes wrong

What typically goes wrong

  1. Progress is reported against a baseline that the team already regards as obsolete.

  2. Change is managed as a commercial event rather than as information about the design.

  3. Entitlement is accumulated rather than resolved, so a dispute is quietly manufactured during delivery and argued about years later.

  4. Risk registers list risks without anybody owning the decision each risk implies.

  5. Assurance is scheduled to arrive after the decisions it should have informed.

Questions to ask

Questions worth asking

  • What would have to be true for this report to be wrong?

  • Which changes have altered how the asset will be operated, not just what it costs?

  • Are we tracking the production of information, or only the production of works?

  • What do the people doing the work believe that the reports do not say?

Writing

Writing on delivery

17 articles

  1. An extension of time is tested against records made during the delayA claim for more time turns on three separate questions. Was the contract's notice procedure satisfied? Is the event one for which the contract allows an extension, or whose risk it otherwise places on the employer? Did it actually delay completion? Money is a separate claim, with its own proof of causation and amount. Each question is later tested against what was written down while the event was happening, by whichever party has to prove the point. Records do not create entitlement, a record of an event does not prove that it delayed completion, and the prevention principle does not rescue a claim under every contract or every governing law.14 min read
  2. The score that is not a numberA technical score on a qualitative criterion records what evaluators judged. The weighting decides how much of the award that judgement controls; it does not turn the judgement into a measurement. What makes the score answerable is a record that a reader outside the room can test against the solicitation and the proposal, and the instruments examined here require different parts of that record.9 min read
  3. Three award rules make you disclose how the criteria are weighed. None makes you defend it.The WTO agreement, the UNCITRAL Model Law and the EU directive all require the relative importance of the evaluation criteria to appear in the tender documents. None says what the weighting should be, and the Model Law's own commentary calls it discretionary. The GPA and the Model Law specify the arithmetic completely in exactly one situation, an electronic auction, where a machine does the ranking. Meanwhile a 70/30 split under the World Bank's own price formula prices one technical point at 3.4% of the contract and puts a 30 point quality lead beyond the reach of any price at all.12 min read
  4. Private projects overrun too. The difference is who counts.Government projects are said to run late and over budget while private ones finish. A 2004 study, using what its authors described as the largest dataset of its kind at the time, tested ownership statistically and found privately owned bridges and tunnels escalated more on average than publicly owned ones; its authors called the conventional view an oversimplification. What differs is not the outcome. It is who is counted, and what a private owner has that a public one does not, which is structure rather than virtue.15 min read
  5. The payment chain is a loan, and the contractor is the lenderA monthly certificate under Saudi Article 109 takes 80 days as the regulation is written, 86 on a real calendar with every office on time, and 128 if one payment order is returned at the wrong moment. On a programme of 1.2bn a year that is 283m to 421m of the contractor's own money standing in the project permanently, borrowed at the contractor's rate, and priced back into the tender. No rule names it, and nothing in the chain prices it.25 min read
  6. Reliability can be specified like mass. Building owners do not.The committee that writes the world's dependability standards says reliability should be specified the way dimensions and mass are. Rail has had a published process for specifying and demonstrating it since 2002. The buildings sector's reference specification for what a contractor hands over asks for the manufacturer's projection of how many hours a repair will take, and never how often one will be needed.10 min read
  7. The certified value and the booked value are two different recordsWhile a project is being built, its cost lives in two places. The project keeps a record of what has been built and certified. Finance keeps a record of what has been booked. The standards assume they agree. The only thing that makes them agree is a reconciliation, and one auditor has spent 27 years documenting what happens when it is not run.11 min read
  8. A dashboard computed from your own beliefs is not informationThe test for any instrument on a capital programme is whether its output contains something the inputs did not. A rule applied, a calculation done, a source consulted. A rating a team gives itself contains none of these, and colouring it does not add one. One public dashboard has carried both kinds side by side since 2009, and an auditor has re-rated the self-assessed column and published the result.10 min read
  9. Moving a date is not the same as re-planningWhen a programme slips, the recovery plan is usually the old plan with later dates on it. That is a translation, not a calculation, and it omits what the evidence says the extension itself costs. A large study of major construction found that each extra year of implementation correlates with cost overrun rising by 4.64%, and a plan that only moves dates has not applied it.9 min read
  10. The ground was always there. The record was not.Unforeseeable physical conditions is a contract mechanism, not an explanation. The utilities under a site were installed by somebody who holds a record of them, and that record fails to reach the design for a structural reason. The organisation holding it does not bear the cost of it being wrong. Britain priced that failure at 2.4 billion pounds a year before building a national register to fix it.9 min read
  11. Every programme performs well against a baseline it can moveA government builder completed 36 major construction projects and routinely met its cost and schedule goals. It had rebaselined 25 of them, and its reports did not say so. When asked why they had moved a baseline, 4% of project managers gave their own cost or schedule performance as the reason.9 min read
  12. The critical path cannot show a delay nobody scheduledA programme schedule is required to contain the owner's activities as well as the contractor's. A schedule that contains only the contractor's, with the owner's approvals and decisions shown as single milestones or not at all, is incomplete. An incomplete network does not produce an approximate critical path. It produces an invalid one, and it is invalid in a direction that always favours the same party.8 min read
  13. Your contingency and their contingency are different moneyTwo bodies an owner is likely to cite define contingency and management reserve in opposite directions. One says contingency is for unknown unknowns and sits with the owner. The other treats it as the allowance for what experience says will happen. Both are defensible, and an owner and a contractor using the word across a table are frequently discussing different money, held by different people, against different risks.7 min read
  14. A forecast that never moves is not stable, it is unexaminedDelivery assurance measures progress against a baseline. Testing the baseline is a different exercise, and it is the one the monthly report does not contain. A forecast that holds flat and then steps was not stable, it was unexamined, and two numbers usually available in an afternoon will show which.6 min read
  15. You can place the activity outside. You cannot place the accountability thereClause 8.3 was retitled in the 2024 edition from Outsourcing to externally provided processes, products, technologies and services. The committee says the requirements did not substantially change. The four nouns still describe a category of arrangement wider than what outsourcing usually names, and the wider category is the one nothing in the audit plan is pointed at.7 min read
  16. Programme risk is not the sum of its functionsA capital programme does not simply contain larger versions of procurement, payment and resourcing. It creates chains that run through all of them, and a chain belongs to no function. That makes under-coverage a design problem in the audit plan rather than a question of materiality, and it has a method attached.11 min read
  17. Engaging an engineer satisfies the standard. Deferring to one does not.The 2024 Standards require an internal audit function to obtain the competencies it does not have, which reads as permission to bring in an engineer. That is the easy half. The obligations that decide whether the exercise was worth commissioning all start after the engineer has arrived.7 min read

Every stage, in one index

The seam that follows · Delivery to handover

Between delivery and handover, accountability transfers, and the party holding much of the delivery knowledge approaches the end of its obligations.

80days

from a Saudi contractor's invoice to payment under the procurement regulations, on a five-day week: 10 and 15 working days, then 45 calendar days. The English translation says 98.

Source · Government Tenders and Procurement Law, Executive Regulations, Article 109 (Arabic text)