Recorded incidents and confirmed fatalities by month.
Event forms by share of recorded activity.
Attributable perpetrator categories.
State and territory distribution.
GENNISCAPE is delivered across three service tiers. Your organization's current tier provides the views shown above; the analysis you requested is included at a higher tier.
Pricing is not publicly advertised and is set per engagement. Please contact your account manager to discuss the tier appropriate to your operating footprint.
Click the map to place it.
Inactive areas are kept but no longer match.
A rule fires when a released incident falls inside its area and meets every threshold set. Leave a threshold blank to ignore it.
None selected means any category.
None selected means any actor.
Rejecting keeps the item with its decision; deleting removes it. Delete a duplicate or a mis-typed entry — reject something a person judged unsuitable.
An analyst entry is report grade on submission, because a person is vouching for it. Automated items enter as unverified and need promoting.
The new account can sign in immediately. Passwords are stored hashed and cannot be read back.
Type decides whether the organization ever sees row-level records; tier decides how deep its reporting goes.
What each role is permitted to do. Defined in backend/src/roles.js, documented in
ACCESS_MODEL.md, and asserted against that document by the test suite — so it is shown
here rather than edited here. Changing it is a code change and a review.
What each tier includes, cumulatively. Role and tier are both necessary and neither is sufficient.
Resolved server-side from organization type and tier. Note that every client tier resolves below
internal: the event-level annex reaches internal organizations only.