Verity for tour operators
A fixed departure is a set of supplier commitments made before the guests exist. Verity tracks viability against those commitments while the decision can still be taken.
Runs alongside your existing booking and accounting systems.
Verity / Departures
LiveDepartures scheduled
38
Below minimum
9
Committed to suppliers
₹1.8 Cr
Guides unassigned
7
Needs attention
Illustrative figures. Verity shows your own departures in this shape.
How the business runs
A fixed-departure tour operator publishes dates, commits hotels, vehicles and guides against them, and then sells seats. That order is the defining commercial risk: the cost base is contracted months before the revenue exists, and the operator carries the difference until the departure either fills or is cancelled.
Each departure therefore has a viability point — a minimum number of travellers below which it loses money — and a cancellation window before which it can be cancelled cheaply and after which it cannot. Nine departures below minimum inside their cancellation windows is a decision that has to be taken now and is usually taken late.
The second characteristic is allocation. Guides, vehicles and specialist equipment are shared across departures, and a guide double-booked across two dates is discovered when both are confirmed.
The third is that an itinerary change touches several suppliers, and communicating it to all of them is a manual task where one is always missed.
The fourth is that supplier commitments have their own deposit and cancellation terms, none aligned with when travellers pay.
Verity tracks viability against commitments, allocates guides and vehicles across departures, and propagates itinerary changes to every affected supplier.
What Verity calls these things
What gets in the way
Tour operating difficulties come from contracting a cost base against departures that may not fill.
Viability decisions are taken late
A departure below its minimum can be cancelled cheaply before a window and expensively after it, and the review usually happens after.
In Verity Viability and cancellation windows sit on the departure, so the decision is prompted while it is still cheap.
Commitment exposure is not sized
Supplier commitments accumulate across departures and the total exposure against seats sold is rarely assembled.
In Verity Committed cost and seats sold are recorded per departure, so exposure is a current number.
Guides and vehicles are double-booked
Shared resources are allocated per departure and the conflict appears when both confirm.
In Verity Allocation is recorded against dates, so a conflict is visible when the second commitment is made.
Itinerary changes miss a supplier
A change is communicated to most affected suppliers and one is missed, producing a failure on the ground.
In Verity Components are linked to the itinerary, so a change surfaces every supplier it touches.
Deposit schedules do not align with sales
Supplier deposits fall due on their terms regardless of how the departure is selling.
In Verity Deposit dates and sales progress sit together, so funding decisions are informed.
Agent bookings arrive with incomplete details
Travel agents book seats and traveller details, documents and requirements arrive late.
In Verity Required details are checklist items per traveller with an age against departure.
The complete system
One system across departures, commitments, allocation and travellers.
Work
Each departure is work with its itinerary, components, minimum viable size, seats sold, committed cost, cancellation window and state.
Why it matters here The departure is where committed cost and uncertain revenue meet.
In practice Nine departures below minimum with cancellation windows closing.
Suppliers
Suppliers carry their commitments per departure, deposit and cancellation terms, reliability and balances.
Why it matters here The cost base is contracted before it is sold, on terms the operator does not set.
In practice One point eight crore committed against sixty-two percent sold.
People
Guides, vehicles and equipment are resources with availability, qualifications and allocation across departures.
Why it matters here Shared resources across fixed dates produce conflicts that surface late.
In practice One guide allocated to two departures on overlapping dates.
Workflows
Viability review, cancellation decisions, deposit payments and itinerary changes move through defined steps with recorded outcomes.
Why it matters here The cancellation decision has a date after which it becomes much more expensive.
In practice A viability review prompted before the cancellation window rather than after.
Relationships
Travellers and agents carry their bookings, documents, requirements, payments and history.
Why it matters here Agent bookings arrive with details missing, and departure readiness depends on them.
In practice Traveller details outstanding against a departure inside thirty days.
Orders
Bookings record seats, price, payment schedule and cancellation terms per traveller.
Why it matters here Seats sold against minimum is the single number the departure turns on.
In practice Seats sold against minimum viable size per departure.
Locations
Destinations carry their suppliers, requirements, seasonal factors and historical performance.
Why it matters here Destination-specific requirements repeat across departures.
In practice Permit requirements from the last departure to the same destination.
Reports and analytics
Seats against minimums, committed exposure, allocation conflicts, departure margin and supplier reliability come from the records.
Why it matters here The operator’s core risk is quantifiable and usually is not quantified.
In practice Committed exposure against seats sold across the season.
Verity AI
Verity AI answers from your own departure, supplier, allocation and booking records, respects permissions, and can create assigned follow-ups.
Why it matters here The valuable questions are about decisions with a closing window.
In practice "Which departures are below minimum inside their cancellation window?" returns nine.
Records
Itineraries, permits, traveller documents and supplier confirmations attach to the departure.
Why it matters here Ground failures are usually a document or permit nobody checked.
In practice Permits required for a route, checked before departure rather than at it.
Communication
Changes and confirmations attach to the itinerary component and the supplier they affect.
Why it matters here An itinerary change missed by one supplier becomes a failure on the ground.
In practice A revised arrival time propagated to every affected component.
Control
One permission model and one audit trail across every record.
Why it matters here Committing supplier cost against an unsold departure is the operator’s central risk decision.
In practice Commitments above threshold requiring approval against current sales.
Work in motion
These already happen. Recorded per departure, the risk decision is taken on time.
Calculating the minimum from committed cost rather than from habit is what makes the later decision possible.
Nine departures below minimum inside their windows is a decision that gets more expensive daily.
A double-booked guide is discovered when both departures confirm, which is far too late.
Propagating to every affected supplier is exactly the step where one is always missed.
Ground failures are usually a document or a permit rather than an operational surprise.
Verity AI
Verity AI reads the same departure, supplier, allocation and booking records the operator creates as it works. It answers across departures, respects permissions, and can turn an answer into decisions and chases.
Verity / Ask
Verity AI only returns what the person asking has permission to see.
Without chasing
Each runs from the departure records at the point the condition is met.
When
A cancellation window approaches on an under-sold departure
When
A resource is allocated to overlapping departures
When
An itinerary change is recorded
When
A supplier deposit falls due
When
Traveller documents remain outstanding
What you can understand
Commitment against sales, per departure.
All of it comes from recording commitments, bookings and allocation against the departure they belong to.
One system, different ways of seeing it
Everyone works from the same records.
Owner
What have we committed and what have we sold?
Viability against minimums, committed exposure, margin by departure, cancellation decisions.
Operations
Is this departure ready?
Allocation and conflicts, supplier confirmations, permits and documents, itinerary changes.
Sales and reservations
What needs filling and what is missing?
Seats against minimum, agent bookings, traveller details outstanding, payment schedules.
Where it is used
Minimums calculated from committed cost with the window on the departure, so the decision is taken while it is still cheap.
Contracted supplier cost recorded against seats sold, making the operator’s central risk a current number.
Guides, vehicles and equipment allocated across dates, so conflicts surface at the second commitment.
Components linked to suppliers, so a change reaches every one it affects rather than most of them.
Documents, permits and confirmations as checklist items aged against the departure date.
Required traveller details tracked per booking, since agent bookings arrive incomplete.
Plain-language questions across viability, exposure, allocation and readiness, with decisions raised in the same step.
Getting there
Your booking and accounting systems continue and are mapped during implementation. Departures with itineraries, supplier commitments and terms, resources and live bookings are brought across.
Implementation runs about four weeks: discovery and mapping, configuration, migration, then an ongoing operations partnership.
Questions
Verity AI answers questions from your own departure, supplier, allocation and booking records: which departures are below minimum inside their cancellation window, what is committed against seats sold, where guides are double-booked, which travellers have documents outstanding. Each answer can become a decision or a chase.
Because the cost base is contracted before the revenue exists. A departure below its minimum can be cancelled cheaply before a supplier window and expensively after it, so the decision has a date — and it is usually reviewed after that date rather than before.
Committed supplier cost is recorded per departure against seats sold, so total exposure across the season is a current number rather than something assembled when a departure fails to fill.
Guides, vehicles and equipment are resources with availability allocated against dates, so a conflict is flagged when the second commitment is made rather than when both departures confirm.
Components are linked to the suppliers that deliver them, so a change surfaces every affected supplier with a notification task and confirmation tracking — which is exactly the step where one supplier is normally missed.
Required traveller details and documents are checklist items per booking with an age against the departure date, so incomplete agent bookings are chased rather than discovered at check-in.
No. Booking and accounting systems continue and are mapped during implementation. Verity holds departures, commitments, allocation, readiness and the reporting across them.
About four weeks: discovery and mapping of departure structure and supplier terms, configuration of minimums and windows, migration of departures and bookings, then an ongoing operations partnership.
Each one has a date after which the decision costs far more. Tell us how viability is reviewed today.