Blue Hill Avenue: build assumptions by block, not one corridor section
A segment register helps estimators distinguish platform, median, bike and access assumptions across the proposed Blue Hill Avenue corridor.
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
- 2 min
- Published
An estimator reviewing Blue Hill Avenue should not extend one typical section across the corridor. The City's September 2026 proposed design changes bus platform locations, bicycle accommodation, median treatment and access by segment. Carry a segment-specific assumption until the issued plans establish the actual package and quantities.
Read the corridor at its proposed stage
The City's block-by-block presentation describes a proposed design, not final bid drawings. The project hub identifies the corridor between Warren Street and River Street. The following matrix is estimating analysis of those dated owner statements, not issued requirements.
| Segment | Owner's proposed distinction | Estimator's question |
|---|---|---|
| River Street to Babson Street | Platforms near Fairway replace two stop pairs; health center left turn restricted with access via Babson | Identify platform limits, crossing work and maintained access in issued plans |
| Johnston Road to Brookview Street | Tree-planted median retained; one lane each direction; platforms between Ansel and Balsam; west-side bike path | Identify median protection, platform and path boundaries and access provisions |
| Washington Street to Warren Street | Two lanes each direction, no changed turning movements or bike lanes; served by platforms at Castlegate and Supple/Wayne | Check platform limits and connections without importing the other sections' bike path |
The City says the sidewalk-level bike path starts at Woodhaven, not at the bridge. It also identifies a separate station near the Fairmount Line bridge. That distinction affects the scope assumptions for the adjoining section, but the public summary does not establish platform dimensions or utility phasing.
Turn the register into a bid question
Assign each segment a source page and design revision, a location limit, the affected trade interfaces and an owner for outstanding information. Ask for plans showing curb, drainage, signals, accessible crossings and work-zone access at each transition. Carry quantities only from a suitable issued basis; parking and tree counts in a presentation are not a takeoff. A segment with a retained median can still require work at an adjoining crossing, so resolve the boundary in the drawings rather than assuming no impact.
No current tender or construction start is established by these materials. Trace package responsibilities to project evidence and check the actual issued revision before turning this preliminary register into a bid.
Related reading
Construction scope generation: a practical guide for GCs
How general contractors turn drawings, specifications, addenda, and company standards into trade scopes a subcontractor can price, an estimator can trace, and a senior reviewer can challenge.

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.

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.