---
title: 'White Stadium renovation: separate the public and private scope before pricing'
url: 'https://piper-ai.com/resources/white-stadium-renovation-contractor-scope-guide'
description: 'Separate White Stadium’s public and private contracting contexts, then use an interface register to identify scope questions before pricing a trade package.'
contentTypes: [guide]
publishedAt: '2026-11-22T04:05:53.653Z'
updatedAt: '2026-11-22T04:05:53.673Z'
author: 'Ido Gedanken, CEO'
readingTime: 2
---

# White Stadium renovation: separate the public and private scope before pricing

White Stadium is an active renovation, not a newly advertised general-contractor opportunity established by the sources here. For a contractor considering remaining work, the first pricing question is which team issued the package and where its obligations meet the other team's work. Obtain the actual issued documents before assigning a boundary or assuming a package is available.

## What the public record establishes

The [City project page](https://www.boston.gov/departments/schools/project/white-stadium) identifies Boston Public Schools as owner, a partnership with Boston Legacy Football Club (BLFC), and construction underway in Franklin Park. The City's [February 10, 2026 progress announcement](https://www.boston.gov/news/mayor-michelle-wu-shares-progress-updates-white-stadium) identified BOND as general contractor for the publicly funded East side and described the separately funded BLFC West side. It said public bidding for the East side was complete at that time. The [supplier diversity page](https://www.boston.gov/departments/mayors-office/white-stadium-supplier-diversity-initiative) distinguishes City contracts subject to public procurement law from BLFC contracts under different constraints.

These descriptions establish separate contracting contexts, not the exact boundary of a current trade package. They do not establish a current invitation, eligibility or any contractor's right to bid.

## Build an interface register before carrying scope

The following questions are illustrative. They do not assign responsibility for actual White Stadium work. Ask the issuing team for current drawings, specifications, interfaces, schedule and written answers.

| Interface | Owner or issuer and evidence to request | Estimate treatment until resolved |
| --- | --- | --- |
| Utility connection | Ask issuing team for connection point, utility drawings and responsibility matrix | Identify tie-in, shutdown and testing assumptions; flag exclusions |
| Field and track | Ask for current boundary details, elevations and sequence | Separate preparation, edge work and reinstatement assumptions |
| Shared access | Ask each relevant team for site logistics and access windows | Carry a stated access basis and identify potential conflicts |
| Testing and turnover | Ask for commissioning, acceptance and handover requirements | Identify who performs, witnesses and documents each test |

For each row, add a named question owner, document revision, deadline and response. If the issued documents do not place a connection or testing obligation clearly, seek written clarification from the package issuer rather than assigning it to the other side by assumption. Carry an explicit allowance only under the bid instructions and make its uncertainty visible to the decision-maker.

## Treat the schedule as a changing input

The February announcement is a historical progress statement. The [current project page](https://www.boston.gov/departments/schools/project/white-stadium) lists expected completion in 2027, while the separate [construction updates page](https://www.boston.gov/departments/mayors-office/white-stadium-construction-updates) describes work toward a summer 2027 opening. Neither is a guarantee. Obtain the package schedule and verify access, sequencing and milestones with the issuer before pricing. A historic announcement cannot establish today's available work or field conditions.

Use the [construction scope generation guide](https://piper-ai.com/resources/construction-scope-generation-guide) to frame packages, [construction addenda management for gc estimators](https://piper-ai.com/resources/construction-addenda-management-for-gc-estimators) for revisions, and [spot scope gaps before you carry](https://piper-ai.com/resources/spot-scope-gaps-before-you-carry) to close unresolved interfaces.
