Hydrant flow test report app for fire contractors
A hydrant flow test proves the system can still deliver what it was designed for: the technician opens the most hydraulically disadvantaged outlets, reads static and residual pressures and the flow, and compares them with the design figures on the block plan. The certifier and the owner want to see the numbers, the outlets used and whether the result passes. SurveyThanks records each outlet as its own row and puts the comparison in the report rather than in a technician’s notebook.
Built for fire contractors running teams of roughly 3–50 inspectors.
Sample Hydrant flow test report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Hydrant flow test report
Hydrant flow test — Ring main, Building B
- Site
- Fictional Logistics Park, Lot 7
- Water supply
- Town main via booster assembly
- Test date
- 22 April 2026
| Outlet | Static / residual pressure | Flow | Result |
|---|---|---|---|
| H4 (north dock) | 610 kPa / 350 kPa | 10 L/s | Result: Pass |
| H6 (most disadvantaged) | 600 kPa / 240 kPa | 10 L/s | Result: Below design |
| Booster inlet caps | 2 of 4 missing | — | Result: Action |
| Block plan at booster | Present and legible, dated 2019 | — | Result: Pass |
Fields captured on site
Your firm builds the form in-app, so these are a starting point rather than a fixed schema. Every field is captured on the device, with or without signal, and lands in the hydrant flow test report where your template puts it.
Per outlet tested
- Hydrant ID (barcode or tag)
- Location on block plan
- Static pressure
- Residual pressure
- Measured flow
- Pitot or flow-meter reading photo
System
- Water supply type
- Design flow and pressure from block plan
- Booster assembly condition
- Isolation valve positions
Outcome
- Pass / fail per outlet
- Calculated pressure loss
- Recommendations
Standards the report works to
- AS 2419.1Fire hydrant installations — System design, installation and commissioning
- Gives the design flows and pressures the test results are compared against.
- AS 1851-2012Routine service of fire protection systems and equipment
- Sets the routine service and flow test schedule for hydrant systems.
Load the standards you hold into your reference library and the drafted prose is written against them rather than against a general model.
How the hydrant flow test report gets built
Capture it once, offline
Your firm builds the fire hydrant testing form in-app — 25 field types, nesting repeatable groups, compound AND/OR visibility rules, reusable modules and calculated fields. Field capture works with no signal: jobs, forms, photos, notes and audio all queue in an idempotent outbox that only clears once the server confirms receipt.
Link it to your buildings, fire compartments and rated elements
Enter buildings, fire compartments and rated elements once, as a register. Every one of your penetrations, defects and rectification items then points at a stored row rather than a name somebody typed — and the links survive a disconnected device.
Render your own template
The hydrant flow test report renders into the Word template you already use — your letterhead, your section order, your clause library — with conditionals, loops over repeats, composable sub-templates and photo grids.
Reviewed before it leaves
You write the review framework: a checklist of what a hydrant flow test report must contain, plus the prose standards you would mark a junior against. Link it to a report template and it runs every time that template renders. Each finding comes back graded info, minor or major, quoting the sentence at fault, and a person accepts or dismisses every one.
Because the structured submission behind the report is held too, the review is a comparison rather than a proofread: The report says sprinkler coverage is throughout; the form records the warehouse only.
Checks a fire safety framework usually carries
- Every rated element assessed carries a defect status, not just a description
- A BAL determination shows the inputs it was derived from
- Non-conformances cite the clause of the standard they fail
- Rectification items are specific enough for a contractor to price
Questions
- Can we test several hydrants in one flow test?
- Yes. Each outlet is a row in a repeatable group, so a simultaneous test of two or three outlets is recorded together and the report tabulates them side by side.
- Does the app compare results against the design figures?
- The design flow and pressure are entered once per system, and calculated fields work out the pressure loss for each outlet. The pass or fail call stays with the technician.
- Can we attach the gauge photos to each outlet?
- Yes. Photo-with-comment fields sit inside the outlet row, so each photo lands next to the reading it proves in the finished report.
What this is not
Worth knowing before you book a demo, so neither of us wastes the half hour.
- Not field-service dispatch. No timesheets, no parts, no inventory. Scheduling exists to get an inspector to a site.
- No signature capture. If your deliverable has to carry a signed sign-off on the artefact itself, this is not the tool yet.
- Field capture is what works offline — jobs, forms, photos, notes and audio. Reports, chat, scheduling and the inbox need a connection.
- No client portal. Reports go out as a file or a password-protected link.
Other fire safety work we cover
- Passive fire penetration surveysPenetration register
- Smoke detector testingDetector test register
- Sprinkler system inspectionsSprinkler test report
- Asset protection zone inspectionsAPZ compliance report
- Bushfire attack level assessmentsBAL report
- Bushfire hazard reduction auditsHazard reduction report
- Evacuation diagram auditsDiagram compliance report
- Evacuation drill recordsDrill observation report
Other disciplines
Rebuild your hydrant flow test report in SurveyThanks
Bring the Word template you already send clients. If you are coming off another field-forms tool, a filled report can be uploaded, read field by field, and re-rendered into your template.