Your cost report is five months too late
Everything in this track has been about knowing what a job has cost. But by the time a cost is a cost, it has already happened. The money is spent. The report tells you where the body is buried, not that somebody is in danger.
There is one number that turns earlier — weeks earlier, sometimes months — and last week's single record is what finally lets you calculate it.
Once the hours and the tonnes live on the same line, you can divide one by the other. And that number is the closest thing project controls has to an early warning system.
It is called productivity, and almost everybody measures it upside down.
Flip the ratio
Ask a site manager how his gang is doing and he will tell you tonnes per day. Five tonnes a day, good. Two and a half, bad. Output per unit of time — it feels natural, and it is nearly useless, because a good day and a bad day sit close together and the trend is hard to see.
Turn it over. Measure hours per tonne.
The plan was five tonnes a day from a gang working forty man-hours a day — eight man-hours to fix a tonne of steel. The gang is fixing two and a half tonnes a day from the same forty man-hours. Sixteen hours a tonne.
The ratio between them is the productivity factor: sixteen over eight, 2.00. It is taking exactly twice the labour to build a tonne of this structure as the estimate allowed. That single number is the cleanest statement of what has been wrong with this job since Week 2, and it does not blend, average, or hide inside anything. Above 1.00 is money walking off the site, one tonne at a time.
Earned hours
Now do to hours what earned value did to money.
Earned value took the work you completed and priced it at the plan's rate. Earned hours does the same in labour: the work you completed, costed at the plan's hours. You placed 114 tonnes. At the planned eight hours a tonne, that work was worth 912 man-hours. That is what you earned.
What you spent was sixteen hours a tonne — 1,824 man-hours.
Earned hours over actual hours is 0.50. A performance factor of a half: every man-day on that wall bought half a day of planned work. And you have seen those exact numbers before — 22.8 gang-days earned against 45.6 spent, straight from Week 8. This is that paradox again, but told in the one currency a site agent can act on before breakfast.
Because that is the point of hours. Material is a price you argued over once, months ago, and it is fixed. Plant is a hire rate. But labour is a fight you have every single morning — who is on the deck, how many, doing what, how well — and it is where jobs are won and lost. The performance factor is the CPI of the one thing you can still change today.
And the money agrees. Those 912 wasted hours, at $28.80 a man-hour, are $26,266 — which is, to the dollar, the labour variance we split out of the overrun back in Week 6. Same loss, reached three different ways, closing on the same number every time. That is what an integrated system feels like when it is working.
“Cost tells you what happened. Productivity tells you what is happening. One is a post-mortem; the other is a pulse.”
— WHY THE HOURS COME FIRST
By the time it is a cost, it is history. The hours are today.
Why it leads
Here is the reason productivity is worth more than any other number on your report: it turns first.
In the very first week the gang started on that wall, the performance factor was 0.50. Not drifting towards it — already there. A slow gang is slow on day one, and if you are measuring hours per tonne you know it on day one.
The CPI, meanwhile, takes months to admit the same thing. It has material in it, bought at a price that looked fine. It has plant. It has the smoothing effect of a big control account. So it drifts — 0.95, 0.90, 0.84 — gently, deniably, until around month six the trend is finally undeniable and everyone agrees there is a problem. Five months after the hours told you.
Everything downstream of productivity is lag. The productivity factor is the leading edge, and on this job it was screaming from the first week that the gang was half as fast as the estimate assumed. Nobody was listening to the hours, so everybody waited for the cost.
What actually moves it
A performance factor of 2.00 is a symptom, not a cause, and the causes are boringly physical. Congestion — too many trades on one deck. Access — the gang waiting for a crane shared with three others. Rework — the six tonnes cut wrong from late detailing, done twice. Information — bar schedules arriving the morning of the pour instead of the week before. Supervision, morale, weather, a gang that is simply too big for the face it is working.
None of those appear in a cost report. All of them appear in the hours, immediately, and every one of them is something a site manager can attack this week rather than explain next quarter. That is the entire value of measuring productivity: it points at a cause while the cause is still standing on the deck.
Practical insight
Pick your most labour-intensive activity and work out two numbers from the last month: the hours booked to it, and the quantity it produced. Divide. That is your hours per unit. Put the estimate's figure next to it.
If the actual is worse and you did not already know — did not know last week, in real time, without doing this calculation — then you are running your labour off the cost report, which means you are running it five months late.
Then ask the harder question: is anyone on this project looking at hours per unit every week? If the answer is no, your earliest warning system is switched off, and you are waiting for the cost report to tell you something the foreman's timesheet knew in the first fortnight.
Key takeaways
✔ Cost is a post-mortem — by the time it is a cost, it has happened. Productivity is a pulse, and it turns weeks to months earlier.
✔ Measure hours per tonne, not tonnes per hour. Flipped, the problem cannot hide.
✔ Planned 8 hours a tonne became 16. The productivity factor is 2.00 — twice the labour per tonne.
✔ Earned hours is CPI for labour: 912 earned against 1,824 spent is a performance factor of 0.50.
✔ That is Week 8's 22.8 vs 45.6 gang-days, restated in the unit a site manager can act on today.
✔ 912 wasted hours at $28.80 is $26,266 — exactly Week 6's labour variance. Three routes, one number.
✔ The factor was 0.50 in week one; the CPI took five months to admit it. Productivity leads, cost lags.
✔ It points at physical causes — congestion, access, rework, information — while they are still on the deck.
What is coming next
That is Phase C closed. You can measure what a job has cost, what it has produced, and how hard it is working — the complete picture of the project as a machine for turning money into structure.
But a project is not only a machine. It is a business, and a business does not run on cost. It runs on cash — and cost and cash are not the same thing, as anyone who has ever been profitable and insolvent in the same month will tell you.
Next week Phase D opens with the two curves that decide whether a contractor survives: the money going out, and the money coming in, and the terrifying gap between them.
Enjoyed this lesson?
Join with Google to get each new lesson the moment it's published — and help me see which topics matter most to you. No spam, one email a week, unsubscribe anytime.
Already following on LinkedIn works too — this is just for the weekly email.