Muñiz and Orchard Gardens: distinguish heat-pump and roof study scope
Compare two Boston school studies by project ID, roof assumption and the evidence needed before a construction package can be priced.
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
For an early preconstruction review, carry two separate school records. The July 2026 City notice identifies heat pumps at Margarita Muñiz Academy and both roof and heat pumps at Orchard Gardens. A shared program heading is not a basis for assigning a full roof replacement to each school. Nor does a heat-pump-only label rule out roof work that a later design may establish.
The distinction is a study-stage reading, not a construction scope. The July 29 Public Facilities Commission notice sought authority for Skanska owner project manager services and Rist-Frost-Shumway design services through feasibility and schematic design. It does not establish executed contracts or a construction tender.
Keep each school and its evidence separate
| Record | Dated owner evidence | Estimator's next evidence request |
|---|---|---|
| Muñiz Academy, 20 Child Street, MSBA 202500350549 | July notice: heat pump; October report as of October 2: OPM selection and heat pump | Feasibility and schematic documents identifying equipment, roof penetrations and any proposed roof work |
| Orchard Gardens, 906 Albany Street, MSBA 202500350257 | July notice: roof and heat pump; October report as of October 2: OPM selection, heat pump and roof | Roof survey, proposed extent and mechanical interfaces in the issued design |
The October MSBA project overview records those categories and project IDs at its October 2 reporting date. It is a snapshot, not proof that selection or subsequent design has progressed since then.
An earlier March appropriation attachment used heat-pump-and-roof language for Muñiz. Keep that discrepancy in the record rather than silently overwriting it. The later July notice and October report provide the narrower school-specific basis for this review; neither proves a Muñiz roof element can never return.
Build a reviewable package assumption
For Muñiz, label roof replacement unconfirmed, and separately ask whether the eventual mechanical design touches roofing, supports or penetrations. A small roof interface and a replacement roof are different cost and package questions. For Orchard Gardens, start a roof-plus-mechanical interface log, but do not assign quantities or trade responsibility from a program label. Request existing-roof condition, limits of replacement, proposed equipment locations, penetrations and any sequencing constraints from the issued set.
At each school, record the source date and revision beside the assumption, the affected estimate line, the open question and the person responsible for resolving it. If the schematic design changes a roof boundary, update both the roof and mechanical assumptions. The scope generation guide explains how to trace package responsibilities to project evidence; the addenda guide helps teams check the actual issued revision when a bid set exists.
Turn the study into bid boundaries
Before inviting trade prices, obtain the actual issued drawings, specifications, schedule and any addenda for each school. Reconcile roof limits, electrical supply, equipment supports, testing and restoration between the relevant packages. Record any unresolved interface as an explicit qualification or question, rather than embedding an assumed assignment in a carry. Capacities, final bid responsibilities and a construction tender were not established by the cited study records.
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.