Blogconstruction estimate QA QC16 November 202615 min read

Construction Estimate QA/QC: A Pre-Bid Review Process

Construction Estimate QA/QC: A Pre-Bid Review Process ! Estimate review title card with sketched tools QA/QC on a construction estimate means two things working together: a process that keeps errors out of the estimate (quality assurance), and an independent review that catches the ones that got in anyway (quality control), both finished before the bid goes out.

QA/QC on a construction estimate means two things working together: a process that keeps errors out of the estimate (quality assurance), and an independent review that catches the ones that got in anyway (quality control), both finished before the bid goes out. The reliable way to run it is to read the full bid package, check the estimate in fixed layers, have someone who did not build it review it, and keep a record of what was found and fixed. ArosBid is built around that routine: it reads the entire set of bid documents, including front-end clauses, and automates error checking while the people on your team keep authority over what gets submitted.

arosbid
arosbid.com
Review Bids With Greater Confidence
ArosBid helps construction teams check bid documents, track compliance, and reduce the risk of errors before submission.
Visit

TL;DR

  • QA is the process that prevents estimate errors. QC is the independent review that finds the ones that remain. You need both before submission.
  • Scope gaps are the costliest misses because there is no arithmetic error to find. Review has to look for what is missing, not only re-check math.
  • Use a fixed sequence of checks: documents and addenda, scope, quantities, pricing and quotes, assumptions and exclusions, then the bid form and compliance items.
  • Assign a reviewer who did not build the estimate, and record who reviewed what, what they found and what was resolved.
  • Track disqualifications, win rates and preparation time so you can see whether the review is paying off.

Table of Contents

What QA/QC means for an estimate

The terms come from construction delivery, and they carry over to estimating with the same logic. San Francisco Public Works’ QA/QC plan describes quality assurance as the systematic process of checking whether work meets specified requirements while it is being developed, and quality control as checking that the finished product meets those requirements once a phase is complete.

The National Institutes of Health’s Office of Research Facilities applies this directly to construction documents in a July 2024 guidance note. QA focuses on preventing defects inside the team’s own process from the start of the project. QC is a review by experienced people who were not involved in producing the documents, including a page-by-page turn of everything, written documentation of discrepancies, a back-check that corrections were made, and a signed approval for release.

For an estimate, the mapping is straightforward:

QA (prevent) QC (detect)
When From the moment you decide to bid After the estimate is assembled, before submission
Focus The process: templates, standard assumptions, takeoff conventions, who owns which trade The result: quantities, prices, scope and bid form
Who The whole estimating team A reviewer independent of the estimator
Output Fewer errors enter the estimate A documented list of findings, fixes and a sign-off

The NIH note also makes a point worth keeping: effective QA reduces the time and effort the later QC step takes, and the scale of QC should match the project’s complexity. A small repeat job and a hospital package do not need the same review depth.

This article is about the estimate and bid package. It does not cover field inspections, test plans or construction-phase quality control.

Where estimates actually go wrong

The recurring failures are less about arithmetic than about inputs and omissions:

  • Superseded information. Quantities taken from an old drawing revision, or an addendum that never reached the person pricing the work.
  • Missing scope. Work that is required but priced nowhere, often because it is spread across drawings, specifications and front-end documents.
  • Stale or mismatched quotes. A vendor quote that was valid when entered but expired, excluded something, or covered a different scope by the time of submission.
  • Unstated assumptions. Productivity, access, delivery and disposal assumptions that live in one estimator’s head.
  • Bid form and compliance misses. A required form, bond, acknowledgment or clause response left out, which can lead to disqualification before price is even looked at.

Scope gaps deserve the most attention. They are the hardest to catch because a missing line item produces a clean-looking total. Reviewers who only re-check calculations will pass the estimate. The check has to compare the estimate against a list of what the job should contain, such as a CSI division checklist, and ask what is not there. A good example of how this plays out at the drawing level is this list of common structural drawing omissions: items that are required but not shown are exactly the ones that slip through takeoff.

The cost of getting this wrong is large. A presentation at the 2025 Signatory Contractors Conference, The Power of Estimating, cites FMI Corporation’s finding that 35% of construction change orders come from scope errors. The same presentation cites a US study that puts average hard-bid win rates at 10 to 12% and estimating costs at 3 to 4% of revenue. At those rates, a bid lost to an avoidable disqualification or a bid won with a missed scope item both waste real money.

A review sequence that works

The most useful structure is a fixed order of layers, so every estimate is checked the same way regardless of who built it or how close the deadline is. Here is a sequence for a trade or general estimate.

Six stages of pre-bid estimate review

1. Documents and addenda

Confirm the estimate is built on the current drawing set and specification revisions, and that every addendum has been logged and read by whoever priced the affected trade. The failure mode is quiet: the takeoff is accurate, but for a sheet that was replaced. Keep a bid-day log of addenda, with the date received and who acknowledged it. Our guides on addendum management and addenda tracking on bid day show how to set that up.

This is also where front-end documents get read: instructions to bidders, general and supplementary conditions, and submission requirements. Clauses buried there decide whether your bid is accepted. ArosBid reads the full document set, including those front-end clauses, and flags conflicts between documents before you commit to a number.

2. Scope

Compare the estimate against the scope you are supposed to cover, trade by trade. Use a division checklist and walk through it looking for omissions. Items that are commonly required but not drawn include testing and balancing, commissioning support, temporary utilities, firestopping at penetrations, start-up and training, and closeout documentation. These examples come from an MEP-focused checklist, but every trade has its own list.

Also check the interfaces. Work that sits between two trades is the most likely to be priced by neither.

3. Quantities

Verify takeoff scale, units and sheet references. Cross-check major quantities with a second method, for example a quick order-of-magnitude calculation or a comparison to a similar past job. A 10% error in material quantities on a $1 million project is $100,000 of exposure, so the biggest quantity lines should always get a second look.

4. Pricing and quotes

Check that unit rates are current, that borrowed rates from past jobs have been updated, and that every vendor quote is within its validity window on the day of submission. Compare each quote against the scope it was meant to cover and confirm its exclusions are either carried in your estimate or covered by another quote. Quotes for the same package rarely cover the same scope, which is why a side-by-side comparison matters. Our quote comparison matrix gives trade templates for it.

A common pitfall here is timing. A quote can be correct when it is entered into the estimate and expired by the time you submit. Build a quote date and validity check into the final pass, not just the first.

5. Assumptions, exclusions and clarifications

Write assumptions down. Productivity, working hours, access, delivery, mobilization, disposal and temporary conditions should each appear as an explicit line in the estimate or the proposal. Check that every answer you received to a bidder question has been priced, and that exclusions in the proposal match what the estimate actually leaves out.

One technique that sharpens this step is asking the estimator to list the conditions that would make the estimate badly wrong: a hidden scope gap, a weak labor assumption, an expired quote, a quantity taken from the wrong revision, unverified access or delivery. If the list is empty, the review was not honest.

6. Arithmetic, summary and bid form

Check that the summary matches the detail, markups and taxes are applied consistently, contingency is deliberate, and the numbers on the bid form match the estimate. Then run a pass/fail check on every submission requirement: forms, signatures, bonds, insurance certificates, acknowledgments of addenda, and any specific format or deadline instructions. Our bid compliance checklist puts the pass/fail items first, because a missing mandatory item can end the bid regardless of price.

For a longer version of the whole sequence, see our 3 stage estimate review checklist and our list of 10 bid checks that reduce estimating errors.

Who reviews, and how to document it

The single biggest improvement to a review is independence. Authors are poorly placed to see their own assumptions, which is why the NIH guidance calls for QC by experienced people who were not involved in producing the work. In an estimating team, that usually means a peer checks a junior estimator, and a senior estimator or chief estimator looks at the result before it goes out. Scale this to the job. A small bid may need one second reader. A large institutional package may justify several reviewers by trade or an outside reviewer.

Then make the review leave a trail. The Texas Department of Transportation’s San Antonio District procedure for reviewing and documenting construction estimates (May 2025) requires a named cost estimate review checklist for each milestone submittal, with proof of the review, such as redlines, saved alongside it under a matching file name. You are not a state agency, but the principle carries over: review evidence is part of the estimate record.

A workable minimum for each bid:

  1. A checklist completed per layer, with the reviewer’s name and date.
  2. A findings log: what was found, who owns the fix, and whether it was resolved.
  3. A back-check that the fixes were made, not just agreed.
  4. A sign-off before release, by the person who has authority to submit.

When the review finds a missing activity, fix the cause as well as the bid. Add the item to the template or checklist so the next estimate starts with it already there.

Making it fit your existing tools

Most estimating teams already live in Excel, Outlook, a takeoff package and a project management system. A review process that requires abandoning them will not survive bid season. The practical approach is to keep those tools as the place the work happens and add one control layer on top that tracks four things:

  • Which documents and addenda have been received, and which have been read.
  • Which vendor quotes are in, leveled and still valid.
  • Which checklist layers have been completed and signed.
  • What remains open before the submission deadline.

Spreadsheets can hold a checklist, but they do not read a 600-page specification and they do not tell you that an addendum arrived in someone’s inbox and was never acted on. That is where a purpose-built layer helps. For more on setting up one gate in the workflow, see our guide on making estimating auditable with one review gate.

Measuring whether QA/QC is working

A review process earns its time only if you can show a result. Track a few numbers per bid and per quarter:

  • Disqualifications and non-compliant bids. Count them and record the reason each time. A recurring cause points to a checklist gap.
  • Findings per review, by layer. If most findings are in documents and addenda, fix intake. If most are in scope, improve your division checklists.
  • Win rate and hit rate by package type. The conference presentation cited above puts average hard-bid win rates at 10 to 12%, which gives you a baseline for comparison.
  • Preparation time. Note how many days each bid had and how many hours the review took.
  • Post-award variances. When a won job comes in over or under, trace the difference back to the estimate and log it. This is the debrief that keeps QA improving.

The same presentation cites an Associated General Contractors finding that detailed reviews increase estimating accuracy by 25%. Treat that as a reason to invest in review depth, then measure your own results against your own history.

How ArosBid supports the routine

ArosBid is bid management and estimating software for construction trades. It covers automated document review, compliance checks, takeoff, estimate, vendor quote tracking and leveling, bid/no-bid evaluation, proposal assembly, buyout and debriefing, so the review layers above sit inside one flow instead of across scattered files. It integrates with Excel and Outlook, as well as major takeoff, cost and project management tools, so your team keeps the tools it already uses.

What we think about estimate QA/QC

We see estimate QA/QC as a document problem first and a math problem second. Most disqualifications and costly misses start in the paperwork around the estimate: a clause in the front end that conflicts with the specifications, an addendum that changed the scope, a quote that does not cover what the drawings require.

That is why our approach reads the entire bid package, not just the drawings or the spreadsheet. Automation is good at reading every page and flagging conflicts and missing items. People are good at judgment: whether to bid, how to price risk, what to exclude. We built ArosBid so the software does the checking and your estimators and managers keep the authority over what is submitted.

We also think the review should not end at submission. Running the full cycle from intake through buyout and debrief means the findings from each bid feed the next one, and the checklist gets better with every job.

arosbid team

See it on your next bid

If your team is ready to put a structured review in front of every submission, ArosBid’s construction bid management software runs the bid cycle from document intake through compliance checks, quote leveling and proposal assembly. Estimators can start with the estimating software for trade estimators, and the pricing page lists the One Desk, The Department and The Whole Year plans.

arosbid

FAQ

What is the difference between QA and QC on a construction estimate?

QA is the set of practices that prevents errors: templates, standard assumptions, takeoff conventions and clear ownership. QC is the independent review of the finished estimate that finds the errors that remain. Strong QC with weak QA means you find many defects late, while strong QA means fewer defects exist to find.

Who should review a construction estimate before submission?

Someone who did not build it. A peer can check a junior estimator’s work, and a senior estimator or chief estimator can review before sign-off. The reviewer should record what was found and what was fixed, and the person with authority to submit should approve the final version.

What should an estimate QA/QC checklist include?

At minimum: current drawings, specifications and all addenda; scope checked against a division list; quantities verified; current rates and valid vendor quotes; written assumptions and exclusions; arithmetic and summary consistency; and a pass/fail check of every bid form and submission requirement. Add trade-specific items for the work you price.

How long does an estimate review take?

It depends on the size and complexity of the bid, so scale the review to the job. Build the review into the schedule rather than squeezing it into the last hours before the deadline. Late reviews tend to become math re-checks, which miss scope gaps and stale quotes.

Can we run estimate QA/QC without changing our software?

Yes. Keep Excel, Outlook and your takeoff and project tools as the places where work happens, and add a layer that tracks documents, addenda, quotes and review sign-offs. ArosBid is designed to integrate with those tools rather than replace them.

Sources

Claims about ArosBid describe how the product works. Pursuits, companies, and prices named in examples are fictional demo data.

Book a live demo
NextDBE Requirements for Construction Bids: 2026 Guide