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

A design-maturity register keeps the Rutherford Avenue estimate tied to the alternatives, right-of-way and future package decisions still open.

Guide2 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. What the May presentation establishes
  2. Register the alternative before carrying a cross-section
  3. Reconcile the next design issue

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 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 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 assumptionEvidence to obtainConsequence if unresolved
At-grade replacement and street gridCurrent plans, limits and existing-structure treatmentCarry boundary and demolition uncertainty
Side or center bus prioritySelected alternative and platform sectionsDo not price a single assumed layout as final
Linear park and crossingsCurrent limits and interfaces with road and landscapeIdentify transitions and access scope
Permitting and right of wayCurrent approvals and property statusSeparate assumed access from secured rights
Ryan Playground coordinationInterface documents and package limitsAvoid assuming a shared contract or duplicate carry
Future procurementIssued bid package and phasingIdentify 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, and check the actual issued revision before a buyout decision.

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.