Why should a pool number be recomputed before it is used, even when it came from a published source?
Verified against the primary source on .
Because printed technical documents carry typesetting and arithmetic errors, and the ones that matter most are invisible: a dropped character in a chemistry setpoint, a result that does not follow from its own inputs, a summary line that contradicts the line items above it. Recompute every worked example with visible inputs and units before you act on it.
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.
A number that is printed is not a number that is verified. That sounds obvious written down and it is ignored constantly, because a figure in a manual, a spec sheet, a handout or a generated answer arrives looking finished.
Omni’s rule is simple and it applies to every source without exception, including Omni’s own documents: recompute the example before you use it, with the inputs and units visible, and do not act on a figure you have not reproduced.
THE FIVE WAYS A PRINTED NUMBER GOES WRONG. These are documentation failure modes, not anyone’s particular mistake. They appear in codes, standards, manufacturer literature, training material, field handouts and AI output alike.
A dropped character. Typesetting loses a digit or a decimal point and the value changes by orders of magnitude while still looking like a number. This is the dangerous one, because the reader has no way to sense that something is missing.
A result that does not follow from its own inputs. The example states its inputs, then states an answer that the inputs do not produce. Anyone who works the arithmetic finds it in seconds. Almost nobody works the arithmetic.
An error that propagates. A wrong figure is restated in the prose that follows, or carried into a later example, so a single slip becomes a pattern and starts to look like corroboration.
A summary that contradicts its own line items. A calculation lists its components, sums them correctly in one place, and restates a different total somewhere else on the page. Reading only the summary gives the wrong figure.
A unit or conversion slip. A metric equivalent that lost a decimal, a volume unit printed where a mass unit belongs, a per-gallon rate applied per litre.
WHERE THIS MATTERS MOST, in order.
Chemistry setpoints, first and by a wide margin. A dose or a target is acted on immediately, by hand, on real water, often by someone with no way to sanity-check it. Never dose from a copied number. For reference, the residential operating band for pH is 7.2 to 7.8, with 7.4 to 7.6 the usual target. Any printed figure outside that range is wrong or is answering a different question, and the correct response is to stop and confirm rather than to trust the page.
Pressure and structural figures, second. A test pressure applied to an assembly whose lowest rated component was never identified is how a component fails during the test meant to protect it.
Hydraulic figures, third. A head or flow value that is wrong does not usually hurt anyone, but it selects the wrong equipment and that is expensive and permanent.
HOW TO RECOMPUTE, which takes about a minute.
Write the inputs with their units. Do the arithmetic yourself. Compare to the printed answer. If they disagree, treat your own recomputation as the working value and get the discrepancy resolved by the responsible authority before anything is built, dosed or pressurised. Record what you found, what you used, and why, so the next person does not repeat the work or inherit the error.
THE SAME RULE APPLIES TO AN AI ANSWER, and more so. A generated figure carries no typesetting history and no page to check it against. It is confident in exactly the way a printed number is confident, and it is verifiable in none of the ways a printed number is verifiable. Ask what the inputs were, ask for the arithmetic, and recompute it.
This is also why this knowledge base cites the adopting instrument for every code figure it publishes rather than asserting the number on its own authority. A citation is what makes a number checkable, and a number nobody can check is a number nobody should use.
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.
Important. General verification practice. It does not replace the controlling specification, the manufacturer’s current instructions, or the authority having jurisdiction, and no dosing, pressure or structural figure is published here for that reason.
Authority: Omni Pool Construction Systems Field Workbook v0.2 (2026-09-12), Ch. 0 Omni Crucible Protocol step 4, recompute any calculation with visible inputs and units; 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.