DDC bid addenda: reconcile scope and estimate before acknowledging the revision
A DDC addendum can change more than a drawing. Trace the revision into trade scopes, quote qualifications, bid forms and the estimate before final approval.
Author
Ido Gedanken, CEOPublished

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- Type
- Guide
- Read
- 3 min
- Published
On this page
- Confirm the RFx baseline before chasing scope changes
- Follow the requirement into the work already done
- Record the pricing treatment separately from the notice
- Recheck acknowledgments against substantive coverage
- Close the technical and submission decisions together
- Carry the addendum through scope, quotes and final review
Before a GC submits a DDC construction bid, each issued addendum needs two closeouts: the required acknowledgment and the effect on the work being priced. A checkmark in the response cannot establish that trade scopes, quotes and estimate lines have been refreshed.
The material question for the chief estimator is which existing commitments the revision invalidates. The answer can reach a package already sent out, a quote already selected or a sequence already used to price general conditions.
This guide adds a NYC procurement check to the broader addenda management workflow. It is for GC bid preparation, not a determination of whether a specific response is legally responsive.
Confirm the RFx baseline before chasing scope changes
DDC's construction-contract page directs construction solicitations to PASSPort. Use the current solicitation and its instructions as the bid baseline, rather than a folder inherited from another pursuit.
MOCS guidance for RFx responses distinguishes an addendum from a new round: substantial changes can require a new response. The submission owner should check that distinction before assuming a previously prepared response remains the right one.
The package lead then confirms which documents changed. An altered due date, replaced specification and revised drawing may need different actions. Do not send every revision through a retakeoff pass simply because it has an addendum number.
Follow the requirement into the work already done
Consider an illustrative revision that changes a rated partition detail. The quantity change may be small while the scope consequence reaches framing, backing, penetrations and firestopping. The example is a review scenario, not a finding from a DDC project.
Start with the current package responsibility. Identify which issued scope sheets reference the old condition, which quotations rely on it and which estimate treatments assumed it was covered. Ask whether any boundary moved without a corresponding owner.
This is the operational distinction in drawing-revision impact review. The marked-up sheet identifies a change; the estimating review determines which commitments need attention.
Record the pricing treatment separately from the notice
Use this illustrative reconciliation structure to make the follow-up reviewable.
| Revision effect | Package action | Estimate evidence |
|---|---|---|
| New requirement in an issued trade package | Reissue affected scope and obtain pricing treatment | Quote revision or documented review adjustment |
| Work transferred between trades | Confirm both sides of the boundary | Removed carry and receiving package coverage |
| Changed access or work period | Recheck sequence and relevant qualifications | Labor, logistics and duration assumptions |
| Changed response instructions | Submission owner reviews current instructions | Correct form, round and required acknowledgment |
The estimator may need a temporary carry where revised pricing cannot be obtained in time. Record its basis and acceptance. Silence in the quote should remain visible rather than become an implied inclusion.
Recheck acknowledgments against substantive coverage
A proposal can list the latest addendum while retaining an exclusion that conflicts with its new requirement. Conversely, a missing reference is a reason to seek confirmation, not proof by itself of what the subcontractor priced.
Compare the response with the requirement, then obtain written clarification through the appropriate channels. Keep the original quote and later response distinguishable. A reviewer needs to know what arrived, what was interpreted and what the GC ultimately decided to carry.
For changes to school phasing or street access, the relevant local guide is linked from the NYC public-bid review hub.
Close the technical and submission decisions together
At final review, the estimate lead confirms treatment of each material revision. The submission owner confirms the response instructions, forms and current round. Neither should approve the other's lane by inference.
The bid-attachment register is useful here because a changed instruction can reopen a previously completed document. Keep unresolved impacts visible until the accountable reviewer accepts or resolves them.
Carry the addendum through scope, quotes and final review
When a revision arrives, the useful output is a set of affected commitments the team can act on. Piper can surface scope that needs another look and compare proposals against the intended current requirements through scope generation and bid leveling. A changed requirement and a quote still tied to an earlier basis can then be reviewed in the same project context.
That context also feeds Final Bid Review, where the estimate is checked for potentially missing scope, duplicated coverage or stale assumptions. Findings keep their supporting sources so the estimator can decide what changes. The GC continues to distribute binding revisions, obtain acknowledgments and verify the correct PASSPort response and round.
Where this fits in Piper
Scope Generation
Turn drawings, specifications, addenda, and company standards into source-backed trade scopes.
Bid Leveling
Compare subcontractor bids against the intended scope so the low number does not hide an expensive gap.
Final Bid Review
Review the estimate against the project behind it and focus senior attention on what still deserves judgment.
Related reading
NYC public construction bid review: connect the requirement to the number
A NYC public-bid review should trace owner requirements into scope, quotes, schedule and the final number. A practical review map for small GC precon teams.

NYC construction bid attachments: build the register from the solicitation
Build a NYC public-bid attachment register from the solicitation. Keep DOL registration, agency requirements and submission evidence distinct from scope review.

Construction addenda management for GC estimators
Addenda are official bid-document revisions. Log them, distribute them, retakeoff the deltas, and require subcontractor acknowledgments so your estimate and every bid reflect the final scope.

What Changed? How Drawing Revisions Cascade Through Scope, Bids, and the Estimate
A drawing revision is not only a sheet delta. Trace what it does to trade scopes, live bids, and the estimate before bid day locks the number.

Final bid review: a QA/QC playbook for general contractors
The pre-submission gate between a working estimate and a price you are prepared to submit, explain, contract around, and build. Workflow, checklists, review lanes, delivery-method playbooks, and the KPIs worth tracking.

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.