Phoenix's rewritten fire code hands the watch clock to the fire marshal, and the four-hour figure is not in it

PHOENIX, Ariz.

The fire code that governs a Phoenix commercial building changed this year, and the provisions that decide what a property does when a required fire protection system fails are narrower than the version most contractors still carry. Phoenix adopted the 2024 International Fire Code with a local amendment packet under Ordinance G-7464, adopted December 17, 2025 and effective February 17, 2026. The 2018-based code the city worked under before that date is archived.

Two sections of the current text now carry most of the practical weight. Section 901.7 leaves the protective response to a required system's failure with the fire code official. Section 117, retained in the amendment packet as Phoenix's own fire watch provision, sets the qualifications, duties and release conditions for the people who fill the gap.

What the amendment does not contain is as consequential as what it does. There is no grace period, no patrol interval and no staffing ratio in the adopted local text that a property manager can apply without the Fire Department's direction, and the figures that circulate as Phoenix practice are not printed in it.

Section 901.7: the decision, not the clock

Section 901.7 addresses a required fire protection or life safety system taken out of service. Its first question is not how long a system may stay down. It is what safety function has been lost, who is exposed by that loss, and what the fire code official directs in response, including whether the affected space must be evacuated, occupied under an approved fire watch, or both.

The amendment splits the administrative path in two. Section 901.7.4 governs preplanned work: before the work is authorized, the property notifies the Phoenix Fire Department and completes an impairment-tagging process on the affected system. Section 901.7.5 governs the unplanned failure, the riser that trips overnight or the panel that goes dark after a storm, and applies an emergency response procedure instead of the preplanned sequence.

Section 901.7.6 closes the loop, requiring verification and notices when the system returns to service. That step is separate from a repair invoice. A building that treats a technician's ticket as its release has documented the repair and skipped the notification the code describes.

For a property manager the sequence produces an unusual artifact: the record that matters is not the maintenance log but the written direction from the official. A staffed post with no stated basis is a cost. A post opened on the official's instruction, staffed to the official's number and closed on the official's release is a defensible program.

Section 117: who may serve, how many, and until when

Phoenix's fire watch section is unusually concrete for a local amendment, and it is the part of the packet most often summarized inaccurately. Personnel assigned under Section 117 must be at least 18 years old, must be capable of performing the assigned duties and communicating, and must be able to walk the assigned area.

Section 117.3 gives the fire code official the authority to specify the number of personnel and the hours of their assignment according to the facility's conditions and size. The number is a decision, not a formula, and it is made by the authority that will inspect the result.

Section 117.4 defines the assignment itself: continuous rounds, watching the assigned areas, maintaining a log that is accessible, submitting a copy of that log to Fire Prevention, and continuing the watch until Phoenix Fire Department permission to terminate is received. Section 117.1.1 places the cost of providing the watch on the property owner, tenant or controlling occupant.

Read together, the sections describe a loop rather than a shift. The official decides staffing and duration. The post runs continuously until released. The log goes to Fire Prevention. The building pays for it. Any arrangement that breaks the loop at the release step is the one most likely to be found incomplete after a fire.

The four figures that are not in the text

Four numbers circulate in Phoenix commercial real estate as though the city had adopted them.

The first is a four-hour grace period before a watch is required for an out-of-service system. The current amendment does not establish it. Sections 901.7.4 and 901.7.5 require a managed impairment response, and the official's direction can require protective measures immediately, at any hour.

The second is a staffing formula of one person per floor, or one person per 50,000 square feet. Section 117.3 assigns that judgment to the fire code official, who sets the number for the facility's conditions and size. No floor count or square-footage divisor appears in the reviewed local text.

The third is a mandatory 30-minute patrol interval. Section 117.4 calls for continuous rounds, and the official may impose stricter site-specific expectations. The source reviewed does not establish a universal return interval for all impairments.

The fourth is a three-year retention term for patrol logs. Section 117 requires an accessible log and a copy to Fire Prevention. No blanket three-year term was verified in the amended text, although other records and contracts can carry their own retention obligations.

The practical risk in all four is the same. Each is a defensible engineering or management choice dressed as a legal minimum, and a manager who cites one to an inspector is citing something the city did not write.

Jurisdiction is a parcel question, not an address question

Phoenix's corporate limits extend into more than one county, and several incorporated cities sit inside the same metropolitan footprint, each with its own fire authority and its own code history. A Phoenix mailing address is therefore not evidence of which code applies to a parcel, and a campus that crosses a boundary can carry two.

Maricopa County's own determination on county-owned facilities adds another layer, and Phoenix adopted its 2024 building codes on a track separate from the fire code. The verification belongs in the impairment file before the first call is made, because the answer determines which department is notified and whose release ends the watch.

Two numbers that are published, and one that is not

The amendment lists 602-495-5555 for the Phoenix Fire Department in its planned-impairment and restoration provisions. The city's current public Fire Prevention listing uses 602-262-6771 for regulatory inquiries and fireprevention.pfd@phoenix.gov for code questions. Neither line replaces 911 for smoke, fire, injury or imminent danger, and neither substitutes for the official direction the code requires.

Assembly, events and coverage the department orders

Phoenix's amendment packet also reaches the events side of the same question. A temporary assembly with intact systems still draws a coverage expectation from the department, and the direction may add personnel for the event rather than for an impairment. The two authorizations look identical on an invoice and carry different scopes, which is why the basis for the post belongs in the file beside the post itself.

The valley's storm season adds a third case with no repair ticket attached. A monsoon outage that takes power and communications off a site can leave detection and notification degraded in a building where nothing mechanical has broken. The decision to put people in the space then belongs to the same official, for the same reason, and the record that supports it is the same record.

The environments where the decision arrives at 2 a.m.

The volume issued today works through the property types where impairment decisions carry the most exposure: high-rise office and residential towers with a disabled riser, hotels and hospitals that cannot empty, multi-tenant buildings where the tenant controls the work and the owner controls the system, construction and demolition sites with an ignition source on every level, and industrial, distribution and battery energy storage facilities where the hazard does not pause for a repair window.

It also treats hot work as a separate discipline rather than a fire watch variant. OSHA's welding and cutting standards for general industry and construction impose their own fire prevention duties, and a permitted hot-work operation inside a building with an impaired suppression system is an overlapping exposure that one post cannot automatically cover.

Arizona Department of Public Safety licensing runs alongside all of this without replacing it. The state licenses security guards and agencies; the city authorizes a fire watch and decides how it is staffed. A licensed contractor is not, by virtue of the license, an approved watch.

Published today

The findings above are drawn from Volume 16 of the USPA Fire Safety Knowledge Base, published today: a 40-chapter technical reference covering Section 901.7 impairment administration, Section 117 watch duties, jurisdictional verification, staffing engineering, documentation, seven worked scenarios and a claims audit of the figures in circulation. It carries 16 official sources, four figures, and a free two-page field brief for property teams.

The volume does not replace the code. It cites the adopted packet, the ordinance and the department's published policy, and it separates what Phoenix writes from what contractors repeat.

USPA also provides fire watch coverage in Phoenix, industrial security guards and a national emergency fire watch response, and the volume itself is available in the knowledge base.

Disclosure: USPA Nationwide Security publishes both the volume described in this article and The Watchline. The regulatory findings above are drawn from the primary documents listed under Sources, not from company statements.

This article was updated after publication to clarify the separation between the repair verification in Section 901.7.6 and the Fire Department release described in Section 117.4.