Fire Pump Weekly Test Log

This template covers the core weekly run test record for a fire pump: suction pressure, discharge pressure, run time, and any operational observations. It is designed to document the test as a repeatable checklist item set, not to replace a full maintenance program. Use it to capture what was checked, what was observed, and who verified the result. It works best when paired with your site’s inspection and corrective-action process.

This is a recurring weekly log, so it should be completed on the site’s weekly test cadence. If your facility follows a different internal schedule or a stricter local requirement, configure the recurrence to match that standard. The key is consistency: the same test, at the same interval, with the same fields recorded each time. Missing weeks create gaps that make trend review and compliance evidence weaker.

The log is typically run by a trained facilities, maintenance, or fire protection technician, with a designated DRI responsible for completion and follow-up. The person performing the test should be able to verify readings, note abnormal conditions, and escalate blocking issues. If your organization separates operator and reviewer roles, use the template to capture both the tester and the verifier. Keep the assignment clear so there is no ambiguity about ownership.

Yes, the template is aligned to the weekly documentation pattern used for fire pump testing under NFPA 25. It helps you record the operational evidence that a weekly run test was performed and observed. It is not a substitute for the code itself, local amendments, or a licensed inspector’s judgment. If your jurisdiction has additional reporting requirements, add those fields before rollout.

A common mistake is recording only that the test happened without capturing the actual readings or observations. Another is combining multiple checks into one vague item, which makes it hard to verify whether each step passed. Teams also sometimes mark every issue as critical, which hides the difference between a minor note and a blocking defect. Finally, skipping the verification step or failing to follow up on abnormal pressure changes reduces the log’s value.

Yes, it can be customized for electric or diesel fire pumps, different gauge layouts, and site-specific observation fields. You can add items for jockey pump status, controller indicators, room condition, or transfer switch checks if your process requires them. Keep each checklist item independently verifiable so the log stays easy to complete and audit. Avoid adding compound items that force a single yes/no answer to cover multiple conditions.

Compared with ad-hoc notes, this template gives you a consistent structure for the same weekly test every time. That makes it easier to spot drift in suction or discharge pressure, confirm the run duration, and review exceptions over time. Freeform notes often miss one of the required fields or make later review difficult. A structured log also supports cleaner handoffs between the technician, supervisor, and compliance reviewer.

Treat abnormal readings as a blocking issue and record the observation clearly in the log. Then route the finding into your corrective-action or work-order process so the pump is not left with an unresolved defect. If the issue affects fire protection readiness, escalate it according to your site’s emergency and maintenance procedures. The log should show both the test result and the follow-up path.