A sprinkler valve is closed for a repair, and the work crew heads home at five. The system is still shut. Someone needs to know that, and someone needs to write it down.

Record keeping is the unglamorous side of commercial fire protection systems. A shutdown, planned or not, is called an impairment in NFPA 25. Facility managers who log it well can answer an inspector, an insurer or a fire marshal in minutes.

Impairment is a defined term

NFPA 25 uses the word impairment for a system, or part of one, that is out of order. Chapter 15 covers how to handle it. A National Fire Sprinkler Association overview of NFPA 25 says that includes the coordinator's role and fire watch rules.

The standard separates impairments from deficiencies. A deficiency is a condition that could hurt performance without taking the system out of action. Many inspection reports sort findings both ways, so the difference affects what gets logged.

Planned shutdowns and emergencies

Chapter 15 addresses both preplanned and emergency impairments. A planned one leaves time to notify people and arrange interim protection. An emergency, such as a broken pipe, needs the same steps under pressure.

Local rules vary, and the edition of NFPA 25 adopted locally matters. The authority having jurisdiction, often the fire marshal, decides what is required.

What a useful impairment log captures

Summaries of Chapter 15 describe a consistent set of items. Wording differs by edition and by local rule, so treat this list as a starting point.

  • The system or section affected, and which control valves were closed.
  • The reason for the shutdown and its expected duration.
  • The date and time it began, plus the name of the impairment coordinator.
  • Who was notified, such as the fire department, alarm monitoring company and insurer, and when.
  • Where tags were placed, since valves and fire department connections are typical spots.
  • Any interim protection, such as a fire watch or temporary water supply.
  • The date and time of restoration, and who verified the system.

Who Handles Each Step of an Outage

Chapter 15 expects the building owner to assign an impairment coordinator. In practice that is often the facility manager or a trusted designee. The role is about coordination, not about doing every task personally.

Contractors, alarm companies and security staff all touch an impairment. Writing the roles down before a shutdown avoids guessing during one.

Tags, signs and handoffs

NFPA 25 calls for a tag showing that a system or part has been removed from service. Summaries say tags go on the affected control valves, and often on the fire department connection.

Guidance describes a good tag as showing what is impaired, when it started and who is responsible. Shift changes are where information gets lost. A one-line handoff note keeps the status visible.

Gaps that turn up in files

  • Entries with a start time but no restoration time.
  • Notifications marked done, with no name or time.
  • Tags removed with no note of who verified the system.
  • Planned work that never produced a log entry at all.
  • Records scattered across email, paper and personal notes.

Each gap is easy to fix with a one-page form. A standard form also helps new staff learn what to capture.

The ten-hour question

Many summaries say compensating measures are expected after more than 10 hours out of service in a 24-hour period. Typical measures include evacuating the building, posting an approved fire watch, or arranging a temporary water supply.

Some local policies set shorter limits. A manager should read the adopted rule and write the applicable threshold into the building's own procedure.

Reporting to insurers and inspectors

Insurers often want to hear about a shutdown, and summaries of Chapter 15 list them among the parties to notify. A written entry shows when the call was made and who took it. Policy terms differ, so managers should read their own.

Inspectors look at the log differently. They see whether past shutdowns were handled and closed out in a consistent way. A tidy history builds confidence, while gaps invite more questions.

Training closes the gap between a good form and good practice. Walk new staff through one completed example. Then they know what a finished entry looks like.

Closing the loop on restoration

A log entry is incomplete until the system is back in service. Restoration involves inspecting and testing the affected parts, removing tags, and notifying everyone again. Chapter 15 sets out detailed steps for this stage.

Store the finished record with inspection and testing reports. When a question comes up months later, one folder should answer it.

A complete file does not change what a system can do. It does show that people kept track of its status.