Use NFPA 25 document review to reconcile system identities, as-built references, inspection and test records, open deficiencies, and handover responsibilities. Groundbook can flag inconsistencies in supplied PDFs. Physical inspection, testing, and maintenance require qualified people on the actual system.
What does NFPA 25 cover?
NFPA 25 is the Standard for the Inspection, Testing, and Maintenance of Water-Based Fire Protection Systems. NFPA describes NFPA 25 as a standard for inspection, testing, and maintenance of water-based fire protection systems.
NFPA’s official NFPA 25 page identifies the 2026 edition as current when checked on September 30, 2026. Confirm the edition, local amendments, and project scope that actually govern the work. The publisher’s newest edition does not establish local adoption.
Distinguish an operating-system maintenance record from the installation design review covered by NFPA 13 or NFPA 20. Record the system scope and requirements applicable to the facility. A completed drawing checklist is not an inspection or a maintenance record.
Collect the system and its operating records
Bring the available as-built drawings, risers, component and valve lists, operation and maintenance information, inspection and test reports, deficiency logs, and relevant handover specifications. Identify the dates, authors, and system boundaries covered by each record.
Some records may cover only part of a site or a particular activity. Preserve those limits. A recent report for one building must not be treated as evidence for every building sharing the water supply, and an asset list alone does not establish the component’s current condition.
Connect operating evidence to identifiable assets
| Review question | Sources to compare | Decision to record |
|---|---|---|
| System boundary | Report cover, building list, riser, site system map | Record which system and locations each activity actually covers. |
| Asset identity | Valve tags, equipment list, drawings, report identifiers | Resolve renamed or unmatched components before assigning a report result. |
| Record completeness | Specified handover list, available reports, document register | List missing evidence with an owner and next action; do not mark it complete. |
| Open deficiencies | Finding log, response record, subsequent evidence | Keep unresolved conditions and ambiguous closure statements visible. |
| Alterations | Current as-built issue, change documents, affected records | Ask the responsible team whether records still describe the altered installation. |
| Responsibility | Owner procedures, contractor scope, contact and response information | Identify who must verify, investigate, or act on an open item. |
Use the document review process to manage evidence and the finding triage guide to assign unresolved questions without assuming their technical severity.
Example: a report cannot be matched to the current valve list
Hypothetical example. A supplied report records work on valve V-7, while the current as-built riser and asset list use revised tags without a cross-reference. The handover log treats the report as complete for the renamed valve.
The report’s valve identifier cannot be matched to the current asset list from the supplied information. Please confirm the component identity and report scope, then provide the cross-reference or additional evidence needed to close this handover item.
The responsible team establishes the identity and what the report covers. If physical verification or additional work is needed, record that action explicitly. Updating a tag in the log cannot establish that an inspection or test occurred.
Use Groundbook to reconcile maintenance documentation
Upload the current project PDFs and relevant specifications to Groundbook. Identify the governing issues and add the applicable NFPA 25 reference from a copy you are licensed to use, where the license permits uploading it. State the edition, amendments, review area, and known exclusions in your instructions.
Compare supplied fire protection as-built drawings, asset lists, maintenance information, and inspection and test records. Flag unmatched identifiers, unclear report scope, missing handover evidence, and open deficiencies. Cite the source records and applicable supplied NFPA 25 reference.
Treat each result as a document question for the facility’s responsible team. Verify dates, asset identities, and activity scope before classifying it. Keep actual deficiencies distinct from missing paperwork so the next action addresses the underlying condition.
Groundbook does not inspect, test, maintain, or determine the present condition of a physical system. This guide does not provide an inspection-frequency schedule or certify that a facility has fulfilled its maintenance obligations.