# Subcontractor Bid

> The price and scope a subcontractor offers to perform a trade package, and the offer that -- once accepted -- becomes the basis of the subcontract.

- Source: https://briq.ai/acu/object/subcontractor-bid
- Department: Preconstruction & Estimating (https://briq.ai/acu/department/preconstruction)
- Catalog code: PRE 102 · Level: Foundation · Track: Operations · 10 min read
- Also known as: Sub Bid, Trade Bid, Subcontractor Proposal, Sub Quote, Trade Quote

## Definition

A subcontractor bid is the priced offer a specialty contractor submits in response to a bid package, stating what it will perform, for how much, and under what inclusions, exclusions, and qualifications. It is simultaneously a number and a scope statement: the price is only meaningful in light of exactly what the bidder priced and what it left out. Once accepted, it becomes the basis of the subcontract, so the scope it defines and the qualifications it carries flow directly into the contractual relationship. A subcontractor bid is not itself a contract -- acceptance and the executed subcontract create the binding obligation -- but on public work and where a bid bond is posted, the bid may bind the bidder to hold its price and enter the contract if selected.

## Why it matters

The subcontractor bid is where most of a general contractor's cost is actually set, because the majority of scope on most projects is subcontracted. The general contractor's own estimate is largely an assembly of sub bids plus its self-perform work and markup, which means the quality, completeness, and comparability of the sub bids determine the quality of the prime bid. Weak sub bids produce a weak prime bid no matter how good the general contractor's own estimating is.

Its exclusions and qualifications, not its price, are usually what matter most. A bid's number is easy to compare; its scope is not, and the low bid is frequently low because it excluded something the others included or qualified away a risk the others priced. The exclusions and qualifications are where the real cost hides, which is why reading them -- not just the bottom line -- is the essential skill in evaluating a sub bid.

It becomes the scope baseline for the entire subcontract relationship. Whatever the accepted bid says it includes and excludes is, in practice, what the subcontract obligates, and every future scope dispute is judged against it. A vague or heavily qualified bid accepted without clarification becomes a vague subcontract, and the ambiguity is litigated in the field for the life of the job.

It carries a phenomenon unique to bidding -- the risk that the low bid is low by mistake. A subcontractor that misread the drawings, forgot a scope item, or made an arithmetic error can submit a number well below the others, and a general contractor that carries it forward inherits the consequence when the sub either walks, seeks relief, or performs the work at a loss and cuts corners. The unusually low bid is a warning to verify, not a windfall to bank.

## Lifecycle

1. **Invitation and package review** — The subcontractor receives the bid package and reviews the drawings, specifications, and scope narrative to decide whether and how to bid. A sub that misreads the package here prices the wrong scope, and the error propagates all the way to award.
2. **Takeoff and pricing** — The sub measures its scope and prices it from its own rates, crews, and vendor quotes. This is the sub's own estimate, and its production assumptions and material quotes carry the same risks as any estimate.
3. **Scope definition and qualification** — The sub decides what it will include, exclude, and qualify. This is where competitive pressure meets risk management -- excluding scope lowers the price but shifts the boundary argument to later, and a sub's exclusions are as much a bidding strategy as its number.
4. **Bid-period questions** — The sub raises questions on ambiguities through the general contractor. A cluster of the same question across subs signals the package is unclear and should be resolved by addendum before pricing is finalized.
5. **Submission** — The bid is submitted on the required form by the deadline, with alternates, unit prices, and qualifications. On public work a late submission is rejected outright; disciplined receipt protects the process on private work too.
6. **Leveling and clarification** — The general contractor levels the bid against the package and other bids and pushes clarifications on gaps. This is the window to resolve scope while the sub is still competing and cooperative.
7. **Award or carry into prime bid** — The leveled bid is either awarded or carried into the general contractor's prime bid to the owner. An un-leveled bid carried into the prime imports the sub's scope gaps into the general contractor's own number.
8. **Subcontract execution** — On award, the accepted bid's scope, price, and qualifications are incorporated into the executed subcontract. Whatever ambiguity survived into the accepted bid survives into the contract and is argued in the field.

## Anatomy

- **Bidder identification and license** — The subcontractor's legal entity, license, and contact. Determines who is bound and whether the firm is licensed for the work in the jurisdiction.
- **Package and scope bid** — Which trade package the bid responds to. Prevents a sub from being compared against the wrong scope on a multi-package job.
- **Base bid price** — The headline lump-sum or scheduled price. Meaningful only in light of the inclusions and exclusions behind it.
- **Inclusions** — What the sub states it has priced, ideally referenced to specification sections. Where a sub claims scope others excluded, revealing the basis of a price difference.
- **Exclusions** — What the sub explicitly did not price. The field that most often explains a low bid and the first place to look when a number seems too good.
- **Qualifications and assumptions** — Conditions the bid is contingent on -- soils, escalation, schedule, access. Often buried in a cover letter and frequently where risk is quietly shifted back to the general contractor.
- **Alternates** — Prices for the owner-requested options. Comparable only if every bidder priced the same alternates on the same basis.
- **Unit prices** — Rates for quantity swings. A bid low on base but high on unit prices carries hidden exposure the moment quantities move.
- **Allowances carried** — The allowance amounts the bid includes. Must match what the package directed and what other bidders carried, or the bases are not comparable.
- **Bid validity period** — How long the price is held open. A short validity period can expire before award and force a re-bid or a price increase.
- **Bid bond or security** — Any bid bond posted. Where required, it binds the sub to hold its price and enter the contract if selected and protects the general contractor against a withdrawn low bid.
- **Addenda acknowledged** — Which addenda the bid accounts for. A bid that fails to acknowledge a material addendum was priced against superseded scope.

## Failure modes

- **The mistaken low bid** — A sub misread the drawings, dropped a scope item, or made an arithmetic error and submitted a number well below the field. A general contractor that banks it inherits the consequence -- the sub walks, seeks relief, or builds at a loss and cuts corners -- and the apparent bargain becomes the project's biggest risk.
- **Exclusions read as fine print instead of scope** — The evaluator compares base prices and treats the exclusion list as boilerplate. The low bidder's exclusions are exactly why it is low, and ignoring them means awarding a bid that is missing scope the general contractor will have to buy elsewhere at a premium.
- **Qualifications buried in a cover letter** — A qualification that shifts material risk -- unsuitable soils excluded, price held only thirty days, escalation passed through -- sits in a cover letter the evaluator never reads past. The bid looks competitive only because the qualification gave the risk away, and it surfaces after award.
- **Bid priced against superseded documents** — The sub priced an early drawing set and never acknowledged the addendum that changed the scope. The number is against the wrong job, and the low bidder is often the one that missed the addendum, so the apparent savings is a scope it never priced.
- **Validity period expired before award** — The bid holds its price for thirty days but the award takes sixty, and the sub raises its number or withdraws. The general contractor, having carried the old price into its prime bid, is now short the difference on a job it may already have won.
- **Scope ambiguity carried into the subcontract** — A vague or heavily qualified bid is accepted without clarification, and its ambiguity becomes the subcontract's ambiguity. Every boundary question is then argued in the field, and the moment to resolve it cheaply -- before award -- has passed.

## Metrics

- **Bid coverage per package** — Number of responsive sub bids received per package against a target of at least three. Thin coverage weakens the general contractor's own bid and its leverage.
- **Low-bid deviation** — How far the low bid sits below the next and the mean. A large deviation is a warning of a mistaken or scope-short bid, not a signal of a bargain.
- **Exclusion materiality** — The value of scope a bid excluded relative to its base. Measures how much of the headline price advantage is really missing scope.
- **Addendum acknowledgment rate** — Share of bids that acknowledged all material addenda. Flags bids priced against superseded documents before they are carried forward.
- **Bid-to-subcontract scope drift** — Difference between the accepted bid scope and the executed subcontract scope. Measures how much ambiguity survived into the contract.
- **Bid validity adequacy** — Whether the bid's validity period covered the actual time to award. Flags the risk of expired prices before the award is made.

## The AI shift

- **Conversational** — The bid stops being a number on a form and becomes something you can question. You can ask what a bidder excluded relative to the package scope, whether it acknowledged all addenda, where its cover letter buries a risk-shifting qualification, or whether its price is far enough below the field to suggest a mistake -- with each conclusion tied to the page of the bid it came from.
- **Generative** — For the subcontractor, drafting the bid shifts to a reviewed draft: from the package and its own rates, a system assembles the priced scope, inclusions, exclusions, and qualifications on the required form for the estimator to adjust. For the general contractor, a system drafts the extraction of each bid's terms against the package scope for review rather than manual transcription.
- **Orchestrated** — The bid stops being an isolated document. It is checked against the package scope for exclusions, against the addenda log for acknowledgment, and against the other bids for comparability, then flows into leveling and, on award, into the subcontract scope so the bid, the leveling, and the contract all agree rather than drifting apart.
- **Autonomous** — The routine motion runs without a person driving it: bids extracted and checked against package scope and addenda on receipt, exclusions and qualifications surfaced, unusually low bids flagged for verification, validity periods monitored against the award timeline, and un-leveled bids blocked from the prime estimate -- while humans own the award, every judgment about a qualification, and the decision to trust or question a low number.

## Prompts

### Conversational — Evaluating a single sub bid that came in suspiciously low.

```text
The low bid on our roofing package came in twenty percent under the next bidder. Read the full bid document including the cover letter and any attachments and tell me whether this number is trustworthy. Check what scope it excluded relative to the package scope narrative, whether it acknowledged all issued addenda, whether it carried the allowance the package directed, and whether the cover letter contains any qualification that shifts risk back to us -- warranty length, escalation, unsuitable-substrate exclusions. Tell me specifically whether the gap to the next bidder is explained by excluded scope, a missed addendum, or something that looks like a genuine mistake. Cite the page for each finding.
```

**Expected output:** A verdict on whether the low bid is real, with the gap explained by named exclusions, missed addenda, or possible error, each tied to a bid page -- not a restatement that it is the lowest number.

**Follow-ups:**

- If it is missing scope, what would the leveled number be against the other bidders?
- Draft the clarification questions I should put to this bidder before we rely on the price.
- Is there enough here to suspect a bidding error we should let them correct or withdraw?

### Generative — A subcontractor preparing its own bid from a package.

```text
Help me assemble our bid for this concrete package from the attached bid package and our rate library. Price our scope from the takeoff, then draft the bid on the required bid form with a clear inclusions list referenced to the specification sections we are covering, an explicit exclusions list for the boundary items we do not carry -- excavation, dewatering, embeds by others, final grading -- and any qualifications we need on soils, weather, and escalation. Carry the allowance the package directs, price the requested alternates and unit prices, note which addenda we have acknowledged, and state our bid validity period. Keep the qualifications on the bid form itself rather than buried in a cover letter so we are not accused of hiding them. Flag anything in the package that is too ambiguous for me to price without a clarification.
```

**Expected output:** A submission-ready bid on the required form with spec-referenced inclusions, explicit exclusions, transparent qualifications, acknowledged addenda, and flagged ambiguities -- a draft the estimator adjusts, not a hidden-qualification bid.

**Follow-ups:**

- Draft the bid-period questions we should send on the ambiguities you flagged.
- Which of our exclusions are most likely to be challenged, and how should I word them?
- Produce a short cover letter that summarizes our scope without hiding anything material.

### Orchestrated — Processing all bids for a package as they arrive and readying them for leveling.

```text
As bids arrive for the glazing package, process each one for me. Extract the base price, inclusions, exclusions, qualifications, alternates, unit prices, allowance, validity period, and acknowledged addenda, and check each against the package scope and the addenda log. Flag any bid that failed to acknowledge a material addendum, carried a different allowance than the package directed, or has a validity period shorter than our expected time to award. Surface every qualification that shifts risk. Then lay all the bids out against the baseline scope so they are ready to level, and tell me which bidders are missing scope the others priced. Do not rank them yet -- I want the comparison prepared, not the decision made.
```

**Expected output:** Every bid extracted, checked against scope and addenda, qualifications surfaced, and laid out against the baseline ready for leveling -- with compliance and expiry flags raised but the ranking left to the human.

**Follow-ups:**

- Now propose the add-backs so I can see the leveled totals.
- Which bids need a clarification before I can rely on them, and what should I ask?
- Which of these prices will expire before our likely award date?

### Autonomous — Standing policy for handling incoming subcontractor bids across all packages.

```text
Handle incoming subcontractor bids continuously under these rules. On receipt for any package, extract every bid's base price, inclusions, exclusions, qualifications, alternates, unit prices, allowance, validity period, and acknowledged addenda from all documents including cover letters. Check each against the package scope and addenda log, and flag any bid that missed a material addendum, carried the wrong allowance, or has a validity period too short for the expected award timeline. Surface every risk-shifting qualification prominently. Flag any bid whose price deviates far enough below the field to suggest a mistake so we can verify before relying on it. Lay bids out against the baseline scope ready for leveling, and block any un-leveled bid from being carried into a prime estimate. Never accept or reject a bid, never finalize a leveled add-back, and never dismiss a qualification -- route every judgment to me with the supporting bid pages.
```

**Expected output:** Incoming bids extracted, compliance-checked, and prepared for leveling as a short exception queue -- missed addenda, wrong allowances, expiring prices, suspicious lows, risk-shifting qualifications -- while acceptance, leveling values, and qualification judgments stay human decisions.

**Follow-ups:**

- Show me every bid flagged for a missed addendum or an expiring price.
- Which low bids across open packages look far enough off to warrant a verification call?
- Which qualifications this week shift the most risk back to us?

## Maturity ladder

- **Level 0 — Level 0 — Number on a fax** — Bids arrive as loose numbers with little scope detail, are compared by headline price, and their exclusions and qualifications are barely read. The mistaken low bid rides straight through to award.
- **Level 1 — Level 1 — Collected and compared** — Bids are collected on a form and lined up by price with some exclusions noted, but qualification analysis, addendum checking, and validity tracking depend on the estimator's time and diligence.
- **Level 2 — Level 2 — Scoped and verified** — Bids are evaluated against the package scope, exclusions and qualifications are extracted, addendum acknowledgment and allowances are verified, and validity periods are tracked against the award timeline.
- **Level 3 — Level 3 — Assisted** — Bid terms are extracted from documents for review, exclusions and qualifications are surfaced, unusually low bids and missed addenda are flagged, and bids are laid out against the baseline ready for leveling.
- **Level 4 — Level 4 — Operated** — Extraction, scope and addendum checking, qualification surfacing, low-bid flagging, and validity monitoring run unattended inside guardrails, while acceptance, leveling values, and qualification judgments remain human decisions.

## FAQ

### Is a subcontractor bound to its bid once submitted?

It depends on the context. On private work a bid is generally a revocable offer until accepted, though a general contractor that reasonably relied on a sub's bid in its own prime bid may in some jurisdictions hold the sub to it under promissory estoppel. On public work and where a bid bond is posted, the bid typically binds the sub to hold its price and enter the contract if selected, and withdrawing can forfeit the bond. The binding obligation is fully clear only once the bid is accepted and the subcontract is executed.

### Why is the exclusion list more important than the price?

Because the price is only meaningful in light of what it covers, and the low bid is frequently low precisely because it excluded scope the other bidders priced. A number ten percent below the field may be missing far more than ten percent of the scope, and the excluded work does not disappear -- it becomes something the general contractor must buy elsewhere, usually at a premium. Reading the exclusions and qualifications, not just the bottom line, is what separates evaluating a bid from merely ranking it.

### What should a general contractor do about a suspiciously low sub bid?

Verify before relying on it. An unusually low bid often reflects a misread drawing, a dropped scope item, or an arithmetic error, and carrying it into the prime bid means inheriting the consequence if the sub later walks, seeks relief, or performs at a loss. The right move is to confirm the bidder acknowledged all addenda, understood the full scope, and stands behind the number -- and to be prepared to allow a genuine bidding-error withdrawal rather than hold a sub to a mistake that will fail the project. A verified low bid is a win; an unverified one is a liability.

## Related objects

- [Bid Leveling Sheet](https://briq.ai/acu/object/bid-leveling)
- [Bid Package / Invitation to Bid](https://briq.ai/acu/object/bid-package)
- [Subcontract](https://briq.ai/acu/object/subcontract)
- [Detailed Estimate](https://briq.ai/acu/object/detailed-estimate)
- [Bid Addendum](https://briq.ai/acu/object/bid-addendum)
- [Contractor Prequalification](https://briq.ai/acu/object/prequalification)