---
title: 'RLFMP 1476: Dolphin Way, crossings and Parcel C1A workfronts'
url: 'https://piper-ai.com/resources/rlfmp-1476-dolphin-crossings-parcel-c1a-scope-boundaries'
description: 'A scope-area register for the RLFMP streetscape bid separates Dolphin Way, sidewalk crossings, and Parcel C1A access and parking.'
contentTypes: [guide]
publishedAt: '2026-11-17T23:27:49.182Z'
updatedAt: '2026-11-17T23:27:49.191Z'
author: 'Ido Gedanken, CEO'
readingTime: 2
---

# RLFMP 1476: Dolphin Way, crossings and Parcel C1A workfronts

For a GC preparing a scope review of Raymond L. Flynn Marine Park bid 1476, do not treat the public description as one undifferentiated roadway package. The [owner's project page](https://www.bostonplans.org/procurement/procurement-portal/rfp-listing-page?id=1476) identifies Dolphin Way redesign, sidewalk and crossing configurations on three named streets, and access and parking improvements at Parcel C1A. Set up separate workfronts, then use the issued plans and specifications to define their limits and interfaces.

## What the streetscape notice actually identifies

The project is titled **Raymond L. Flynn Marine Park (RLFMP) Streetscape Improvements Construction**. The owner describes alignment with City of Boston streetscape standards as part of an ongoing effort to transfer the streets. That statement supplies context for the design; it does not establish that a transfer of road ownership has occurred. The page identifies Parcel C1A on Terminal Street as occupied by the Boston Police Department Harbor Patrol, but does not set out its operating or construction access rules. [Owner project page](https://www.bostonplans.org/procurement/procurement-portal/rfp-listing-page?id=1476).

As checked November 16, 2026, the project page showed **Open**, available November 9, a pre-bid meeting scheduled for November 19 at 10 a.m., and a bid due December 17 at noon. The [City bid notice](https://www.boston.gov/bid-listings/16637316) also advertised the December 17 noon Boston-time deadline. These are advertised dates, not evidence of an award or that the meeting occurred; verify the current notice and any addenda before acting.

## Separate the workfronts before assigning trade coverage

The following register translates the public description into review questions. It does not assign quantities or assume construction means.

| Workfront | Public description | Questions for the issued documents |
| --- | --- | --- |
| Dolphin Way | Redesign of Dolphin Way. | What are the plan limits and required work, and where does this scope meet the crossing areas? |
| Drydock Avenue | Sidewalk and crossing configurations. | Which segments and crossings are included, and how are their limits shown? |
| Black Falcon Avenue and Terminal Street | Sidewalk and crossing configurations. | Are limits and interfaces shown separately for each street, including the connection to Parcel C1A? |
| Parcel C1A on Terminal Street | Access and parking improvements. | What work is specified inside and outside the parcel, and what access or sequencing requirements apply? |

For bid leveling, ask each relevant trade to identify the plan sheets and workfronts included in its quote. Compare boundaries at the street-to-parcel connection and at each crossing against the same revision. If a quote excludes an interface, record who is expected to carry it or seek clarification; do not silently price a presumed gap as if the public description were a complete scope.

## Resolve the missing issued details

The public page requests contact information to obtain the bid documents. The issued IFB was not downloaded for this review. Consequently, the register cannot establish curb, signal or utility quantities, traffic restrictions, pricing units, stormwater design, access rules or duration. Review the actual drawings, specifications and addenda for those matters and submit project-specific questions through the procurement process where needed.

Keep 1476 distinct from Massport maintenance M677, Fid 1458 realignment and the future flood barrier A5. A shared street name alone does not make them the same contract or establish a scope interface. Use the project-source guide to verify the package identity, then [trace scope changes to the controlling revision](https://piper-ai.com/resources/construction-addenda-management-for-gc-estimators) as addenda arrive.
