Your Board Asked If You’re Ready for NG9-1-1. Here’s What to Tell Them.

  • Home
  • Newsletters
  • Your Board Asked If You’re Ready for NG9-1-1. Here’s What to Tell Them.
DateNov 3, 2026

By Brian Brady, COO and VP of Business Development, Gistic Research, Inc.

Sooner or later, someone on the board asks:

“Are we ready for NG9-1-1?”

It might be a county commissioner, the 911 board chair, or a city manager reviewing next year’s budget.

Whatever the setting, there’s usually one number within reach: the compliance percentage from the latest validation report.

“We’re at 82 percent.”

That sounds like an answer. It isn’t.

The board can’t tell whether 82 percent is good or bad, whether things are improving, or what it’ll take to finish.

In “Reading Your NGCS GIS Discrepancy Report,” I explained why that percentage can mislead the people working with the data.

This article is for the people reporting the results and the people deciding what to do next.

The Four Questions Your Board Is Really Asking

When someone asks if you’re ready, they’re usually asking four things:

  1. Will calls reach the right place?
  2. Do we line up with our neighbors?
  3. When do we have to be done, and are we on track?
  4. Once we get there, can we keep it that way?

Each question deserves a plain answer. None can be answered by a percentage alone.

1. Will Calls Reach the Right Place?

In NG9-1-1, GIS data helps validate caller locations and determine which answering point and responders are responsible.

The map isn’t just a picture of the system anymore. It’s part of the system.

Focus your report on the layers that matter to call delivery:

  • Provisioning boundary
  • PSAP and emergency service boundaries (law, fire, EMS)
  • Road centerlines and address ranges
  • Site/structure address points

For each layer, give the board three facts:

Is it clean? What’s left? Who owns the fix?

For example:

“PSAP boundary: clean. Fire boundaries: two gaps along the county line. Fix agreed with the fire district; due in March.”

That’s a status update the board can act on.

For more on what specific errors mean at cutover, see my earlier article, “At Cutover.”

2. Do We Line Up With Our Neighbors?

This is the question many status reports skip.

Your data can pass every local check and still fail where it meets the county next door.

Misaligned boundaries can create gaps no one covers or overlaps claimed by two agencies.

Tell the board:

  • Which shared boundaries have been reviewed?
  • Which have been agreed upon?
  • Which still need attention?
  • Are neighboring agencies participating?

If a neighbor isn’t participating, say so.

That’s a governance problem, and it’s exactly where a board or state office can help.

3. When Do We Have to Be Done, and Are We on Track?

Boards understand deadlines.

Give them the real one: when your state 9-1-1 program or core services provider expects provisioned data, not an optimistic internal target.

If your state hasn’t set a date, explain the deadline you’ve committed to.

Then show the critical path.

In my experience, GIS is often on it. Network and call-handling equipment can be ready while everyone still waits for the data.

A useful status report might say:

“State target: June. Boundaries on track for January and centerlines for April, leaving eight weeks of margin.”

If there’s no margin, that’s what the board most needs to hear.

4. Once We Get There, Can We Keep It That Way?

NG9-1-1 GIS isn’t a one-time cleanup.

New addresses, renamed roads, and annexations keep changing the map. Those changes need to reach live data in days, not months.

Make the ongoing workload visible.

The board should know:

  • Who’s responsible for maintaining the data after compliance?
  • How many staff hours does maintenance take each week?
  • What happens when that person leaves?
  • Which tools does the team depend on?

If the answer is “one person, working around other duties, with tools that weren’t built for this,” the board should hear it before there’s a crisis.

NG9-1-1 readiness isn’t just about reaching compliance. It’s about staying there.

A One-Page Board Report That Works

Here’s the format I’d take into a board meeting:

1. Deadline

State provisioning target, time remaining, what compliance means, and the consequences of delay.

2. Call-Critical Layers

Status, remaining issues, responsible person, and target completion date for each layer.

3. Shared Boundaries

Each neighboring agency and whether the common boundary has been reviewed and agreed upon.

4. Progress Trend

Are open issues declining? At what rate?

A small chart showing progress over time tells a better story than a single compliance score.

5. Ongoing Maintenance

Who’s responsible for keeping the data current, and how much effort will it take?

6. The Ask

What specific budget, staff time, or outside support does the board need to approve?

Notice what’s missing: the stand-alone 82 percent.

If the board wants a score, show its trend alongside the status of the call-critical layers.

Without that context, a percentage can mislead in either direction.

Be Specific About What You Need

Most boards are deciding among three approaches.

Option 1: Keep It In-House

Fund the staff time and tools needed to manage standards and ongoing maintenance.

Option 2: Bring In Help

Use a qualified GIS integrator to do the heavy lifting while your agency retains control of its data and visibility into the work.

Option 3: Use a Hybrid Approach

Bring in outside expertise to reach compliance, then transition ongoing maintenance to internal staff.

Whatever you propose, connect it to a funding path.

Many states have NG9-1-1 GIS grant programs, and software or maintenance may be allowable expenses.

I’ve covered Florida’s 911 grant program in an earlier article. Your state 9-1-1 office can confirm what’s eligible locally.

In an upcoming article, I’ll explain how a West Virginia county pursued outside help without giving up control of its data.

Where GIVE Fits

I’ll keep this brief because this article is about the conversation with your board, not a software pitch.

GIVE (Geospatial Integration, Validation, and Editing) is designed to make GIS readiness visible without rebuilding a report before every meeting.

With GIVE:

  • Errors are flagged during editing, rather than waiting for the next validation cycle.
  • Open issues are organized in one place, making it easier to understand what remains.
  • Changes are recorded, including what changed and who made the edit.
  • Neighboring agencies can collaborate in one environment to resolve shared boundary issues.

Instead of reconstructing your GIS readiness status every time someone asks, you have a current picture of the work.

That’s how you turn “we’re at 82 percent” into an answer a board can actually use.

Have a Board Meeting Coming Up?

If you’d like help turning your current GIS status into a board-ready report, send it over.

Where feasible, we can run a baseline validation of your data and prepare a one-page summary designed for a board audience.

The board’s question is fair.

They deserve an answer they can act on.

#NG911 #GIS #PublicSafety #LocalGovernment #911

Brian Brady is COO and VP of Business Development at Gistic Research, Inc. Gistic has developed collaborative GIS and data-quality solutions for public agencies since 2005. Brian writes about NG9-1-1 GIS standards, data quality, collaboration, and the practical transition from legacy workflows to continuously maintained NG9-1-1 environments.

Add a Comment