Why labour costs arrive too late to act on
- margin
- cost control
- companies
Ask a director when they knew a job was losing money, and the honest answer is often "when it was finished".
That is not a failure of attention. It is arithmetic about how the information moves.
Trace one day
Follow a single day of labour from the site to your screen.
- Monday. Four men work. The hours exist on a paper sheet, or in a supervisor's head, or in a message.
- Friday. The sheet is collected, if it is collected.
- The following week. It reaches the office and someone types it in.
- Month end. It is coded to a cost head and lands in the report.
- Two weeks later. You read the report.
Three to five weeks between the money being spent and the number reaching the person who can do something about it.
Why the delay is the whole problem
Nobody minds a report being three weeks old when the job is going well.
The trouble is that a job going wrong looks exactly like a job going well, for three weeks. The overrun starts on a Monday. You find out about it a month later. By then you have spent another month at the same rate.
An overrun you see in week two is a decision — change the gang, change the sequence, change the order. The same overrun at handover is a loss. Same money, and the only difference is when you found out.
Where it actually breaks
It is worth being precise, because the fix depends on which link is failing.
Capture. The hours are not recorded at the time. Everything downstream is then a reconstruction, and reconstructions are late and approximate.
Transport. They are recorded but they sit — in a van, in a thread, in a pile on a desk until someone collects them.
Coding. They arrive but nobody knows which project or which element they belong to, so they wait for a person who does.
Reporting. Everything is in the system, but the report runs monthly, so a cost from the 2nd waits four weeks for the 30th.
Most firms have a problem at capture and blame it on reporting. Buying better reporting does not fix a number that does not exist yet.
The test
There is one question that finds your real lag.
A bricklayer worked last Tuesday. On what date does that day appear against the project's labour cost, on a screen I can see?
If the answer is a specific date this week, your control is good and you should spend your attention elsewhere. If the answer is "month end" or "I would have to ask", you have found where your margin goes.
Ask the same question about a subcontractor day, and about plant on hire. The lags are usually different, and the longest one sets how blind you are.
What actually shortens it
- Record at the point of work. Not at the end of the week, and not by someone who was not there.
- Attach the project when the hour is recorded, not when it is coded. Coding later means guessing later.
- Look weekly, not monthly. A month-end cycle guarantees a month of blindness no matter how good the data is.
None of that is a software feature. It is a sequence. Software either supports it or gets in its way.
This is the problem VORDO was built for. Hours are recorded on site as they happen, against the project, and the cost lands against the budget the same day. Not in March. Register now and put a live job through it.