The Platform
What would your crew and office use?
TourRecap Field is the planned daily workspace for guides and drivers. TourRecap Office is the development console for the operations team. Explore what can be shown today and what the first pilots would need to validate.
Founding Pilot Program now forming · Field pilots beginning Q3 2026 · Production rollout follows pilot validation · Planned capabilities subject to field co-design
Office: development build
Screens demonstrate an Office workflow using illustrative data.
Field: planned for validation
The Playbook and crew workflow are product concepts for pilot co-design.
Rider: later
The guest experience is outside the first pilots.
TourRecap Field
For guides, drivers, and crew
The day's Playbook on the device already in the field — planned for 2026 pilots and shaped with the crews who run it.
Role-specific Playbooks
The planned Playbook gives each role the route, responsibilities, and operating notes for its part of the day.
Next actions & handoffs
The proposed workflow shows what comes next, who takes over, and what context they need.
Field capture, offline
Offline notes, photos, and operating events are planned for field validation, including how recorded changes reconcile when connectivity returns.
Closeout
The planned closeout asks the crew to review what changed and identify unresolved issues while the day is fresh.
Product concept
Day 3 · Playbook
TourRecap Field — product concept · planned for 2026 pilots · subject to field co-design
TourRecap Office
For operations and management
The Office development build demonstrates departure status, assigned actions, and their history using illustrative data.
Live Departures & attention
Today's active departures with ranked attention — what deserves intervention, surfaced instead of hunted. See the Live Departures console
Crew coordination & evidence
Assign actions, ask the guide, and see the field evidence that explains the operating condition.
Closeout, improvement & route memory
Planned closeout and improvement workflows would turn the day's record into proposed updates. An authorised person must approve changes for the next departure.
Live Departures — development build · illustrative fixture data
Alongside Your Systems
Keep your booking and reservation systems
Your existing systems continue to manage reservations, payments, CRM, and finance. TourRecap focuses on the tour day. Discuss how your itineraries and operating notes would become Playbooks, including setup responsibilities, before committing to a pilot.
Planned Guest Experience
TourRecap Rider — for the people on the tour
A guest surface scoped to what guests should see — nothing more. Planned for later field co-design, and not part of what the first pilots are asked to judge.
Status & safety sharing
Permitted status and safety information, shared on the operator's terms.
Messages & Need Help
A direct line to the crew, and a Need Help path when the day calls for it.
The active tour
The information that matters mid-tour: today's plan and what's relevant now.
TourRecap Rider — planned capability · subject to field co-design
Built on Trust
The ground rules
The same principles hold across Field and Office — and across the planned Rider experience.
Offline workflows — planned
Pilots should validate access to the daily plan and capture in the connectivity conditions your crews face.
Multilingual workflows — planned
Language needs and usable translations are part of field co-design with participating crews.
Privacy by purpose
Data is collected for an operational purpose, visible to the roles that need it.
AI advisory, human authority
In the planned improvement workflow, AI may draft proposals; authorised people review and approve operational changes.
Founding Pilot Program
See the platform against your own operation
Pilot partners bring real routes, real crews, and real departures — and shape what TourRecap becomes.
See the current build and discuss fit. No pilot commitment.