Jackson Mann site planning: separate community-center, housing and school assumptions
Keep the community center, housing and possible school as separate concept scenarios until the Jackson Mann program is adopted.
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
At the Jackson Mann site, the community center, housing and possible school are planning variables with different evidence needs. Build separate concept scenarios instead of combining them into one implied contract. Keep the assumed program visible until the owner adopts a scenario.
The Jackson Mann study has not settled one program
The Jackson Mann site at 500 Cambridge Street is in study and planning. The city describes an October 2026 proposal and feasibility work across public assets and housing. This is not evidence of an open construction opportunity. Source: Allston-Brighton Community Center Education adopted profiles.
Keep the center, housing and possible school as separate variables
This register separates the dated public record from the evidence needed to assign and price the work. Proposed questions do not establish contract scope.
| Interface | What the record establishes | What the estimate needs |
|---|---|---|
| Community center | The city is testing center sizes in the shared-site study. | State the assumed program and source version; price alternative sizes separately. |
| Housing | The feasibility work tests a housing mix. | Keep unit mix and quantity as variables until an adopted scenario supplies them. |
| School | The study identifies a possible elementary school; the adopted education profile lists Allston Elementary design to be scheduled. | Treat school inclusion and scope as a decision fork, not a final site or procurement commitment. |
| Shared access and utilities | Programs share a site-planning context. | Model access, service and temporary-work interfaces as provisional allowances with a named source and decision owner. |
Compare scenarios with one changed assumption
A useful concept register has two columns for each scenario: what the city record says and what the estimator assumed. For example, one option can include a possible school and another omit it; hold center and housing assumptions constant when isolating the difference. Neither option represents an adopted design.
Request an adopted program before treating it as a package
Obtain the adopted program and site alternative, survey, utility information, access concept, delivery boundaries and latest owner decision. Record the author and version of each assumption and retire superseded scenarios.
When the owner selects a scenario, use scope generation to turn its confirmed program and interfaces into package responsibilities. Keep superseded scenario assumptions in the revision trail, so a later estimate does not silently retain an abandoned option.
Related reading
Construction scope generation: a practical guide for GCs
How general contractors turn drawings, specifications, addenda, and company standards into trade scopes a subcontractor can price, an estimator can trace, and a senior reviewer can challenge.

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.