TourRecap Office
Live Departures
The office console for the operating day: every active departure, ranked attention with clear ownership, and the evidence behind every operating condition.
Live Departures — development build · illustrative fixture data
Portfolio Awareness
What is operating, and where
Today's active departure portfolio on one screen: counts by condition, positions on the map, and every departure's stage.
Live Departures — development build · illustrative fixture data
The whole operating day
Ten departures across three continents read at a glance — without opening ten group chats.
Last verified field position
Each departure shows where it last verifiably was, reported through the work the crew is already doing — not through tracking people.
Attention Routing
What deserves intervention — and who owns it
Exceptions rank themselves in the Needs Attention rail; office actions carry an owner, a due time, and a consequence.
Acknowledging a signal, assigning the action, and asking the guide all happen in the console — and every step lands on the record with a name and a timestamp.
Live Departures — development build · illustrative fixture data
Evidence Drill-Down
What explains the operating condition
Attention and critical conditions expose their supporting signals and the office's response where present; a gray departure explains its stale or missing data honestly.
Live Departures — development build · illustrative fixture data
Signal to response
The ferry cancellation, the office's question to the guide, the chartered replacement — one linked thread from field signal to resolution.
History that stays
Resolved actions and acknowledgements remain on the day's record; closeout starts from what actually happened.
The Selected Departure
One departure, in operating depth
Stage progress, field freshness, open actions, and the day's evidence for whichever departure the office selects.
Live Departures — development build · illustrative fixture data
Truthful Status
Four conditions, told honestly
The console's job is to be believed. Status colors mean one thing each — and no data is reported as no data.
Status and field freshness are separate dimensions: a departure can be delayed in reporting yet still normal, and delayed freshness does not by itself change the status code.
Operating substantially as planned — no attention, critical, or unknown condition. No office action is called for.
A field signal is waiting on the office — behind plan, a cancelled connection, a question from the crew.
Something consequential needs the office now, with an active office response expected.
Field data is stale or no report has been received; the current state is unknown. Gray is never dressed up as normal.
Live Departures — development build · illustrative fixture data
Live Departures — development build · illustrative fixture data
Location, Stated Carefully
Awareness, not surveillance
Live Departures shows each tour's last verified field position — where the departure verifiably was, reported through the crew's actual work. It is operational awareness of the tour, not continuous tracking of employees.
Founding Pilot Program
Put your season on this screen
Pilot partners will run real departures through Live Departures — and shape what the console becomes.