What a Rural Water Utility Actually Needs From Its Website

We shipped a website for a rural Mississippi water association this summer. On paper it’s the least glamorous project imaginable — no product to sell, no brand story, no funnel. In practice it was one of the most clarifying builds I’ve done, because a water utility website strips web design down to its honest core: nobody is here for you. They’re here for one answer.

Nobody has ever browsed a water association’s website recreationally. Every single visitor arrives with a problem: the water’s off, the water’s brown, the bill is due, there’s a boil-water notice going around Facebook and they want to know if it’s real. The whole site has to be designed around the worst version of that visit — a worried person, at 2 AM, on an old phone, with one bar of rural LTE.

Design for that visitor and you’ve designed for everyone.

The 2 AM test

Here’s the actual scenario that shaped the build. A member’s water cuts off in the middle of the night. They search the association’s name from bed. What happens next decides whether your office phone melts down at 7:59 AM.

So the homepage leads with system status — current outages and active boil-water notices, dated, in plain language, above everything else. Not in a news feed three clicks deep, not in a PDF, not “check our Facebook page.” The single most important piece of content on the site is whatever’s wrong right now, and when nothing’s wrong, the site should say that too: all clear, last updated this morning. A dated “all clear” builds more trust than any mission statement, because it proves somebody’s home.

The rest of the priority order fell out of asking the office one question — what do people actually call about?

1. Is my water safe / why is it off — status and notices, front and center.
2. Pay my bill — one obvious button, straight to payment, no scavenger hunt.
3. Start or stop service — what to bring, what it costs, when someone’s at the office.
4. Reach a human — the office number, tap-to-call, with real hours.

Everything else — board members, meeting minutes, the annual water quality report, the tariff sheet — matters for compliance and for the handful of members who want it, and it’s all there. But it lives below the four questions, not in front of them.

Boring engineering is a feature here

The technical decisions all follow from the same visitor. Rural coverage is genuinely bad, and the phones people carry are genuinely old. So the site is static — plain fast pages, no app framework rebuilding the screen, no scripts fetching things before the words show up. It loads in about a second on a weak connection, which is the difference between a member reading “boil-water notice lifted” and a member giving up and calling the after-hours line.

Two decisions I’d defend anywhere but were non-negotiable here:

Notices are web pages, not PDFs. A PDF is where information goes to be unread on a phone. Every notice is a real page — searchable, screen-reader-friendly, loads instantly, and Google can index it, which matters when the whole county is searching “boil water [town name]” at the same time.

The office can update it without calling a developer. A status system that requires a web guy to post an outage is a status system that will always be out of date. The people who answer the phones post the notices — quickly, from the office, in a workflow built to be hard to get wrong. If your utility’s site can’t be updated by the people who know what’s happening, it isn’t infrastructure, it’s decoration.

Why this matters beyond water

I’m writing about a water association, but the lesson applies to most local organizations: the website’s real job is almost never what the homepage template thinks it is. It’s the three or four questions your phone rings with, answered instantly, in the order people actually ask them — on the worst phone, on the worst night.

That’s a different starting point than “what should the site look like?” It’s “what does the 2 AM visitor need?” Answer that first and the design follows. If your organization’s site can’t pass the 2 AM test, that’s exactly the kind of build we do — small, fast, and honest about what it’s for.