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.

Guide4 min read

Published

Tower crane above steel reinforcement

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. Establish which procurement you are actually pricing
  2. Give the review a chain the chief estimator can follow
  3. Review local conditions before accepting trade coverage
  4. Separate a document acknowledgment from its cost consequence
  5. Close the submission lane independently
  6. Review the estimate against the current bid package

A regional GC reviewing a NYC public-building bid needs to answer two questions before submission: is the response complete, and does the number carry the work the documents require? A compliant-looking attachment folder cannot answer the second question. A reconciled estimate cannot answer the first.

For a small preconstruction team, the useful checklist connects each material requirement to its source, responsible package, pricing treatment and unresolved decision. That connection lets a reviewer follow a restriction in the bid documents into a subcontractor quote, the estimate and the preliminary schedule.

This guide is a review method for GC and CM teams preparing public-work bids. It is not a universal list of required forms. The issued solicitation, procurement route and agency instructions determine those obligations.

Establish which procurement you are actually pricing

Start with the owner, solicitation identifier, delivery method and current response instructions. Do not reuse the last agency's compliance checklist without reading this package.

DDC's construction-contract guidance identifies competitive sealed bids alongside other procurement routes and directs construction solicitations to PASSPort. That does not make a DDC bid, an SCA school package and a transit contract interchangeable.

Record the document baseline before assigning review work: drawing index, specifications, contractual requirements, exhibits and issued revisions. Identify missing referenced attachments. An unanswered dependency belongs in the review log even when the team cannot resolve it immediately.

Give the review a chain the chief estimator can follow

Use this illustrative review structure. It is a working scaffold, not an agency form or a record from an actual project.

RequirementScope and pricing questionEvidence needed before approval
Restricted access to an occupied areaWhich trade carries protection, moves and reinstatement?Exhibit reference, package assignment and quote treatment
Revised equipment or detailWhich prior scope or carry may now be stale?Addendum reference and affected estimate lines
Required bid attachmentWho completes and checks the current version?Solicitation instruction and submission record
Fixed turnover milestoneDoes sequence support the duration carried in general conditions?Activity logic, work calendar and estimate basis

A line marked reviewed should mean someone followed that chain. It should not mean someone opened the PDF.

Review local conditions before accepting trade coverage

On occupied school work, start with the construction exhibit and phasing review. On street work or a building package using the right-of-way, review embargoes, protected streets and access assumptions.

If the sequence depends on evenings or weekends, use the night-work scope checklist. An assumed work window can change supervision, temporary protection, deliveries and the estimate's duration basis. It needs an owner before the number is approved.

These are triggers for a project-specific review, not assertions that every NYC public project carries every listed requirement.

Separate a document acknowledgment from its cost consequence

A subcontractor can acknowledge a revision and still leave its new requirement unpriced. Ask the package lead what changed in scope, which quotations were reopened and whether the selected carry remains supported.

The DDC addenda review guide follows that decision. The existing final bid review playbook covers the broader approval process.

Do not silently convert unresolved scope into contingency. Record the treatment, its basis and who accepts it. A priced allowance, an explicit clarification and a missing answer are different conditions.

Close the submission lane independently

Assign a submission owner who checks the current response, not a copy exported earlier in the week. Reconcile the owner's bid breakdown, alternates, required attachments and acknowledgment instructions against the latest package.

Use the NYC bid-attachment and registration guide to build a source-led register. The portal's saved state and submitted state must also be distinguished under the applicable instructions.

At approval, the chief estimator should see a short list of open decisions with consequences and owners. The team should be able to explain which items are closed, which are carried with a basis and which prevent submission.

For technical requirements, the NYC building-code prebid review separates applicability from package coverage. Verify the contractor registrations required for the actual work. Where rail operations affect the package, use the NYC rail-access review and the issued operator requirements.

Review the estimate against the current bid package

A final review is more useful when the chief estimator can follow an issue back through the scope, the quote and the requirement that created it. That is the connection Piper’s Final Bid Review is designed to support: checking the estimate against drawings, specifications, addenda, trade scopes and subcontractor proposals, with findings linked to their sources.

Piper is the AI operating system for preconstruction. The project understanding used to prepare scope also informs the review of the number, so each workflow can build on the work already done. The team decides how to resolve a finding, what risk to accept and whether the bid is ready to submit.

ShareLinkedInX

Where this fits in Piper

Final Bid Review

Review the estimate against the project behind it and focus senior attention on what still deserves judgment.

Related reading

Guide7 min

Surveys: the questions worth asking before you bid

A standing pre-bid questionnaire turns the things your best estimator always remembers to check into something the whole company checks every time. How to build one, who answers what, and how to keep it alive.

Tower crane above steel reinforcement

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.