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.
For multi-day guided tour operators
Keep departures coordinated. Know where you're needed.
TourRecap is being built to give guides and support crews a shared daily plan, bring field issues to the office, and carry approved route updates into the next departure.
See the current build and discuss fit. No pilot commitment.
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 · illustrative data
Built for repeat routes, multi-day departures, and guides, drivers, and support crews. For cycling, trekking, and multi-activity tours where each departure can improve the next.
A cycling tour day
One change in the field. A clear response from the 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.
A daily plan for the crew. Clear priorities for the office.
A Playbook brings together the day's route, responsibilities, timings, and operating notes.
TourRecap Field
The planned Field experience gives guides and drivers their part of the day. Crews would record changes and notes against the relevant stop, with the context the office needs.
Product concept
Day 3 · Playbook
07:30Hotel departureLead guideConfirmed
09:15Rice terrace climbAll crewStandard
12:00Lunch stop — riversideDriverStandard
15:30Ferry crossingLead guideWatch item
Field note + photo → attached to the ferry crossing as evidence
Field product concept · planned for pilot validation
TourRecap Office
The development build shows issues, office actions, and their history. A manager can see the response to an issue without reconstructing it from separate conversations.
Office development build · illustrative data
What will this ask of our team?
- What would guides record?
- The planned workflow includes field changes, notes, and day closeout. A pilot should measure the interaction burden alongside any benefit, while guides are doing their real work.
- How would we get started?
- Discuss your existing itineraries, operating notes, and crew roles in the walkthrough. The pilot scope should make setup responsibilities, training, and review effort clear before participation.
- What about our current systems?
- TourRecap does not replace your booking or reservation system. Sales, payments, and guest bookings stay there. How existing information becomes a Playbook is part of the pilot discussion.
Offline capture and multilingual workflows are planned areas for field validation. Your routes, devices, and connectivity belong in that discussion.
See the issue, the owner, and the response.
In the Office development example, a cancelled ferry becomes an assigned replacement-transport action with a due time and a recorded response.
Office development build · illustrative data
The console shows the last verified field position and reporting freshness. Missing information stays visible as unknown. In the planned improvement workflow, people approve changes before the next crew uses them.
Start by seeing whether a pilot fits your operation.
Use a short walkthrough to see the current build, discuss one of your routes, and understand what a pilot would need to prove.
See the current build and discuss fit. No pilot commitment.
Founding Pilot Program now forming · Field pilots beginning Q3 2026 · Production rollout follows pilot validation · Planned capabilities subject to field co-design
Explore the Founding Pilot Program
Meet the company behind the proposed workflow. About TourRecap