1. Home
  2. Use cases
  3. Execute

Execute · Projects in construction

Where should recovery money go, and what does it buy?

Execute turns the cost and progress your project systems record each month into a P80 cost and finish for every unit, then prices each way out in money: what it costs, how much time it buys and what that time is worth. A contractor's milestone date is one piece of evidence, not the forecast.

Output: P80 cost and finish for each unit, updated from actuals; recovery options priced in money and previewed before money is committed; approved budgets and re-phasing sent back to the systems that run the job.

Who it is for

For the people who decide where recovery money goes

Project directors, project controls, finance business partners and lenders' engineers. Execute is the decision model on top of the systems that run your projects: it reads what they record each month and turns it into a decision on where money and recovery effort go.

  • Project directors
  • Project controls
  • Finance business partners
  • Lenders' engineers
  • Owner's team

Questions it answers

  1. What will each unit cost and when will it finish, at P50 and at P80?
  2. Is remaining contingency enough for the P80, and what do pending claims do to it?
  3. Which contractor dates are optimistic, and are they moving between reports?
  4. Which unit drives the programme finish, and what is a month of delay worth?
  5. Which recovery buys the most time per dollar: a second shift, a crew move or resequencing?

In the product

Where recovery money goes, decided each month

The Execute screen for a five-unit programme in construction, in the illustrative coastal refiner workspace. This month's actuals become a P80 cost and finish for each unit, and every way out is priced in money before anyone commits it.

  • Read from the systems of recordCost ledgers, progress and schedule exports arrive as your teams already keep them; nothing is re-keyed.
  • Every way out priced in moneySecond shifts, crew moves and resequencing are re-run on the same scenarios, so the cheapest recovery per week saved is plain.
  • Approved budgets go backOnce approved, the budget change and the re-phasing are sent back to the systems that run the job, with a tripwire to watch.

What Capibud produces

A monthly money decision, with the range attached

Earned-value measures are the starting point. Capibud blends them with a reference-class prior, simulates the risks that remain and checks the result against crew ceilings and calendar windows.

01

P80 cost and finish

For each unit and the programme, from correlated scenarios, with the chance of finishing within budget authority.

02

A money decision per unit

Fund recovery, price options, hold the budget or release money, with the reasons stated in plain terms beside each.

03

Contractor date checks

Reported milestone dates against Capibud's P50 and P80, and how far the reported date moved across recent reports.

04

Contingency coverage

Remaining contingency against the P80 need, with pending change orders simulated at their likelihood of being granted.

05

Priced recovery

Second shifts, crew moves and resequencing priced in money and previewed against shared crew ceilings before anyone commits.

06

Budgets sent back

Approved budgets, re-phasing and change orders follow the authority matrix with maker-checker, then go back to your cost and schedule systems.

Worked example

Phase 1 of an AI campus, sixteen months in

Illustrative demo — not client data

A synthetic hyperscale campus has six packages and a combined budget authority of $1,185M. At the September data date, CPI is 0.96 and SPI 0.95. Only 42% of 2,000 correlated scenarios finish within authority, and remaining contingency covers 73% of the P80 need.

The data-hall fit-out drives the finish: P80 about six months beyond target, at roughly $520,000 a day. Crews on that package are at 79% of what the work in hand needs, so the first recovery option to price is a second shift.

The same campus, from option choice to construction, is in the data-centre developer case.

Monthly review · September Synthetic workspace · USD
PackageBudgetP80 costP80 finishvs targetVerdict
Shell and core$176M$187MOct 2026Sep 2026Proceed
Long-lead electrical$228M$257MFeb 2027Dec 2026Recover
230 kV substation$106M$120MAug 2027Mar 2027Recover
Cooling plant$150M$177MMar 2027Jan 2027Escalate
Backup generation$96M$98MJan 2027Dec 2026Proceed
Data halls 1–3 fit-out$325M$392MFeb 2028Aug 2027Escalate

Illustrative demo — not client data. Synthetic execution history; one seeded engine run. Budgets are at award; package P80s do not sum to the programme P80.

Contractor dates vs Capibud P80 Days the report is earlier
Utility line ready230 kV substation114 days
Transformers deliveredLong-lead electrical105 days
Hall 1 energisedData halls fit-out60 days
Cooling commissionedCooling plant49 days

Bars scale to 120 days. A reported date is evidence; Capibud's P80 also reflects productivity, remaining risks and crews.

How it works

From the monthly pack to a priced recovery

1Read actualsCost ledgers, progress reports and schedule exports are read as your systems record them. Lines that mix cost roles are held for review.
2UpdateEarned value is blended with a reference-class prior, so one good or bad month does not swing the forecast.
3SimulateRemaining risks, interfaces between units and shared factors are simulated together; crew ceilings and calendar windows are applied.
4Price optionsRecovery options are re-run in the engine and shown with their cost, their effect on P80 finish and their effect on value.
5RouteRecovery money and change orders go through the authority matrix. Approval sends the budget and re-phasing back to your project systems, and can be undone.

What it connects to

Recovery money comes from the same envelope

A recovery plan is a capital decision. In the committee it competes with new projects and capex lines, and it often wins: protecting a committed programme is cheap value.

Committee

Recovery as a candidate

Extra crews or shifts are pooled with every other use of capital.

The capital committee
Evaluate

Back to the sanction

Overruns feed the reference class used for the next sanction.

Evaluate
Brain

Drift caught early

New actuals or a contractor's listed peer falling trigger a priced proposal.

The brain
Record

Every change order

Who approved what, on which forecast, is kept in the hash-chained log.

The record

Honest limits

What Execute does not do

Execute decides where money and recovery effort go. It works from what the site reports and your project systems record.

  • Your planners own the network. The critical-path schedule is built and kept by your planning team; Capibud reads it and puts a range on the result.
  • Files today, connectors on your credentials. Schedule exports (XER, XML), ERP extracts, Excel and CSV are read today; API connectors switch on with your own credentials.
  • What is recorded is what is ranged. If progress is over-reported, the forecast inherits it. Capibud flags inconsistencies; it cannot measure the site.
  • Productivity windows are inputs. Monsoons, festival leave and turnaround draws on crews are modelled as you describe them, labelled as estimates.

Bring us the project that keeps slipping.

A Decision Sprint can take one recovery plan from your monthly reports to a priced, routed decision in six weeks.

Talk to us →