USPA Nationwide Security

Volume 16Phoenix, AZ

Phoenix Fire Watch & System Impairment Regulations

Phoenix's 2024 Fire Code effective February 17, 2026, Section 117 fire-watch duties, official-set staffing, and the impairment notification and release process under Section 901.7

Fact check

Phoenix property managers get a blanket four-hour grace period before a fire watch is required for an out-of-service fire protection system.

Not supported. Sections 901.7.4 and 901.7.5 of the Phoenix amendments require a managed impairment response: Phoenix Fire Department notification and an impairment-tag process before preplanned work is authorized, and an emergency response procedure for unplanned outages. No universal four-hour waiver appears in the adopted local amendment, and the fire code official's direction can require immediate protective measures.

Edition detail
Approved edition 1.0
Edition detail
2024 International Fire Code with Phoenix Amendments, adopted by Ordinance G-7464, effective February 17, 2026, including Sections 117, 403.11.1, 901.7, 901.7.4, 901.7.5 and 901.7.6; Arizona Department of Public Safety security licensing; OSHA 29 CFR 1910.252, 1926.352, 1910.157 and 1910.38; referenced NFPA 25 and NFPA 72 as incorporated.
Edition detail
28 pages
Edition detail
16 cited sources
Edition detail
Research cutoff 2026-11-07

By Brian Fitzgibbons, Director of Operations

No account, no payment. One email address delivers the complete edition and the library link.

The short version

What this jurisdiction actually requires

Written for the Phoenix property manager, high-rise engineer, construction director, hotel or healthcare operator and industrial facility safety lead deciding what to do the night a required detection or suppression system is out of service.

  • Phoenix adopted the 2024 International Fire Code with Phoenix amendments under Ordinance G-7464, effective February 17, 2026. The 2018-based code is archived, and renumbered provisions make older operating practice unreliable.
  • Section 901.7 leaves the response to an impaired required system with the fire code official: evacuation, an approved fire watch, or both, depending on what safety function was lost.
  • Section 901.7.4 requires Phoenix Fire Department notification and an impairment-tag process before preplanned work is authorized; Section 901.7.5 applies an emergency response procedure to unplanned failures; Section 901.7.6 requires verification and notices at restoration.
  • Section 117 sets the watch qualifications: a minimum age of 18, the capacity to perform assigned duties and communicate, and the ability to walk the assigned area. The fire code official sets how many people are assigned and when.
  • Section 117.4 requires continuous rounds, an accessible log, submission of a copy to Fire Prevention, and continuation of the watch until Phoenix Fire Department permission to terminate is received. Section 117.1.1 places the cost on the owner, tenant or controlling occupant.
  • The local text does not establish a universal four-hour grace period, a one-guard-per-floor or per-50,000-square-foot ratio, a mandatory 30-minute patrol interval, a GPS platform requirement, or a three-year log retention term.
  • The adopted amendment lists 602-495-5555 for planned impairment and restoration contact; the public Fire Prevention listing uses 602-262-6771 and fireprevention.pfd@phoenix.gov. Neither replaces 911 for smoke, fire, injury or imminent danger.
  • Arizona Department of Public Safety licensure and Phoenix fire-watch compliance are separate questions, and neither one substitutes for the Fire Department's approval of a specific post.

Field reference

The Phoenix decision card

Immediate issueWhat the responsible manager must knowSource
Code edition in force for a city parcel2024 IFC with Phoenix amendments, Ordinance G-7464, effective February 17, 2026. Verified.[S01] [S02] [S03]
Preplanned work that takes a required system out of serviceSection 901.7.4: notify the Phoenix Fire Department and complete the impairment-tag process before authorization. Verified.[S02]
Unplanned failure of a required systemSection 901.7.5 emergency response procedure applies; protective measures follow the official's direction, not a waiting period. Verified.[S02]
How many watch personnel and for how many hoursSet by the fire code official under Section 117.3 for the facility's conditions and size; no published per-floor or square-footage ratio. Verified.[S02]
What the assigned watch must actually doSection 117.4: continuous rounds, watch of the assigned areas, an accessible log, a copy to Fire Prevention, and continuation until Fire Department permission to terminate. Verified.[S02]
Releasing the watch after repairsSection 901.7.6 requires verification and notices at restoration, and Section 117.4 requires Fire Department permission before the post closes. Verified.[S02]
Who pays for the watchSection 117.1.1 assigns the cost of providing the fire watch to the owner, tenant or controlling occupant. Verified.[S02]
Contractor licensing for guard serviceArizona DPS security licensure is a separate requirement from fire-watch authorization. Verified.[S05]
Hot work during an impairment or construction phaseOSHA 29 CFR 1910.252 and 1926.352 set welding and cutting safeguards alongside the fire code's own hot-work provisions. Verified.[S06] [S07]

Informational only. Applicable adopted codes, written orders and the authority having jurisdiction control in every case.

Inside the edition

Chapter index

The edition reads the 2024 Phoenix Fire Code and its amendment packet rather than a national shorthand. It keeps two instruments apart: the Section 901.7 impairment process for a required system taken out of service, and the Section 117 fire watch, with its qualifications, official-set staffing and hours, continuous rounds, log submission and release only on Phoenix Fire Department permission. It also documents what the local text does not say, so a manager can stop citing a four-hour grace period, a per-floor guard ratio or a 30-minute patrol interval as Phoenix law.

Download the two-page brief
  1. 01

    What this publication covers—and why source hierarchy matters

    A single fire-watch request often implicates several subjects that have different legal purposes.

  2. 02

    Jurisdictional boundaries: a Phoenix mailing address is insufficient

    Phoenix contains a large urban footprint, but the greater Valley of the Sun also includes incorporated cities, tribal lands, unincorporated Maricopa County areas and fire-district territories with potentially different adoption dates and enforcement organizations.

  3. 03

    Code history: what changed in 2026

    Phoenix City Council adopted the 2024 IFC with Phoenix amendments on December 17, 2025 through Ordinance G-7464; the City lists an effective date of February 17, 2026.

  4. 04

    Section 901.7: required protection systems out of service

    The operational problem begins with the nature of the impairment.

  5. 05

    Preplanned and emergency impairment administration

    Section 901.

  6. 06

    Section 117: who can serve, how many, and whose job it is

    The Phoenix Fire Code's local Section 117 is the principal distinction from a generic nationwide fire-watch guide.

  7. 07

    Section 117.4: enforceable duties, logs and release controls

    A good fire-watch manual should be organized around actions that an inspector can confirm at the facility.

  8. 08

    Planned impairments: the authorized-work package

    Planned shutdowns lend themselves to strong preventive controls, and they often become emergencies because a manager treats the pre-work permit as a formality.

  9. 09

    Unplanned system failures: first-hour emergency management

    An emergency impairment can originate in an electrical fault, sprinkler leak, pump failure, flooding, panel trouble, accidental isolation or unplanned utility disruption.

  10. 10

    Staffing engineering: continuous rounds and route capacity

    Phoenix's Section 117.

  11. 11

    Communications and the first minutes of a discovered fire

    Under Section 117.

  12. 12

    Documentation engineering and audit integrity

    A fire-watch log is evidence of patrol performance; it is not a replacement for the system repair record.

  13. 13

    Arizona DPS security regulation and fire-watch assignments

    Arizona's Department of Public Safety licenses security guard businesses and regulates registered guards under Title 32, Chapter 26 of the Arizona Revised Statutes.

  14. 14

    Special assemblies, events and PFD-directed coverage

    Phoenix Section 403.

  15. 15

    Construction and demolition: a different ignition environment

    Phoenix construction projects present constantly changing fire risk.

  16. 16

    Hot work: distinct permits, training and post-work monitoring

    Welding, grinding, torch cutting, brazing and allied hot work can project sparks, transfer heat through partitions and ignite hidden combustibles.

  17. 17

    High-rise, hospitality, healthcare and multi-tenant operations

    In a high-rise, a partial system failure may disable portions of a voice evacuation network, smoke-control interface, standpipe or phased alarm operation.

  18. 18

    Industrial, distribution and energy-storage facilities

    Phoenix's industrial facilities can combine high-piled storage, deep rack aisles, heavy equipment, temporary maintenance work, battery equipment and large roof spaces.

  19. 19

    Arizona climate, outages and operational continuity

    Phoenix presents specific environmental stresses that can alter field conditions.

  20. 20

    Fire Prevention costs, fees, enforcement and municipal service claims

    The adopted Phoenix Section 117.

  21. 21

    Regulatory myths and their evidence-based answers

  22. 22

    A management model for reliable compliance

    The strongest operating model uses explicit ownership of every decision.

  23. 23

    Worked scenario 1: multifamily tower with a disabled alarm riser

    The impairment coordinator identifies the exact impacted notification circuits, confirms the boundary with the alarm contractor, and contacts the responsible Phoenix authority under the applicable impairment process.

  24. 24

    Worked scenario 2: warehouse sprinkler riser isolated for repair

    The coordinator verifies which risers and aisles are unprotected and follows Phoenix's impairment process; management obtains the protective action required by the authority.

  25. 25

    Worked scenario 3: hotel during a planned sprinkler shutdown

    Section 901.

  26. 26

    Worked scenario 4: a concert event with intact systems

    Phoenix Section 403.

  27. 27

    Worked scenario 5: construction hot work during a partial impairment

    The operator should assess both hot-work and system-impairment duties under their distinct provisions.

  28. 28

    Worked scenario 6: monsoon-related power and communications disruption

    Management documents which protection functions still operate and which are impaired, and verifies jurisdiction for each affected building.

  29. 29

    Worked scenario 7: repair is complete but watch release is missing

    The technical repair may be valid, but the administrative closeout is incomplete.

  30. 30

    Final executive synthesis

    Phoenix's current legal architecture is unusually clear about who makes the staffing decision and who may close an assignment.

  31. 31

    Appendix A. Fire-watch activation and authorization worksheet

  32. 32

    Appendix B. Personnel qualification and induction record

  33. 33

    Appendix C. Fire-watch tour record — Phoenix §117.4

  34. 34

    Appendix D. Shift handoff and relief protocol

  35. 35

    Appendix E. Fire Department notification and communication log

  36. 36

    Appendix F. Route mapping and staffing-feasibility sheet

  37. 37

    Appendix G. Hot-work interaction and separation record

  38. 38

    Appendix H. System restoration, log submission and release checklist

  39. 39

    Appendix I. Technical review and audit checklist

  40. 40

    Primary-source reference registry

    The following references identify primary official sources.

  41. The complete edition runs 28 pages and carries the full analysis, forms and citation registry.
Figure 1. Verifying the local fire authority for a parcel inside the Phoenix metropolitan area.
Figure 1. Verifying the local fire authority for a parcel inside the Phoenix metropolitan area.
Figure 2. From discovery and official notification to verified restoration under Section 901.7.
Figure 2. From discovery and official notification to verified restoration under Section 901.7.
Figure 3. Route-based staffing for continuous rounds; no citywide interval is inferred.
Figure 3. Route-based staffing for continuous rounds; no citywide interval is inferred.
Figure 4. Separate service, patrol and official-decision evidence streams.
Figure 4. Separate service, patrol and official-decision evidence streams.

Free delivery

Get the complete Phoenix edition

The complete edition carries the code-by-code analysis, fire-watch design methodology, incident scenarios, the field forms, the permit review matrix and the full source registry. It is free, and it is sent to one address of your choosing.

  • Complete edition as a PDF, downloadable for one hour from the email.
  • The two-page field brief, always free to read.
  • A link to every other published volume in the library.
  • No account, no payment, no subscription required.

Need coverage on a site tonight? Dispatch answers around the clock at (800) 214-1448.

Free complete edition

Email me the complete Phoenix guide

One email address is all we ask for. You will receive the full edition as a PDF, the free two-page field brief, and a link to the rest of the regulatory library. No account, no payment, no subscription.

We use your address to send this guide and to honour the contact choice above. It is not sold, and it never appears on a public page. See the privacy notice.

Evidence

Source and evidence registry

Every citation is listed so a reader can check the underlying document rather than take a summary on trust.