---
title: 'The lowest subcontractor quote expires before award. What do you carry?'
url: 'https://piper-ai.com/resources/subcontractor-quote-validity-bid-leveling'
description: 'Compare the quote price, price hold and award timeline separately so the carry records both its basis and any unresolved exposure.'
contentTypes: [guide]
publishedAt: '2026-11-22T17:58:03.541Z'
updatedAt: '2026-11-22T17:58:03.562Z'
author: 'Ido Gedanken, CEO'
readingTime: 5
---

# The lowest subcontractor quote expires before award. What do you carry?

Carry a number that matches the decision date and the evidence available today. If the lowest mechanical quote is held only until next week and award is expected later, retain its submitted price, but do not present that price as confirmed through award. Either document a separate estimator adjustment, carry a different supported quote, or carry the low quote with an explicit unresolved exposure and an assigned decision to resolve it.

The right choice depends on the project and the evidence, not a standard escalation percentage. A later written extension can change the comparison; it does not erase the original proposal or automatically resolve its other qualifications. The actual quote and project agreements control the terms. This is an estimating method, not a conclusion about enforceability.

The [ASA Houston discussion of price volatility](https://asahouston.org/asa-model-documents-can-help-subs-deal-with-price-volatility/), published in 2018, describes limiting bid validity and using express escalation terms as separate subcontractor proposal tools. That is useful context for reading an actual offer, not a current escalation forecast or a universal validity period. The method below uses the dates and conditions stated in each fictional quote.

## The comparison date is part of the price

A chief estimator preparing a carry before buyout needs at least three dates: the date of the comparison, the date through which each bidder says its price is held, and the expected date of the trade award. The third date is a planning assumption, not a promise. If it moves, the carry may need a new decision even if the scope is unchanged.

First establish [the common basis for a bid level](https://piper-ai.com/resources/construction-bid-leveling-guide): drawings, specifications, addenda, scope and commercial assumptions. Then distinguish a bidder's stated hold from a GC's own estimate of exposure after it. A proposal can have a price hold and a separate escalation provision; read their wording together rather than treating the hold date as the only commercial condition. [Reviewing exclusions and qualifications](https://piper-ai.com/resources/review-subcontractor-exclusions-and-qualifications) is still necessary before comparing either price.

## A fictional mechanical package

The following dates, terms and prices are invented to illustrate a carry decision. Assume the same reviewed mechanical scope and no other leveling adjustments. The team compares on June 3, plans to submit its estimate June 5 and expects trade award July 10. Both bidders have confirmed their stated prices on June 3, but neither has confirmed a change to the written terms.

| Item | Bidder A | Bidder B |
| --- | --- | --- |
| Proposal | A-17 dated June 1 | B-42 dated June 2 |
| Submitted base | $980,000 | $1,015,000 |
| Written price hold | Through June 15 | Through July 15 |
| Other price term | After June 15, price subject to supplier reconfirmation; no revised amount stated | Price held through July 15 subject to stated scope and schedule |
| Status on June 3 | Confirmed now; award-date price pending | Confirmed through planned award on stated terms |

A is $35,000 lower as submitted. That difference is observable in this fixture; it is not the cost of later escalation. A's proposal supplies no July 10 price. B's stated hold spans the planned date, but its scope and schedule conditions still matter. If award slips beyond July 15, B's basis needs attention too.

On June 16, absent a new written confirmation, mark A's original hold **expired** and its award-date price **unconfirmed**. Do not silently continue to label $980,000 as a confirmed July price. Conversely, an expired hold does not itself tell the estimator what the new price will be. Keep the original submission as history and ask for an updated written position.

## Separate the hold from an estimator adjustment

A hold is a bidder's stated price condition. An adjustment is the estimating team's separately identified amount or allowance for its own comparison. They answer different questions. If the team has a defensible project-specific basis for an adjustment to A, show the basis, preparer, approval and date; do not overwrite the $980,000 quote or describe the adjustment as a revised subcontractor price.

For example, if the team documents a hypothetical $20,000 adjustment, A's evaluated carry would be $1,000,000 ($980,000 plus $20,000), still $15,000 below B. That arithmetic does not prove the adjustment is sufficient. The register should identify its basis and owner, and show that A's actual later price remains unconfirmed. If no credible basis is available, leave the adjustment undecided rather than manufacturing precision.

An escalation trigger deserves its own entry: what event activates it, which costs or scope it addresses, and what evidence or calculation the bidder proposes. In this fixture A asks for supplier reconfirmation; that is not a quantified escalation formula. An extension that holds the same price through July 10 could remove that particular timing uncertainty on the stated conditions, while any remaining scope, schedule or supplier qualifications still require review.

## Three carry decisions, three evidence trails

1. **Carry A with a separate adjustment.** Keep $980,000 as submitted and identify the adjustment and its rationale. The decision owner accepts that the resulting amount is an estimate, not A's confirmed award price. Obtain a written update before relying on a later award price.
2. **Carry B at $1,015,000.** The submitted hold covers the planned award in this example. Record why the $35,000 higher submitted amount was selected, the conditions on B's hold and the date that would trigger another review. This choice does not establish that B is always the better buy.
3. **Carry A without an adjustment, with exposure explicit.** The estimator may decide the available evidence does not support a quantified adjustment. Show $980,000 as the carry with award-date confirmation pending, identify who accepts that unresolved exposure and set a decision deadline. A blank adjustment is not evidence of zero exposure.

If the estimating process requires a firm award-date basis before a carry can be approved, an unresolved quote needs escalation to the decision owner. Do not convert an unanswered question into a bidder commitment just to close the comparison.

## Ask each bidder a written, bounded question

Ask A: “For proposal A-17 and the scope and schedule identified in it, will you hold the $980,000 price through July 10? If not, provide the price or conditions you can confirm through that date, including any supplier reconfirmation trigger and any changed qualifications.” Ask B: “Does B-42's $1,015,000 hold through July 15 cover the current scope and planned award and procurement schedule? Identify any conditions or changes.”

Save the reply with its date and proposal identifier. An affirmative extension should identify the price, deadline, scope, applicable conditions and any superseded term. If it is ambiguous, record the ambiguity and request clarification. If a bidder supplies a new number, retain the old quote and make the new effective selection visible; do not mix an earlier price with later terms without explaining the basis.

## Keep the price basis visible through award

[Piper bid leveling](https://piper-ai.com/use-cases/bid-leveling) compares subcontractor bids against project scope with source-linked findings. The estimating team reviews those findings and decides the carry. The same judgment is needed when a hold date or schedule changes: a source-linked item is useful only if the team records what decision it supports.

Use this register for each proposal and update it at the next decision point:

| Register field | Record for the current decision |
| --- | --- |
| Basis and date | Scope revisions and comparison date; planned award date and owner |
| Source and submitted price | Proposal ID and date; original price without GC adjustment |
| Price status | Confirmed for which date and conditions; pending confirmation; or hold expired |
| Hold and trigger | Written end date, escalation or reconfirmation condition, and source location |
| GC adjustment | Separate amount or unpriced; rationale, preparer, approval and date |
| Carry and decision | Selected amount, bidder, decision owner, reason and unresolved exposure |
| Next evidence | Exact extension or revised terms requested, responsible person and response deadline |
| Change control | What written reply changes, next review date and history of prior selections |
