By Dustin Barre, ServiceNow CMA and Senior Director of ServiceNow Solutions at iTech AG
There’s been a lot of conversation lately about Emergency Event Management on ServiceNow, and rightfully so. The ability to detect an event, correlate signals from multiple systems, and activate a response plan is a massive step forward from the clipboard-and-radio-call approach that still runs a lot of emergency operations today.
But here’s the question that doesn’t get enough attention: what happens after the plan activates?
Knowing there’s an emergency is one thing. Getting the right people to the right place, with the right information, carrying the right equipment, following the right protocols. That’s where the real complexity lives. And that’s where most organizations still have gaps.
The Activation Gap
For example, an organization has a solid detection layer. Alerts come in. A response plan exists. But the moment it moves from “we know there’s a problem” to “we need boots on the ground,” things start to break down.
Who’s available? What crew has the right certifications? What are they walking into? What kind of PPE do they need? What equipment should be on the truck?
In a lot of organizations, those answers live in someone’s head. Or in a spreadsheet. Or in a system that the dispatcher doesn’t have access to in the moment. So the crew gets dispatched with incomplete information and figures it out when they arrive.
In a routine maintenance scenario, that’s an inconvenience. In an emergency, that’s a safety risk.
It’s Not Just About the Emergency. It’s About the Response.
This is where the conversation needs to shift. Emergency management and emergency response are two different things, and the gap between them is where risk lives.
Management is about knowing what happened. Detection, correlation, notification, plan activation. Response is about what you do about it. Dispatch, field execution, safety compliance, documentation. Most platforms focus on the first half. iTech AG built our offering around the second.
The key insight is this: the type of emergency determines the response, and the assets at the location determine what that response actually requires. When those two things are connected in the platform, the crew doesn’t show up guessing. They show up prepared.
Mapping Assets to Response Requirements
Let’s make this concrete. Take a hazardous material spill.
OSHA’s HAZWOPER standard defines four levels of PPE protection, Level A through D, and the difference between them isn’t cosmetic. Level A means a fully encapsulating vapor-tight suit with a self-contained breathing apparatus worn inside it. Level D means a standard work uniform. Sending a crew in Level D gear to a situation that requires Level A isn’t a minor mistake. It’s a life-threatening one.
The right level depends entirely on what spilled. An acid requires chemically neutralizing absorbents and vapor-tight protection. A solvent requires polypropylene absorbents and organic vapor cartridges. A biological agent requires biohazard-rated containment and disinfection protocols. Each one also demands different monitoring instruments. Multi-gas detectors, photoionization detectors, pH meters, and sometimes radiation survey equipment, all depending on the material involved.
When the asset record at that location already identifies the hazardous material type (corrosive, flammable, biological, radiological) the work order carries that context from the moment it’s created. The dispatcher doesn’t make a phone call. The crew doesn’t consult a binder. The PPE level, the spill kit type, the monitoring instruments, and the decontamination protocol are all driven by the hazard profile that’s already in the system.
No guesswork. No radio calls asking “what are we walking into?” The work order already knows.
The Pattern Scales
Hazmat is the most visceral example, but the principle applies to every type of emergency. The specific assets and data points change. The architecture doesn’t.
A structural collapse requires entirely different response context. Material type, load ratings, inspection history, age. Is it aging concrete? Steel under stress? Timber compromised by moisture? That determines what shoring equipment the crew brings, what secondary collapse risks they monitor for, and what PPE they need beyond standard construction gear. And the critical question in any collapse isn’t just “what fell.” It’s “what else is about to?”
A flood or storm flips from response to triage. Crews need to know what’s at each location and how critical it is. Life safety systems first. Utility infrastructure second. Data and communications third. And if the floodwater is contaminated, the entire PPE and containment profile escalates.
An electrical or industrial fire depends on what’s burning. A Class B flammable liquid fire requires foam. A Class C electrical fire requires non-conductive agents and de-energizing the equipment first. A Class D combustible metals fire requires specialized dry powder because water or standard chemicals can cause a violent reaction. The asset record tells the crew which one they’re walking into.
A critical asset failure like a generator going down may not look like an emergency, but the cascading impact can be just as severe. The fire pump loses backup. Elevator recall fails. Refrigeration goes down. Sump pumps stop and flooding starts. The response depends on understanding system dependencies and knowing what’s downstream of the failure.
In every case, the quality of the response is determined by the quality of the asset data behind it.
Bringing the Data In
Here’s the practical reality: most of this data already exists. It’s just not in ServiceNow.
Facility and infrastructure assets like bridges, walkways, parking structures, and utility corridors live in GIS platforms like Esri ArcGIS, which carry geospatial data, condition scores, and inspection history. EAM systems like IBM Maximo manage structural maintenance lifecycles and condition assessments. Building management systems track HVAC, electrical, fire suppression, and critical building infrastructure. Specialized platforms like Bentley AssetWise manage bridge inspection data with material types, load ratings, and condition indices.
The opportunity isn’t rebuilding all of that in ServiceNow. It’s integrating it. When that data flows into the CMDB and is mapped to locations, every emergency request that comes in carries the context those systems already hold. The dispatcher sees it. The work order carries it. The crew arrives with it.
That’s what turns a generic dispatch into an informed, equipped, safety-conscious response.
How We Built This on ServiceNow
Our Emergency Response offering ties this together across the full lifecycle.
It starts with the asset and location model. Hazardous material profiles, facility data, criticality ratings, system dependencies, all mapped in the CMDB and enriched through integration with the systems that already track them.
When an emergency request comes in, the platform already knows what’s at that location. The work order isn’t a blank ticket. It’s a context-rich dispatch package.
The dispatcher sees the full picture. Territory planner shows where crews and assets are. The dispatcher workspace shows who’s available, who has the right skills and certifications, and where the emergency is relative to available resources. Auto-assignment and dynamic scheduling handle the matching. The dispatcher confirms and dispatches. The hard work of identifying the right crew is already done.
The crew arrives prepared. On the Now Agent mobile app, the crew leader has the full work order with hazard context, location details, and everything the team needs. If they’re heading to a remote site with spotty connectivity, they cache the data and work offline. They launch a structured assessment that captures on-site conditions in a standardized format. Guided playbooks walk them through the response protocol step by step, ensuring consistency and compliance regardless of who’s running the crew that day.
Documentation builds itself. When the work is complete, the recap document consolidates time worked, assessment results, hazard details, and sign-off. That’s not a report someone writes after the fact. It’s a compliance-ready record built in real time by the people who were actually on scene.
Leadership has real-time visibility. SLAs, task priority, crew utilization, resolution trends, all visible from a manager workspace. Not in a follow-up meeting three days later. Right now.
The Bigger Picture
There’s been strong work across the ServiceNow ecosystem around Emergency Event Management architecture, and the focus on breaking down fragmentation between systems is the right conversation to be having. But the lifecycle doesn’t end at activation. It ends when the crew has resolved the incident safely, with the right equipment, following the right protocols, and the documentation proves it.