You're sitting in an emergency operations center. Radios crackle. In real terms, phones ring nonstop. In real terms, three different agencies just sent conflicting reports about the same evacuation route. The incident commander needs a decision now — but nobody can agree on what's actually happening on the ground The details matter here..
Sound familiar? This is exactly why NIMS exists. And it's why one specific management characteristic matters more than most people realize.
What Is Information and Intelligence Management
Information and Intelligence Management is the NIMS management characteristic that follows established processes for gathering, analyzing, assessing, sharing, and managing incident-related information and intelligence.
That's the textbook definition. Here's what it actually means in practice.
It's the system that stops the chaos I just described. It's the difference between "I heard the bridge is out" and "Engineering confirmed at 14:23 that the north span has structural damage — here's the photo, here's the alternate route, here's who's been notified."
NIMS breaks this characteristic into a few core pieces:
Established Processes for Gathering
You don't wing this. Still, every agency involved agrees beforehand on how information gets collected. In practice, what format they use. Think about it: who reports what. What the validation steps are. When the fire department sends a situation report, it looks the same whether it's Engine 3 or Engine 47 sending it.
Analysis and Assessment
Raw data isn't intelligence. Someone — usually the Planning Section — has to turn "water level rising" into "projected crest at 0600 tomorrow, 2 feet above 100-year flood stage, impacts these three neighborhoods." That takes established analytical methods, not guesswork Still holds up..
Information Sharing Protocols
This is where most incidents fall apart. Still, information and Intelligence Management defines who gets what, when, and how. Here's the thing — the PIO doesn't learn about the evacuation order from Twitter. The logistics chief doesn't find out about the road closure when his trucks hit the barricade.
Operational Security
Not everything gets shared with everyone. Sensitive law enforcement intelligence. Personal identifiable information. Plus, critical infrastructure vulnerabilities. The characteristic includes processes for handling classified or sensitive data without choking off the flow to people who legitimately need it.
Why It Matters / Why People Care
Here's the thing: every after-action report from every major incident since 9/11 says the same thing. That said, communication failures. Information gaps. Conflicting reports. Duplicated efforts because the left hand didn't know what the right hand was doing.
Information and Intelligence Management is the direct answer to all of it.
The Cost of Getting It Wrong
- Hurricane Katrina: Critical situational awareness didn't reach decision-makers for days. Evacuation orders, resource requests, damage assessments — all moving through broken channels.
- Deepwater Horizon: Multiple command structures, inconsistent data formats, no unified common operating picture for weeks.
- Camp Fire (2018): Alert and warning systems failed partly because information gathering and dissemination processes weren't integrated across agencies.
People die when this characteristic fails. Not metaphorically. Actually Still holds up..
The Payoff When It Works
During the 2020 Midwest derecho, Iowa's emergency management used established information management processes to coordinate across 57 counties. Damage assessments followed a standardized template. Resource requests flowed through a single system. The common operating picture updated every two hours. FEMA later cited it as a model for multi-jurisdictional information management Easy to understand, harder to ignore..
That's not luck. That's doctrine applied Small thing, real impact..
How It Works
The characteristic doesn't operate in isolation. This leads to it's baked into the Incident Command System structure. Here's how it moves through the system Not complicated — just consistent. Worth knowing..
The Planning Section Owns the Process
Technically, the Planning Section Chief is responsible for information and intelligence management. Finance feeds cost data. Operations feeds tactical intel. But everyone feeds it. On top of that, logistics feeds resource status. Liaison feeds agency-specific information.
The Planning Section doesn't just collect — it curates. Day to day, prioritization. Synthesis. Validation. Turning noise into signal.
The Information Cycle
NIMS teaches a continuous cycle. It looks like this in practice:
Collection — Field observers, sensors, agency reports, open source, public reports, 911 calls. All flowing in through established channels using standardized forms (ICS 213, 214, 209, etc.).
Processing — Raw data gets timestamped, geolocated, categorized, and tagged. Duplicate reports get merged. Conflicts get flagged for resolution.
Analysis — Patterns emerge. Trends get projected. Gaps get identified. "We have zero visibility on the east flank" becomes an intelligence requirement, not just a complaint Surprisingly effective..
Dissemination — The right products go to the right people. The Incident Action Plan. The situation report. The briefing map. The PIO talking points. The logistics forecast. Each audience gets what they need in a format they can use.
Feedback — Recipients confirm receipt, ask clarifying questions, report actions taken. The loop closes. Or it should.
Tools That Make It Work
You'll see these in any well-run EOC:
- Common Operating Picture (COP) — A single display (digital or physical) showing the current situation. One map. One timeline. One truth.
- Information Management Plan — Written at the start of the incident. Defines reporting formats, frequencies, distribution lists, security classifications, and archival procedures.
- Standardized Forms — ICS forms aren't bureaucracy. They're interoperability. When everyone uses ICS 214 for activity logs, you can actually read each other's logs.
- Information Exchange Requirements (IERs) — Pre-defined data exchanges between systems. CAD-to-CAD. WebEOC-to-WebEOC. No manual re-entry.
Integration With Other NIMS Characteristics
This characteristic doesn't float alone. It connects directly to:
- Common Terminology — Everyone calls the same thing the same name. "Division A" means the same thing to fire, law, and public works.
- Integrated Communications — The hardware and software that moves the information. Radios, networks, data links.
- Unified Command — Multiple agencies sharing one information picture. No "my data vs. your data."
- Comprehensive Resource Management — You can't track resources without information management. Resource is information.
Common Mistakes / What Most People Get Wrong
I've sat in dozens of EOCs. Consider this: i've reviewed dozens of after-action reports. These mistakes show up every single time Worth knowing..
Treating It As "The Planning Section's Job"
Operations officers who don't report tactical developments because "that's Planning's thing." PIOs who write press releases without checking the current situation report. Logistics chiefs who order resources based on yesterday's forecast That's the part that actually makes a difference..
Information and Intelligence Management is everyone's job. So planning facilitates. Everyone participates.
Confusing Data With Intelligence
A spreadsheet of 911 calls is data. Because of that, a heat map showing call clusters shifting northeast over three hours — with overlay of road closures and shelter locations — is intelligence. Most EOCs drown in data and starve for intelligence Turns out it matters..
The fix: analytical products, not just raw feeds. Someone has to think about what the data means.
Over-Classifying Everything
"Law enforcement sensitive" becomes the default stamp. Suddenly the fire chief can't see the active shooter intel that explains why his crews are being staged three blocks out. The public works director can't see the hazmat plume model because it's "FBI only.
NIMS is clear: classify only what must be classified. Now, share everything else by default. The characteristic includes processes for controlled sharing — not blanket denial That alone is useful..
No Information Management Plan
Incident starts. Planning scrambles to build a plan after the chaos begins. Everyone starts reporting in their own format. By the time it's written, half the incident is over Not complicated — just consistent..
The plan gets written in the first hour. Or it should. Template exists.
— No Information Management Plan — Incident starts. Template exists. Or it should. Planning scrambles to build a plan after the chaos begins. The plan gets written in the first hour. By the time it's written, half the incident is over. Here's the thing — everyone starts reporting in their own format. Fill in the blanks Most people skip this — try not to. Which is the point..
The Path Forward
Information and Intelligence Management isn’t a checkbox; it’s the oxygen that fuels every other NIMS characteristic. Without it, Common Terminology becomes guesswork, Integrated Communications drowns in noise, and Unified Command fractures into silos. The fix isn’t complex: start with the plan. Develop a tailored IAP template that embeds roles, data standards, and analytical priorities before the first radio call. Train teams to treat every shift handoff, every resource request, and every PIO update as a data point in a living system.
Invest in tools that transform raw data into actionable intelligence—heat maps, resource dashboards, predictive models. And above all, cultivate a culture where “information management” isn’t a buzzword but a shared responsibility. Empower frontline responders to contribute insights, not just logs. When every operator understands their role in the information ecosystem, incidents don’t just get managed—they get understood That alone is useful..
The next time you’re in an EOC, ask: Are we swimming in data or diving through intelligence? The answer will tell you if you’ve mastered this characteristic—or if you’re still drowning in the noise.
