01
Two people, one number
The moment a site supervisor, a QS and the MD each need the current figure, a file that lives on one laptop starts producing three answers. The reconciliation meeting is the tax you pay for that.
SPREADSHEETSExcel is not the problem.
Excel is not the problem.
Outgrowing it quietly is.
Spreadsheets fail a contracting firm at a predictable point: when more than one person needs the same number at the same time, and when the number has to be defended later. Below that point Excel is cheap, flexible and entirely reasonable. Above it, the cost is not licence fees — it is claims assembled the night before, variations never billed, retention nobody chased, and a version history that cannot survive a dispute.
THE FOUR BREAKPOINTS
You can name the day it stopped working.
02
The number has to be defended
A claim queried by the S.O., a subcontractor disputing what was certified, an audit asking how a figure was reached. A spreadsheet stores the result, not the reasoning — and rarely who changed what, when.
03
The same data is re-keyed
Measured work re-typed into a claim, the certified figure re-typed into an invoice, the invoice re-typed for e-invoicing. Each hop is a chance to be wrong, and each correction has to be chased through every downstream copy.
04
Work happens away from the desk
Progress, photos and quantities are captured on site. If the record only exists in a file back at the office, it gets reconstructed from memory on a Friday — which is exactly when it gets rounded.
WHERE THE MONEY ACTUALLY GOES
Not in the spreadsheet. In the gaps between them.
A variation instructed on site and never billed. Retention on a finished job nobody chased. A claim that sat three extra days because the file was on someone else's laptop. A supplier invoice that did not match the delivery, discovered after payment.
None of those are spreadsheet errors. Every one of them is a handoff nobody owned.
SIDE BY SIDE
Honest about both columns.
| Spreadsheets | Moorstack | |
|---|---|---|
| Cost to start | Effectively nil | A build fee |
| Flexibility to change | Immediate | Scoped, then built |
| Several people, one current figure | Manual reconciliation | One record |
| Who changed a figure, and when | Rarely recoverable | Audit trail |
| Claim built from the site record | Re-keyed | Assembled |
| Variation claimed or missed | Depends on memory | Tracked against the BQ |
| Retention chased | Depends on memory | Carried on the record |
| Statutory deadlines computed | Manual, if at all | Computed, provision cited |
Two rows genuinely favour spreadsheets. We have left them in.
The claim side of this is covered in more detail under JKR progress claims, and the statutory clocks under CIPAA payment deadlines.
COMMON QUESTIONS
Including when to stay put.
Is Excel actually bad for a construction company?
No. For a small firm running one or two jobs with a single person holding the figures, Excel is cheap, flexible and hard to beat. The honest question is not whether Excel is bad but whether your firm has passed the point where a single-owner file still works — usually when several people need the same current number, and when figures have to be defended to an S.O., a subcontractor or an auditor.
What actually goes wrong with spreadsheet-based claims?
Three things, repeatedly. The claim is assembled the night before from a measurement book, a WhatsApp group and last month's file, so it takes days and arrives late. Variations instructed on site never make it onto a claim because nobody was tracking them against the bill of quantities. And when the S.O. queries a figure, there is no trail showing how it was reached, so the query costs another cycle.
Can't we just use better spreadsheets?
Often yes, and for a while that is the right answer — shared cloud files, locked formula cells, a naming convention. What structure cannot fix is that a spreadsheet stores a result rather than a reasoning, and that every downstream copy has to be corrected by hand when an upstream figure changes. If your firm is losing money in the gaps between documents rather than inside any one of them, more spreadsheet discipline will not reach it.
What does Moorstack do differently?
The record is entered once and every module reads from it, so the job, the claim, the invoice, the subcontractor account and the audit trail cannot disagree. The platform never writes a figure your QS did not enter — it stores it, formats it, and shows its arithmetic. What you gain over a spreadsheet is not cleverness; it is that the same number appears everywhere and can be explained afterwards.
Do we lose flexibility by moving off spreadsheets?
Some, and it is fair to say so. A spreadsheet can be restructured in five minutes; a platform is scoped and then built. That is why each Moorstack build is mapped to one firm's actual workflow rather than forcing a generic product on you — and why the scope is agreed in writing before anything is built. If a firm's processes are still changing weekly, it is usually too early.
When is it too early to move?
If one person holds all the figures and that works; if you run a handful of jobs a year; if nobody has ever queried a claim you could not explain; if cash timing is not a problem. Those are honest signs to stay where you are. We would rather tell you that on the call than sell you a build you do not need yet.
BEFORE YOU MOVE
We'll tell you if it's too early.
Thirty minutes with both founders on one of your real workflows. If spreadsheets are still the right answer for your firm, that is what you will hear.