B Branch: separate accessible platforms from track and BU work
A dated scope register distinguishes the B Branch platform package from separate track and university accessibility projects.
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
On this page
A B Branch station estimate should start with the A26CN05R package boundary, not the older Blandford track description. The A26CN05R public listing observed on November 16, 2026 separates track work and Boston University accessibility improvements from the station accessibility project. That difference changes which interfaces need coordination and which work should be carried in the package.
Compare the dated descriptions
The MBTA public listing observed on November 16, 2026 describes design-build final design and construction to raise and widen boarding areas, provide accessible paths to the public right of way, separate users from vehicles and address barriers at multiple grade crossings. It says track work and Boston University accessibility improvements will be completed under separate projects.
An older A26CN05 RFQ listing, closed October 31, 2025, included track realignment at the Blandford portal. That historical description does not establish that the A26CN05R package includes the same work. The A26CN05R solicitation details were not reviewed beyond the public listing.
The listing could not be independently retrieved on November 17, 2026. Recheck its operative version before making a procurement or pricing decision; this comparison preserves the dated observation.
Maintain an adjacent-package register
| Work boundary | Dated public description | Estimator's follow-up |
|---|---|---|
| Platforms | November 16 listing raises and widens boarding areas | Obtain station list, platform limits and issued design basis |
| Accessible paths | November 16 listing connects to public right of way | Identify path endpoints and adjoining responsibilities |
| Grade crossings | November 16 listing addresses barriers at multiple crossings | Obtain crossing details and interface scope |
| Track | November 16 listing says separate project | Identify schedule, physical interface and coordination owner |
| University accessibility | November 16 listing says separate project | Obtain limits and adjoining-package interface |
| Blandford realignment | Older RFQ included it | Do not carry under A26CN05R package without current documents |
These follow-ups are estimator analysis, not additional owner requirements. Separate procurement does not eliminate the need to coordinate access, survey and construction boundaries. It also does not establish the duration or timing of any service closure.
Tie the carry to the current issue
Record each package's document date, scope limit, adjacent project, assumed handoff and open question. If an issued drawing changes a boundary, notify each affected trade and update both the carry and interface register. No exact station list, final platform length, award or accessibility certification is established here. Verify the owner and issued procurement record and trace the controlling revision before pricing.
Related reading
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.