Fire Hydrant Method Statement

This fire hydrant method statement is the second release in BuildMEP’s growing library of practitioner-written, field-tested method statements for MEP and fire protection work — not templates copied from a textbook. It’s built from a real underground fire hydrant installation: HDPE feed main, large-diameter welded feeder mains, and the two-stage hydrostatic test sequence actually used to commission it.

Each method statement is delivered as an editable file, so you can drop in your own project name, logo, and reference numbers and have it ready to submit to your consultant or client the same day. These aren’t generic checklists pulled from a standard’s appendix — they follow the actual sequence a crew works through on site, including the coordination points and sign-offs that consultants actually check for during submittal review.

Who this fire hydrant method statement is for

This document is built for MEP contractors, fire protection subcontractors, and site engineers who need to submit a method statement for an underground fire hydrant installation and don’t want to start from a blank page or a generic downloaded template. It’s equally useful for consultants and facility managers who want a clear reference for what a proper installation, testing, and commissioning sequence should actually include before they sign off on someone else’s submittal. If you’re coordinating pipe welding, thrust restraint, and a multi-zone hydrostatic test together — the parts of hydrant installation that most often trip up a first submittal — this covers all three in one document rather than forcing you to stitch together separate references.

Why a fire hydrant method statement matters

A method statement isn’t paperwork for its own sake — it’s the document that tells a consultant, a safety officer, and the crew on site exactly how a system will be installed, tested, and commissioned, in what order, and against what acceptance criteria. A weak or generic one gets flagged in submittal review and sent back, costing days on a schedule that usually can’t afford them. A method statement written from actual project execution — not adapted from a code appendix — tends to hold up because it already accounts for the sequencing and documentation a reviewer expects to see.

This is closely related to the water supply sizing covered in the underlying Fire Hydrant System Method Statement article, and pairs directly with the Fire Pump Installation, Testing & Commissioning Method Statement — that document covers what happens once water reaches the pump set, while this one covers getting it there. For the distribution side, see the Fire Sprinkler System Method Statement. All three sit together under the Fire Protection Systems guide, which organizes the full protection layer — passive, water-based, and portable — in one place.