DisasterHub
WorkbenchOne place for emergency managers and government comms directors to get the word out when it matters most.
The problem
In a crisis, residents piece together what’s happening from websites, PDFs, social media, the news and alert systems.
Emergency teams have the verified facts. Turning them into clear, accessible guidance, in more than one language, fast, is the hard part.
Alert systems send the alert. Residents still need one trusted place to understand what it means and what to do.
What we’re trying
DisasterHub doesn’t manage incidents. It manages public understanding, next to the tools emergency teams already use.
A comms team builds a phone-first public page from approved blocks: alerts, updates, evacuation zones, a shelter map, contacts. In English and Spanish. Every change is previewed, approved and logged, and a page can roll back.
A public chatbot answers only from approved sources and cites them. Stale content gets flagged, and leaders get a nightly report. Seven demos built on past incidents are live, from a hurricane to a water crisis.
Next: a test with two people editing at once, and a full WCAG 2.1 AA check.
What we’ve learned
We built it four times: WordPress in 2024, static mockups, a React prototype, and now a custom app on Cloudflare.
Some scenarios don’t belong on a hub. Utility companies own outage messages, and an earthquake gives no warning to build a page ahead of time. We cut both.
One Worker serving every page beat a separate site for every customer.
Governments bring their own sign-in, so we moved to WorkOS to support the identity providers they already use.
From the log
Stage changes, launches and the things that broke. We write it all down.
Read the whole logDisasterHub gets a second editor
Two people can now edit safely at the same time, and the editor got an accessibility pass.
Seven demos, one address
Hurricane, wildfire, extreme heat, a train derailment and more. The demos each live at their own address, for example hurricane.disasterhub.us.
A chatbot that cites its sources
Residents can ask DisasterHub questions and get answers only from approved sources, with citations.
DisasterHub goes to production
The admin went live, and a test agency published, then restored, its first page.
The DisasterHub app begins
A React hurricane demo on Cloudflare, the start of today’s app.
DisasterHub on paper
Static mockups for a Charleston hurricane, a Sonoma wildfire and a flash flood.
The first DisasterHub prototype
A first build in WordPress: one hub for emergency information.
Where it’s headed
- Napkin
Sketch it
An idea on paper, a problem worth chasing. Nothing built yet.
- Workbench
Build it
The crew is building. Not public yet, but the log is.
We’re here - Sea trial
Test it for real
Real people are using it. Expect rough edges, and tell us about them.
- Set sail
Ship it
It graduates into an Awesome Cause product, with support behind it.
- Scuttled
Or stop it
Any stage can end here, on purpose. The log says what we learned.