Tour operationsHow to run a 40-person departure without phone chaos
A departure with forty travellers can turn into a day of phone calls within an hour of leaving the office. The information sits in too many places at once: a PDF voucher, an Excel sheet, a tour manager's notebook and a dozen private chats that nobody else can see.
The short answer
Give the whole group one current trip plan, send the same message to everyone at the same time, and agree in advance who answers each kind of question. Keep one-to-one chats for personal issues only. A calm first morning usually comes from preparation done in the week before, not from having a faster phone on the coach.
Find where the information lives today
Before you change anything, map where the trip information currently lives. Ask the team to list every place they update or check during a departure. In most offices the list includes the booking system, a shared spreadsheet, the vendor emails for hotels and coaches, the tour manager's own phone and whatever group chats were created for the trip. Write them down in one column, then mark the ones that the travellers themselves use.
This exercise usually shows that the same fact exists in three or four places with slightly different times. A coach pickup at 6:30 in one file and 6:45 in another is enough to cause a morning of confusion. The goal is not to remove every source. It is to decide which one is correct and to make sure everyone else points to it.
Ask the team which questions they dread most, and note where each answer currently lives. Those answers are the first ones to put in the plan.
Ask who owns each source. A source with no owner goes stale quickly. Give the trip plan to one named person in the office, and give the day-to-day updates to the tour manager. Everyone else asks, rather than edits.
A stage-by-stage checklist for tour managers, from two weeks before departure to the morning the group leaves, with a copy-ready format.
AskAditi · 19 November 2026 · 6 min read
Be honest about what the current system costs. Count how many times a day someone repeats the same answer, and how much of the tour manager's time goes on it. That number is often the strongest case for changing the process, because it makes the benefit concrete for the people who do the work.
Build one trip plan everyone can read
The trip plan is the single version of the truth for the group. It should be short enough to read on a phone and detailed enough to answer the questions travellers will actually ask. A day-by-day layout works well, with each day broken into timed items: breakfast, departure, stops, check-in, free time, dinner and the evening brief.
For example, a three-day trip to a hill station might have an entry like this in the plan: "Day 1, 06:30 breakfast at the hotel dining room, 07:15 coach leaves from the main lobby, 10:00 tea stop at the agreed point, 13:00 lunch at the restaurant on the plan, 15:30 check-in at the resort." Hypothetical times, but the structure is the point. Each line answers a question that would otherwise come as a message.
Include the things people look for on the day: the coach number or registration, the hotel name and address, the names and numbers of the tour manager and office contact, the pickup points with landmarks, and the rule for bags. Keep the plan in the same order the travellers experience the day, so a reader can find the next step without scrolling far.
Name the file and its version clearly, for example with the trip code and the date of the latest change, and keep only one live copy. When a colleague wants to adjust a detail, they should send the change to the owner rather than editing a copy. Old copies are the usual source of the argument at the coach door about what the sheet said.
When the plan changes, the change should be made in the plan first and then announced. Do not send a message with a new time while the old time still sits in a spreadsheet that someone may send later. A simple rule helps: update the plan, then send the broadcast, and note the change in the plan's history.
Send the same message to the whole group
Group chats feel like the natural place for updates, but they become hard to manage once forty people reply at once. A better pattern is a broadcast to the whole list for shared information, and one-to-one chats for individual questions. Shared facts such as a change of pickup time, a bag rule or a weather note should reach every traveller in the same words, so nobody has to ask a neighbour what was said.
The message rhythm matters more than the number of messages. A practical pattern for a multi-day trip looks like this:
The evening before departure, send a brief for the next day with the wake-up time, breakfast time, pickup point and the coach contact.
Half an hour before each pickup, send a short reminder with the place to stand and the time.
At a stop, send an update only if the time or plan has changed. Silence means the plan still holds.
After a long or tiring day, send one message that says what tomorrow starts with, rather than a list of every item.
Each message should be short, plain and complete. A reader who only sees the latest message should still know what to do next.
Do not assume that a message was read simply because it was sent. Before the trip, check which travellers have replied and which have not, and ask the tour manager to confirm the quiet ones in person at the first pickup. A message is a tool for reaching people, not proof that they know the plan. If you have a tool that schedules these messages, use it to avoid sending the same reminder twice from two phones. Keep the rhythm the same across the whole trip, even on quiet days, so travellers learn when to expect a message.
Agree who answers what
Most of the phone noise comes from questions that nobody has been assigned. A traveller asks about a room change, a tour manager is busy with a coach, and the office is asleep. Decide in advance who answers each category of question, and write the answer down where the team can see it.
A simple split works for most departures. The tour manager handles anything on the trip: timings, pickups, meals, the group and the coach. The office handles anything involving bookings, payments, vouchers and changes to the plan. Emergencies have a separate route, which should be the fastest and most direct: the tour manager calls the duty contact at once, and the duty contact is named on the plan.
Write this into a one-page responsibilities note, attach it to the trip plan, and read it aloud at the pre-departure briefing. Keep it short enough that a new team member can understand it in a few minutes. The note matters most on the day when the usual person is unavailable.
Set out the hours as well. If the office closes at a certain time, say so in the plan and name who answers the phone after that. A traveller who knows a question will wait until morning is calmer than one who keeps calling the same number.
Run a rehearsal on the first morning
Even a well-prepared departure has a few gaps that only show up in practice. Use the first morning to test them. Before the coach leaves, check that every traveller has the right pickup point and that the message reached every phone. Ask two or three travellers to read back the plan for the day, and listen for any detail they have wrong.
If a few travellers did not receive the brief, send it again to them one by one rather than to the whole group. Repeating a long message to everyone creates the noise you were trying to avoid. Note the cause for next time, whether it was a wrong number, a saved contact with a typo or a phone with messages turned off.
Check the things that nobody thinks to check as well: whether the coach has enough seats for everyone, whether the driver has the list of stops, and whether the luggage space matches the number of bags. Small checks like these prevent the kind of delay that looks like a communication problem but is really a planning problem.
Keep a short log of the questions asked during the first two days. Patterns in that log tell you what to add to the plan, what to move earlier in the brief and which answers the office should write down once and reuse. A departure gets calmer each day when the team learns from the questions it receives.
An example of a clean day
Here is how the same morning can look with a shared plan and a clear rhythm. The evening before, the group receives a brief with the pickup time, the place to meet, the breakfast time and a reminder to keep one bag ready. In the morning, the coach number is shared, and each traveller receives a reminder thirty minutes before the pickup. At the first stop the tour manager posts one line: the group is on time, the next stop is at the planned time, and anyone who needs help should write to the tour manager directly.
Compare that with a morning where the brief was on a voice note, the pickup point changed at the last minute in a single chat, and nobody knew which bus was theirs. The trip is the same, but the second morning produces forty questions and a tired tour manager before lunch.
Mid-trip, the pattern matters even more. Shared updates should stay brief and arrive at the same times, and personal questions should move to one-to-one chats. When a traveller asks something already covered in the plan, point them to the plan rather than restating it from memory, so every answer matches. After the departure, spend ten minutes with the team noting which questions came up and which answers were missing. That log should shape the plan for the next trip.
How AskAditi helps
Sends the same brief, reminder or broadcast to a whole trip at once, and lets you schedule it ahead, through broadcasts.
Lets travellers ask about their own day and answers from the trip plan you upload, so many routine questions never need the tour manager's phone.
Keeps the team's inbox in one place, with a clear handoff to a person when a question needs one, as explained for tour operators.
Next step
Choose one departure in the next few weeks and rebuild its trip plan in one place, with one owner and one message rhythm. When you are ready to try it on a live trip, start free and load the plan into AskAditi before the first briefing.
Ready to try AskAditi?
Connect your WhatsApp number, add a trip or a room, and try Aditi in the test chat before any traveller or guest writes in.