TourRecap Office
Live Departures
See what needs the office, who owns the action, and what happened. The development build below demonstrates a response to a cancelled ferry using illustrative data.
Founding Pilot Program now forming · Field pilots beginning Q3 2026 · Production rollout follows pilot validation · Planned capabilities subject to field co-design
Live Departures — development build · illustrative fixture data
Attention Routing
What deserves intervention — and who owns it
In this development example, the ferry cancellation appears in Needs Attention. The office assigns a replacement-transport action with an owner and a due time.
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.
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.
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
See what this could show your operations team
Explore the current Office build and discuss what a pilot would need to establish on your departures.
See the current build and discuss fit. No pilot commitment.