Skip to main content

Whoever you are in this decision, the current setup is working against you.

  • For the director or general manager

    Three deadlines, one year, and all of them land on you.

    Accessible web content, a plain-language report twice a year, and a service line inventory posted publicly. Any one of them is a project. Together they are the same project, and buying three answers is how a utility ends up with three things nobody can maintain.

  • For the water quality and compliance manager

    You write the report, you keep the inventory, and you dread the PDF.

    Every year the same layout fight, the same folded insert, the same questions on the phone from people who could not read it. The data is already in your LIMS and your GIS. What is missing is a way to publish it that a resident can actually use.

  • For the public information and customer service lead

    When an advisory goes out, the phones do not stop.

    Half the calls are people asking what the notice meant, and half are people who never got it. The page they land on has to load fast on a phone, read at an eighth-grade level, and be there in Spanish, and you need to be able to change it yourself at 2am.

A note on vocabulary: utilities publish through GIS map viewers as often as through BI platforms. Both are embedded third-party viewers, and the keyboard walk is where both of them fail.

Don't take our word for it. Type a street.

This is not a screenshot. It is the product's own address lookup running on this page against the demo utility's service line inventory, keyboard and screen reader support included. It is also the entire Lead and Copper Rule Improvements publication requirement, solved.

Loading the live demo…

This isn't optional. Here's the legal landscape.

  • ADA Title II web rule. WCAG 2.1 AA for public entity web content and apps, large entities by April 26, 2027. Your map viewers and dashboards are web content. DOJ, April 2024 (opens in a new window)
  • Consumer Confidence Report rule revisions. Systems serving more than 10,000 move to twice-yearly reports, with a push toward plain language and translation. The annual PDF was already the weakest thing a utility published; now there are two of them. EPA (opens in a new window)
  • Lead and Copper Rule Improvements. Baseline service line inventory due November 1, 2027, and systems serving more than 50,000 must post it publicly online. Address-level data, on the open web, that anyone can search. EPA (opens in a new window)
  • SDWA public notification. Tier 1 within 24 hours, Tier 2 within 30 days, Tier 3 with the annual report. The channel you notify through has to work for everyone you are notifying. 40 CFR 141 Subpart Q (opens in a new window)

Your utility already assembles every one of these datasets. The only question is how well you publish them.

How this is different

The old way

This way

The annual report as a folded PDF insert
A report you can search, translate, and read aloud, twice a year
Inventory posted as a 40MB spreadsheet download
Type your address, get your record, by keyboard
Embedded map viewers that fail a keyboard walk
Schematic maps with a full table alternative, every tile reachable
Advisories that need a developer to publish
Your PIO edits the notice and the guidance at 2am, no deploy
Spanish handled by a browser translate button
Hand-written translations, correctly marked, never machine guessed
Results colored red and green
Icon, word, and position: readable in grayscale

See it as your customers would.

The demo utility is fictional. The architecture is not.

Look for the demo bar at the top of the portal to find your way back.