Plan, brief, and monitor travel with an AI-powered workspace that finds emergency facilities, assesses risk per leg, and generates intelligence dossiers.
01 · Plan
One planning surface: AI chat on the left, the live itinerary building on the right, operator assignment and activation beside it, the risk picture underneath. Talk through the trip — by keyboard or voice, with a live transcript — and the conversation turns natural language into a structured itinerary, surfacing emergency-facility results and intelligence products inline as you go.
Prefer control? Switch to manual entry and build the same itinerary segment by segment — flights, accommodation, ground transport — with an operator assignable on every segment and timezones resolved per leg.
Two advisors to Nairobi, 16 to 21 July — flying from London, meetings in the CBD.
Itinerary parsed — 2 segments, 1 stay. Assign operators below.
Itinerary
Your travel plan will appear here as we build it
Flight - LHR to NBO
Kenya Airways KQ101 | 16 Jul, 10:05
Operator assigned
Sentrim Boulevard
Nairobi, Kenya | Check-in: 16 Jul 2026 | Check-out: 21 Jul 2026
Draft saved
However the trip arrives — spoken, typed, or as a booking PDF — it lands in the same structured, assignable itinerary.
Upload a booking PDF and build the mission from it — the itinerary lands in the same structured plan as a typed or spoken brief.
Draft missions persist with autosave — a status chip shows the save state, and the drafts list brings you straight back to where planning stopped.
Every travel-risk AI route enforces authentication, MFA, seat licensing, origin validation, and per-user rate limits — with sanitized errors.
02 · Assess
The AI assesses the full itinerary and streams the work live — agent progress first, then the synthesis as it is written. Every assessment is tied to the exact version of the itinerary it was written for — edit the plan and a freshness check asks whether the stored assessment still holds. The interface never guesses.
Then it stays on watch: when breaking events land for any country on the mission, a banner prompts a re-assessment — mid-planning or mid-mission. Route security analysis and a comprehensive AI travel dossier round out the intelligence package before anyone boards.
Risk Assessment — Streamed Live
Itinerary Fingerprint
Anchored to the mission itinerary itself — edit the plan and the fingerprint changes with it.
Assessment
High (72/100)Recommended check-in cadence pre-fills the mission: Every 6 Hours
Freshness Check
Is this assessment still current for the itinerary as edited? Asked, answered — never assumed.
Risk Change
Re-assessBreaking events in a mission country raise the prompt — mid-planning or mid-mission.
Six facility categories returned by GIS lookups — each result carries its distance, bearing, and coordinates, ready to focus on the map or push to the field.
Hospitals
Police
Embassies
Airports
Border Crossings
Assembly Points
Aga Khan University Hospital
Hospital · Aga Khan Health Services
Distance
2.4 km / 1.5 mi
Bearing
NE · 052°
Coordinates
-1.2622, 36.8172
Send to operator. Push a hospital, RV, or evacuation point to a field operator as a chat location pin — stripped to label and point before it leaves.
03 · Monitor
Active, overdue, and emergency missions in one live view — each with a countdown, a status chip, and the full check-in and SOS picture one click away, kept current in real time. This is the mission page behind it.
Trip Overview
Destination
Nairobi, Kenya
Countries
Kenya
Dates
16 Jul 2026 — 21 Jul 2026
Duration
6 days
Mission Team (2)
Travellers (1)
A. Hassan (GBR)
Itinerary (2 legs)
Leg 1 — Flight
MediumKenya Airways KQ101
London
LHR
16 Jul, 10:05 GMT+1
Nairobi
NBO
16 Jul, 20:50 GMT+3
Leg 2 — Road
HighEscorted transfer
Nairobi
NBO
16 Jul, 21:30 GMT+3
Nairobi CBD
Hotel
16 Jul, 22:15 GMT+3
Check-ins (25)
Needs attention (1)
M. Reyes
Operator17 Jul, 06:00 GMT+3
MissedAwaiting response (1)
A. Hassan
Traveller17 Jul, 12:00 GMT+3
SentNext check-in (2)
J. Okafor
Operator17 Jul, 18:00 GMT+3
PendingA. Hassan
Traveller17 Jul, 18:00 GMT+3
PendingEscalation Chain
Step 1
Traveller · Push / In-app
Step 2
Mission owner + Admins · Push / In-app / Email
Step 3
On-call roster · Push / In-app / Email
Effective ladder — trip override → org default
Live countdown and status chip on every active mission
Lifecycle timeline records every transition — timestamp, from → to, human or system actor, reason
Impact preview before complete or cancel — linked alert rules, zones, check-ins, debrief. A failure can never render as zero impact
Cadence is yours — every hour, twice daily, once daily, every six hours, or a custom schedule, with daily slots at the traveller's local time — and the default is pre-filled from the risk assessment's recommendation. "Missed" is never an opinion: a check-in is marked missed the moment it stays unresolved past its hard deadline, and response times are captured.
Separate ladders run for check-ins and SOS. Each step fires on its configured interval to the audiences you choose — the traveller, admins, the on-call roster, the mission owner, the mission team — over push, in-app, and email. Overrides resolve per mission before the org default, edits are conflict-checked, and the mission page shows the effective ladder that will actually run.
A duty officer can acknowledge a missed check-in with an attributed timestamp and note — an audit record that does not stop the ladder.
Draw the operational area straight onto the live basemap — polygon or rectangle. Threat intelligence inside a live zone is delivered to the mission's travellers; operator entry and exit is monitored against it. Auto zones cover each destination country and are always on.
Mission Zones
+ New zoneKenya
Auto — KEN + 25 km buffer, always on
Nairobi CBD perimeter
Mission zone
04 · Field
Assign licensed Operator-app users to the mission — with active-trip conflicts surfaced before you double-book anyone. In the field, the Operator app carries the parsed itinerary, the risk assessment, the dossier briefing, the check-in schedule, and the emergency facilities.
Responding is one tap — Safe or SOS — with device location captured automatically, reachable from the push notification, the trip screen, or a deep link. Offline, the response queues and the outcome on screen stays honest.
Travellers without the app are covered too: a branded web brief gated by a single-use access code. Re-sending revokes the prior link and issues a fresh one — and delivery status is tracked per recipient, failures included.
Scheduled Check-in
Mission — Nairobi · 17 Jul, 12:00 GMT+3
Device location attached automatically. Poor signal? The response queues — and the screen tells you so.
SOS, End to End
Traveller Briefs
A. Hassan
Web brief · access code required
DeliveredK. Mwangi
FailedFailures surface honestly — re-send revokes the old link and issues a fresh code.
05 · Debrief
On completion or archive, the mission produces a versioned debrief artifact. Read it in place, download the PDF, regenerate a new version, send it to the traveller or share it by link — and flag anything that needs a second look.
0
Emergency facility categories, GIS-validated
0
Check-in cadence options
0s
Press-and-hold to arm SOS — accidental triggers designed out
0
Seconds of SOS audio evidence (up to)
plan · assess · monitor · respond · debrief
AI-planned missions, itinerary-anchored risk assessments, scheduled check-ins with an escalation ladder behind every silence, and a field app built for the worst day. One workspace, from first draft to debrief.