---
title: 'Rutherford and Sullivan Square: keep the estimate tied to design maturity'
url: 'https://piper-ai.com/resources/rutherford-sullivan-square-pre25-design-estimate-review'
description: 'A design-maturity register keeps the Rutherford Avenue estimate tied to the alternatives, right-of-way and future package decisions still open.'
contentTypes: [guide]
publishedAt: '2026-11-21T23:50:42.861Z'
updatedAt: '2026-11-21T23:50:42.885Z'
author: 'Ido Gedanken, CEO'
readingTime: 2
---

# Rutherford and Sullivan Square: keep the estimate tied to design maturity

The May 2026 Rutherford Avenue and Sullivan Square presentation is a design-maturity record, not a construction-ready scope. A preconstruction estimate should carry the selected alternative and its revision explicitly, then distinguish priced work from unresolved right-of-way, permitting and package interfaces.

## What the May presentation establishes

The [City's May 6 pre-25% presentation](https://content.boston.gov/sites/default/files/file/2026/05/2026-05-06_Rutherford%20Avenue%20Pre-25%25%20Community%20Meeting.pdf) describes an at-grade corridor, a new street grid and a linear park. It anticipated a May 21 submission to preserve funding, design, permitting and right-of-way work in 2026–2030, and a 2031 construction start. Those were expectations at the presentation date, not proof of submission approval or a guaranteed start. The [project hub](https://content.boston.gov/departments/transportation/project/rutherford-avenue-sullivan-square-design-project) identifies coordination with Ryan Playground; coordination does not establish a shared contract.

## Register the alternative before carrying a cross-section

The City compared side-running and center-running bus priority. Its table identifies more design and phasing flexibility and more linear-park space for side-running, alongside curb and right-turn management. Center-running requires more platform space and has less design and phasing flexibility in that comparison. These are design tradeoffs, not construction productivity estimates.

| Estimate assumption | Evidence to obtain | Consequence if unresolved |
| --- | --- | --- |
| At-grade replacement and street grid | Current plans, limits and existing-structure treatment | Carry boundary and demolition uncertainty |
| Side or center bus priority | Selected alternative and platform sections | Do not price a single assumed layout as final |
| Linear park and crossings | Current limits and interfaces with road and landscape | Identify transitions and access scope |
| Permitting and right of way | Current approvals and property status | Separate assumed access from secured rights |
| Ryan Playground coordination | Interface documents and package limits | Avoid assuming a shared contract or duplicate carry |
| Future procurement | Issued bid package and phasing | Identify scope owner and bid basis |

This register is an estimator's recommended review, not the City's issued scope allocation. Record design milestone, source revision, cost assumption, responsible reviewer and date of the next decision for each line. A mature-looking budget should not turn unselected cross-sections or unverified utility relocations into commitments.

## Reconcile the next design issue

When the next set arrives, compare the selected transit arrangement and platform boundaries against the carry, then separately review property, utility and construction-phase assumptions. Record what changed and which trade estimates are stale. [Trace package responsibilities to project evidence](https://piper-ai.com/resources/construction-scope-generation-guide), and [check the actual issued revision](https://piper-ai.com/resources/construction-addenda-management-for-gc-estimators) before a buyout decision.
