A schedule says nothing about money. Three numbers per work package — budget, physical percent complete, actual cost — and the forecast for the whole project appears while there is still something to do about it.
One row per package, in the same cut your actual costs are recorded in. Physical percent means measured progress — tonnes welded, metres of pipe, metres of cable, m² coated — not a percentage given by eye.
This page runs entirely in your browser. What you type is saved on this device only — so a refresh does not lose your figures — and never reaches any server: no upload, no email, no analytics. Save the file and it works with no connection at all.
| Work package | Budget | Physical complete, % | Actual cost to date |
|---|
The total hides which package is bleeding. This table does not.
| Package | Value performed | Spent | CPI | Forecast | Variance |
|---|
This page computes cost, not schedule. The schedule index (SPI) needs a planned value curve — what should have been earned by today — which is a different input and is not asked for here. It is left out deliberately: the documented case this page is built on had a perfect schedule index and lost €2.1 million anyway.
The forecast assumes the cost performance so far continues. That is the standard assumption (EAC = BAC ÷ CPI). If you know a specific reason the rest will run differently, the forecast is a floor to argue with, not a verdict.
Percent by eye destroys the whole calculation. A progress figure produced to match the milestone gives an earned value that matches the milestone. The indicator has to be countable by someone who is not being measured by it.
If you cannot fill this table — that is the finding. It means the yard holds two of the three rows of data (planned budget, actual cost) and cannot tell "on time" apart from "on budget" until the project closes.
This is one reading, taken by hand today. The same count can run by itself on a project you have on the floor now: the documents your yard already produces go to one place, and every week the count comes back — leak by package, forecast to completion — without anyone stopping to take a measurement.