CityIntel — Platform Overview

What you get

Live feed + incident drilldownsReal-time items with context, sources, and time-windowed relevance filtering.

Alerts & forecastsStructured protests/events data, risk tiers, and upcoming windows for planning.

Asset & traveller exposureOptional inputs to understand “who/what is near” and to prioritise response.

Panic AlarmA simple activation flow for staff; supports shared use via invite code (no bulk logins required).

Best-fit use cases Corporate security & GSOC dashboards, duty-of-care monitoring, event risk planning, executive travel support, and incident comms triage.

Quick navigation

How it works Data & coverage Panic Alarm Onboarding checklist Privacy & security Next steps

How it works

CityIntel surfaces items across a live feed and structured alerts. Items are grouped and de-duplicated to reduce noise. Filtering focuses on incident-likely content and keeps relevance scoped to a time window (e.g. last 6–24 hours).

Signal first: prioritise disruption, protest activity, transport impacts, violence, evacuations, closures.
Context next: show related items, locations, and (optional) nearby assets/travellers.
Action last: analysts can escalate, brief, and share links or reports.

Data & coverage

CityIntel combines curated event/alert inputs with live-source monitoring. Coverage varies by region and source availability. Where needed, organisations can add local sources for improved fidelity.

Alerts dataset: structured protest windows, risk levels, city grouping and short analyst blurbs.
Live news: time-windowed ingestion, dedupe, and incident-likelihood scoring.
Organisation context (optional): assets, travellers, and internal notes to drive prioritisation.

If you have specific coverage needs (countries/cities/sites), we can tune sources and filters.

Panic Alarm

The Panic Alarm provides a fast, low-friction way for staff to request help. It supports two modes:

Logged-in staff: no invite code needed, activation is tied to the user profile.
Shared/mobile use: staff enter an invite code + name, enabling activation without issuing many logins.

On activation, the dashboard can display a global banner and responders can open the Panic page to see details.

Onboarding checklist

Confirm org name + admin users.
Add key locations (HQ, sites, high-value venues) into Assets (optional).
Add travellers or travel policy scope (optional).
Choose alert window defaults (24h / 7d) and risk threshold definitions.
Set Panic Alarm invite code (and who should respond).

Privacy & security

CityIntel is designed for operational awareness. Keep messages brief and avoid highly sensitive personal data. Suggested practice: store only what responders need in the moment.

Least sensitive by default: the Panic flow can store location as text-only (no precise coordinates).
Role gating: admin-only areas (analytics/ops) are separated from general user views.
Audit readiness: options for event logging and organisational controls can be enabled as needed.

Next steps

Agree coverage scope and who will use the platform.
Set up your organisation configuration + invite codes.
Optional: add your assets/travellers for exposure prioritisation.
Schedule a short walkthrough and define escalation workflows.

Contact: CityIntel • Provide your preferred email/phone in this section for client versions.

What each page does

A quick breakdown of the main areas your team will use day‑to‑day.

Dashboard

Global Risk & Live Exposure summary bar (high/med/low counts “now”).
Risk shading for a longer window (currently built around ~6 months of historical signals).
Quick access to Manage assets and Manage travellers.

Assets

Maintain offices/sites with coordinates and metadata.
Assets are checked against incidents to flag potential exposure.

Travellers

Maintain traveller locations / itineraries (hotel, city, dates where available).
Travellers are overlaid on the map and matched to incidents by proximity.

Alerts

Newest alert stream for fast triage.
Includes protest / unrest‑type items as well as disruptions (transport, public safety, etc.).
Designed around a rolling history (often 1–2+ months depending on source/window).

Events

Higher‑level event tracking, timelines, and “what changed since last update”.
Useful for longer incidents (multi‑day protests, escalating disruptions, repeat alerts).

Live Feed / Test Page (development)

Real‑time feeds by city/region with click‑to‑open incident detail panel.
Map centres on the incident city and overlays nearby assets/travellers (when configured).
You can add/remove feeds instantly and test with mock feeds to preview the final experience.

Intelligence Brief

Structured analytical reporting (not a live alert stream).
Regional situation summaries, escalation outlooks, security forecasts and operational advisories (where enabled).

Reports

Export and reporting views (PDF/CSV-style outputs where enabled).
Typically used for sharing with stakeholders and audit packs.

Trends & Forecasts

Longer‑window patterns for planning (risk trends by geography/category).
Supports decisions like route changes, staffing advisories, and asset protection.

Sources

Where data providers and source settings are configured (where enabled).
Used to control coverage, filters, and which feeds appear across the platform.