The City of Boston’s Façade Inspection & Safety Program is often viewed narrowly as a regulatory requirement. In practice, the ordinance functions as a risk management and asset-planning tool that—when executed properly—provides building owners with clarity, predictability, and long-term value.
Understanding the ordinance’s terminology—particularly the classifications of Safe, Unsafe, and Safe With a Repair and Maintenance Program (SWARMP)—is essential to realizing these benefits.
Boston’s Façade Inspection & Safety Program, codified in Section 9-9.12 of the City of Boston Municipal Code, is intended to protect public safety by requiring systematic evaluation of exterior walls and appurtenances where deterioration or detachment could pose hazards to pedestrians and occupants.
The ordinance applies to:
- Buildings over seventy (70) feet in height
- Certain unoccupied buildings exceeding 35,000 cubic feet

It does not apply outside the City of Boston.
For occupied buildings over 70 feet tall, the ordinance mandates a hands-on façade inspection at least once every five (5) years by a Massachusetts-licensed design professional (registered architect or engineer) with façade assessment expertise.
For qualifying unoccupied structures, inspections are required annually. Reports must be filed with the City of Boston’s Inspectional Services Department (ISD) for issuance of an exterior wall certificate.
Façade Classifications Under the Ordinance
A critical component of the ordinance is the classification assigned to the façade. Each designation carries specific meaning and obligations.
Safe
Definition
A Safe classification indicates that no conditions were observed that pose a threat to public safety at the time of inspection. The façade is performing as intended, with no significant distress or instability noted.
Examples
- Intact masonry with tight mortar joints and no displacement or cracking
- Secure stone or precast panels with no signs of movement or anchorage distress
- Minor weathering consistent with age but not affecting safety or performance
Important: A Safe designation does not mean maintenance-free. Environmental exposure and aging continue, and periodic monitoring remains prudent.
Unsafe
Definition
An Unsafe classification is assigned when conditions present an immediate or potential hazard to persons or property. These conditions require prompt action and formal notification to ISD.
Examples
- Loose or displaced masonry units at risk of falling
- Delaminated concrete with exposed reinforcement and active spalling
- Cracked or displaced terra cotta or stone elements lacking adequate support
Required Response Timeline
When unsafe conditions are identified:
- Within 12 hours: The design professional must notify ISD
- Within 24 hours: Public protection measures (sidewalk sheds, fencing, netting) must be installed
- Within 10 days: Repair work must commence by a qualified contractor
Proper coordination is critical. Delays increase liability exposure, cost, and operational disruption.
Safe With a Repair and Maintenance Program (SWARMP)
Definition
A SWARMP classification indicates that the façade is currently safe but exhibits conditions likely to deteriorate into unsafe conditions before the next inspection cycle.
Examples
- Deteriorated mortar joints requiring repointing
- Early-stage cracking or corrosion distress
- Sealant failures or flashing deficiencies contributing to moisture intrusion
Under SWARMP, the façade remains safe only if the recommended repairs are completed in accordance with the submitted program and schedule. Failure to execute the plan may result in reclassification and enforcement action.
Why Inspection Quality Matters
The ordinance’s value is directly tied to the quality of inspection and reporting.
An experienced design professional provides value by:
- Accurately categorizing conditions
- Documenting findings consistent with ISD expectations
- Developing realistic SWARMP schedules aligned with budgeting cycles
- Coordinating rapid stabilization and repair when required
When inspections are thorough, façade reports become multi-year capital planning tools—not just compliance paperwork.
A well-prepared report should:
- Differentiate between immediate repairs, near-term maintenance, and long-term restoration
- Identify deterioration trends and root causes
- Support phased repair strategies aligned with reserve studies and capital budgets
Stakeholders Impacted by the Ordinance
The ordinance affects multiple ownership and management groups:
Condominium and Homeowner Associations
Residential mid-rise and high-rise buildings often fall within the ordinance’s scope. Boards must plan inspections, budget for SWARMP programs, and communicate clearly with owners regarding funding and timelines.
Commercial Landlords and Office Owners
Downtown office towers face heightened exposure due to pedestrian traffic. Unsafe classifications can disrupt tenant operations and require sidewalk closures or protective installations affecting building access.
Institutional Owners
Hospitals, universities, and civic buildings must integrate façade compliance into broader facility management programs, often across multiple structures of varying ages and systems.
Property Managers and Facility Directors
For managers overseeing multiple assets, the ordinance functions as both a compliance requirement and an early-warning system. Proper documentation supports capital planning and reserve forecasting.
Strategic Value Beyond Compliance
The Boston Façade Ordinance is fundamentally a public safety regulation. However, its greatest value emerges when approached strategically.
A clear understanding of Safe, Unsafe, and SWARMP classifications—combined with the involvement of an experienced design professional—allows owners to:
- Reduce risk
- Respond efficiently to hazards
- Plan façade investments confidently
- Align façade work with long-term capital improvement strategies
When properly executed, compliance becomes more than a requirement. It becomes a foundation for responsible long-term stewardship of the building envelope.
Principal
Duffy Engineering


