A fire marshal calls two weeks after your sprinkler impairment closed. He isn’t asking whether the watch happened. He’s asking you to prove it: who you called, when the watch started, who signed off when the contractor restored the system, and where that paperwork lives now. You remember the impairment. You don’t have the file.
Yes, most adopted fire codes expect a documented record of a fire watch, not just the fact that one occurred, and the authority having jurisdiction (AHJ) can ask to see it during or after the impairment. The record generally needs four pieces: the order or permit that triggered the watch, the notifications sent to the fire department and other parties, the patrol log proving the rounds happened, and the authorization and release entries showing who started and ended the watch. Local adoption and the specific AHJ’s expectations vary, so confirm the exact format with your fire marshal’s office, but the substance of what gets asked for is consistent across jurisdictions.
The code expects an evidence trail, not a verbal account
Fire watch requirements under the International Fire Code’s impairment provisions and under NFPA 25 for water-based systems are written around the idea that someone qualified is monitoring a hazard the automatic system would normally catch. The code doesn’t stop at requiring the watch. It expects the building to be able to demonstrate, after the fact, that the watch actually met the standard.
That demonstration is the documentation. An AHJ who shows up mid-impairment wants to see a current patrol log and the order or permit authorizing the watch. An AHJ who shows up after the fact, during a routine inspection or in response to a complaint, wants the whole file: who was notified, who authorized the start, who verified the restoration, and who released the watch. Local amendments and the specific fire marshal’s practice affect exactly what’s checked, so treat the categories below as the baseline every AHJ tends to ask about, then confirm specifics locally.
The stakes for getting this wrong aren’t limited to an awkward phone call. A fire watch with no paper trail can leave a property manager unable to prove the building was ever brought back into compliance, which matters if a fire occurs anywhere near the impaired system months later and an insurer or a plaintiff’s attorney starts asking questions. Documentation isn’t paperwork for its own sake. It’s the only thing standing between “we handled it” and “we can prove we handled it” once the impairment is history.
An order, a permit, or a tag starts the paper trail
Every fire watch has a trigger, and the trigger should be on paper before the first patrol starts. That might be a fire marshal’s written order following an enforcement action, a hot work permit issued under NFPA 51B, or an impairment tag placed on a sprinkler riser or fire alarm panel when a contractor takes the system offline. Whatever form it takes, this document is the top of the file. It states what’s impaired, why, and what response the code or the order requires.
Property managers sometimes treat the tag or the permit as throwaway paperwork once the watch starts. It isn’t. When an AHJ asks for the record later, this is the document that establishes the watch was actually required and that the response matched the trigger. Losing it, or never having a written version of a verbal order, is a documentation gap that’s hard to fix retroactively.
Hot work and construction watches need their own permit trail
Not every fire watch starts with a broken system. A watch triggered by hot work under NFPA 51B, or by construction activity under the local building code, generates its own paperwork before a single patrol begins. A hot work permit typically documents the specific operation, the location, the combustibles cleared from the area, the fire watch duration required after work stops, and the name of the person responsible for the watch. That permit is the trigger document for this category of watch the same way an impairment tag is the trigger for a sprinkler or alarm outage.
Construction sites carry an added wrinkle: the trigger and the watch duration can both shift as the job progresses. A standpipe that goes into service partway through a build changes what’s required. A fire watch coordinator on an active job site should treat the permit file as a living document, updated whenever the site’s protection status changes, rather than a one-time form filled out on day one and never revisited.
Notification records prove who was told and when
Under most adopted impairment rules, several parties need to know a system is out of service, and the code cares about proof of that notification, not just the notification itself. The fire department typically gets a non-emergency call at the start of the impairment and again at restoration. The fire code official or AHJ gets notified where the code or the order requires it, following the pattern set out in IFC 901.7. The alarm or monitoring company needs to know so it doesn’t treat live signals as false alarms during the impairment, and any insurance carrier tied to the property usually has its own notification terms under the policy or the impairment permit.
The gap almost every site falls into is treating these calls as informal. Someone phones the fire department, gets a name, and moves on without writing it down. Weeks later, when the AHJ asks who was notified and when, memory is what’s left, and memory does not hold up as documentation. A simple notification table, with a column for the party, the time, and the source requirement, closes that gap and takes minutes to fill in as the calls happen. The alternative is trying to reconstruct times from memory during an inspection, which rarely goes well.
FFWG’s notification and authorization record lays out exactly this structure: a table of who was told and when, alongside blocks for who authorized the watch to start, who verified the restoration, who removed the impairment tag, and who released the watch at the end. Those five data points, kept in one place, are what most AHJs are actually looking for when they ask to see the file.
A useful discipline is assigning one person, the impairment coordinator, as the sole owner of this record. That might be the facility manager, a site superintendent, or the fire watch provider acting on the owner’s behalf. One owner, one file, beats a record scattered across three people’s phones and a contractor’s paper log, and it gives the AHJ a single person to ask when a question comes up later.
The patrol log is the record of what the guard actually did
Notification records prove the process. The patrol log proves the work. Every round a guard walks should generate a timestamped entry: the time of the patrol, the areas checked, any hazard noted, and any corrective action taken. If extinguishers or hose stations are part of the coverage area, the log should reflect that they were checked and found ready, not just that the guard was present in the building.
A blank or thin patrol log is one of the fastest ways a fire watch gets flagged in an AHJ review. If the log shows the same handwriting entering the same generic note every hour, or shows large unexplained gaps, an inspector reasonably questions whether the rounds happened at all. A patrol log that shows specific findings, varying language, and consistent intervals matched to the code-required frequency reads as a genuine record because it looks like one.
Authorization and release entries close the loop on both ends
A fire watch has a start and an end, and both need a named person attached to them, not just a timestamp. The authorization entry answers: on whose authority did the watch begin, and under what order or permit? The release entry answers the same question for the other end: who verified that the system was restored, who confirmed with the contractor or alarm company that it was actually back in service, and who gave the authority to stand the watch down.
That second half gets skipped more often than the first. A contractor finishes the repair, tells the building’s maintenance staff it’s done, and everyone assumes the watch is over. If nobody with authority formally verified the restoration and signed a release, the file has a start with no clean end. An AHJ reviewing that file after the fact sees a watch that may have been stood down before the system was actually confirmed working, which is exactly the failure mode fire watch requirements exist to prevent.
Poor documentation carries its own consequences
A fire watch that happened but can’t be proven creates real exposure on two fronts. The code side is straightforward: an AHJ who can’t verify the watch met the required standard can treat the impairment period as though no compensating measure was in place at all, which can mean citations, fines, or a harder look at every future impairment the property files. Some jurisdictions also tie occupancy decisions to a documented, approved fire watch during an active impairment, so a thin file can affect whether a building is allowed to stay occupied while a system is down.
The insurance side can be worse. Carriers that write property coverage with fire protection conditions attached often reserve the right to deny or reduce a claim tied to a loss that occurred during an undocumented or improperly staffed impairment period. If a fire happens during or shortly after a watch with no notification record, no patrol log, and no clean authorization-and-release trail, the property owner is left arguing the watch was adequate with nothing to back it up. That’s a difficult position to be in during a claims investigation, and it’s entirely avoidable with a file that took minutes to maintain in real time.
An insurer’s documentation standard can run alongside the AHJ’s
The fire marshal isn’t always the only party asking for a file. A property’s insurance carrier, operating through the policy and its own impairment program, frequently has parallel notification and documentation requirements that don’t automatically match the AHJ’s. The two authorities are answering different questions: the AHJ is protecting occupant life safety under the adopted code, and the carrier is protecting the property it insures under the policy. Neither can waive the other’s requirements, and meeting the AHJ’s standard doesn’t automatically satisfy the carrier’s.
FFWG’s page on fire marshal versus insurer requirements lays out the practical approach: run both notification lists from the start of the impairment, staff and document the watch to whichever standard is stricter, and get close-out confirmation from both parties before standing the watch down. Building one combined file that satisfies both audiences, rather than two separate ones, is usually less work than it sounds and prevents the situation where a marshal’s sign-off gets mistaken for a carrier’s approval.
What a property manager should keep before the AHJ ever asks
The practical move is to build the file as the impairment happens, not after. A complete file that would satisfy most AHJ reviews includes:
- The order, permit, or impairment tag that triggered the watch, filed immediately, not reconstructed from memory later.
- A notification table showing the fire department, the AHJ, the alarm company, the insurance carrier, and affected occupants, each with a name, a time, and the source requirement that made the call necessary.
- A patrol log with a timestamped, specific entry at every required interval, covering areas checked, hazards noted, and extinguisher or hose station readiness.
- An authorization entry naming who started the watch and under what order.
- A verification entry naming who confirmed the restoration with the contractor or alarm company.
- A release entry naming who removed the impairment tag and who gave the authority to stand the watch down.
Keep all of it as one file, physical or digital, in a location the next inspection can actually find, rather than scattered across texts, emails, and a contractor’s paperwork. If a fire watch is running right now and no one is confident the documentation would hold up to a review, that’s a fixable problem mid-impairment, not just an after-the-fact lesson. A guard trained on log completion and a coordinator tracking notifications can close most of the gap before the watch ends.
The Fast Fire Watch Company provides certified fire watch guards nationwide, with fire watch services built around exactly this kind of documentation discipline: trained patrol logging, tracked notifications, and a clean authorization-and-release record for every watch we staff. We can have certified guards on site in under 3 hours, 24/7. Call 1-800-899-7524 to get a fire watch started with a file that will hold up when your AHJ asks to see it.
