Booster-pump pressure logs before low-pressure complaint review

Direct answer

Before reviewing a low-pressure complaint on a domestic water booster system, record the complaint location, fixture or zone served, time window, building demand condition, suction pressure, discharge pressure, remote pressure if used, system setpoint, pressure sensor point ID, pump run status, lead and lag pump sequence, VFD speed or frequency, hand/off/auto status, alarms, low-suction or dry-run status, check valve and isolation valve status, PRV setting or downstream pressure where relevant, bypass position, tank precharge or tank isolation status where safe to verify, recent trend data, correction made, recheck readings, open exceptions, responsible reviewer, and final release decision.

The record belongs before the complaint is closed because one gauge photo cannot prove whether the booster lacked inlet pressure, failed to stage a lag pump, was following a remote sensor, was in sleep or no-flow mode, had an open bypass, had a PRV or tank problem, was limited by alarms, or served a different pressure zone than the fixture complaint. A useful log separates source pressure, boosted pressure, control intent, actual pump response, and distribution-side restrictions.

Use this field note as documentation guidance only. The engineer, plumbing designer, manufacturer literature, utility rules, adopted code, approved drawings, startup report, controls sequence, owner standard, qualified service technician, and site safety plan control the actual test method, setpoints, pump operation, tank precharge, valve adjustment, electrical work, lockout, and release.

Start with the complaint zone

Low pressure is not a building-wide conclusion until the record proves the boundary. Start by naming the exact complaint: floor, riser, pressure zone, tenant, fixture group, time, duration, demand condition, hot or cold water side, and whether the problem appeared during peak use, after a power event, after maintenance, after a valve closure, or during normal operation.

Then connect the complaint to the booster system. Identify the booster package, pump numbers, controller, pressure zone, remote sensor if used, tanks, PRVs, bypass piping, upstream meter or backflow assembly, and downstream risers or distribution branches. If the complaint fixture is not served by the booster being reviewed, say that before changing anything.

This step prevents a controls note from being assigned to a distribution problem. A low shower on the top floor, a flush-valve complaint on one riser, a hose bibb outside a pressure zone, and a whole-building complaint can point to different checks. The log should make that distinction visible.

Separate suction, discharge, and remote pressure

Record suction pressure as close to the booster suction header as the approved test setup allows. A booster cannot create a reliable discharge record if the inlet condition is unknown. If suction pressure is low, fluctuating, or protected by a low-suction cutoff, the record should keep that fact separate from pump performance.

Record discharge pressure at the booster discharge header and, when the system controls from a remote sensor, record the remote pressure value and point ID. A controller may be maintaining a remote pressure setpoint while the local discharge gauge reads higher or lower than expected. Do not collapse those values into one pressure number.

Also record whether the gauge, transducer, or BAS point was trusted for the review. If a gauge cock is closed, a transducer is failed, a line is blocked, a sensor range is wrong, or the BAS point is mapped to the wrong package, write that as an exception. Pressure logs are only useful when the measurement point is named.

Log pump staging and control mode

The pressure log should show how the package tried to respond. Record which pump was lead, which pumps were available, which pumps were in hand, off, auto, fault, standby, sleep, or unavailable, and whether alternation, lead-lag staging, emergency power, no-flow shutdown, pressure setback, or remote control changed the expected sequence.

For variable-speed systems, capture speed, frequency, percent output, current, drive status, setpoint, and alarm state where those values are available. For constant-speed or pressure-switch systems, capture cut-in, cut-out, pressure switch status, pump call, and actual pressure response. The record should show whether the package called for pressure and whether the pump package answered.

Do not interpret a stopped pump as a failure without the mode. A pump may be stopped because the controller is satisfied, the system is in sleep mode, emergency power is limiting the package, a lead-lag timer changed sequence, a low-suction protection is active, the pump is in hand or off, or the VFD has an alarm. Write the mode first, then the conclusion.

Valves, tanks, and PRVs can make the pump look wrong

A pressure complaint can survive a healthy pump package. Record suction and discharge isolation valves, bypass valves, check valves, strainers, backflow devices, PRVs, pressure-sustaining valves, zone valves, and any recently operated valve that could affect the served zone. If a bypass is open, a check valve leaks, or a PRV is hunting, the pump log should not blame the pump alone.

Where a drawdown tank, bladder tank, or pressure tank is part of the system, record whether the tank was in service, isolated, waterlogged, damaged, or safe to verify. Tank precharge checks must follow the manufacturer and safety procedure, including the required water-side pressure condition. Do not add air to a suspect or damaged tank because a checklist says tank.

PRVs deserve their own line in the log. Note upstream pressure, downstream pressure, setpoint if known, strainer condition if checked, bypass status, and whether the valve is upstream of the booster, downstream of the booster, or part of a pressure-zone boundary. A low-pressure complaint downstream of a PRV is not automatically a booster failure.

Use trends instead of one gauge photo

A single gauge photo captures a moment. A pressure complaint usually needs time. Save a trend across the complaint window when the system has BAS, controller, or drive history. Include suction pressure, discharge pressure, remote pressure, setpoint, pump status, speed, lead/lag state, alarms, building demand proxy, and any low-suction, high-discharge, no-flow, dry-run, VFD, or communication event.

The trend should show cause and response. Did suction pressure drop before the discharge complaint? Did discharge pressure sag while the drive was already at maximum speed? Did a lag pump fail to stage? Did the controller go to sleep while demand continued? Did a pressure sensor read satisfied while fixtures were low? Did a PRV or bypass isolate the complaint zone?

If trends and field gauges disagree, keep both. A disagreement can mean a bad gauge, closed gauge cock, plugged sensing line, failed transducer, wrong sensor range, stale BAS point, wrong point mapping, or a real hydraulic difference between the booster and the complaint fixture. The useful record writes the conflict and the next qualified check.

Minimum booster-pump pressure log

Use the service ticket, startup form, BAS trend, pump-controller report, manufacturer checklist, or owner PM form first. Add this packet where the required form does not connect the complaint, pressures, pump response, controls, valves, tanks, and release decision clearly enough.

Before low-pressure complaint checklist

Run this check before clearing the complaint, changing setpoints, overriding a drive, opening a bypass, or blaming the pump package.

• Confirm the complaint location, fixture or zone served, time window, demand condition, and whether the booster actually serves that point.
• Record the booster tag, pump numbers, controller, VFDs, pressure zone, remote sensor, tank, PRV, bypass, and recent maintenance or power events.
• Capture suction pressure at the named point and note fluctuation, low-suction status, dry-run status, and source-side holds.
• Capture discharge pressure at the named point and compare it to the active setpoint and alarm limits.
• If remote sensing is used, record remote pressure, point ID, sensor location, and whether the controller is using that point.
• Record lead pump, lag pump availability, hand/off/auto status, speed or frequency, current, run proof, and active faults.
• Review controller, BAS, and VFD logs for low suction, high discharge, no-flow, dry-run, communication, sensor, and alarm events.
• Check valve positions and restrictions that can affect the served zone: suction valve, discharge valve, bypass, check valve, strainer, backflow device, PRV, and zone valve.
• Record tank status and precharge verification only under the manufacturer and site safety procedure.
• Attach a trend or timed log across the complaint window and a recheck after correction.
• Write unresolved sensor, gauge, PRV, valve, tank, controller, pump, utility, or distribution questions as open holds.
• Write the final status: released, released with monitoring, partial release, held, locked out, or recheck required.

Weak and strong booster notes

Weak note: pressure was low, adjusted booster, ok now.

That note does not identify the served zone, suction pressure, discharge pressure, remote sensor, setpoint, pump staging, VFD speed, alarms, valve positions, tank condition, PRV status, trend window, correction, or recheck.

Stronger note: Domestic water booster BP-2 reviewed for low-pressure complaints at Level 11 east restroom group on June 9 from 06:40 to 08:15. Complaint zone confirmed served by BP-2 high-zone riser. Controller in auto using remote pressure sensor RP-11E. Trend shows remote pressure fell from 58 psi to 39 psi during peak demand while discharge header stayed at 72 to 75 psi and suction pressure stayed between 48 and 51 psi. Lead pump P-2A ran at 61 Hz; lag pump P-2B remained unavailable with VFD fault active since 05:58. Bypass valve closed, suction and discharge isolation valves open, downstream PRV PRV-11E inlet 72 psi and outlet 39 psi during complaint. PRV strainer found restricted under approved service procedure, cleaned, and downstream pressure rechecked at 56 psi with P-2A at 49 Hz and no active low-suction alarm. P-2B VFD fault remains open with pump vendor. Released Level 11 east zone for monitored operation with BP-2 partial capacity hold until P-2B is restored.

The stronger note works because it proves the booster had source pressure, identifies a distribution-side pressure drop, keeps the lag-pump fault open, and separates the immediate complaint release from the remaining equipment hold.

Common mistakes

The first mistake is logging only discharge pressure. Without suction pressure, the reviewer cannot tell whether the pump package had enough inlet pressure to work with.

The second mistake is treating setpoint as delivered pressure. A setpoint is an instruction, not proof that the served fixture received pressure.

The third mistake is ignoring the remote sensor. A booster may be controlling from a high-floor sensor while the skid discharge gauge looks strange to someone standing in the pump room.

The fourth mistake is changing setpoints before saving the complaint window. Once the setting changes, the original evidence is gone.

The fifth mistake is skipping valves, PRVs, bypasses, strainers, check valves, and tanks. Those components can create the complaint while the pump package appears healthy.

The sixth mistake is closing the ticket while alarms remain active. A temporary pressure recovery does not clear a low-suction fault, VFD fault, failed lag pump, sensor fault, unsafe tank condition, or unresolved utility-side limitation.

Questions that come up

Does low pressure always mean the booster setpoint is too low? No. The complaint can come from low suction pressure, a failed pump, a lag pump that did not stage, a remote sensor problem, a PRV, a closed valve, a clogged strainer, a bypass, a tank issue, peak demand, or a fixture-zone mismatch. The pressure log is there to separate those paths.

Should the log include hot-water complaints? Yes, if the pressure complaint is on a hot-water branch, but the record should identify whether the booster serves the cold-water supply, the hot-water system, or both through the building distribution. Do not let a domestic booster note replace water-heater, mixing-valve, recirculation, or fixture-specific review.

Can a technician adjust tank precharge during the complaint review? Only under the manufacturer instructions, qualified procedure, and safety controls. The log can record tank status and whether precharge verification is required. It should not authorize unsafe tank work.

Does a normal pump-room discharge gauge clear a top-floor complaint? Not by itself. The log should compare pump-room discharge with remote pressure, zone pressure, PRV outlet pressure, riser condition, and the actual complaint location.

Compliance and safety limits

This field note is not booster-pump design, pump selection, pressure-zone design, code approval, startup commissioning, VFD programming, controls programming, PRV adjustment instruction, tank precharge procedure, electrical instruction, lockout procedure, or water-utility instruction. The engineer, plumbing designer, manufacturer, owner, AHJ, utility, startup provider, qualified technician, and site safety plan control the work.

Do not use this checklist to bypass lockout, electrical safety, stored pressure, tank integrity warnings, flood prevention, pressure relief, pump dry-run protection, VFD restrictions, controller passwords, manufacturer limits, utility cross-connection requirements, confined-space rules, ladder or access controls, or site-specific safety procedures. Do not override low-suction, dry-run, high-discharge, or drive protections to make a pressure complaint disappear.

Sources checked

• ICC Digital Codes, 2024 International Plumbing Code, Chapter 6 Water Supply and DistributionUsed for current model-code context around potable water supply and distribution pressure boundaries.
• ASPE Pipeline, The Future of Domestic Pressure Booster System Design Is Here TodayUsed for plumbing-engineering context around domestic pressure booster systems, redundancy, maintenance, and sizing responsibility.
• Xylem Bell & Gossett, Domestic Water Pressure Booster DesignUsed for booster design context around minimum suction pressure, remote fixture pressure, piping losses, pressure worksheets, and recording measurements near booster suction.
• Armstrong Fluid Technology, Design Envelope Booster Sequence of OperationUsed for packaged domestic booster controls context around setpoints, suction and discharge sensors, remote sensors, lead alternation, VFD operation, sleep/no-flow mode, low-suction and low-discharge limits, and alarm modes.
• Armstrong Fluid Technology, Pressure Booster System Start-up ChecklistUsed for startup-record context around total discharge pressure, suction pressure, tank precharge, gauge cocks, incoming suction pressure, voltage, amperage, and safe electrical warnings.
• Taco Comfort Solutions, Booster Pump Sets Installation, Operation, and MaintenanceUsed for booster package context around check valves, sleep mode, suction and discharge gauges, lead-lag verification, dry-run/no-flow protection, low-suction switches, high-discharge switches, VFDs, and alarm logs.
• Xylem Bell & Gossett, TechnoForce e-MT Pump Controller ManualUsed for controller context around suction and discharge displays, differential pressure switches, VFD control, alarms, trends, lead/lag definitions, run proof, and dry-run cautions.
• Watts, Water Pressure Reducing Valves GuideUsed for PRV context around reducing higher supply pressure to a lower downstream pressure, fluctuating supply pressure, code pressure limits, and closed-system/thermal expansion considerations.
• Amtrol, Pressuriser Water Pressure Booster Installation and OperationUsed for pressure-booster tank and control context around precharge, cut-in/cut-out, bypass valves, supply valves, blocked controls, waterlogged tanks, short cycling, and safety warnings.
• OSHA, 29 CFR 1910.147, Control of Hazardous EnergyUsed for lockout and hazardous-energy boundaries during pump, control, and pressure-system service.

Related guides