George Washington Bridge Pavement Maintenance: Scope and Procurement Forecast

Review George Washington Bridge Pavement Maintenance scope, forecast timing and estimating questions before preparing a bid from the issued documents.

Guide2 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. Forecast scope and procurement timing
  2. Separate pavement, concrete and curb work
  3. Estimating investigation, not confirmed requirements
  4. Before committing the bid team
  5. Review the issued scope

Routine pavement maintenance spans roadways on grade and bridge spans, with asphalt patching, crack repair and resurfacing alongside full- and partial-depth concrete pavement repair, sidewalk and curb work. This is independent Piper analysis, not an agency notice. Research checked November 15, 2026.

Forecast scope and procurement timing

The Port Authority construction forecast workbook identifies GWB714003 at George Washington Bridge. Its entries are:

  • GWB - Maintenance Pavement Repairs via WO: 2026 Q4 procurement forecast; published procurement approach: SBE.

The workbook reference identifies the forecast entry; verify the solicitation identifier when an advertisement is issued. The quarter is a forecast of procurement timing, not a bid deadline, construction start or guarantee of release. The Port Authority construction procurement page explains the forecast context and directs readers to advertisements for active solicitations. Confirm current status there; this snapshot does not establish an open bid.

Separate pavement, concrete and curb work

The takeoff cannot be treated as one uniform asphalt overlay. Separate bridge-span work from on-grade locations and distinguish patch, crack, resurfacing and concrete repair quantities; the forecast supplies no quantities or repair limits.

Estimating investigation, not confirmed requirements

  • Where are the repair limits and how will locations be ordered?
  • Which concrete and asphalt repair types have separate pay items or unit-price mechanisms?
  • Who carries sidewalk and curb reinstatement and transitions between old and repaired pavement?

Record each answer against the drawing, specification, schedule or clarification that establishes it. If the issued documents leave a boundary unclear, identify the affected trade carry and seek clarification through the solicitation process before relying on an exclusion.

Before committing the bid team

Find the current advertisement, solicitation, drawings, specifications and all addenda, if issued. Match the reference and exact title, establish the document baseline, then compare scope assignments with the bid form and trade quotes. Check whether the actual procurement approach and requirements have changed since the forecast. The NYC public construction bid review gives the team a review structure; use the addenda management guide when revisions arrive. The NYC public project directory provides a path to other named packages.

Review the issued scope

Once the team has the relevant project documents, Piper's scope-generation workflow can help organize scope from documents the user supplies. The estimator still needs to check the output against the controlling documents and resolve the open interfaces before carrying a price.

ShareLinkedInX

Related reading

Guide4 min

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.

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.