Revised subcontractor quotes: replace the right number without losing the terms

Reconcile a price-only email and a replacement proposal without losing prior qualifications or counting a scope plug twice.

Guide5 min read

Published

Construction scaffolding interior

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.

Book a demo
On this page
  1. Three fictional excerpts, two different revision paths
  2. Build the revision-chain register
  3. Remove the plug only when the source supports it
  4. Perform a changed-only review, then check dependencies
  5. Hand the next estimator a reproducible selection

Replace only the part of a subcontractor proposal that the revision actually identifies, and keep the earlier source visible until the remaining terms are resolved. A new price can absorb a GC plug, leave it in place, or leave the scope silent. The estimator needs evidence of which happened before changing the carry.

For a preconstruction manager handing a bid level to another estimator, the useful record is not “latest quote wins.” It is the selected price, source for each material term, unresolved questions, and the reviewer who made that selection. A replacement proposal also needs that review: a document labeled replacement may change more than price, and an item absent from it is not automatically included.

Autodesk’s revision guidance describes recording proposal updates received by phone or email and retaining access to original and revised versions. Keeping versions available is one part of the record. The review below addresses a separate estimating question: which price, scope and adjustment the source supports for the current comparison.

Three fictional excerpts, two different revision paths

The following interior finish package, dates, documents and amounts are invented. The GC's comparison basis requires wall finish, protection and final cleaning in the work area. The estimator originally allows $8,000 for final cleaning where it is not included. Assume the two bidders otherwise address the same basis for this example.

  • Bidder A, PDF A-10, June 2: “Base price $420,000. Wall finish and protection included. Final cleaning excluded. Proposal subject to access during normal hours.”
  • Bidder A, email A-10-R1, June 5: “Revise our A-10 base price to $428,000. This price includes final cleaning. No other changes to A-10.”
  • Bidder B, replacement PDF B-20-R1, June 5: “This proposal replaces B-20 in its entirety. Base price $435,000. Wall finish, protection and final cleaning included. Work assumes clear access during normal hours; off-hours work excluded.”

A's email changes a price and explicitly changes cleaning. It also says no other changes, so the reviewer records the earlier access qualification as the bidder's stated continuing term, subject to checking the actual source and any later clarification. B's replacement directs the reviewer to use B-20-R1 as its proposal basis, but its new exclusion and access assumption still need to be compared with project requirements. “Replacement” is not a scope-coverage test.

The fixture includes explicit language about cleaning to make the accounting traceable. Had A's email only said “price is now $428,000,” the estimator could not infer that cleaning was absorbed just because the increase equals the old plug. The old exclusion would require review and written clarification. A matching dollar difference does not identify the work purchased.

Build the revision-chain register

The common basis for a bid level identifies the project scope and revisions being compared. The chain register then identifies which bidder document supplies each selected term. Link or attach the actual documents in the project record; the short quotations above are only teaching excerpts.

Bidder and sourceSelected price and scopePrior terms and open decisionsReviewer action
A: A-10 PDF, then A-10-R1 email$428,000 from R1; cleaning included expressly in R1Normal-hours access from A-10; check that it fits the projectSelect R1 price and cleaning; retain A-10 for remaining terms
B: B-20-R1 replacement PDF$435,000 and cleaning included from R1Clear normal-hours access assumed; off-hours excludedReview R1 against scope and schedule; obtain clarification if project needs off-hours work

The B-20 original remains in the history, but the fixture's replacement language points to B-20-R1 for the selected proposal. Do not silently splice a favorable old term into B's new price. If a replacement is unclear about what it replaces, record that as an open question rather than deciding incorporation by convention. The actual proposal and project agreements govern the commercial relationship; this register is a review tool, not a legal incorporation rule.

For each real revision, record receipt time, quote identifier, author, source location and the specific scope, price or term changed. Identify the selected source for each material item and whether it is confirmed, unresolved or superseded for the comparison. A document can have both a superseded price and a qualification still relevant to the team's review. Keep those statuses at item level rather than applying one label to the entire chain.

Remove the plug only when the source supports it

Before A's revision, the illustrative evaluated amount was $428,000: $420,000 submitted plus the GC's $8,000 cleaning plug. After R1, the submitted price is $428,000 and the email expressly includes cleaning. If the team accepts that inclusion on the same scope basis, remove the old cleaning plug from the active calculation. The evaluated amount remains $428,000, not $436,000.

The unchanged evaluated amount hides a material change in its composition. Previously $8,000 was the GC's assumption; now the submitted price includes the item under A's written revision. Preserve both versions and the reason for retiring the plug. This is explanatory arithmetic, not evidence of a market pattern or a saving. If the written inclusion covers less than the required final cleaning, retain a separately supported residual adjustment or seek clarification; do not delete the plug solely because the words “cleaning included” appear.

B's $435,000 has cleaning included in the replacement. The team should not add the same $8,000 there either unless an identified part of the required work remains outside B's scope. On the stated fictional basis, A is $7,000 lower after the cleaning adjustment, before any unresolved access or schedule differences are evaluated. That comparison is conditional, not an award recommendation.

Perform a changed-only review, then check dependencies

A changed-only review focuses attention without pretending the unchanged record can be discarded. For A, inspect the revised price and cleaning, then check the surviving access term against the current schedule. For B, compare the replacement against the earlier level and the required scope, including the new off-hours exclusion. Note each added, removed, changed or silent item and its source. Reviewing exclusions and qualifications helps distinguish a stated exclusion from an unanswered item.

A price revision may also affect the estimate line, bid tab, scope coverage and handoff. Update each dependent record deliberately and date the decision. If an off-hours requirement is later confirmed, obtain a price or document a separate GC assumption for each affected proposal. Do not take the same cleaning plug out of the trade level while leaving it embedded elsewhere in the project estimate without a clear owner. For the broader change-propagation problem, see why a finished estimate becomes stale.

Hand the next estimator a reproducible selection

A useful handoff identifies the package and comparison date; the source chain; the selected price and scope; retained qualifications; retired, active and unresolved adjustments; and the reviewer and decision date. It also names the next question and owner. For A, that question might be whether normal-hours access matches the actual schedule. For B, it might be whether the bidder can price any required off-hours work. Neither question is answered by the cleaning arithmetic.

Piper bid leveling compares subcontractor bids against project scope with source-linked findings. The estimating team reviews and decides which proposal and adjustment to carry. Keep the underlying revision record available so the next reviewer can verify which source supports that decision.

ShareLinkedInX

Related reading

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow

See Piper on your project

Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.