Mary Ellen McCormack: distinguish Building A turnover from the next construction phase
Treat Building A acceptance and resident transition as evidence gates for a successor phase, not as completed milestones inferred from a forecast.
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
A forecast completion date for Building A does not prove the successor work area is ready. At Mary Ellen McCormack, test acceptance, resident transition, utilities and public-space access separately before relying on a next-phase start.
What the developer forecast says about Buildings A and its successors
The developer’s information forecasts Building A in fall 2026 and successor work in early 2027, following A completion. It describes 492 homes in the later buildings, including senior housing in C1. These forecasts do not establish actual completion or an open contract. Source: Developer MEM information.
Keep completion, financial closing and construction commencement separate
The BHA’s October 28, 2026 draft 2027 annual-plan supplement, pages 69 and 74, reports that the 94-unit Building A closed and construction began in March 2025. It forecasts A completion in November 2026, Building C financial closing in spring 2027 and Building B closing in fall 2027. These are the draft’s reported milestone and forecasts, not an approved final plan or evidence of acceptance, occupancy or handover.
A financial closing forecast is a different event from the developer’s forecast of successor construction commencement. Keep the source, building label and milestone type in separate fields; do not silently equate BHA’s B/C labels with every developer B1/B2 or C1/C2 suffix. The developer page also retains prospective winter-2025 start language, so use it as a source account rather than proof that construction has not started. Obtain the current package schedule and actual release evidence before committing to the successor work area.
Test the predecessor handoff rather than assume it
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 |
|---|---|---|
| A acceptance | The developer describes 94 replacement homes in Building A. | Request actual acceptance and turnover status, open work and the party authorizing handoff. |
| Resident move | The program links replacement housing to phasing. | Verify the relocation plan, actual readiness and who controls the release of the next work area. |
| Utilities and services | Continuity is a practical interface to resolve. | Obtain cutover plans, service ownership and any required temporary service basis. |
| Park and access | The developer associates Veterans Park, a tot lot and splash pad with the program. | Confirm completion, access and protection obligations for each phase rather than assuming transfer. |
| Successor package | The developer describes later B1/B2 and C1/C2 buildings. | Identify the current package limits, milestone dependencies and the controlling schedule revision. |
Keep the successor start conditional
In an illustrative schedule review, the successor start remains conditional until the responsible party documents both the predecessor handoff and access to the successor work area. A forecast date can be a planning assumption, but it should not be entered as an achieved milestone.
Request acceptance, relocation and utility evidence
Request the accepted handoff record, current relocation and utility plans, park boundaries, schedule and issued successor documents. Verify actual status directly before making a pursuit or sequencing decision.
A confirmed handoff becomes part of the successor package scope. Keep later document changes connected to the acceptance and access assumptions they affect; do not let a forecast start conceal an unresolved predecessor condition.
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.