When most people think about a 911 call, they think about speed. How fast does it connect? How quickly does someone answer?

But speed on its own doesn’t solve the problem. If a call gets somewhere quickly but lands in the wrong place, nothing is gained. In some cases, things get worse.

That’s the tension NG911 is designed to resolve. Not just faster calls but smarter routing. And it begins with whether the system can trust the location data it receives.

At a practical level, location data in NG911 is checked, formatted, and compared against multiple sources before and during routing. The goal is to make sure the information is reliable enough to get the call where it needs to go.

What actually counts as location data?

It’s broader than most people expect.

We’re not just talking about a street address tied to a landline anymore. Location can come from several places at once including a civic address, GPS coordinates, a mobile device, even the network itself.

Each of those sources tells part of the story, but not always in the same way. Some are precise. Some are incomplete. Some conflict with each other.

Validation is what brings order to that mix. It allows the system to interpret different inputs as one usable, consistent location.

Where does validation happen?

There’s a tendency to imagine validation as a single checkpoint. A quick yes or no before the call moves on.

In reality, it’s more layered than that.

The process begins before the call even enters the NG911 environment. Service providers structure and pass along location data based on what they have available.

From there, Location Information Servers step in, acting as intermediaries that store and translate that data into a form the system can use.

By the time the call is moving through the ESInet, validation is happening again and this time against GIS data that determines where the call should actually go.

Each layer adds context. Each layer reduces uncertainty.

What does the system actually check?

At its core, the system is asking a simple question. Can this location be trusted?

To answer that, it runs through a series of checks. Addresses are standardized so they match expected formats. Data is compared against known records like MSAG and GIS datasets. Coordinates are reviewed to make sure they fall within reasonable geographic boundaries.

And when something doesn’t line up including missing fields or conflicting inputs, the system has to decide what to do next.

All of this happens quickly, often in less time than it takes to describe it. But the outcome shapes everything that follows.

Why GIS plays such a central role

If there’s a backbone to all of this, it’s GIS.

In NG911, GIS isn’t just supporting the system, it’s guiding it. It defines jurisdictional lines, service areas, and ultimately where calls should be routed.

That means even well-formatted location data can lead to the wrong outcome if the GIS data behind it isn’t aligned or up to date. Validation depends on reference points. GIS provides those reference points.

What happens when the data doesn’t hold up?

Not every call arrives with clean, usable location data, and when that happens, the system doesn’t stop. It adapts.

Calls may be routed based on partial information. They may be sent to a broader or default PSAP. And in many cases, the burden shifts to the call taker to fill in the gaps.

These are the moments where system design meets real-world pressure.

Why this matters on the PSAP side

From a PSAP perspective, all of this upstream work shows up in very practical ways. When validation is strong, calls arrive where they should, information is clearer, and decisions can be made faster. When validation isn’t strong, uncertainty creeps in. Calls take longer to process, more questions need to be asked, and the margin for error gets tighter.

So while validation may happen outside the PSAP, its effects are felt inside it.

What this means going forward

There’s a shared responsibility here that’s easy to overlook.

Providers, network operators, and PSAPs are all contributing to the same outcome. Accurate routing depends not just on technology, but on the quality and alignment of the data behind it.

Maintaining GIS accuracy, understanding where breakdowns can occur, and staying coordinated across systems aren’t side tasks. They’re central to how NG911 performs.

The result of quality GIS data means the call gets where it needs to go, which is the only thing that matters.

Contact our experts at Synergem Technologies to discuss where you are in the upgrade to Next Generation 911.