FR Get in touch
← Back to home

One engine, applied at three moments.

The cost of a week of delay is born in the investment case, runs during execution, and is settled at close-out. These three steps are not three products: it is the same calculation, read at three different moments. Here is what each one asks for, and what it returns.

/01 At the start

Understand where your projects lose value.

The diagnostic is the entry point of the whole approach, and the only step that looks backwards. We go through your closed cases one by one, down to the root cause, to build the reference set everything else will rest on.

What you give us

  • Your investment cases exactly as they are, with no reformatting
  • The schedule approved when funds were committed, and the actual one
  • Close-out minutes, where they exist
  • Three projects for the express format, ten to fifteen for the portfolio

What you get

  • The cost of delay on each case, as a range, never a single figure
  • The mechanisms that repeat from one project to the next
  • An estimating reference set: cost per unit of sizing, capital structure, spend profile, appraisal lead times
  • The conventions your cases actually applied, and how widely they vary
  • One live project run through the predictive model

Your data does not need to be clean. Across the portfolios we have worked through, the field that names a project's nature is a free-text box, not a nomenclature: dozens of distinct values for a few dozen projects. Sorting it out is part of what we deliver, not a prerequisite we put on you.

What the diagnostic most often brings to light is not a failed project, it is an unwritten convention. A contingency rate running from 0 to 12% across cases, a residual value assumed anywhere from 0 to 80%: two cases appraised under different assumptions cannot be weighed against each other.

/02 Before you commit

Appraise the value, and predict the risk.

This is where the cost of one week is born, and it is not decreed: it is derived from how the case builds its value. It is also where the project receives its execution score, before the first euro is committed.

What you give us

  • The investment case being prepared
  • The technical nature of what will be built
  • The economic purpose: why the money is being committed
  • The milestones envisaged and the dependencies already known

What you get

  • The cost of one week of delay, as a range, with the assumptions used
  • The share of value lost pro rata, and the share that falls in one block at a hard date
  • An execution score built on eight verifiable indicators, each read at a named milestone
  • The delay expected for this nature of project, read from your own history
  • What remains to be checked before committing

Cost and delay are not read on the same axis. Cost is compared against economic purpose, delay against the technical nature of what is built. The same purified-water equipment counts as growth if it serves new capacity, as compliance if it closes a regulatory gap. The two axes cross; they never convert into one another.

The width of the range is itself information. It measures what the case left unlocked. A wide spread is not a calculation flaw: it is the share of promised value that depends on events outside the project, and that delivering on time will not be enough to realise.

/03 During the project

Measure the consequence, foresee the drift.

The cockpit reads what your systems already produce and draws the priced consequence of every slippage. It replaces no tool, asks for no additional data entry, and writes nothing back into your systems.

What you give us

  • Your schedule exports, in the formats you already use
  • A periodic financial extract
  • Your project meeting minutes

What you get

  • Actual delay, measured against the date approved at commitment, not against the latest schedule
  • Projected drift at the rate observed since commitment, with no coefficient added
  • Contingency drawn down against physical progress, the only line that moves before the finish date does
  • Spend compared with the observed profile of its purpose
  • The frozen points of the score, those that cannot be recovered, and who decides on the rest
  • A decision queue where every week of waiting is priced
  • Chasers escalated to the right level: owner, then project manager, then sponsor

A score is worthless unless it says what can still change. Some indicators are read at a milestone already passed: contractor capability is read at award, scoping is read at scoping. Showing them as levers would be a comfortable lie. SEI marks them as frozen, and names the authority that can act on the rest.

The delay starts before the project exists. Between the submission of a case and the decision to commit, two to nine months go by depending on the nature of the investment, and no project dashboard sees it. A week of indecision in committee weighs as much as a week of site delay.

What the cockpit does not do: build a schedule, keep your accounts, or replace your project management tool. It displays consequences; it does not produce the source data.

Thirty minutes is enough to know if this is for you

You describe your projects, we tell you honestly whether a diagnostic makes sense, and which one. No commitment.

Get in touch →