Two estimators can look at the same drawings and come back with two different numbers. One of them measured the job. The other one had a feel for it, based on the last few jobs that looked roughly similar. Only one of those numbers is actually built on the job in front of you, and that's the role of data in cost estimating in one sentence: the number is only as good as where its quantities came from.
That's the whole argument, really. Everything else is detail.
A guess is still a guess, however confident it sounds
A confident estimator can make a rough number sound certain. But confidence isn't accuracy, and a quantity scaled up from memory doesn't become more reliable because it was delivered without hesitation.
If nobody measured the substructure off the drawings, nobody actually knows how much concrete the job needs. They know how much a similar job needed, which isn't the same thing. The foundations might be deeper. The footprint might have a stepped bit. The drawings might show a thickened slab under a new wall that the last job didn't have.
The role of data in cost estimating, in plain terms
When people talk about the role of data in cost estimating they often mean software, databases and dashboards. Those have their place, and on big schemes with a team of estimators they can save a lot of time. But on a real job, the data that decides your price comes in a few plain forms:
- Measured quantities. Metres, square metres, cubic metres and numbers of items, taken off the drawings for this job. The foundation of everything else.
- Current rates. Labour, material and plant rates that reflect the market now, in the region where the job is.
- Your own cost history. What similar work actually cost you on past jobs, recorded in a way you can compare.
- The specification. What the architect or client has actually asked for, which decides which rate belongs against which quantity.
- Known site conditions. Access, storage, working hours, neighbours. They don't show on a floor plan, but they show up in the cost.
Of all of those, measured quantities come first because they're the one piece you can't borrow from another job. Rates can be checked against the market. Your history can be looked up. The quantities have to come off these drawings.
What measuring off the drawings actually changes
When quantities are taken off the drawings element by element, to NRM2, the number in front of you reflects this job, not a job that looked a bit like it. Groundworks, superstructure, finishes, external works, each measured against what's actually shown, not what usually gets used on a build this size.
It also changes what you can do with the estimate afterwards. A measured quantity can be checked. If the client's QS queries the blockwork, you can point to the drawing and the measurement. If a variation comes in, you know what the original quantity was, so you can price the difference. A guessed figure gives you nothing to point at.
Here's a simple hypothetical. Say you're pricing a rear extension and you allow for the blockwork by feel, based on the last one you did. The last one had a single window. This one has bi-fold doors across most of the back wall and a tall corner window. The measured blockwork is noticeably less, but the lintels, the steel and the cavity closers go up. A feel-based number gets both of those wrong, in opposite directions, and you won't know which way the total has moved until you're ordering materials.
Get the quantities right and the rest is arithmetic. Get them wrong and no amount of polish on the final document saves you.
Why this matters more than which software did the sums
There's a lot made of tools and spreadsheets in this trade, and some of them are genuinely useful. None of them fixes a quantity that was wrong to begin with. A digital takeoff tool will measure what you click on. It won't tell you that you missed the drainage run on the second sheet. A spreadsheet will multiply correctly. It won't know the rate you typed in is two years old.
Software makes good data faster to handle. It doesn't create it. The same goes for published cost guides: handy for a sense check, but they describe an average job, and averages don't have your site access, your ground or your client's spec.
Your own history is data too
The one data source most contractors underuse is their own finished jobs. If you record what each element actually cost, in the same order you priced it, you build up a picture no published guide can give you: your costs, your trades, your region. It's the best sense check there is for a new price, and there's a practical approach to it in sense checking a price against your own job history.
That only works if the original estimates were measured and broken down properly. A lump sum from five years ago tells you nothing about what the roof cost. This is the part of the role of data in cost estimating that pays back over years rather than on a single tender: each properly measured job makes the next price easier to check.
For our part, we measure every job off your drawings, to NRM2, so the quantities you're pricing from are the job's actual quantities, not a rough idea of them. Rates go on at current UK prices, local to the job. What comes back is a breakdown you can check line by line against the drawings.
A simple test for any estimate
Pick any line in the estimate and ask where its quantity came from. If the answer is a drawing reference and a measurement, it's data. If the answer is "that's about what it usually is", it's a guess, however neatly it's been typed up.