Skip to main content
Brickato logoBrickato
PricingBlogContact
Log InOpen app
Brickato logoBrickato

Build Smarter, Brick by Brick.

Product

DiscoverPlanExecuteMonitorCompleteHandoverView all productsPricing
Comparevs Autodesk Formavs ConWizevs Fieldwirevs Procorevs Togal.AIvs TrunkTools

Company

AboutBlogContactFree trial

Connect

LinkedInFacebook
Privacy PolicyTerms of ServiceAre you an AI agent? See this page in plain text

© 2026 Brickato. All rights reserved.

Compare Subcontractor Bids Without Missing Exclusions
  1. Home
  2. Blog
  3. Compare Subcontractor Bids Without Missing Exclusions
Back to Blog
bid comparisonsubcontractorsscopepreconstructiondocument intelligence

Compare Subcontractor Bids Without Missing Exclusions

Compare subcontractor bids on equal scope by normalising exclusions, qualifications, alternates, programme, and commercial risk.

B
Brickato Editorial TeamAugust 9, 2026 · 9 min read

Quick Answer

To compare subcontractor bids properly, build one common scope baseline from the tender documents. Break each submission into inclusions, exclusions, qualifications, alternates, quantities, programme commitments, and commercial terms. Then normalise the offers by pricing missing scope and recording risk allowances.

Do not select on the submitted total alone. Compare the likely delivered cost of an equivalent scope, with every adjustment traceable to the source.


Table of Contents

  1. Start with the client's requirement
  2. Build a common comparison structure
  3. Make exclusions visible
  4. Normalise quantities and alternates
  5. Compare programme and delivery
  6. Review commercial qualifications
  7. Separate price from confidence
  8. Hold a focused clarification meeting
  9. Where AI helps
  10. Bid comparison checklist
  11. Frequently asked questions

Bid A is 8 percent cheaper.

It also excludes access equipment, testing, temporary protection, design coordination, and weekend work.

By the time those items are added back, it is no longer the cheapest bid. It may not even be the second cheapest.

The problem was not arithmetic. The problem was comparing totals before comparing scope.

Start with the client's requirement

The comparison should not begin with the subcontractors' spreadsheets. It should begin with the tender scope.

Create a baseline from the drawings, specifications, BOQ, schedules, addenda, and clarifications. Organise it into work items that can be marked as included, excluded, qualified, or unclear for each bidder.

For a facade package, the baseline might include:

  • Design responsibility and calculations
  • Primary cladding and support system
  • Insulation, membranes, and fire barriers
  • Sealants, flashings, and interfaces
  • Access, scaffolding, and lifting
  • Samples, mock-ups, testing, and certification
  • Protection, cleaning, and handover documents
  • Programme, sequencing, and coordination

Without a common baseline, each bidder defines the package differently and the comparison rewards whoever omitted the most.

Build a common comparison structure

Use the same columns for every submission.

Comparison areaBidder ABidder BBidder C
Submitted price
Scope inclusions
Exclusions
Qualifications
Quantity basis
Alternates
Programme
Design responsibility
Testing and certification
Commercial departures
Normalisation adjustments
Risk allowance
Evaluated total

An empty cell is not a confirmation. Mark it as unclear and resolve it.

Make exclusions visible

Exclusions often sit at the end of a proposal, outside the pricing table. Some are explicit. Others appear through phrases such as "by others," "if required," "subject to design," or "not included unless noted."

Group exclusions into three categories:

Known missing scope: The tender requires it and the bidder clearly excludes it.

Conditional scope: The bidder includes it only under a stated condition that may not match the tender.

Unclear scope: The submission is silent or uses wording that prevents a reliable conclusion.

For each item, decide whether to:

  • Request confirmation
  • Add a normalisation value
  • Carry a risk allowance
  • Allocate the item to another package
  • Reject the departure

Do not quietly fill gaps with optimistic assumptions. Make the adjustment visible in the comparison.

Normalise quantities and alternates

Two bidders can price the same work against different quantity bases.

One uses the BOQ. One performs its own takeoff. A third offers a lump sum but excludes quantity growth. Their totals are not directly comparable.

Record:

  • Quantity source and revision
  • Measured quantity by major item
  • Rate structure
  • Treatment of provisional quantities
  • Remeasurement terms
  • Included waste factors
  • Currency, tax, escalation, and validity assumptions

Keep base scope separate from alternates. A lower-cost alternative may be valuable, but it should not make a non-compliant base bid look cheaper. Compare compliant offers first, then assess alternates on their own merits.

Compare programme and delivery

Price can be neutralised by delay.

Ask every bidder for:

  • Mobilisation period
  • Design and submittal duration
  • Long-lead procurement items
  • Production capacity
  • Installation sequence and crew assumptions
  • Testing and approval lead times
  • Required access and predecessor work
  • Ability to meet phased or sectional milestones

A bidder with the lowest evaluated total may still create programme exposure if its lead time does not fit the project sequence.

Do not convert every delivery risk into a number. Some risks should affect selection, negotiation, or management planning even when the commercial value is uncertain.

Review commercial qualifications

Commercial departures can change the value of an offer without changing its headline price.

Compare:

  • Payment terms and retention
  • Bonds and insurance
  • Warranty period
  • Delay and performance liability
  • Design responsibility
  • Price validity and escalation
  • Change valuation rules
  • Limits of liability
  • Proposed contract amendments

Route material departures to the commercial or legal owner. A bid comparison is not legal advice, and a spreadsheet should not hide a contractual position that requires approval.

Separate price from confidence

An evaluated total is useful, but it can create false precision.

Add a confidence view beside the number:

Confidence areaHighMediumLow
Scope completenessClear inclusions and exclusionsMinor open itemsMajor ambiguity
Quantity basisVerified and alignedSome assumptionsMaterial mismatch
ProgrammeDemonstrated and achievableNeeds confirmationConflicts with project dates
Commercial positionLargely compliantNegotiable departuresMajor unapproved departures
Evidence qualitySources attachedPartial supportUnsupported statements

This does not replace judgement. It prevents a neat total from disguising an incomplete bid.

Hold a focused clarification meeting

Do not spend the meeting reading the proposal back to the bidder.

Send the open comparison items in advance. Use the meeting to confirm scope boundaries, close qualifications, and understand delivery assumptions. Record every answer and request a revised written submission where the answer changes the offer.

Verbal confirmation should not be the final basis of selection.

Where AI helps

Subcontractor comparison requires the team to read several submissions against the same tender package. Each bidder uses different headings, terminology, and levels of detail.

Brickato's tender analysis platform can compare uploaded packages, search across exclusions and qualifications, and return answers with page-level citations. The source links let the estimator verify exactly where each bidder included, excluded, or qualified an item.

Useful questions include:

  • Which bidders exclude testing required by specification section 08?
  • Where do the three facade bids assign design responsibility differently?
  • Which submission does not include the access and lifting requirements shown in the tender scope?
  • What warranty period does each bidder offer, and where is it stated?

AI can organise and surface the evidence. The team still sets normalisation values, judges delivery confidence, and approves the selection.

For related quantity risk before award, see When the BOQ Doesn't Match Reality.

Bid comparison checklist

  • Build the baseline from the client's tender documents
  • Use the same comparison structure for every bidder
  • Capture explicit, conditional, and unclear exclusions
  • Record the quantity and revision basis of each offer
  • Keep compliant base scope separate from alternates
  • Compare design, testing, access, and temporary works
  • Review programme and procurement assumptions
  • Route commercial departures for approval
  • Show every normalisation adjustment separately
  • Add a confidence assessment beside the evaluated total
  • Obtain written confirmation of material clarifications

Frequently asked questions

What is bid leveling?

Bid leveling is the process of adjusting different submissions to a common scope and commercial basis so the evaluated totals are meaningfully comparable.

Should exclusions always be priced back into the bid?

Not automatically. First confirm whether the tender requires the item, whether another package owns it, and whether the departure is acceptable. Then decide whether to add a value, carry a risk allowance, or reject the exclusion.

How should missing prices be handled?

Request clarification where time allows. If the item must be evaluated before a response arrives, use a documented estimate or benchmark approved by the bid owner. Keep the adjustment visible rather than changing the submitted total.

Is the lowest evaluated total always the best choice?

No. Scope confidence, programme, technical compliance, capacity, and commercial departures also matter. The final decision should show both cost and risk.

Can supplier alternatives be compared with the base requirement?

Evaluate the compliant base offer first. Assess alternatives separately for cost, performance, programme, approvals, and design impact.

Compare the work before you compare the number

The lowest bid is sometimes the best bid. But you can only know that after the offers describe the same job.

Build one scope baseline. Make every exclusion visible. Normalise the differences. Then choose with the evidence in front of you.

Keep reading

Related Brickato capabilities

  • Construction Tender Analysis AI — Bid Review with Citations
  • Construction Domain AI — Contracts, BOQ & RFIs

Related articles

  • When the BOQ Doesn't Match Reality: Quantity Discrepancies
  • Construction Tender Document Analysis: Manual vs. AI