A new apartment complex opens. Its street name is on the entrance sign, but the same address appears differently in the county map and the dispatch system. The problem belongs to more than one department. The useful first step is knowing who owns the record and how a correction moves from that owner to the people who need it.
Next Generation 911 (NG911) depends on geographic information system (GIS) data to help route calls to the appropriate answering point. The National 911 Program explains that local addressing and GIS staff, dispatch leadership, and neighboring jurisdictions all have roles in maintaining that data. A map that looks right on a public website does not by itself prove the data used for 911 routing has been corrected.
Start with one contact for each layer
Ask the 911 authority to identify its approved data stewards. The street centerline owner may sit in public works, while the address point owner could be in county GIS or a municipal addressing office. Emergency service boundaries may have separate owners. Record the role, the reporting channel, and a backup contact. Verify the list with the departments named in it rather than assuming the person who distributes a map can edit its source.
| Data to review | Question for the owner |
|---|---|
| Site address points | Who confirms the official address and handles new buildings or address changes? |
| Road centerlines | Who maintains the official name, aliases and address ranges when a road is extended or renamed? |
| Answering-point and service boundaries | Who resolves a mismatch where neighboring jurisdictions meet? |
| Downstream systems | Who confirms when an accepted correction is available in the systems that need it? |
Record a discrepancy so someone can act on it
Use a restricted agency channel. Write down the record ID if available, the value observed, the expected value and its source, the systems where the mismatch appeared, and the date it was found. Include the practical impact, such as “new construction does not appear in the address lookup.” Omit caller names, call recordings and other details that are not needed to correct the record. Keep the issue open until the responsible team verifies the appropriate systems, rather than closing it when an email is sent.
Practice the handoff with a fictional example
Suppose a training record shows “Example Lane” in one system and “Example Court” in another. First, the addressing office confirms the authoritative name. Next, the GIS steward checks the matching road segment and associated address points. The dispatch technology lead then confirms how the correction reaches the appropriate system and how to validate it in an approved environment. If a boundary is affected, involve the neighboring authority before closing the ticket. This is a planning exercise; do not call 911 to test a data change.
Make the review repeatable
Keep a small queue with an owner, status and next review date for each mismatch. Review it when new subdivisions open, streets change, or service boundaries are revised. Check a sample after corrections and keep notes on where the handoff broke down. One confirmed update is more useful than a long list of issues with no assigned owner.
Official reference: National 911 Program GIS tools and checklists. For a related HUB911 guide, read questions to ask before applying for a 911 dispatcher role.