Metering data gives you a record an inspector cannot argue with. A single-point flow test during a walkthrough shows you what a fixture does at that moment, but a submeter shows you what it does over a week of actual occupancy, including the peak-hour surges and the after-hours drift that a visual check will never catch. If you are trying to prove compliance rather than just assume it, the meter log is your exhibit A.
Why Metering Data Beats Visual Inspection
A code inspector with a bucket and a stopwatch is measuring one faucet, one time, under conditions that may not resemble a Tuesday morning rush. Flow rate compliance under IPC 604.4 is a static spec, but restroom fixtures do not behave statically. Aerators clog, cartridges wear, solenoids stick, and mixing valves drift, all of which change flow and temperature output over time in ways a single spot check misses entirely.
Submetering at the branch line or fixture level turns compliance from a guess into a dataset. Instead of asserting a lavatory faucet meets 0.5 GPM, you can show a week of logged flow that stays under it, including the moments when three fixtures run simultaneously and supply pressure sags. That is the difference between telling an inspector “it’s compliant” and handing them a printout.
Reading Flow Logs Against Code Maximums
The baseline number to check every log against is the EPAct/IPC cap of 0.5 GPM for public lavatory faucets. This is lower than the 2.2 GPM residential allowance and lower still than the 2.5 GPM (1.8 GPM in California) shower head cap, so if your logging software defaults to residential thresholds, reset it before you start pulling data. A fixture reading 0.6 or 0.7 GPM consistently is not a rounding error, it is a fixture out of spec, usually from an aerator swap that did not match the original restrictor or a cartridge that no longer seats fully.
Look for three patterns in the raw log, not just the average:
- Steady-state overflow – flow consistently above 0.5 GPM regardless of time of day, which points to a hardware mismatch or missing restrictor.
- Pressure-spike overflow – flow exceeds the cap only during low-demand hours when static pressure is highest, which points to a pressure-compensating aerator that has failed.
- Intermittent overflow – occasional short spikes with no clear pattern, which usually means a partially seated cartridge or a solenoid on a sensor faucet that is not fully closing.
Averages hide all three of these. A fixture that spikes to 0.9 GPM for ninety seconds twice a day but averages 0.48 GPM will pass a lazy review and fail a real one.
Spotting ASSE 1070 Valve Drift Early
ASSE 1070 sets the mixed-water temperature limit at 110°F for fixtures in public and commercial settings, primarily to prevent scald injury at lavatories used by children, the elderly, or anyone with reduced sensation. A mixing valve in spec on installation day does not stay in spec indefinitely. Thermostatic elements degrade, check valves in the hot and cold legs start passing slightly, and the failure mode is almost always a slow upward creep in delivered temperature rather than a sudden jump.
Temperature logging catches this months before anyone gets scalded or an inspector runs a manual test. Set your logging interval to capture temperature at the point of use, not at the valve body, since the two can differ by several degrees depending on run length and insulation. A valve reading 108°F today and 111°F next month is telling you exactly when it will fail, not just that it eventually will.
| Symptom in log | Likely cause | Action |
|---|---|---|
| Gradual temp rise over weeks | Thermostatic element wear | Schedule valve rebuild or replacement |
| Sudden temp spike, single event | Check valve failure on hot leg | Inspect and replace check valves immediately |
| Temp fluctuates with building demand | Undersized valve for peak load | Re-evaluate valve sizing against fixture count |
Metering Sensor Faucets for Cycle Faults
Sensor faucets add a failure mode that manual faucets do not have: the cycle itself. A solenoid that hangs open after the sensor loses line of sight will register as continuous low flow rather than a spike, which is easy to miss if you are only watching for overflow events. A solenoid that fires repeatedly without a full close between cycles shows up as a sawtooth pattern in the log, short bursts of flow with no real gap, usually caused by sensor range drift or a mounting position that catches reflections off a nearby surface.
High-traffic restrooms are where this matters most, since a faucet cycling 400 times a day gives the solenoid four times the wear of one in a low-traffic application, and cycle faults compound faster. Facilities specifying commercial touchless faucets for airports, stadiums, or hospital common areas should expect to log cycle counts alongside flow volume, because a faucet that is technically flow-compliant but cycling incorrectly is still a maintenance ticket waiting to happen, and eventually an inspection flag.
Cross-reference cycle count against flow volume per cycle. A faucet averaging 0.4 GPM but delivering it in a single 8-second burst per cycle is behaving differently than one delivering the same average across twelve short bursts, and only the log tells you which.
Building an Inspection-Ready Data Package
A 7-day logging interval is the practical minimum for catching peak-hour anomalies, since anything shorter misses the weekday-to-weekend usage shift and anything longer starts accumulating storage overhead without adding much diagnostic value. Log flow rate, temperature, and cycle count (for sensor fixtures) at intervals tight enough to catch a 90-second spike, not just hourly averages.
When you assemble the package for an inspector or compliance file, include:
- Fixture ID and location matched to the building’s plumbing plan
- Raw log export, not just summary averages, covering the full 7-day window
- Flagged events where flow exceeded 0.5 GPM or temperature exceeded 110°F, with timestamps
- Maintenance record showing any corrective action taken and the date
- Reference to the applicable code section (IPC 604.4 for flow, ASSE 1070 for temperature) next to each fixture’s data
This is the file that turns an inspection from an adversarial spot-check into a documentation review, which is a faster and more predictable process for everyone involved.
What to Check Before You Call It Done
Pull one full week of logs before assuming any fixture is compliant, not a single day. Confirm your logging thresholds are set to commercial limits (0.5 GPM, 110°F), not defaulted to residential values. Flag any fixture showing intermittent spikes even if its average looks fine, since averages are exactly what hide the failures that matter. If a mixing valve shows any upward temperature trend across two consecutive weekly logs, schedule service before the next inspection cycle, not after. And if you are managing more than a handful of fixtures, build the data package as a standing template so each inspection cycle is a matter of exporting current logs against a known-good format, not reconstructing the process from scratch.
