01 / Before the ride
A plan for guide and driver
Planned Field workflow
The guide reviews the day's stops and watch items. The support driver sees their responsibilities and timings. The proposed Playbook brings those instructions together.
How It Works
What changes during a tour day?
A changed plan needs context, an owner, and a response. Start with a cycling-tour example, then see how the proposed workflow carries the day from preparation to an approved update.
Founding Pilot Program now forming · Field pilots beginning Q3 2026 · Production rollout follows pilot validation · Planned capabilities subject to field co-design
A cancelled ferry, from crew to office
02 / During the day
The ferry is cancelled
Office development example
In the Office build, the team can inspect the ferry issue, assign a replacement-transport action, ask the guide, and record the response. The planned Field workflow would give the crew a way to report the change.
03 / Before the next departure
An update the next crew can use
Planned improvement workflow
The proposed closeout brings the change and response into the day’s record. An authorised person reviews a suggested route-note update before it becomes part of the next Playbook.
Illustrative cycling-tour day. Office screens use development data; the full Field-to-Office journey is planned for pilot validation.
The proposed five stages
The full workflow below is planned for pilot validation. It depends on crew input and office review; the pilot should measure the work involved as well as the result.
Prepare
The operator and pilot team would prepare the Playbook: the plan and the route, who is responsible for what, the known risks, the suppliers, the standards each stop is run to — and the alternatives when the day doesn't cooperate.
Run
Each role would work from its own view of the Playbook: guides see their day and their next actions, drivers see theirs, and handoffs carry the context with them.
Capture
The crew would record changes during the day — field observations, media, receipts, and operating events land in the tour-day record while they're fresh.
Close
The crew would review plan versus actual: what ran to standard, what changed and why, and which exceptions still need a response.
Improve
The day's record would support proposed Playbook improvements. Authorised people review and approve changes before the next departure uses them.
The loop complements the systems that get a trip booked and planned; TourRecap focuses on executing, recording, closing, and improving the operating day.
The Compounding Loop
Carry approved learning into the next departure
The planned improvement workflow requires human approval before a proposed change becomes an operating instruction.
- Approved Playbook
- Field execution
- Evidence
- Review
- Proposed improvement
- Human approval
- Improved Playbook
Season one
The Playbook is your itinerary plus your standards — everything the operation already knows, made explicit.
Every departure after
The aim is to retain what the crew learned and carry useful, approved updates into the next departure. Pilots should establish which changes actually help.
The office view
See the demonstrated Office response using illustrative development data in Live Departures.
Founding Pilot Program
Discuss the workflow against one of your routes
See the current build and discuss what the proposed workflow would ask of your team.
See the current build and discuss fit. No pilot commitment.