What a site cost report should tell you, and what most of them do not
Most site cost reports answer one question — how much has been spent — and that is the least useful of the four questions that matter. A report built only on payments made tells you where you have been, at a point where the decisions it should inform have already been taken.
The four numbers
A site cost report that supports a decision carries four quantities, not one. Each answers a different question and they are routinely conflated.
| Number | Question it answers |
|---|---|
| Budget | What we said this would cost |
| Committed | What we are already contractually obliged to spend |
| Incurred | What has been consumed or billed to us, paid or not |
| Paid | What has left the bank |
What we said this would cost.
What we are already contractually obliged to spend. The one that gets omitted.
What has been consumed or billed to us, paid or not.
What has left the bank. Easy to produce, and the least useful on its own.
Committed cost is the one that gets omitted
Paid is easy to produce — it comes straight from the bank. It is also the furthest behind reality. By the time a payment clears, the decision that caused it was taken weeks earlier and cannot be revisited.
Committed cost is the useful one. A purchase order issued for steel is money spent, whether or not the steel has arrived and whether or not the bill has been paid. A work order awarded to a subcontractor is committed in full the moment it is signed. A report that shows ₹40 lakh paid against a ₹1 crore budget looks comfortable; the same project with ₹85 lakh already committed is not comfortable at all, and the difference between those two readings is the point at which something can still be done.
This is also the number that is hardest to produce, because it requires purchase orders and work orders to exist as records rather than as WhatsApp messages.
Why material cost is usually wrong
The common approach charges material to a site when it is purchased. That is the date the money moved, so it feels right, and it produces a site cost that is wrong in both directions.
Material bought for site A and used on site B charges the wrong project. Material bought in bulk across three projects charges whichever one was named on the bill. Material still sitting in the yard is charged to a site that has not consumed it.
Charging on issue rather than on purchase fixes this, and it requires a rate to charge at, since the same material was bought at different prices across the year. A moving average is the usual answer: each receipt updates the average, each issue is charged at the average on the day. It is not the only valid method, but it is the one that behaves sensibly when prices move and stock turns over, and it does not require tracking individual batches.
Returns need handling too. Material returned from a site should credit at the rate that site was charged, not at the current average — otherwise a return during a price rise hands the site a profit it did not earn.
Why labour cost is usually wrong
Two causes, both upstream of the report.
The first is the split day — a worker on two sites in one day, charged entirely to one. Over a month with a crew that moves, this redistributes a meaningful amount of cost between projects, always in the same direction: the site whose supervisor keeps the register best absorbs the cost of the one who does not.
The second is the loaded rate. A day of labour is not the base wage. It is the base, plus overtime at its own rate, plus holiday rate where it applies, plus allowances, plus the employer-side statutory costs that attach to permanent staff. A report built on base wages understates labour by a consistent margin, which is worse than a random error because it looks stable and therefore trustworthy.
Permanent staff are an allocation, not a site cost
A site engineer on a monthly salary who covers three projects does not have a site cost. The salary is a company cost, and any per-site figure is an allocation made on some basis — days present, floor area, contract value.
That allocation is legitimate for reporting and misleading for decisions. It should be visible as an allocation rather than merged into direct cost, because a project that looks unprofitable only after absorbing a share of head office salary is a different problem from one that is unprofitable on its direct costs, and the two call for different responses.
The report nobody reads
A cost report produced monthly, a fortnight after month end, describes a situation six weeks old. For a project running nine months, that is a report arriving after a fifth of the remaining time has elapsed.
The frequency that matters is not the report, it is the capture. If material issues, attendance and purchase orders are recorded as they happen, the report is a query and can be run on any day. If they are reconstructed at month end, no reporting frequency saves it.
Common questions
What is committed cost in a construction project?
Money the project is contractually obliged to spend but has not necessarily paid — issued purchase orders, awarded work orders, agreed subcontracts. It is a better early-warning indicator than spend, because it reflects decisions already taken rather than payments already cleared.
Should material be charged to a site when bought or when issued?
On issue. Charging on purchase misattributes material bought for one site and used on another, and charges a site for stock still sitting in the yard. Charging on issue needs a valuation rate, usually a moving average updated on each receipt.
How should salaried staff be costed to a project?
As a visible allocation rather than a direct cost. A salaried engineer covering three sites has no true per-site cost, so any figure is an apportionment. Keeping it separate from direct cost preserves the distinction between a project unprofitable in itself and one unprofitable only after overhead.
How often should a site cost report be produced?
The report frequency matters less than the capture frequency. If issues, attendance and orders are recorded as they happen, the report can be run on any day. If they are reconstructed at month end, the report is always describing a situation that has already moved on.