Turn Up the Signal: Writing Emergency Alerts People Actually Understand
A wildfire alert went out to a Utah community earlier this month. The message told residents they were in “Set” status for possible evacuation. It listed a location. That was about it — no listed source, no timestamp, and the hazard itself only became clear because outside information filled in what the alert didn’t say.
If you work in emergency management, you know exactly what “Set” status means. You’ve seen the Ready, Set, Go framework a hundred times. You assume your community has too.
They probably haven’t.
The Jargon Gap
Ready, Set, Go started in California in 2009 as a plain-language framework to help residents prepare for wildfire. Get ready: harden your property. Get set: pack a bag and build an evacuation plan. Go: leave. It worked because it borrowed language everyone already understood — the same three words used to start a race.
Somewhere between that origin and its adoption as a nationwide model by the International Association of Fire Chiefs and federal agencies, the plain-language framework became operational shorthand. To anyone outside your program, “Set status” doesn’t parse. It sounds like insider language, because nobody outside the program uses it that way.
Emergency alerting researcher Dr. Jeannette Sutton flagged exactly this problem in a recent post on The Warn Room, breaking down the Utah wildfire alert sentence by sentence: missing the source of the message, missing the time it was issued, and missing an explicit statement of the hazard. The only thing the alert communicated clearly was location.
Here’s the part that most of us miss: that same Wireless Emergency Alert actually did contain more information — a full explanation of the hazard, guidance about packing a go-bag, a link to more information. It just lived in the WEA’s optional 600-character instructions field, which is only visible to a subset of recipients, roughly the 60% of U.S. phones that are iPhones. Everyone else — meaning tens of millions of people, many on Android devices — only got the short, confusing version.
The gap wasn’t a technology problem. It was a message design problem, and it happened for a common reason: it was drafted under deadline pressure, mid-event, with no time to workshop the wording.
What Clear Alerts Require
Good emergency messaging has always come down to the same handful of questions, and they’re the backbone of the Warning Lexicon research that alerting professionals rely on: Who is sending this? What is the hazard? Who does it affect? Where? What should people do? When does this apply?
Miss any one of those, and your community is left guessing instead of acting. In a fast-moving event, that guessing costs time you don’t have.
Message Review Closes The Gap
This is the exact problem Connect Rocket Community’s Message Review feature was built to catch. Message Review is an AI-powered writing assistant that evaluates your draft notification against the same emergency communications research behind the Warning Lexicon, checking that your message clearly conveys source, hazard, impacts, location, guidance, and time before it ever reaches a resident’s phone.
Draft your text message the way you normally would, click Review Message, and Message Review flags what’s missing or unclear — vague status language, an undefined hazard, a dropped location — and suggests revised text that fixes it. If it needs a detail you haven’t provided, like the specific hazard, it drops in a placeholder you can tab through and fill in, rather than guessing or leaving a gap.
It doesn’t stop at text. Because Connect Rocket treats visual messages (text, email) and audio messages (voice calls) as fundamentally different formats, Message Review generates a suggested email with the extra detail that SMS character limits don’t allow, along with a voice script written for how people process spoken information under stress. You can accept the suggestions, edit them, or write your own — Message Review makes recommendations, but you decide what goes out. Every account can also configure a context prompt with organization-specific details, so the suggestions reflect how your agency really operates.
Message Review doesn’t replace judgment. What it catches is the moment where a tired duty officer, working fast, drops “Set status” into a text field and assumes everyone will understand it the way they do. That assumption is where confusing alerts come from, and it’s built to catch it before the message ships.
Your community shouldn’t need to have attended your public education campaign to understand what to do when your alert lands on their phone. Write it so they don’t have to.
