Known limitations
An honest list of what the platform does not currently do well, so you can plan around it rather than discover it mid-assessment.
Where a limitation is being worked on, we have said so without committing to a date. Dates change; the limitation is what matters for your planning today.
Data and coverage
NIBRS events are not rendered on the map
BaseScores for many US locations are powered by NIBRS data, but individual NIBRS incidents are not yet drawn as map events.
The score is valid and accurate — this is a display limitation only. Affects rural US locations and smaller jurisdictions using NIBRS reporting. If you need to show a stakeholder the incidents behind a score at one of these locations, use the Events List rather than the map.
On the roadmap.
International regions without a BaseScore
Africa, the Middle East, Eastern Europe, and most of South Asia have civil unrest coverage but insufficient underlying crime data to produce a BaseScore.
Affected locations show unrest events on the map with no score. Coverage expands as new data sources are added.
Ongoing expansion.
City-level events do not appear on the heat map
Incidents reported only at city or district level have no specific point to plot. They contribute to counts and analytics but cannot be drawn on the map. See Data sources and recency.
Inherent to source data precision — not expected to change.
Platform features
No native side-by-side location comparison
The platform does not currently support a native comparison view across locations.
Workaround: the My Locations dashboard shows scores side by side and sorts by BaseScore or change percentage, which covers most comparison needs. For anything more structured, export to CSV and compare externally.
On the roadmap.
CSV export does not include tags or custom metadata
The CSV export from My Locations includes core location data and scores, but not tags or custom metadata fields.
On the roadmap.
Filter combinations cannot be saved
The dashboard does not support saving custom filter configurations for reuse. Filters need to be reapplied each session.
On the roadmap. Frequently requested.
Threshold alerts and notifications are not generally available
Threshold-based alerts — notify me when a BaseScore rises above a set level — and event notifications are not yet generally available.
If this capability matters to your workflow, tell your CSM. Customer demand is a direct input into prioritization, and this is one where it counts.
On the roadmap.
Route analysis is not yet available
Assessing threat conditions along a travel corridor, rather than at point locations, is not currently supported. Analysis today is location-based.
Workaround: save key points along a route as individual locations and assess them together.
On the roadmap.
BaseScore does not include civil unrest
BaseScore is calculated from crime data. Unrest events are tracked and mapped but do not feed the score, so a location with active unrest and low conventional crime can carry a lower BaseScore than the situation on the ground suggests.
Workaround: read the unrest events directly alongside the score. See the BaseScore scale.
By design, not a defect — but worth knowing before it surprises you.
Historical scores cannot be reviewed
BaseScore is calculated on a trailing window. There is currently no way to look back at what a location scored at an earlier date.
Workaround: if a score matters for a report or a QBR, capture it — with its filter settings — at the time.
On the roadmap.
Things BaseScore is not designed for
Not defects — design boundaries worth knowing:
- Real-time alerting. BaseScore is a trailing index refreshed monthly in most areas. It is not built for same-day incident awareness. See Data sources and recency.
- Arithmetic. The scale is logarithmic. Averaging or subtracting scores does not produce meaningful numbers. See The BaseScore scale.
- Fine-grained cross-region distinctions. Ranking across regions is sound; treating a three-point difference between very different data environments as meaningful is not. See Comparing across regions.
Something not on this list?
If you have hit a limitation that is not documented here, tell your CSM. This page is only useful if it is complete.