Tour operations managed in spreadsheets and WhatsApp groups -- guide assignments, vehicle allocation, and passenger manifests updated manually and sent by email the night before departure?
No system connecting the booking front end to operations, so passenger details have to be re-entered into the operational spreadsheet every time a new booking comes in?
Tour Operator Software Development
Tour operators managing departures in spreadsheets and WhatsApp groups face a specific set of operational risks. A guide assigned to two departures on the same day because the availability spreadsheet wasn't updated. A passenger manifest emailed the night before departure with an error because the booking data was re-entered manually from the website.
We build custom tour operator software for tour operators, DMCs, and ground handlers. Tour product management, booking and reservation handling, guide and vehicle assignment, manifest generation, and passenger communication -- connected in one system so bookings flow into operations without manual re-entry.
Tour product management -- departures, pricing, availability
Booking and reservation management
Guide and vehicle assignment with manifests
Passenger communication and documentation
Custom tour operator software manages the full tour lifecycle -- product management, departure scheduling, booking intake, guide and vehicle assignment, manifest generation, passenger communication, and operations reporting. It replaces the spreadsheet and WhatsApp combination that most tour operators use to run departures. RaftLabs builds tour operator software for ground handlers, DMCs, adventure operators, and group tour companies that need one system connecting the booking front end to the operations team on the ground.
100+Products shipped
·24+Industries served
·FixedCost delivery
·12-14Week delivery cycles
The spreadsheet-and-WhatsApp system has a failure mode
Tour operators running departures on spreadsheets have built a system that works -- until it doesn't. It works when the team is small, the departure calendar is manageable, and everyone in the office knows the state of every booking because they discussed it this morning. It fails when a booking comes in while two people are editing the same availability spreadsheet. It fails when a guide is assigned to a departure in WhatsApp but that assignment isn't reflected in the manifest the operations coordinator is working from. It fails when a booking from an OTA channel isn't entered into the system for 24 hours and the departure appears available when it isn't.
The operational cost of these failures is real: double-booked guides, incorrect manifests handed to drivers, passengers showing up at the wrong pickup point because the pre-departure email used a template that wasn't updated. Each failure is a customer service event. Repeated failures affect the operator's reputation on review platforms.
Custom tour operator software connects the booking intake to the operations workflow so the manifest is built from the bookings, not transcribed from the bookings. Guides are assigned in the same system that holds the departure calendar. Passenger details flow from the booking form to the pre-departure communication without a human re-entering them.
What we build
Tour product management
Tour creation with full itinerary -- day-by-day or segment-by-segment -- departure calendar with configurable schedule, and group size limits with availability count tracking. Pricing tier configuration: single, twin share, triple, solo supplement, child, and group discount rates. Seasonal pricing rules applied automatically to departures within defined date ranges. Tour category management for organising products by type, destination, and duration. Product availability management with block periods and special allocation for specific sales channels. Tour product publishing workflow with draft, review, and live states so pricing and itinerary errors are caught before the product goes on sale.
Booking and reservation management
Booking intake from web, agent, and phone channels into a single reservation system. Passenger details collection per booking: name, contact details, dietary requirements, medical notes, and emergency contact. Booking amendments -- passenger name changes, room type changes, date changes -- with audit trail. Waitlist management for sold-out departures with automatic offer when a cancellation creates space. Booking confirmation and documentation delivered by email -- confirmation letter, booking terms, and pre-departure pack. Agent booking management with commission tracking and agent statement generation. Cancellation workflow with fee calculation per the booking's terms and refund processing.
Operations and manifest management
Departure manifest generated automatically from confirmed bookings -- passenger names, dietary requirements, room assignments, pickup points, and any special notes from the booking record. Manifest update on every booking change so the operations team always has the current passenger list without manual rework. Guide and driver assignment with the manifest linked to the assigned staff member -- they see the current passenger list in the guide app or portal before departure. Activity and meal bookings for each departure managed against the passenger count. Pre-departure operations checklist with task assignment and completion tracking. Departure status tracking: pre-departure, in progress, completed, and post-tour follow-up pending.
Guide and driver management
Guide profiles with availability calendar, language skills, certifications, and tour product qualifications. Availability management preventing double-assignment -- the system blocks a guide from being assigned to two departures with overlapping dates. Guide assignment to specific departures with confirmation notification sent by app or portal. Briefing notes delivered to the guide before departure -- passenger list, special requirements, pickup schedule, and emergency contact for the departure. Post-tour feedback recording by guide with notes on passenger incidents, supplier issues, or product changes to review. Guide rating and performance history for assignment decisions on future departures.
Passenger communication
Booking confirmation with full itinerary and booking terms sent immediately at the time of booking. Pre-departure pack sent at a configurable number of days before departure -- meeting point, pickup schedule, what to bring, and destination-specific information. Day-before reminder with guide contact details and final meeting point confirmation. Post-tour feedback request sent 24 hours after the return date. All communications generated from the booking data -- passenger name, departure date, pickup point, and itinerary -- so no manual personalisation is required. Communication history stored against the booking record. Configurable communication schedule per tour type so an adventure tour gets different pre-departure content than a cultural city tour.
Reporting and finance
Departure profitability report combining booking revenue, guide and transport cost, activity and meal bookings, and agent commission to show net margin per departure. Occupancy reporting by tour product and departure date -- fill rate, average booking size, and revenue per departure. Agent commission calculation per booking and per statement period with commission report generation. Supplier cost reconciliation comparing purchase orders raised against invoices received for each departure. Forward revenue report showing confirmed bookings and projected margin for the next 30, 60, and 90 days. Cancellation and refund reporting with reason codes for product and pricing review.
Frequently asked questions
We build for group tour operators running fixed-departure escorted tours, adventure and activity operators with day tours and multi-day trips, destination management companies (DMCs) handling ground arrangements for incoming groups, and ground handlers managing transfers, activities, and accommodation for inbound travel agents. The core platform -- product management, booking, guide assignment, manifest, and operations -- applies across all of these. The configuration differs: a day tour operator needs a high-volume departure calendar with rapid booking processing; a DMC needs complex group itinerary management and agent-facing quotation tools; an escorted group tour operator needs detailed rooming list and departure logistics management. We scope the system for your specific operation during discovery.
Departure changes -- a guide calling in sick, a vehicle breakdown, a pickup point change -- are updated in the system and pushed to the affected passengers and the guide in real time. When a guide is removed from a departure, the system shows available guides with the right skills and availability for that date so the operations coordinator can reassign immediately. Passenger communication is triggered from the system -- a bulk SMS and email with the updated pickup point or guide details goes out to everyone on the manifest with one action. The manifest updates automatically so the replacement guide receives the current passenger list. The audit trail records who made the change, when, and what the previous assignment was.
Yes. Multi-day itinerary management is a core part of the platform. A 10-day tour with accommodation in four cities, activities in each destination, and a rotating guide roster across the itinerary is handled as a single departure with day-by-day resource assignment. Accommodation bookings are tracked against the departure with supplier confirmation status for each property and each night. Activity bookings are linked to the day they occur and the passenger count. Guide assignments can change by day or by destination segment. The passenger manifest shows the full journey so the operations team and each guide assigned to a segment see the relevant portion of the itinerary and the passengers on their leg.
A tour operator system covering product management, booking intake from web and agent channels, manifest management, guide assignment, and passenger communication typically takes 16 to 22 weeks from requirements sign-off to go-live. Complexity drivers that extend the timeline: number of booking channels and integrations (OTA connections, agent portal, website booking widget), multi-currency pricing requirements, and depth of financial reporting. An MVP covering core booking and operations management for a single-channel operator can be delivered in 12 to 14 weeks. We scope the build with a phased approach so you go live with the core system and add channel integrations and reporting depth in subsequent releases.
Talk to us about your tour operator software project.
Tell us your tour types, booking channels, and the operational gaps your current system creates. We'll scope what we'd build and give you a fixed cost.
