Trust & Transparency

    Editorial policy

    FLOW publishes articles to answer the questions clients ask before a standpipe, hydrostatic, hydrant, or trip test — not to flood search results with volume. This page explains who is named as author, how posts are produced, what “Updated” means, and how to reach us with a correction.

    Articles are drafted with AI assistance and published under Taylor Pace’s name.

    Why FLOW publishes

    Building owners, property managers, contractors, and fire-protection partners ask the same practical questions before a test: what the code requires, how often testing is due, what happens on test day, and how reporting works. We publish to answer those questions in plain language, with Virginia’s adopted NFPA editions called out when they matter.

    The goal is a useful reference for people who need to schedule or pass a test — not a library of search-engine filler.

    Who is named as author, and why

    Taylor Pace, FLOW’s owner, is the named author of every article on this site and is responsible for what it says. Author pages live at /blog/authors. Andy Smith appears on the team and has an author profile as a field technician; he has not been named as a reviewer on any post.

    We do not list a “Reviewed by” line unless that person actually reviewed the article. No one is credited with a review they did not perform.

    How posts are produced

    Blog posts are drafted with AI assistance and published under Taylor Pace’s name. A human is responsible for what appears on the live site. Field claims, NFPA edition labels, and scope statements need human review before publish.

    Detailed tooling and edit-checklist items that are not yet confirmed stay out of this page until Taylor provides them. They are tracked as open items, not shipped as facts.

    What “Updated” means

    When an article shows an Updated date, it means the body’s claims changed in a material way — for example a corrected code reference, a rewritten requirement, or a substantive factual fix.

    We do not bump Updated for wording polish alone, for adding a Sources list, for image swaps, or for title/meta-only edits. Small corrections may be logged here or handled by rewriting the affected sentence without restamping the date.

    NFPA edition rule

    Every NFPA citation should name its edition. In Virginia, the 2021 Statewide Fire Prevention Code references NFPA 25, 2020 edition, and NFPA 14, 2019 edition. Other states adopt their own editions — confirm with your AHJ.

    We cite section numbers only when they have been verified for that edition. If a section is not verified, we name the standard and edition without inventing a section number.

    Sourcing standards

    Code and compliance articles should cite primary or AHJ-recognized sources (NFPA standard pages, Virginia DHCD / UpCodes code viewers, and named AHJ guidance) in a Sources list when claims depend on them.

    External sources are linked so readers can check them. We do not invent URLs or section numbers.

    Field claims and first-hand detail

    Claims about what happened on a specific job, anonymized results, or FLOW-specific measurements need human review against real records before they ship. Generic industry ranges are labeled as typical ranges, not as FLOW project data, unless Taylor supplies verified figures.

    Corrections

    See an error? Email support@standpipeflowtesting.com with the page URL and what should change. We correct factual mistakes; material claim changes get an Updated date when the body changes in a substantive way.

    Ready To Schedule Your Service?

    Fast scheduling. NFPA-compliant reporting. Trusted by fire protection professionals.