How often to report, and what changes when you do
A report that restates the same position in new formatting trains people to stop reading it. The movement is the content.
QScope Team · 9 July 2026 · 4 min read
Monthly reporting is the industry default, aligned to the valuation cycle, and for most projects it is the right answer. It matches the rhythm at which reliable information actually exists, and it gives a client something to take to a board meeting.
The question worth more attention is not how often, but what the report is for.
Two different documents
A cost report to a client answers: what will this building cost, is that different from last month, and what should I do about it.
An internal report answers: is this job making the margin we assumed, and where is it leaking.
They draw on the same data and they are not the same document. Sending the internal one to the client is a mistake people make once.
Movement is the content
The most useful line in any cost report is the comparison with the previous report and the explanation of the difference.
An anticipated final cost of £4.31m means very little on its own. An anticipated final cost of £4.31m, against £4.24m last month, with £70,000 of the increase attributable to three named instructions, means something immediately.
Reports that restate the position without explaining the change are the ones that stop being read, and then stop being produced.
When to break the cycle
Some events do not wait for the next report: a significant instruction, a variation that materially changes the outturn, an emerging risk that will move the contingency, a delay event with cost consequences.
Those warrant a short note when they happen. A client discovering a two hundred thousand pound movement three weeks after the decision that caused it, in a routine report, will reasonably ask why they were not told.
The cost of frequency
Reporting takes time, and the time comes out of the same budget as everything else. Weekly reporting on a project where the numbers move monthly produces three reports of noise for every one of signal, and consumes the hours that should have gone into agreeing variations.
The right cadence is the one at which the underlying information actually changes, plus exception reporting for anything that cannot wait.
What makes it sustainable
Reports assembled by hand from spreadsheets get produced late and then get produced less often. Reports drawn from the figures already being maintained get produced on time because producing them costs almost nothing.
That is the real determinant of reporting discipline, and it is a tooling question rather than a discipline question.
QScope builds each report from the same underlying figures, so the movement between two reports is a fact rather than a reconstruction.