Confirm before testing
- Department and station or location
- Unique hose or asset identifier
- Manufacturer and available manufacture details
- Diameter, length, type, and coupling details
- Prior status or relevant service history
Field guide for independent testers
An NFPA 1962-oriented hose testing workflow that ends with a usable record
A good workflow does more than capture a pass or fail. It connects customer scope, hose identity, the approved test procedure, exceptions, quality review, and the report the department receives.
Before fieldwork
1. Confirm the governing procedure and customer scope
Identify the edition of NFPA 1962 adopted for the work, the department's written procedure, applicable manufacturer instructions, and any direction from the authority having jurisdiction. Agree on the equipment population, expected deliverables, exception handling, and department contact before the first test begins.
Standards reminder
This page is a workflow aid, not the standard itself. Requirements vary by adopted edition,
jurisdiction, hose type, manufacturer guidance, and customer policy. Use the current
authoritative documents for test pressures, durations, inspection criteria, and disposition.
Inventory control
2. Reconcile each hose to the department's identifiers
A test result is only useful when it can be matched to the correct asset. Review the customer's inventory before the job and preserve the identifiers they expect to see later.
Resolve while context is available
- Duplicate, missing, or unreadable identifiers
- Equipment present but absent from the source list
- Inventory listed but not presented for testing
- Customer-approved identifier corrections
- Items removed from the planned scope
Field record
Pre-test
During the test
Disposition
3. Capture observations, test data, result, and technician context together
Follow the approved procedure and record enough context for another reviewer to understand what happened. Do not let a summary result replace the underlying observations and test data required by the governing procedure.
Document condition
Record required visual inspection findings, couplings or markings reviewed, and any reason an item does not proceed to the service test.
Record the approved measurements
Capture the pressure, hold duration, date, operator, and other fields required by the procedure being used. Note interruptions or deviations for review.
Make the outcome explicit
Record pass, fail, not tested, or another customer-approved status. Add the deficiency, action, and supporting notes instead of relying on a color or symbol alone.
Quality control
4. Review the job before the department handoff
Run a deliberate closeout check after field entry. The reviewer should be able to reconcile the planned inventory, tested items, exceptions, failures, and report totals without guessing.
- Every in-scope item has a clear final status.
- Required measurements and observations are present and plausible.
- Failed, not-tested, missing, and newly found items are separately visible.
- Identifier changes and field corrections are traceable.
- Report totals agree with the reviewed equipment-level records.
- The export format matches the deliverable agreed with the customer.
Delivery and retention
5. Deliver a clear package and preserve the supporting record
Send the department a report that identifies the job, tested inventory, outcome, exceptions, and any attachments promised in the scope. Record the delivery version and recipient, then retain the supporting records according to the applicable requirements and your agreement.
For a more detailed closeout structure, use the field-to-department report handoff checklist.
See how FireGauge carries the record through these steps
Bring your current checklist or sample deliverable to a short, practical walkthrough.