Flushometer Handover Docs: What Installers Must Give You

After a sensor flushometer install, you should receive four documents at minimum: the sensor detection range recorded in inches, the battery type with expected replacement interval, the GPF rating with compliance certificate (1.28 vs 1.6), and an ASSE 1037 reference for the flush valve itself. If your installer hands you a generic warranty card and a invoice, you have nothing to diagnose phantom flushing with six months from now, and nothing to show an auditor if water-use compliance gets questioned.

Why a generic handover packet doesn’t work for flushometers

A standard plumbing punch list covers things like fixture count, rough-in dimensions, and shutoff valve locations. That’s fine for a tank toilet or a lavatory faucet. A sensor flushometer is a different animal: it has a detection range that gets tuned at install, a power source with a finite life, and a flush volume that’s either compliant or isn’t. None of that shows up on a generic sheet, which means when the unit starts double-flushing or ghost-flushing eight months in, you have no baseline to compare against. You’re troubleshooting blind.

This matters more in facilities with dozens or hundreds of units, where a single mis-tuned sensor range can waste thousands of gallons a year, and where a facilities manager may need to prove GPF compliance to a water utility rebate program or a green building certification auditor. Paperwork isn’t bureaucracy here. It’s the only way to separate a calibration drift problem from a mechanical failure six months after the installer has left the building.

Sensor range and calibration settings to log

Every infrared sensor flushometer has an adjustable detection range, typically somewhere between 3 and 30 inches depending on the model, and the installer sets this during commissioning based on fixture type and stall depth. That number needs to be written down at handover, not left to memory or a factory default assumption.

Ask for the following at minimum:

  • Detection range in inches as set at install (not the factory default range)
  • Sensor mode: occupancy-based or range-based detection
  • Time delay setting between detection and flush trigger
  • Any range adjustments made during commissioning walk-through, with before/after values
  • Installer’s notes on why the range was set where it was (reflective surfaces, stall width, adjacent fixture spacing)

This record matters because phantom flushing is almost always a range problem before it’s a hardware problem. If the sensor range was set too wide for a narrow stall, you’ll get activations from people walking past in the corridor. If you don’t know what it was originally set to, you’re guessing at the fix instead of correcting a known deviation.

Power source and battery schedule records

Sensor flushometers run on battery, hardwired AC, or a hybrid with battery backup. The handover doc needs to specify which, and if battery, the exact type (commonly 3V lithium or 6V alkaline packs depending on manufacturer) along with the expected replacement interval under normal duty cycle.

Low battery voltage is one of the most common causes of erratic sensor behavior, including both missed flushes and phantom flushes, because the sensor’s processing can become unreliable before the unit fully dies. Without a logged install date and expected interval, maintenance staff have no way to know if a malfunctioning unit is six months into a 2-year battery life or overdue for a swap. Get this in writing:

  • Power type (battery, AC hardwired, hybrid)
  • Battery chemistry and voltage
  • Install date of current battery
  • Manufacturer’s stated expected life under typical use (cycles or months, whichever the spec sheet gives)
  • Low-battery indicator behavior (LED blink pattern or audible signal, if equipped)

Build this into your CMMS or a simple spreadsheet with a flag date for proactive replacement. Reactive battery swaps after failure reports cost more in labor and user complaints than a scheduled swap during a routine restroom service visit.

GPF compliance certificates and retrofit kit specs

Federal standard for flush valve toilets is 1.6 gallons per flush maximum, though 1.28 GPF units (sometimes called high-efficiency toilets or HETs) are increasingly standard for new installs and required under some state and local codes and for LEED or WaterSense-adjacent credits. If your facility is being retrofitted from older 3.5 GPF units, or if you’re mixing 1.6 and 1.28 GPF fixtures across a building, you need documentation that states, fixture by fixture, which GPF rating is installed where.

This isn’t optional paperwork. If a water utility rebate program or a sustainability audit asks for proof of water-use reduction, “we think most of them are 1.28” is not an answer. Demand:

Document What it should show
GPF compliance certificate Rated flush volume per fixture, manufacturer certification
Retrofit kit spec sheet Model number of retrofit diaphragm or piston kit if valve body was reused
ASSE 1037 reference Confirmation the flush valve meets ASSE 1037 performance and flow standards
Fixture schedule Location-by-location list matching GPF rating to stall or restroom

ASSE 1037 is the performance standard that covers flush valves for water closets and urinals, addressing things like flow rate consistency and flush volume accuracy. Ask your installer to confirm in writing that the valves installed meet this standard, not just that they’re “code compliant,” since code references vary by jurisdiction and ASSE 1037 is the underlying performance baseline most codes point back to.

If the project involved retrofitting existing valve bodies with new sensor kits rather than full fixture replacement, get the retrofit kit’s model number and spec sheet separately. Retrofit kits can have different flush volumes than the original valve, and that’s exactly the kind of detail that gets lost if it’s not documented at handover.

Baseline readings for phantom flush troubleshooting

Phantom flushing, where the unit triggers with no one present, is usually one of three things: sensor range set too wide, a reflective surface in range (stainless partitions, wet floors, shiny tile), or electrical interference from nearby equipment. You can only diagnose which one you’re dealing with if you have a baseline to compare against.

At handover, request a written note of the installer’s test conditions: what the stall looked like empty, what range the unit was tested at, and whether any reflective surfaces were flagged during commissioning. If phantom flushing starts later, your maintenance team can compare current conditions against that baseline instead of re-diagnosing from zero. This is also useful if a facility later installs new partitions, signage, or commercial kitchen faucets or fixtures nearby that introduce new reflective surfaces into a sensor’s field of view. That kind of change can retrigger range problems that had nothing to do with the original install.

Checklist to demand before sign-off

  • Sensor detection range in inches, as set at install, with mode (occupancy or range-based)
  • Power source type, battery chemistry, install date, expected replacement interval
  • GPF rating per fixture, with compliance certificate (1.6 vs 1.28)
  • Retrofit kit model number and spec sheet, if applicable
  • ASSE 1037 compliance confirmation in writing
  • Baseline commissioning notes: stall conditions, reflective surfaces flagged, range test results
  • Fixture schedule matching location to GPF rating and sensor settings

Before you sign off on the job, walk the punch list against this checklist line by line and refuse to release final payment until every item is in hand. If the installer can’t produce a sensor range value or a battery install date, that’s a sign commissioning wasn’t done properly, not just a paperwork gap. Store these records in your CMMS alongside the fixture’s asset tag so the next maintenance tech who gets a phantom-flush complaint has something real to work from instead of starting over.