Estimating with a gate: quantity take-off that cannot auto-confirm

Friday, late. The invitation closes Monday at noon. The drywall package is open on two screens: Bluebeam markups on the left, the Excel that will become the bid form on the right. An estimator has already told you the take-off is "basically done." The contingency cell looks reasonable. A few lines still say "check against Rev C," but Rev C arrived Wednesday and half the team measured Rev B. Somebody mentioned they ran a chat model overnight against a sheet PDF and pasted quantities into a tab labelled AI draft — verify. The draft looks complete enough to ship.

Your fear is not that you will miss the deadline. Your fear is that you will hit it — and discover after award that the package was short on the wrong trade, priced on last quarter's rates, or soft on contingency that never got named. Underquoting hurts longer than a slow bid. Bond conversations, margin recovery meetings, and the quiet question from the owner about how the number was built all arrive after the export button has already been clicked.

That is the preconstruction problem in plain language: the desk can produce something that looks finished long before it is defendable.

Two tools, one blind export

Most estimating desks still live in a familiar split. Measure in Bluebeam. Price in Excel. Quantities live as markups and markup summaries. Rates live in workbooks that drift between estimators, projects and weeks. Contingency is often a percentage someone typed because it felt right for this class of building — not a named policy line anyone can point to later.

Tools that accelerate measurement help with speed. STACK, Autodesk Takeoff and peers shrink the time from sheet to quantity. They do not, by themselves, create a structural inability to leave the building with an unfinished commercial commitment. The export still happens when a person decides the file looks ready. There is no machine-enforced gate that says: unconfirmed lines remain open, the rate book is not pinned, the estimate class is undeclared — therefore the bid package cannot leave.

Then there is the newer shortcut. An estimator pastes sheets into a personal chat model, asks for a take-off, and gets a table in minutes. It is fast. It is also fragile. There is usually no durable link from each line back to sheet and revision, no versioned rate book behind the pricing, no confirmation record of who accepted which quantity, and no audit trail that will survive a bid protest or a claims conversation. The speed is real. The unit of record is still a conversation and a spreadsheet tab.

If you are not an "AI person," that distinction matters more than the model name. You do not need another assistant that talks about quantities. You need a desk where a quantity cannot become a bid line without a human gate you can defend.

Finished is not the same as cleared

Underquote risk often hides in the gap between looks complete and cleared for export.

A package can look complete while AI-proposed lines are still unconfirmed — sitting in a draft tab, or already pasted into the bid form because someone cleaned the formatting. It can look complete while rates came from whichever workbook was open last Tuesday, not from a pinned, versioned rate book. It can look complete while contingency is a single soft cell rather than named policy lines. It can look complete while nobody has declared what maturity of estimate this is — the AACE-style question of class and basis that experienced chiefs ask instinctively and junior estimators skip under deadline pressure.

None of those gaps stop a file from leaving the folder. That is the structural failure. Review is a social process: ask hard questions if you have time; hope the team caught the soft lines if you do not. When the invitation clock is loud, social process loses to "ship it."

What changes the economics of underquoting is not a faster measure. It is a hard stop: the bid cannot export while those gates are open. Unconfirmed AI lines block export. A missing rate-book pin blocks export. An undeclared estimate class blocks export. The deadline still matters — but the system will not let "basically done" masquerade as released.

The package is the unit of record — not the chat

The durable object on an estimating desk should not be a markup session, a workbook tab, or a chat thread. It should be an estimate package: take-off lines, priced lines, contingencies, and drawing-revision pins held together as one versioned commitment.

Every take-off line should cite its measurement basis — which sheet, which revision, which method. When someone asks six months later why that partition quantity was what it was, the answer should not be "I think we measured the architectural set." It should be a pin.

Rates should come only from a versioned rate book pinned to the package. Suggestions from history or from a knowledge layer can sit beside the book as candidates. Applied rates should not float mid-bid because someone edited a personal workbook after lunch.

Contingency should appear as named policy lines — not an informal markup buried in a summary row. If the chief estimator applied a named allowance for incomplete wet-trade coordination, that fact should be part of the package, not tribal memory.

Drawing revisions should be pinned to the package so the bid is tied to the set that was measured. When Rev D lands after export, that is a controlled change story — not a silent overwrite of the open Excel.

That package is what preconstruction actually commits when it bids. Chat is a drafting surface. Spreadsheets are working paper. The record that has to survive award, protest, bond discussion and claims is the package.

Where the gate earns a name

This is the job of Quantspan: an estimating and take-off workspace where AI may propose quantities, but humans must confirm every AI-proposed line before the package can become a bid export — and where export is structurally blocked while review gates remain open.

AI accelerates the draft. It does not auto-confirm. Proposed lines enter a confirmation queue. Estimators accept, adjust or reject with reason. The queue is prioritised by dollar exposure and structural criticality — so the chief estimator's Friday review is not a flat checklist of every small line first. The lines that can underquote the job rise to the top.

On a live desk that looks like a package workspace: sheets and revisions pinned on one pane, take-off lines with measurement basis on another, a confirmation queue sorted by exposure, a pricing and contingency view that only applies rates from a versioned rate book, and a review-gates board that ages against the bid due date. Bid release is a separate act — BOQ/CSI, Excel, PDF summary and an audit package viewer with checksums tied to the package version — not “save the spreadsheet and email it.” Ad-hoc typed rates require an override reason. Superseded sheet revisions flag open lines that still cite them. Bluebeam markups and Planvector geometry import into the same take-off line schema, so familiar measuring tools do not fracture the bid record.

Measurement basis stays attached to each take-off line. Pricing binds to the pinned rate book. Contingency is applied as named policy. Estimate class is declared as part of clearing the package, not as a footnote someone might add if they remember. When gates clear, export produces the bid artefacts the market expects — together with who confirmed what, against which sheet and revision, against which rate-book version, with which contingency policy.

That audit trail is not a compliance decoration. It is what you need when a competitor protests, when a surety asks how the number was built, or when a later claim depends on whether the bid quantities were grounded or guessed.

Upstream, Planvector can feed revision-pinned geometry into the take-off so measure starts from accepted sheet identity rather than a loose PDF. Contextkeep can supply past-job rates and lessons into the rate-book conversation as governed candidates, not as silent overrides. Downstream, Awardbind and Baselinecast receive released packages when commercial administration and earned-value work need a priced commitment they can cite. Quantspan does not own field execution or contracts. It owns the gate between proposed measure and a bid you can stand behind.

What you should measure after the award

Bids per week is a throughput vanity metric if the wins destroy margin. The buyer KPI that matches the fear of underquoting is different: hit rate on target margin after award, and the variance between AI-proposed quantities and human-confirmed quantities over time.

The first number tells you whether the desk is protecting the commercial intent of the bid. The second tells you whether the confirmation queue is doing real work — catching soft proposals before they become priced truth — or whether humans are rubber-stamping under deadline pressure. If AI proposals and confirmed quantities never diverge, either the model is miraculously perfect or the gate is theatre. A healthy desk expects divergence, records adjustments, and uses that variance to tune where reviewers spend time.

None of that requires you to become an AI specialist. It requires you to treat confirmation as estimating work, not as a tech demo.

First cut on one painful package

Do not start with every trade and every bid form. Start with one package type — high volume, a clear rate book, and a painful Bluebeam-to-Excel handoff you already distrust on deadline nights. Stand up the estimate package lifecycle: AI quantity proposal into a human confirmation queue prioritised by exposure, one versioned rate book pinned to the package, named contingency policy, declared estimate class, and bid export that stays blocked until those gates clear. Keep Planvector in scope only if sheet-revision chaos is part of the underquote story. Keep commercial and field systems in their lanes.

Measure whether any package can export with open gates, how long high-exposure lines sit unconfirmed, and how AI versus confirmed quantities diverge on the first live bids. Scope that cut in a Solution Definition Sprint.

See AEC and built environment, explore Quantspan on the Atlas and Planvector, or bring us the package you almost shipped unfinished.