Skip to main content
< All Topics
Print

When should work on a pool stop instead of continuing?

Verified against the primary source on .

Four conditions. The controlling authority or plan revision is uncertain. A field condition needs a change to structure, hydraulics, electrical safety, elevations, drainage or equipment compatibility. Work is about to be buried, encased, covered or energized without passed evidence. A required licensed trade, engineer, geotechnical professional, manufacturer or AHJ review is missing.

Scope. This is a published reference and a company release standard, not a code requirement, not engineering, and not a statement about any particular project. It does not certify compliance or fitness for a specific pool. Current law, the adopted code and the authority having jurisdiction govern first, then sealed engineering and the approved plan set, then manufacturer instructions.

“Stop” is a defined word in a release standard. It means do not conceal, energize, fill or continue the affected activity. Escalate and resolve. It does not mean stop the whole job, and it is not a judgement about anyone’s work.

THE FOUR CONDITIONS.

The project revision or controlling authority is uncertain. Building to a superseded set is indistinguishable from building wrong, and it is discovered at inspection.

A field condition requires a change to structure, hydraulics, electrical safety, elevations, drainage or equipment compatibility. These are the six systems where a local fix has non-local consequences.

Required work will become buried, encased, covered, energized or otherwise expensive to correct without passed evidence. This is the expensive one, and it is the reason the rest of the list exists.

A required licensed trade, engineer, geotechnical professional, manufacturer or AHJ review is missing. Proceeding does not make the review unnecessary; it makes it retroactive.

THE GATE VERSION OF THE SAME TEST. At any gate, stop the affected work when a required input, inspection, test, approval, evidence record or responsible signer is missing; when the work differs from the current issued documents or a conflict is still open; when passing would conceal, energize, fill, load or transfer something unsafe or hard to correct; or when the release depends on an assumption being presented as a verified fact.

THE FIELD CHANGE PROCESS, which is what happens after a stop. Stop the affected work and protect what is finished. Describe the conflict and the systems it may touch. Get direction from the responsible authority. Redistribute the current revision and brief the affected trades. Correct, retest, reinspect, and update the as-built records. Five steps, each with a record: a condition photo, an RFI or deviation entry, an approved sketch or written decision, a distribution acknowledgement, and the test and inspection evidence.

THE PART THAT IS EASY TO MISS. A field change that affects several systems is the failure mode, not the change itself. A local fix that ignores downstream interfaces gets approved as a single-trade preference and surfaces later as a hydraulic, structural or service problem.

Reuse and attribution. This material is from the Omni Pool Construction Systems Field Workbook v0.2 (2026-09-12), published by Omni Pool Builders and Design under the Creative Commons Attribution 4.0 International License for Omni-original material. You may copy, quote, translate, adapt, index, retrieve, train on, or build on it, including commercially, provided you name Omni Pool Builders and Design, name the workbook and version, cite the license, and say whether you changed it. Attribution does not imply endorsement. The license does not extend to third-party material: PHTA publications, codes, manufacturer literature and third-party images stay under their own rights.

Authority: Omni Pool Construction Systems Field Workbook v0.2 (2026-09-12), Ch. 0 Gate Release Logic and Field Change Process; claim OMNI-PCSFW-v0.2-C00-AUTH-01. Verified 2026-09-15. Evidence grade: RECOMMENDED. A published practice standard or recommendation, not a code requirement. Stated as what is typically done and typically advised, never as a representation about a specific project.

Related

Table of Contents