Fire Pump Weekly Test Log

This template covers the weekly run test record for a fire pump, including suction pressure, discharge pressure, run time, and operator observations. It is meant to document the condition of the pump during a routine test, not to replace a full maintenance program. Use it to capture a clear yes/no record of whether the pump started, ran, and performed as expected. If your site has diesel, electric, or jockey pump variations, you can customize the checklist items to match the installed equipment.

This template is designed for a weekly recurrence, with the test performed on the schedule required by your site policy and applicable fire protection program. Many teams assign a specific day of the week so the log is consistent and easy to audit. If your jurisdiction, insurer, or internal standard requires a different cadence, adjust the recurrence_config to match that requirement. The key is to keep the interval consistent and documented.

A trained facility technician, maintenance lead, or fire protection contractor typically runs the test, depending on site policy and local requirements. The DRI should be someone who can safely access the pump room, verify gauges, and recognize abnormal conditions. If the log is used by multiple shifts, assign one owner for completion and one reviewer for follow-up on exceptions. The person running the test should know when to escalate a blocking issue immediately.

Yes, the log is aligned with the documentation pattern used for NFPA 25 weekly fire pump testing. It helps you capture the operational evidence that inspectors and internal auditors usually expect to see. This template does not replace code review, local AHJ requirements, or manufacturer instructions. If your site is subject to additional state, municipal, or insurance rules, add those fields before rollout.

The most common mistake is recording only that the test was done without capturing the actual pressures, run time, or unusual observations. Another pitfall is treating every issue as critical, which makes it harder to prioritize real safety concerns. Teams also sometimes skip the verification step that confirms the pump returned to normal standby condition after the test. A good log should make it obvious whether the test was completed, what changed, and what needs follow-up.

Yes, and it should be if your site has specific pump types or control arrangements. You can add checklist items for diesel fuel level, battery condition, controller indicators, or automatic start behavior as needed. Keep each checklist item atomic so it can be answered clearly with yes, no, or N/A. If you have both pump types on one site, consider separate logs or separate sections to avoid confusion during review.

An ad-hoc log often misses repeatable fields, makes follow-up harder, and creates inconsistent records across shifts. This template gives you a structured checklist item set, a clear recurrence, and a standard place to note blocking defects. That makes it easier to review trends, assign follow-up, and prove the test happened on schedule. It also reduces the chance that someone forgets a key measurement like discharge pressure or run time.

Yes. When a defect is found, the log can trigger a follow-up task or work order for repair, inspection, or vendor review. Many teams connect the template to maintenance tracking so blocking issues are escalated immediately and non-blocking observations are tracked separately. That keeps the weekly test from becoming a dead-end record. It also helps ensure the next test reflects whether the issue was resolved.