News & intelligence

Person listening to a shortwave radio and taking handwritten notes at a kitchen table during an information-gathering session

In a crisis, information quality can matter as much as food, water, and power. Bad information creates bad decisions: evacuating into danger, ignoring real threats, or wasting scarce resources on rumors. Prepared communities use a deliberate intelligence cycle — collect, verify, prioritize, share, and revise — and the free tools to run it are already available before the first disruption starts.

Information goals

Your information system should answer practical questions quickly:

What happened?
Where is it happening?
How likely is escalation?
What actions are needed in the next 2, 12, and 24 hours?

Avoid collecting information for its own sake. Focus on decision support.

Free monitoring tools

Most of the information you need during an emergency is available at no cost. The challenge is knowing which tools to use and how to layer them.

NOAA Weather Radio All Hazards

National Oceanic and Atmospheric Administration (NOAA) Weather Radio broadcasts continuously on seven VHF frequencies: 162.400, 162.425, 162.450, 162.475, 162.500, 162.525, and 162.550 MHz. It covers all 50 states via more than 1,000 transmitters and broadcasts watches, warnings, and public-safety information around the clock — including non-weather emergencies.

A dedicated NOAA alert radio is the inexpensive, reliable baseline. It activates automatically on emergency alerts without needing internet access, and it runs on batteries when power is out. Find your local transmitter frequency in advance and write it on your communications plan. Do not wait until severe weather starts.

County and municipal alert systems

Most US counties and cities operate an opt-in emergency alert system. The most common platforms are Nixle (text your zip code to 888777 to register), CodeRED (registration via your county's website), and AlertMedia. System names vary by jurisdiction — search "[your county] emergency alerts" to find yours.

These push alerts directly to your phone for evacuations, active incidents, shelter-in-place orders, and public safety events. Registration takes under five minutes and costs nothing. Consider it part of your baseline preparedness, not an optional extra.

Broadcastify scanner feeds

Broadcastify.com aggregates live public safety radio feeds from police, fire, and EMS departments across the US. During a local incident, monitoring the relevant dispatch feed gives you situational awareness 15-30 minutes ahead of social media and local news broadcasts. The service is free for basic listening; a mobile app is available for iOS and Android.

Useful limitations to know: scanner traffic is raw, unfiltered, and uses agency-specific codes and abbreviations. It tells you what responders are doing, not what the broader situation is. Use it as an early-warning signal, not as your primary information source.

Ham radio monitoring

If you have a VHF/UHF capable radio, monitor 146.520 MHz FM — the national 2-meter simplex calling frequency. During regional emergencies, licensed operators coordinate on this frequency and relay information from ARES (Amateur Radio Emergency Service) nets and county emergency management. The 70-centimeter calling frequency is 446.000 MHz FM. Neither requires a license to monitor — only to transmit.

Your area's local repeaters often carry emergency traffic during incidents. Check your county's ARES group for the primary emergency net frequency.

Social platforms are lead indicators, not verdicts. Twitter/X lists, Nextdoor, and local Facebook community groups surface eyewitness reports quickly, but they also amplify unverified claims faster than any other channel. Use social media to identify what to verify, not as a source of confirmed facts.

Social media in a crisis

During the 2017 Hurricane Harvey response, viral social media posts listed addresses of people who needed rescue — but many turned out to be outdated or incorrect, directing responders to locations where the situation had already resolved. Treat social platform reports as leads to investigate, not rescue orders to execute.

Useful discipline: monitor one or two community groups for your immediate area. Avoid chasing national news accounts during a local incident — they lag behind local sources and add noise.

Build layered sources

Never rely on one source. Use a blend of official, local, and observational channels.

Official sources

NOAA Weather Radio (7 frequencies, 162.400–162.550 MHz)
County and municipal emergency alert system (Nixle, CodeRED, or local equivalent)
Utility outage maps and notices
Transportation departments and transit alerts

Local sources

Community groups and neighborhood channels
Trusted local journalists and local broadcast news
Amateur radio nets and local repeaters
Broadcastify feeds for your county's public safety agencies

Direct observation

Reports from known trusted contacts
Visual confirmation from field checks
On-scene updates from your own network

Verification framework

Use a quick reliability triage before sharing or acting on any report.

Source credibility: who is reporting and what is their access to the situation?
Corroboration: is there independent confirmation from an unrelated source?
Specificity: does it include location, time, and concrete details?
Timeliness: is it current or has the situation already changed?
Action relevance: does it actually change what you should do next?

Score each report as:

Confirmed — verified by two independent sources, at least one official
Likely — consistent with other information, one credible source
Unverified — single source, social media, or unknown origin
False/withdrawn — contradicted by better sources or officially retracted

Do not forward unverified high-consequence claims as facts.

The Rule of Two

Never act on a single source, especially social media. If you cannot find the same claim from two independent, unrelated sources, treat it as unconfirmed. For high-stakes decisions — evacuation, shelter-in-place, medical response — require at least one official source (emergency management, law enforcement, or NOAA) as one of the two.

Ask three questions before acting on any report:

Who reported it?
When did they observe it, and what was their proximity?
What evidence do they have?

Field note

Speed is the enemy of accuracy. The most dangerous misinformation during a crisis does not come from bad actors — it comes from well-meaning people who shared something before they checked it. Set a personal rule: no forwarding anything you haven't verified in the last 30 minutes.

Rumor tracking log

Assign one person in your group the role of rumor log keeper. Use a simple table — paper or digital — to track incoming claims:

Time received	Source	Claim	Verified?
14:30	Nextdoor post	Gas leak at Oak/3rd	Pending
15:10	NOAA alert	Tornado warning NW county	Confirmed
15:45	Neighbor (eyewitness)	Road flooded at Route 7	Confirmed

Time received	Action taken	Notes
14:30	Monitoring scanner	Awaiting county alert
15:10	Shelter in place	Expires 16:00
15:45	Route change	She drove it 15 min ago

This reduces repeat confusion — when the same rumor circulates multiple times, the log shows you already investigated it. Update status as claims are confirmed or disproven. At the end of an incident, the log becomes an after-action record.

Create an intelligence board

Maintain one shared board — paper, whiteboard, or digital — with:

Incident summary
Affected zones
Status by category: power, water, transport, security, medical access
Open questions
Next update time

This prevents message sprawl and keeps everyone aligned.

Suggested update cadence:

Active incident: every 2-4 hours
Stabilizing conditions: every 8-12 hours

Intelligence briefing template

For community leaders, a consistent briefing format prevents confusion and reduces the time spent answering repeated questions. Use this at each scheduled update:

SITUATION BRIEFING — [DATE / TIME]

Current situation:
[One paragraph — what is happening right now]

Changes since last update:
[What is new or different from the previous briefing]

Verified threats and status:
[List each active threat — status: active / monitoring / resolved]

Unverified reports (flagged):
[List what is being investigated — do not present as fact]

Recommended actions:
  Next 2 hours:  [immediate actions]
  Next 12 hours: [planning horizon]
  Next 24 hours: [lookahead]

Next briefing time: [exact time]

Keep briefings under five minutes when spoken aloud. Distribute written copies when possible — people under stress do not retain verbal-only information reliably.

Assign information roles

Small groups should designate roles to avoid chaos:

Collector: monitors channels and logs candidate reports
Verifier: checks claims against trusted sources
Synthesizer: creates short situation summaries
Dispatcher: shares updates through agreed channels

Every role needs backup coverage. Use this structure with your leadership framework and communications plan.

Common cognitive traps

Recency bias

The newest report is not always the best report. Check quality and sourcing, not just timestamp.

Confirmation bias

People overweight claims that fit their expectations. Actively seek disconfirming evidence — especially before making resource-intensive decisions.

Emotional amplification

Fear and anger spread faster than facts. Keep updates factual, time-stamped, and calm. Groups that hear panicked updates make panicked decisions.

Information overload

More channels do not guarantee better decisions. Curate sources. A team monitoring three reliable channels makes better decisions than a team drowning in fifteen unreliable ones.

Field note

During real incidents, the biggest accuracy improvements come from turning off sources, not adding them. Pick your three best channels — NOAA, county alert system, and one local source — and mute the rest until conditions stabilize.

Share what people need, not everything you know.

Avoid publishing:

Specific household vulnerabilities
Exact supply caches or movement plans
Personal medical details
Names attached to sensitive risk reports without consent

Use aggregate phrasing when possible: "Three homes on east block need water support" rather than individual addresses in open channels.

24-hour incident cycle template

00:00 Collect and verify updates from core sources
02:00 Publish short situation snapshot
06:00 Re-check high-risk indicators
08:00 Publish action update (what to do today)
12:00 Verify rumors and revise board
16:00 Publish afternoon status
20:00 Publish overnight guidance and next check time

Adjust cadence to event severity.

Practical checklist

Prepared communities win by making better decisions faster. Combine this workflow with weather monitoring and your communications plan to keep information flowing when normal systems fail. For monitoring beyond line of sight, ham radio and General Mobile Radio Service (GMRS) extend your reach when cell networks are congested or down.