62% of construction firms run estimating in a spreadsheet, so the takeoff should end in one.

JBKnowledge's 9th Annual Construction Technology Report found that 62 percent of construction firms run estimating on spreadsheets rather than estimating software. Estimating was the workflow most likely to be living in a spreadsheet, ahead of accounting and bid management. Takeoff itself was lower still, at 27 percent.

Most takeoff tools treat that as a problem to be fixed, usually by replacing the spreadsheet with a dashboard. I think that reads the situation backwards. I am 18 and I work in electrical preconstruction, and the spreadsheet on the senior estimator's second monitor is not a legacy system. It is where the labour rates, the fixture pricing from the supplier, the markup and the exclusions live, and he knows it cold. It has his own columns in it, from jobs that went well and jobs that did not.

A tool that insists on owning the estimate asks him to rebuild all of that inside somebody's web app before bid day. On a Thursday with an addendum landing, that is not going to happen. The number has to arrive where the pricing already is.

What LumenTakeoff does about it

So the output is a spreadsheet, on purpose. Lock in results produces one XLSX with four sheets. Coverage says which pages were counted, which were out of scope and which were unsupported, so nobody has to assume the whole set was read. Quantities is one row per fixture family with its scope state. Findings is what still needs a look. Evidence names where every number came from.

Before any of that is written, a reconciliation check runs. If the counts do not reconcile, the export is refused rather than handing over a wrong number in a tidy format. Alongside the workbook come proof images with every counted instance ringed on the sheet it sits on.

Naming can happen in Excel too. The offline naming sheet is an Excel file with the symbol crops embedded and the set's schedule codes on a second tab. Somebody fills in the type codes in the format they already type in all day, uploads it back, and the names apply to every member signature in each family.

The four figures stay separate when they land in the workbook: detected instances, production count, in bid scope, and how many times the schedule tag appears on the sheet, shown as a document-stated figure with its discrepancy rather than as a count. A spreadsheet is good at holding columns that should not be added together.

It is in the demo phase, tested against real electrical plan sets. The machine counts. You decide.

The machine counts. You decide.