Skip to content

Coverage

This page explains how coverage works, not which cities are covered

A published city list goes stale the moment coverage expands, and a stale coverage list is worse than none — it tells you a location is covered when it isn't. The platform itself is the live answer. This page shows you how to read it, and What's New records expansions as they happen.

How to check whether a location is covered

The fastest check is to add the location and look at it.

  1. Search the address or drop a pin (Adding a location)
  2. Look at whether a BaseScore comes back in the analytic panel

What you see tells you the coverage state:

What you see What it means
A score Covered.
A score, but a blank map Usually covered — see When a location has no score
NA or no score Not covered at that point, or just outside a covered boundary

For a whole portfolio at once, the My Locations dashboard shows the BaseScore for every saved site in one view. Sort by BaseScore and any site returning NA sorts together — that is your coverage gap list, always current, with no document to maintain.

How coverage is structured

Coverage is not a single global switch. It varies along two axes.

Geographic extent. In the United States, coverage is comprehensive, built on law enforcement reporting including NIBRS and local police feeds. Internationally, coverage is city-based rather than nationwide — a country is not "covered" or "uncovered" as a whole. Major metropolitan areas are covered first, with surrounding regions following as source data becomes available.

Data depth. A covered city does not necessarily carry every threat category. Some international cities have deep multi-category coverage; others carry a narrower set of threat types because fewer reliable sources publish there. This is why two covered locations can support different levels of analysis.

To see what is actually feeding a specific location, open the Data Source module in the analytic panel. It shows which sources contribute to that location — the direct answer to "how much confidence should I place in this?"

Why a location near a covered city may still not be covered

Coverage follows the reporting boundaries of the source data, not a radius around a city center. A site in a suburb or outlying area can fall outside the boundary of the nearest covered metro even when the metro itself is well covered.

If that describes one of your sites, tell your Customer Success Manager. Site-level gaps in a covered region are the most common expansion request and the easiest to act on.

Requesting coverage

Coverage expansion is driven substantially by customer demand. If you need a location that is not covered:

  1. Send the list to your Customer Success Manager — full addresses or coordinates
  2. Include the business context: why the location matters, and what decision the data would inform

Named, specific requests with a use case attached are what get prioritized. "More coverage in Asia" is not actionable; "these six sites in Kuala Lumpur, Warsaw, and Jakarta, for a 2027 expansion review" is.

When coverage expands

New coverage is announced in What's New, dated, with the regions named. That record is additive — it never goes stale the way a master list does. Check there for the current expansion history, and your CSM will flag expansions that affect your specific portfolio.