Fire Pump Weekly Test Log
Use this Fire Pump Weekly Test Log to record weekly run tests, churn pressures, controller readings, and现场 observations in one place. It helps facilities prove the pump was exercised, noted issues were captured, and follow-up actions were assigned.
Trusted by frontline teams 15 years of frontline software
Built for: Commercial Real Estate · Healthcare · Warehousing And Logistics · Manufacturing · Education
Overview
This Fire Pump Weekly Test Log template is for recording the weekly run test of a fire pump in a way that is easy to review, audit, and hand off. It captures the core facts that matter during the test: date and time, pump identification, churn or no-flow pressure, run time, controller readings, and field observations such as leaks, vibration, unusual noise, or alarm behavior.
Use this template when your site needs a repeatable record of the weekly test and a clear place to assign follow-up on anything abnormal. It works well for single-pump rooms, multi-pump facilities, and sites where a contractor performs the test but the owner still needs a clean internal record. The log is also useful when you want to spot drift over time, such as pressure changes, starting issues, or recurring controller faults.
Do not use this template as a substitute for a full fire protection maintenance program or for repairs that require a separate work order. It is also not the right fit for one-time commissioning, annual flow testing, or emergency incident reporting. If your site does not perform weekly testing, the recurrence should be adjusted to match the actual inspection cadence. The goal is simple: create a consistent, verifiable record of each weekly test and make any blocking issue visible fast.
Standards & compliance context
- This template is structured to support weekly fire pump testing documentation commonly expected under NFPA 25 Chapter 8 workflows.
- Keep local fire code, insurer, and AHJ requirements in view, since some sites require additional readings or signoff fields.
- If a test reveals a safety-impacting defect, treat it as a blocking issue and escalate through your maintenance or emergency response process.
- Do not use this log to replace required repair documentation, acceptance testing, or annual inspection records.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Set the recurrence to weekly on the day your site performs the fire pump test and assign the DRI who will complete the log.
- Enter the pump identifier, location, controller type, and any site-specific fields needed to match your equipment list.
- Run the weekly test and record each checklist item with a yes, no, or N/A answer, including churn pressure, run time, and controller readings.
- Add field observations immediately after the test, noting any leaks, vibration, abnormal noise, alarm behavior, or other non-blocking and blocking findings.
- Create a follow-up task or work order for any abnormal condition, then verify the corrective action before closing the log entry.
Best practices
- Record the actual pressure and run time values, not just that the pump started.
- Use one checklist item per observation so each answer is independently verifiable.
- Capture abnormal conditions at the time of the test, before the equipment is reset or cleaned.
- Assign blocking findings to a clear DRI and route them to maintenance or the fire protection vendor immediately.
- Keep the recurrence fixed to the same weekly day so missed tests are easy to spot.
- Use N/A only when the item truly does not apply to that pump or controller configuration.
- Photograph visible leaks, gauge anomalies, or controller alarms when your site policy allows it.
- Review repeated non-blocking observations for trend changes before they become a failure.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this Fire Pump Weekly Test Log cover?
This template is for documenting the weekly fire pump run test, including churn or no-flow pressure, run time, controller readings, and field observations. It is meant to capture what was checked, what was observed, and whether any follow-up is needed. Use it as a record of the test itself, not as a full fire protection maintenance program.
How often should this log be used?
Use it on the weekly cadence required by your inspection program, with the recurrence set to the specific day your site performs the test. If your facility tests on a different day due to staffing or access, keep the cadence consistent and documented. The key is that each run test is recorded every week without gaps.
Who should run and complete the log?
The DRI is usually a qualified facilities, maintenance, or fire protection technician who can perform the test and recognize abnormal readings. A supervisor or safety lead may review the completed entry for follow-up on blocking issues. If your site uses a contractor, the internal owner should still verify the record is complete and filed.
Does this template align with NFPA 25 expectations?
Yes, it is designed around the weekly fire pump test pattern used in NFPA 25 Chapter 8 workflows. It supports the kind of documentation inspectors expect to see: date, readings, observations, and corrective action notes. You should still follow your local code, insurer requirements, and site-specific procedures.
What are the most common mistakes when using this log?
The biggest mistake is recording only that the test was done without capturing the actual readings or any abnormal conditions. Another common issue is using vague notes like "looks fine" instead of an independently verifiable observation. Teams also sometimes forget to assign follow-up for low pressure, leaks, controller faults, or other blocking findings.
Can this template be customized for our pump room and controller setup?
Yes, you can add fields for your pump model, controller type, suction source, jockey pump notes, or local alarm checks. Keep the checklist items atomic so each answer is yes, no, or N/A. If your site has multiple pumps, duplicate the log or add a clear pump identifier to each entry.
How does this compare with an ad hoc paper log or spreadsheet?
An ad hoc log often misses one of the required readings, makes follow-up hard to track, or leaves no clear owner for corrective action. This template keeps the weekly test in a repeatable format with consistent fields and a clear verification step. That makes it easier to review trends and prove the test happened when auditors ask.
Can this log connect to maintenance or work order systems?
Yes, the findings can be linked to a work order, CMMS ticket, or ITIL-style runbook when a defect needs repair. Use the log to capture the issue, then route the blocking item to maintenance with a DRI and due date. Non-blocking observations can still be tracked for trend review without interrupting operations.
Related templates
Go deeper on the topic
-
See how automated credential checks, labor rules, and real-time coverage tracking give charge nurses a schedule they can trust before every shift.
-
Interdisciplinary collaboration strategies for large health systems that improve care coordination, reduce errors, and boost team efficiency.
-
Discover proven physician engagement strategies that reduce burnout, improve patient outcomes, and strengthen health system performance. Practical tips for...
-
Boost healthcare employee engagement with proven ideas that reduce burnout, improve retention, and elevate patient care.
Ready to use this template?
Get started with MangoApps and use Fire Pump Weekly Test Log with your team — pricing built for small business.
