Reconnecting Chinatown: distinguish Parcel 21 concept design from decking feasibility
Keep Parcel 21 concept design, public-realm improvements, parcel guidelines and decking feasibility in separate estimating decisions.
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 concept for Parcel 21 is not a construction-ready deck for all four Reconnecting Chinatown parcels. A preconstruction team should keep four outputs separate: Parcel 21 concept design, nearer-term public-realm improvements, guidelines for other parcels, and engineering and financial feasibility of decking. Each can inform a future estimate, but none alone fixes a structural system, quantity or construction sequence.
The City's project scope says it selected a Stoss-led planning team after its December 2023 request for proposals. That is a planning award, not a construction award. The project considers connections across the open cut of I-90 and MBTA infrastructure, a different estimating problem from ordinary sidewalk replacement.
Deliverable and decision register
| Parcel | City-described study output | Decision before a construction carry |
|---|---|---|
| 19 | Public-realm exploration, design guidelines and decking feasibility | Identify any approved near-term limits separately from an unselected deck option |
| 20 | Public-realm exploration, design guidelines and decking feasibility | Request design basis and parcel interfaces before assigning quantities |
| 21 | Concept design, public-realm exploration and decking feasibility | Separate the concept's program from a selected engineered deck design |
| 22 | Public-realm exploration, design guidelines and decking feasibility | Confirm whether any eventual issue set includes the parcel and its connections |
The City bounds Parcel 21 by Marginal Road, Washington Street, Herald Street and Shawmut Avenue. It describes guidelines for Parcels 19, 20 and 22 and feasibility work for all four. Those are different levels of definition. Record the deliverable, date and maturity beside every estimate assumption, and do not copy a concept's apparent geometry into takeoff as an approved scope.
Price uncertainty as a decision, not a hidden quantity
For a conceptual estimate, prepare separate scenarios only when the owner has defined a basis for comparison. State which parcel, assumed limits and design maturity each scenario covers. Keep near-term surface improvements separate from decking so a change in one is visible without silently changing the other. Label any allowance as an estimating assumption and document the information that would replace it.
Request the engineering feasibility findings and subsequent approved design basis before choosing a span or structural system. Rail and highway staging, access and possession constraints, ventilation and fire-life-safety solutions, utility interfaces and schedule are unresolved inputs to investigate with the responsible agencies and design team. They are not established project requirements or quantities in the City overview. The absence of a solution is itself a reason to avoid a fixed construction carry.
Advance only with a defined issue set
A useful decision gate asks: which parcel and improvement are authorized for the next design phase, which documents govern, and who owns the interfaces with transport infrastructure? When an actual procurement is issued, check its revisions and use the scope generation guide to connect package responsibilities to the relevant design evidence.
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.