Congress, Sleeper and A Street: separate City reconstruction from nearby developer work

Map City street reconstruction against Boston Wharf Road and 51 Melcher developer work before carrying Fort Point scope.

Guide1 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. Separate three streets from adjacent developer work
  2. Resolve the Congress-to-Melcher handoffs

A Fort Point estimate needs a boundary by street and responsible project, not a map of every improvement nearby. The City's project page describes reconstruction on Congress, Sleeper and A Street, while separately identifying developer work at Boston Wharf Road and work by the 51 Melcher proponents. Use those descriptions to identify interfaces, then establish actual contract limits from the issued plans.

Separate three streets from adjacent developer work

LocationCity page descriptionProposed estimate boundary check
Congress StreetRaised crossings and grade-separated bicycle facilities with a hardened island are in the described designVerify station limits and intersections against the issued roll plan; identify paving and protection interfaces.
Sleeper StreetNorthbound contraflow and shared southbound bicycle accommodation, raised crossings and traffic calming are describedCheck geometry, staging and access in the controlling issue set rather than assuming the Congress section repeats.
A StreetA separated bike-lane connection and reconstructed sidewalks are described between Congress and MelcherIdentify the exact limit and tie-in to Melcher work.
Boston Wharf Road and CongressCity says the developer reconstructed the intersectionVerify the as-built interface and exclusions before counting reconstruction again.
51 Melcher and A StreetCity describes proponent curb extensions, crosswalks and accessibility contributionsObtain limits and schedule interfaces; do not treat nearby work as automatically part of the City's contract.

The City page calls the street designs final, but this review has not read the large final roll plan or the issued contract. It cannot establish quantities, detour compliance or trade assignments. The developer descriptions are coordination leads, not a substitute for an as-built survey or contract boundary.

Resolve the Congress-to-Melcher handoffs

Ask for the current plan, addenda, property and right-of-way limits, adjacent project schedule and verified existing conditions at tie-ins. Mark each crossing, curb ramp, bike facility and pavement edge once on the scope map; identify who is responsible for any temporary connection and final restoration. Record a question where neighboring work is incomplete or its acceptance is unknown. These are proposed estimating checks, not City requirements.

Past schedule forecasts do not prove completion. Before pricing, check the actual issued revision and trace package responsibilities to project evidence.

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.