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.
Goes to our analysts, not to the platform. Nothing you send here is published to the incident record and nothing identifies you to other subscribers. Where it is worth pursuing we task our own collectors to confirm it independently.
| Name | |
|---|---|
| Role | |
| Organization |
Invitations, password resets and delivery problems are always sent.
At least 12 characters. You are not signed out of other devices.
What your organization holds, in plain language. Read-only — your account manager changes these.
Click a cell to switch a pane on or off for that seat. You can only narrow what your organization holds — a pane your entitlement does not back cannot be switched on, and the menu is all this changes: every request is still answered from the entitlement.
Pricing is not publicly advertised. Your account manager confirms terms.
One point is roughly six analyst hours. A single-location request is one point; a multi-location or thematic assessment is two; a commissioned deep-dive is four. Unused points carry over; each point expires twelve months after issue; points have no cash value and are not refundable.
We confirm and invoice off-platform; the points appear here once granted.
Every report released to your organization, permanently. Open one to read it; the digest lets you verify the file you hold.
You will have a turnaround and a point cost within one business day. Nothing is charged until you accept the quote, and a request can be withdrawn at no cost before that.
Something that happened to you or that you saw. This goes to our analysts and informs our reporting; it is never published as a record and nothing here enters the incident dataset. Tell us what must be left out and we will honour it.
Grant an annual allotment or write an off-platform purchase into an organization's ledger. Every point is good for twelve months from today.
A short branded PDF on a single incident, delivered to every tier without points. Choose the territory and it goes to every organization whose entitlement covers it, or name a subset. A public variant is uploaded separately and is refused unless it carries no client name and no reference to the data owner.
Every deliverable released, with the request, the analyst and the hours logged.
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 organization actually holds. A seat inherits its organization's entitlements and never more — an organization with no grant for a service cannot see that the service exists. Every write here is logged against your seat.
Scope is what geography the grant covers. Tier applies to the data service only.
How finely this organization sees incident positions on the dashboard map and in its memoranda. Regional snaps each incident to the district grid and is every subscription tier's value. Exact is the coded coordinates — a per-organization grant, never a tier, and logged when given. None withholds the map.
What this organization may take out of the platform, and in what shape. An organization with no licence exports nothing. Coded emits one row per incident with the coded fields only; aggregate emits counts and no rows; full includes the narrative and coder notes, which are the part nobody can reproduce. Regional geography replaces coordinates with the territory mean — the same cap the dashboard and the situation map apply.
The effective answer for every capability, per role, in one organization — and the place to change it. Click a cell to cycle it: inherit (the role/tier baseline) → allow → deny. The org-wide column applies to every seat in the organization; a role column beats it. Rows marked ⚠ cross the raw-record boundary — overriding them widens what this organization can see, and the write is audited under its own action. Every change takes effect on the organization’s next request.
What each role is permitted to do by default. Defined in backend/src/roles.js,
documented in ACCESS_MODEL.md, and asserted against that document by the test
suite. Departures from it are made per organization in Access control above, not by
editing the baseline.
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.
A data licence is a service line, not a tier: an organization holding it pulls the coded record by API on the terms set on its entitlement. A key is shown once and stored only as a digest — a lost key is replaced, never recovered. Revoking one takes effect on the next call. A licensed pull never carries coder notes, QC metadata or collector-revealing fields, whatever the terms say.
What each source is worth in the news column. Weight is 0 to 100 and multiplies with recency to set the order; grade is Admiralty-style reliability, shown on every item so a reader can weigh it. What sources exist is fixed in the platform; how far we trust them is yours. Turning one off removes its items from the column.