Concept stage · no hardware built yetFounding pilots Spring 2027 (target)

Every weekly eyewash activation, on the record.

A small node clips onto each plumbed eyewash and records when the valve was opened and how long it stayed open. The person testing it presses a button on the node, and a one-tap email to the lab’s room contacts records who confirmed the visual check. Every Monday, the building’s FlushLog report arrives as a PDF.

Estimated $89 per station · $249 per building gateway · $2 per station per month for reports · founding-site pilots free

FCC notice. This device has not been authorized as required by the rules of the Federal Communications Commission. This device is not, and may not be, offered for sale or lease, or sold or leased, until authorization is obtained.

Page 1 of a sample FlushLog report for Halden Hall, a fictional building: 11 of 14 stations activated in the week of Sep 28 to Oct 4, 2026, 3 missed, and a station log listing each eyewash with its activation time, how long the valve was open, the initials of whoever confirmed the visual check, and a status of logged, late or missed.
Sample report · simulated data for a fictional building. Page 1 of 2, cropped.
Generic example sheet, typeset for this page. Not any institution’s form; the entries are invented.

Two blank weeks. On paper, nobody sees them until someone reads the sheet, often at the next lab survey.

Initials show that a pen was here. They can’t show when the eyewash was activated, or for how long.

How it’s done today: a sheet of paper by the sink.

ANSI/ISEA Z358.1 calls for plumbed eyewashes to be activated weekly. On many campuses, someone in the lab activates the eyewash and initials a sheet taped to the wall.

“Record eyewash flushing on the Weekly Eyewash Maintenance Log, usually posted on the wall near the eyewash.”

Duke University Occupational and Environmental Safety Office, lab safety guidance

Flushproof keeps the same record, filled in when the valve is opened: the time, how long it stayed open, and the initials of the person who checked the station.

Public examples of the weekly paper log. Links go to each institution’s own page; none of them is affiliated with Flushproof.

How it works.

One node per eyewash, one gateway per building, one report per week. Nothing on the station is replumbed.

Concept drawing of a Flushproof installation A wall-mounted plumbed eyewash in front elevation, with its green emergency eyewash sign, two spray heads with dust caps, a bowl, a valve and a push flag. A magnet sits on the push-flag arm. The node clamps to the supply pipe just below the valve. An enlarged detail shows the magnet, the reed switch inside the node, the clamp and the confirm button. A dashed radio link runs to a gateway plugged into a wall outlet, which sends a weekly FlushLog report. A DETAIL A · 2:1 1 2 3 radio link 4 5 Mon 06:00 · PDF to EHS Thu · reminder if a station hasn’t been activated FLUSHPROOF · STATION CONCEPT · NOT TO SCALE REV 0 A 1 2 3 DETAIL A · 2:1 4 5 Mon 06:00 · PDF to EHS Thu · reminder if a station isn’t activated
Concept drawing, not to scale. Final design may change.Detail A shows the push flag at rest (solid) and pushed (dashed).
Magnet on the push flag
A small magnet sits on the flag arm. Pushing the flag to start the flush swings it past the node.
Node on the supply line
Clamps around the pipe just below the valve. A reed switch records when the push flag was opened and how long it stayed open. It can’t sense water itself.
Confirm button
After the test, press it once. An email goes to that lab’s room contacts; whoever taps it confirms that water reached both heads and that caps, access and sign are fine, and the row records their initials. The record shows who tapped the email, not who stood at the station.
Building gateway
Plugs into an ordinary outlet and forwards each record from the nodes in range.
The FlushLog report
Monday morning: a PDF per building for EHS. Thursday: a reminder to the room contact for any station that hasn’t been activated.

Shower tests are run by Facilities; a shower can be logged too if a sensor is fitted to it.

The report, up close.

This is the sample FlushLog for one fictional building and one week. It’s laid out like the paper log it replaces, so whoever reads it at survey time already knows the columns.

Close-up of the sample report's Activated and Valve open columns: for example, Rm 104 activated Sat Oct 3 at 15:36, valve open 3:31.

Sample report · simulated data, fictional building.

Station log

Every station, every week.

Each row is one eyewash: when it was activated and how long the valve stayed open, to the second. Both come from the node, not from someone’s memory at the end of the week.

In the sample: 14 stations, 11 activated, and a site target of the valve open for at least 3:00.

Close-up of the Valve open, Visual check and Status columns for the last five rows: confirmations with initials such as L.W., one row Not confirmed, and two rows with no activation.

Sample report · simulated data, fictional building.

Visual check

Who confirmed the visual check.

The node can’t see whether water reached both heads, the caps are on, the path is clear and the sign is visible. A person can. The person testing presses the station button; the confirmation email goes to the lab’s room contacts, and whoever taps it is recorded by initials, the way the paper log does. The record shows who confirmed, not who stood at the station.

In the sample, CS-304 was activated but nobody confirmed the check, so the report says “Not confirmed” and lists it under Needs attention.

Close-up of the last eight rows of the station log: three rows show No activation recorded and a red Missed status.

Sample report · simulated data, fictional building.

Needs attention

Missed stations are flagged the same week.

A station with no activation shows up in red, by station and room. If it still hasn’t been activated by Thursday, the room contact gets a reminder email; a station that also missed the week before gets a Monday reminder too. The report notes when each was sent.

In the sample, EW-305 in the cold-room vestibule has missed two weeks in a row.

Close-up of page 2: the six most recent weeks of the 13-week grid, 8/30 to 10/4, one square per station per week, with the Weeks column; three stations show red, no activation recorded, in the week of 10/4.

Sample report · simulated data, fictional building.

History and records

Thirteen weeks on one page, ready to print.

Page 2 shows the last quarter, one square per station per week: 172 of 182 station-weeks have a recorded activation. Every activation is kept with its station, time, duration and confirmation, exports as CSV, and prints on demand.

Records are kept as long as the site chooses; the default is 3 years.

Download the sample report (PDF)

Specifications.

There is no prototype yet, so nothing below has been measured. Target means a design goal, not a promise. Estimate is arithmetic. TBD means not decided yet.

Sensing

Activation
Reed switch in the node, magnet on the push flag
Target
Recorded per activation
Start time, and how long the valve stayed open, to the second
Target
Visual check
Button on the node, then a one-tap email to the lab’s room contacts that records initials
Target
Water temperature
Only with an optional probe
TBD

Install and power

Mounting
Clamps to the supply line below the valve; no plumbing work
Target
Battery
2 × AA, 2+ years, to be validated
Target

Connectivity

Gateway
One per building, plugs into an outlet
Target
Gateway network
Wi-Fi or Ethernet
Target
Cellular gateway
For buildings where campus Wi-Fi isn’t an option
TBD
FCC authorization
Not obtained yet. Required before any sale or lease. Pilot units are unpaid evaluation loans, labelled and collected after the pilot
Planned

Reports and records

Weekly report
FlushLog PDF per building, Monday 06:00
Target
Reminders
Email to the room contact when a station hasn’t been activated
Target
Export
CSV and print, any time
Target
Retention
Site setting, default 3 years
Target
Hosting location
Set in the pilot letter, before install
TBD

Compared with what you use now.

OptionCostWhat the record provesWhere it’s strongWhere it falls short
Paper logAbout $0, plus staff timeSomeone initialled a boxFree, familiar, nothing to install or approveCan be initialled without the eyewash being activated; blank weeks surface late
Checklist apps e.g. Mitti (formerly SafetyCulture)Free plan for up to 10 users; paid plans $24–29 per user per monthSomeone tapped “done” at a time and placeCovers every checklist you run, not just eyewashesStill a walk and a tap at every station; no sensor records the activation
Plant monitoring kits e.g. Emerson Rosemount 702About $1,700+ per station, plus a gatewayThe valve opened, with a timestampProven and shipping for years, built for control roomsPriced and packaged for process plants and integrators, not lab buildings
Flushproof conceptAbout $89 per station + $249 gateway, then $2 per station per month (est.)When the valve was opened, how long it stayed open, and who confirmed the visual checkPriced for labs; the weekly PDF follows the paper log’s columnsConcept stage: not built yet

Sources: Mitti (SafetyCulture) Free and Premium plans, checked Oct 2026; Premium is $24 per seat per month billed yearly, $29 billed monthly. Emerson Rosemount 702 safety-shower monitoring kit, about $1,760 before its WirelessHART gateway, from a 2026 price check (Emerson’s own page doesn’t list a price). Flushproof prices are estimates. Wireless eyewash activation logging for industrial plants has been sold by several companies for well over a decade; Flushproof’s difference is the price and the report, not the sensing.

Estimated price.

$89 per station (est.) · $249 building gateway (est.) · reports & audit archive $2 per station per month (est.)

Nothing is for sale yet. Prices are estimates and will be confirmed before anyone is charged.

FCC notice. This device has not been authorized as required by the rules of the Federal Communications Commission. This device is not, and may not be, offered for sale or lease, or sold or leased, until authorization is obtained.

$2,029est.

A 20-station building is $2,029 up front (est.), under a $3,000 purchasing-card limit if that’s yours. Then $40 a month for reports and the audit archive.

  • 20 station nodes × $89$1,780
  • 1 building gateway$249
  • Up front, estimated$2,029
  • Then reports & archive, 20 × $2$40 / month
Download the sample report (PDF)

Founding-site pilots, Spring 2027.

Founding-site pilots are free and run in the Spring 2027 semester. That’s a target: we confirm dates with you first.

What you get
One building: up to 10 stations, a gateway, and one semester of weekly FlushLog reports.
Cost
Free for founding sites while the hardware is uncertified. No payment on this site.
How we judge it
We agree the success test before install. At minimum, it has to log every test flush you run in front of us.
What we’d ask
A room contact for each lab, an outlet for the gateway, and a test flush together at install.
The hardware
Pilot nodes and the gateway are pre-production evaluation units that have not been authorized by the FCC. We lend them for evaluation only, at no charge for the hardware. They carry the FCC notice, stay ours, and we collect them when the pilot ends. No Flushproof hardware will be sold or leased until FCC authorization is obtained.
What it stores
Station, room, activation time and how long the valve was open, the confirmer’s initials and email address, and room-contact emails. No other personal data.

FCC notice. This device has not been authorized as required by the rules of the Federal Communications Commission. This device is not, and may not be, offered for sale or lease, or sold or leased, until authorization is obtained.

Request a founding-site pilot

Step 1 of 2 · three fields

Burak will reply by email. What you enter here is used only to talk with you about a pilot. Privacy note

Got it. A few optional questions?

Step 2 of 2 · every question is optional, and each one helps scope the pilot

Type of organization
How weekly flushes are recorded now

A sentence is plenty. “None” is a useful answer too.

Network for the gateway
Pilot
How you would buy
Other weekly or monthly checks you’d want logged

Thanks. Burak will reply by email.

Your pilot request is in.

    What happens next

    Download the sample report (PDF)

    Where this stands.

    1. Now · Oct 2026

      Concept. This page, the sample report and the design exist. No hardware has been built. We’re starting conversations with EHS and lab-safety offices.

    2. Next

      One demo node on a real eyewash, before any pilot kits are built.

    3. Spring 2027 (target)

      Free founding-site pilots on loaned evaluation units. Dates confirmed with each site.

    4. After the pilots

      A production batch only if the pilots show the record holds up. FCC authorization before any hardware is sold or leased.

    Questions EHS offices ask.

    Will our auditor accept this instead of the wall sheet?

    Ask them first; we can’t answer for them. No rule we found demands paper. The University of Nevada, Reno’s EHS office puts it plainly: “It is up to each group or department how they would like to handle documentation of their activities.” In a 1992 interpretation letter about bar-code inspection records for safety equipment, OSHA said computer-based records are acceptable if they meet the substantive requirements and hard copies can be produced on request. That letter predates Flushproof and says nothing about it.

    Does this make us compliant with ANSI Z358.1 or OSHA?

    No. ANSI/ISEA Z358.1 calls for plumbed eyewashes to be activated weekly; Flushproof keeps the record of that activation. OSHA has not adopted Z358.1, but refers employers to it as guidance. State rules differ: Washington writes weekly activation into law, while California requires it at least monthly.

    Is it an alarm?

    No. It’s a record of weekly tests. If a station is activated outside a scheduled test, the room contact gets an informational email asking whether it was a real use. Don’t rely on Flushproof to summon help.

    What if someone activates it but doesn’t confirm the visual check?

    The activation is still logged with its time and how long the valve was open. The visual-check column shows “Not confirmed”, and the station is listed under Needs attention, as CS-304 is in the sample report.

    Wi-Fi, Ethernet or cellular?

    The gateway is designed for Wi-Fi or Ethernet; tell us in the form which applies to you. A cellular gateway isn’t designed yet, so we list it as TBD.

    Can a lab manager buy it on a P-card?

    That’s the intent. At the estimated prices, a 20-station building is $2,029 up front (est.), under a $3,000 purchasing-card limit if that’s yours, then $40 a month. A PO works too. Nothing can be bought until the hardware has FCC authorization.

    How long are records kept, and can we get them out?

    As long as your site chooses; the default is 3 years. You can export everything as CSV or print any week at any time, and each Monday’s PDF is yours to file wherever you keep audit records.

    A note from the founder.

    I’m Burak Unlu, a computer engineering student at Johns Hopkins in Baltimore. Flushproof is my own project, not a university one. Flushproof starts from the routine that campus safety pages such as Duke’s and Ohio State’s describe: activate the eyewash every week, then record it on a log, usually a sheet posted near the unit. It works, but the sheet can’t show when the eyewash was activated, or for how long.

    Nothing is built yet, on purpose. Before I make pilot kits, I want to work with a few EHS and lab-safety teams. If that’s you, the pilot form on this page reaches me directly, or you can email me at flushproof@burakali.com. It’s at flushproof.burakali.com.

    Burak Unlupebl health inc. · Baltimore, Marylandflushproof@burakali.com
    Request a founding-site pilot