Boston flood reviews: distinguish FEMA flood standards from Article 25A resilience
Use separate maps and design decisions for Boston flood-hazard and coastal-resilience reviews before pricing elevations and closeout evidence.
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
- 1 min
- Published
A Boston estimator should ask the design team for two separate flood-review decisions before carrying utility elevations or enclosure details. The FEMA-based Article 25 Flood Hazard District and the Article 25A Coastal Flood Resilience Overlay District have different bases; a result on one map does not settle the other.
Inspectional Services identifies Article 25 with FEMA's Special Flood Hazard Area and distinguishes the Planning Department's overlay. Boston Planning describes Article 25A's future coastal flood mapping and design elevations. The designer and authorities must establish which provisions apply to this project.
Keep map, datum and evidence in one bid record
| Decision | Responsible evidence | Pricing or handoff effect |
|---|---|---|
| Article 25 | FEMA map version and district determination | Identify flood review and permit documentation |
| Article 25A | Overlay map and resilience design basis | Check separate elevation and design implications |
| Existing work | Designer's substantial improvement or damage assessment and valuation basis | Avoid assuming a limited alteration avoids current standards |
| Details | Design elevations and datum, utility and enclosure details, tests and certifications | Assign trades and detail gaps before leveling |
| Closeout | As-built flood certificate and responsible design professional | Carry survey and documentation through occupancy |
The City describes substantial improvement or damage in relation to improvement or repair cost exceeding 50% of building market value. The designer and authority should determine the applicable valuation, freeboard and standards. Do not calculate a compliance outcome from a preliminary trade total. If the elevation basis changes, revisit equipment supports, penetrations, enclosure work and survey responsibility together.
At bid handoff, show each unresolved map or datum decision, the person who must answer it and the affected allowance or milestone. The code-basis review helps trace the resulting requirements, while the Boston decision guide identifies other independent reviews.
Related reading
Construction code requirements: confirm the applicable basis before assigning scope
A model-code reference is not a project applicability decision. Review connecting adopted requirements, issued design information, trade scope and pricing.

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.