Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Gaithersburg introduces update to Chapter 11 to align with NFPA 2024 standards

December 02, 2025 | Gaithersburg City, Montgomery County, Maryland


This article was created by AI summarizing key points discussed. AI makes mistakes, so for full details and context, please refer to the video of the full meeting. Please report any errors so we can fix them. Report an error »

Gaithersburg introduces update to Chapter 11 to align with NFPA 2024 standards
The Gaithersburg City Council on Dec. 1 introduced an ordinance to update the city's Chapter 11 fire code to align with the National Fire Protection Association's 2024 editions and related standards.

Fire Marshal Michael Semelsberger told the council the changes are largely renumbering and alignment with the state adoption of the 2024 edition but include a handful of substantive updates. Among them: the city would require that building owners submit fire protection system inspection/test reports through a city‑identified third‑party data management company (the "compliance engine" used statewide) rather than directly to the fire marshal; the fire marshal would be able to withhold final approval of permits where inspection and test records are overdue; and the code would add a definition of "work area" to clarify when substantial renovations trigger an automatic sprinkler requirement (for example, when the work area exceeds 50% of a building's gross area).

Semelsberger said the change to require submission through a data manager resolved a recurring compliance problem and that the city contracts with the compliance engine program; he noted a fee is associated with that service. Semelsberger explained the new permit withholding subsection is intended to prompt building owners to update overdue records without delaying plan review.

Council discussion focused on drafting and flexibility: Council members asked whether the ordinance should allow the city to change the designated third‑party provider. City Attorney Frank Johnson and other staff proposed clarifying language to refer to a "city‑identified third‑party management company" or to insert a reservation allowing the city manager to direct an alternate recipient; the council agreed to review wording before the public hearing.

The council moved to introduce the ordinance at the Dec. 1 meeting; the motion to introduce passed. Staff said a public hearing on the ordinance is expected in January.

Ending: The ordinance was introduced; the council directed staff to refine the wording about the city's designated data manager before the public hearing and scheduled further consideration at a public hearing in January.

Don't Miss a Word: See the Full Meeting!

Go beyond summaries. Unlock every video, transcript, and key insight with a Founder Membership.

Get instant access to full meeting videos
Search and clip any phrase from complete transcripts
Receive AI-powered summaries & custom alerts
Enjoy lifetime, unrestricted access to government data
Access Full Meeting

30-day money-back guarantee

Sponsors

Proudly supported by sponsors who keep Maryland articles free in 2025

Scribe from Workplace AI
Scribe from Workplace AI