How to Keep a Fire Watch Log That Passes Inspection

An inspector reads the log before they read anything else

When a fire marshal’s inspector, an insurance adjuster or a building’s own risk manager wants to know whether a fire watch actually happened the way it was supposed to, the log is the first thing they ask for, and often the only thing they read closely. A watch that was walked perfectly but logged poorly looks, on paper, indistinguishable from one that was never walked at all. That is not a technicality; it is the whole point of the log, and it is why the habits below matter more than the format of the form itself.

What makes a log complete

A log that holds up starts with a header naming the building and its address, the system that is impaired under IFC 901.7 or the hot work under way under OSHA 29 CFR 1910.252(a)(2)(iii), and its permit number, the date and time the watch started, the conditions set by the fire code official or the coordinator, the interval, the areas covered, the alarm method, and the names of the coordinator and the officer. From there, every round gets its own entry: the time, the areas actually walked, the exits and extinguishers checked, and the conditions found, even when the finding is simply nothing unusual. The watch closes with a final entry recording the restoration and test, or the end of the post-work period, signed by the officer and, where applicable, the coordinator.

The gap is what fails a log

Almost every log that fails inspection fails for the same reason: a stretch of time with no entry and no explanation. An officer who walks the rounds faithfully but only writes up the shift at the end has, from the log’s point of view, done nothing verifiable, because there is no way to tell the difference between rounds that happened on schedule and rounds that were reconstructed from memory afterward. Entries made in real time, at the moment of the round, are what an inspector is actually checking for, not just their content but their timing.

Entry style	What it shows an inspector	Passes inspection
Timed entry made at the round, with areas and findings	The watch happened as scheduled	Yes
Entries written all at once at the end of shift	Cannot confirm timing of individual rounds	Usually no
A checkmark with no detail	A round happened, but not what it covered	Weak, often questioned
A gap with no note	Unexplained, reads as a missed round	No
A gap with a handover note explaining it	A shift change, accounted for	Yes

Handovers are where logs commonly break down

A fire watch that runs overnight or across several days involves more than one officer, and the moment of handover is where logs most often lose continuity. A complete handover entry names both officers and the time, confirms the incoming officer has been briefed on the interval, the areas, the alarm method and anything found on the previous shift, and picks the log back up without a gap. A log that simply stops under one officer’s initials and resumes under another’s, with no handover entry between them, reads to an inspector as an unaccounted-for period even if the watch never actually lapsed.

Events between rounds still belong in the log

Not everything worth recording happens on a scheduled round. A hazard corrected, a contractor moving into a new zone, a call from the coordinator, a false alarm, or a brief conversation with the fire marshal’s own inspector during a site visit are all entries that belong in the log at the time they happen, not folded into the next scheduled round’s note. A log that only shows the fixed-interval rounds and nothing in between can look sparse next to what actually happened during the watch, and the extra entries are what make the record match reality.

Paper, electronic, or both

A fire watch log can be kept on a paper form, in an electronic guard-tour system, or as a combination of the two, and inspectors generally accept any of them as long as the entries are contemporaneous and complete. A paper form has the advantage of working when a phone or a tablet does not, which matters on a construction site or during a storm-related outage; an electronic system can timestamp entries automatically and make it harder to backfill a round after the fact, which some fire marshals and insurers prefer for exactly that reason. What does not hold up well is a log started on paper and then rewritten cleanly into a computer file at the end of the watch, since the rewritten version loses the timestamp evidence that the original entries were made in real time. Price Protection keeps the original log, whichever format is used, and hands it to the coordinator complete rather than transcribed.

How long a completed log should be kept

Once a watch ends, the completed log becomes part of the building’s impairment or hot-work permit file, and it is worth keeping longer than the outage itself might suggest. An insurer investigating a later claim, a fire marshal following up after an inspection, or a contractor’s own permit closeout can all ask for a log well after the fact, and a building that can produce it quickly is in a stronger position than one that has to explain why the record was not kept. Retaining logs alongside the building’s other fire safety records, restoration test reports and impairment notices is the simplest way to make sure a completed log is still findable months later.

What to do before the inspector arrives

Read the log back as if seeing it for the first time: can every hour of the watch be accounted for, is every round timed, does every gap have a handover or a reason attached, and does the closing entry match what actually happened at restoration or the end of the post-work period. The fire watch log template on this site lays out the structure in a form that is easy to keep consistent shift to shift, whether the watch runs two hours or two weeks. This is a summary, not legal advice. The fire code official or the permit for a specific building sets what its log must contain.