Fire hose test service requirements for US fire departments

Before accepting outsourced hose testing, require a linked package for each hose ID: inventory identity, original test result, repair or retirement disposition, subsequent verification, and confirmed physical location. Separate applicable requirements from department-selected acceptance conditions.

• Requirements to verify: Identify the governing authority, the standard and edition it references, and applicable local purchasing and records provisions.
• Attributed guidance: Snap-tite recommends pre-test inventory and lifecycle records covering inspections, tests, repairs, personnel and removal decisions. Its account is vendor guidance, not the standard itself. [6]
• Proposed contract conditions: Specify the handoff manifest, ID reconciliation, repair authorizations, return-location records, deadlines and department sign-off.

Keep three questions separate: What was the test result? Is the hose authorized for service? Where is it physically located? The proposed acceptance package should answer each.

Number and inventory every length before handoff

Build the handoff list around the identifier on each length, not a bundle count. Snap-tite recommends a complete pre-test inventory, legible identification markings and these fields: [6]

• Unique hose ID: The identifier linking the physical length to its record.
• Size and length: Separate entries for each specification.
• Manufacturer and purchase date: The recorded source and acquisition date.
• Previous test history: The existing testing record.
• Current service assignment: The apparatus, station or other assignment. [6]

As a department-selected control, resolve unreadable, duplicate or missing IDs before transfer. Link a replacement identifier to the existing history. Make this timing explicit in the contract: Snap-tite supports pre-test inventory and legible markings, but the cited page does not establish a before-collection numbering deadline. [6]

Add collection location, custody recipient, collection date and acknowledgment of the IDs transferred. These are proposed handoff controls. Keep service assignment separate from collection location so collecting hose at a central bay does not erase its apparatus assignment.

Illustrative example: H-042 enters the handoff manifest with its specifications, manufacturer, purchase date and previous test record. Its service assignment remains the assigned engine, while its collection location is the central equipment bay. The contractor acknowledges receipt under the same ID. This example follows H-042 through the remaining steps.

Reconcile results and custody separately

Match each handoff ID to a physical location as well as a test record. Snap-tite recommends recording IDs, results, repairs and removal-from-service decisions; use those categories as the foundation for a separate custody check. [6]

Specify a reconciliation worksheet with these fields:

• ID: Match the identifier to the handoff inventory.
• Testing event: Record tested, withdrawn before testing or awaiting evidence.
• Original result: Link the original test record; mark the result unresolved if evidence is missing.
• Current service disposition: Record passed, repair required or retire/replace, supported by the relevant record.
• Custody/location: Record return to a named department location, contractor retention at a named location, authorized transfer for repair or disposal, or unaccounted-for status.
• Open exception: Identify the discrepancy, responsible party and agreed resolution date.

Under this proposed system, withdrawn is not a passing result, and unaccounted for is a custody discrepancy—not a test outcome. Match each handoff ID to one current custody state, then reconcile testing evidence and service disposition independently. Compare ID sets rather than adding overlapping totals: a tested length can also require repair and remain with the contractor.

H-042 at reconciliation: Its testing event reads “tested”; its original result reads “failed—coupling issue,” linked to the original record. Its disposition is “repair required,” its location is the contractor’s named repair bay, and its open exception is missing repair-completion and verification evidence.

Require an exception list for unexpected returned IDs, missing lengths, duplicate entries and records without matching physical hose. The worksheet, custody categories and resolution dates are proposed contract conditions. West Grove Fire Company’s 2016 case study documents electronic results and a final record, not a signed collected-versus-returned reconciliation. [5]

Separate coupling repair from the original test result

A coupling repair entry is not a passing test record. Snap-tite treats couplings, gaskets, threads and expansion rings as inspection items and distinguishes “Repair Required” from “Passed.” West Grove’s case study also describes checking for coupling issues. [5][6]

Specify a record sequence that preserves earlier entries, building on Snap-tite’s recommended test, repair, personnel and disposition fields: [6]

1. Original inspection and test: Preserve the dated result, including failed or incomplete entries.
2. Exception: Identify the affected component and observed problem.
3. Authorized repair: Record who approved the work, what was performed and by whom.
4. Subsequent evidence: Link verification or retest records, dates, personnel and the applicable procedure.
5. Department decision: Record the reviewer’s return-to-service decision separately from repair completion.

Do not replace the original result when later work succeeds. Snap-tite says repair-required hose remains out of service until repairs are completed and verified, and repaired hose may need additional testing. [6] Ask the contractor to specify the applicable retest procedure for each coupling repair.

H-042 after repair: Retain the original coupling-related failure. Attach the repair authorization and completed-work entry, then link subsequent verification or retest evidence under the applicable procedure. Under the proposed acceptance terms, its release status remains “Pending department review” until the designated reviewer records a decision.

Request separately identifiable repair and retest charges so purchasing staff can match charges to authorized work. Separate invoice lines and work orders are proposed purchasing terms, not requirements established by Snap-tite’s workflow or West Grove’s case study. [5][6]

Establish which requirements govern the work

Before finalizing the scope, document the authority having jurisdiction, the standard and edition it references, relevant provisions, and local purchasing and records requirements. Keep these separate from department-selected terms.

The NFPA 1962 excerpt hosted by Gallup contains only a rodent-related visual-inspection provision; it does not establish the applicable edition or full testing and recordkeeping obligations. [3] Obtain the relevant adoption documents and standard text before describing a provision as binding.

MTAS advises considering a 10-year maximum service life under normal operating conditions even when 15-year-old hose still passes an annual test. MTAS also quotes the FSRS as requiring the general criteria of NFPA 1962, including minimum test pressures of 300 psi for attack hose and 200 psi for supply hose. [4] Snap-tite describes annual service testing and thorough documentation as NFPA-aligned practices, but this is a vendor’s account of the standard. [6] Neither substitutes for checking the edition referenced by the department’s authority.

Check equipment and jurisdiction before importing federal rules: OSHA’s cited guidance concerns portable extinguishers and their hose assemblies, while the cited maritime regulation addresses a different jurisdiction. [1][2]

Specify documents, charges and turnaround

Make the acceptance package an explicit deliverable in the testing quote. Use Snap-tite’s inventory and lifecycle fields as the recordkeeping foundation, then add department-selected custody, authorization and acceptance documents. [6]

Proposed document checklist:

• Pre-handoff manifest: Include each ID, size, length, manufacturer, purchase date, previous test history and service assignment. [6]
• Per-ID inspection/test log: Include inspection and test dates, results, personnel, repairs, removal decisions and replacement dates. [6]
• Exception and repair package: Require an exception list, written repair authorizations and subsequent verification or test records linked to the original result.
• Return and closeout package: Require a custody manifest showing physical destinations, an itemized invoice and a department acceptance record.

Ask bidders to price and schedule against the same IDs and deliverables:

• Charges: Ask bidders to identify testing, authorized repairs, subsequent testing, transport, minimum charges and disposal as included, separately priced or not applicable.
• Turnaround: Request scheduling lead time, testing-to-record delivery time, repair turnaround and return arrangements.
• Deadlines: Set record-delivery, return and discrepancy-correction dates. Distinguish planning estimates from contractual commitments.
• Authority: Name who may authorize repairs, approve disposal, resolve discrepancies and accept work. Define escalation for overdue records, disputed charges or missing hose.

Document acceptance before closing the job

Use the following as proposed department acceptance controls, building on Snap-tite’s recommendation to update records immediately and retain inspection, test, repair and disposition histories. [6]

• Account for each handoff ID: Match it to its result, disposition and confirmed location.
• Preserve original results: Retain initial findings alongside later repair or testing records.
• Review exceptions: Resolve discrepancies or leave them explicitly open with an owner and next action.
• Link repair evidence: Connect the repair and responsible personnel to the same ID; review subsequent verification or retesting where applicable.
• Record acceptance: Identify accepted work, open items and corresponding invoice lines.

Accepting contractor work is separate from authorizing return to service. Snap-tite’s workflow keeps repair-required hose out of service until repair completion and verification. [6] Handle unresolved items, partial acceptance and payment under the agreed contract rather than assuming a universal withholding rule.

H-042 at closeout: Its record now links the original failure, authorized repair, subsequent verification, reviewer’s return-to-service decision and confirmed return to its assigned engine. “Repair complete” alone would leave this proposed package open.

Carry the record into the next testing cycle

Update inventory, assignment, actual location, repair history, removal decisions and replacement entries after closeout. Snap-tite recommends immediate post-test updates and maintaining inspection, testing, repair and maintenance histories across the hose’s life. [6]

Assign owners for remaining exceptions, confirm how long the records are kept, and set the next test date for each hose ID under the requirements your authority applies.

The final check is practical: select a hose ID and trace it from handoff through original test evidence, repairs, verification, final disposition and actual location.

References

1. eTool : Evacuation Plans and Procedures – Emergency Standards – Portable Fire Extinguishers – Hydrostatic Testing | Occupational Safety and Health Administration (osha.gov)
2. 46 CFR § 107.257 – Testing of fire hose. | Electronic Code of Federal Regulations (e-CFR) | US Law | LII / Legal Information Institute (cornell.edu)
3. Copyright by National Fire Protection Association (NFPA). NFPA 1962 is (gallupnm.gov)
4. | Replacing fire hose | MTAS – Serving Tennessee City Officials (tennessee.edu)
5. WGFC Conducts Annual Hose Testing Program – West Grove Fire Company (wgfc.org, 2016)
6. NFPA Fire Hose Testing Requirements Explained – Snap-tite Hose (snaptitehose.com)