Your operations manual: SOPs from booking to departure

Every booking in a small agency passes through one head: yours. You take the enquiry, write the quote, chase the advance, book the hotel, brief the driver, and field the 11 pm "flight kab hai?" call. It works, until the week you're on a flight yourself and nobody rechecks whether the transporter's permit is still valid, or whether the hotel actually blocked the rooms it confirmed on WhatsApp three weeks ago.

That's the real cost of not having a tour operator checklist from booking to departure: not lost time, but a client standing at a check-in desk with no room, and a public review that says so. A travel agency SOP format doesn't need software or a large team. It needs eight checkpoints, each one producing a document or a message you can point back to when something goes wrong. In this business, something eventually will.

This is that operations manual: the exact gates, the WhatsApp templates, the Excel trackers, and the vendor audit checklists to run a 3–10 person team without carrying every booking in your own memory.

The eight gates between enquiry and a happy client

An SOP is just a rule: nothing moves to the next stage until the current stage is signed off, on paper or in a sheet, by a named person. For a tour package, that's eight gates:

1. Enquiry logged and qualified
2. Quote sent and quote-to-confirmation
3. Vendor bookings placed and audited
4. Documentation completed
5. T-7 pre-departure pack sent
6. On-tour escalation plan live
7. Post-tour feedback and review capture
8. Vendor scorecard updated

Each gate below has an owner, a script, and a place it gets recorded. Skip a gate and you've moved the risk downstream, usually onto the client, standing at a hotel reception with a printout of a WhatsApp chat.

Gate 1: Enquiry to quote (speed decides who gets remembered)

The clock starts the moment an enquiry lands, whether it's a form fill, a DM, or a forwarded WhatsApp number. Log it before you do anything else. Note destination, dates, pax, budget band, and source in one running sheet. An enquiry that isn't logged is an enquiry that gets answered late or not at all, and speed to lead decides more bookings than price does.

A workable first-reply template, sent within 15 minutes of the enquiry landing:

Hi [Name], thanks for reaching out about [Destination] for [dates/month]! To send you an accurate quote, could you tell me: (1) number of travellers and any kids, (2) approximate budget per person, (3) hotel category preference (3-star / 4-star / boutique)? I'll have a detailed itinerary to you within 4 hours.

The four-hour promise matters more than it sounds. It forces you to log the enquiry the moment it becomes real work, not a "reply later" tab left open on your phone.

Gate 2: Quote to confirmation (lock the advance before you lock a seat)

A quote isn't a booking. Nothing gets vendor-booked until the advance clears, full stop. That single rule prevents more inventory chaos than any other in this list. Get the quotation format right and the confirmation conversation gets shorter, because the client already knows what they're paying for and by when.

Track every quote in one row of a sheet, not scattered across chat threads:

Column	What it captures
Quote sent date	Starts your follow-up clock
Advance due date	Set at quote time, not negotiated later
Advance received	Date and amount, screenshot filed
Vendor booking status	Blank until advance clears

Careful: Never provisionally hold a hotel room or bus seat "just to be safe" before the advance is in. A held-not-confirmed booking is the single most common source of the double-booking complaints that end up on Google reviews. You end up owing two clients the same room.

Gate 3: Vendor bookings (audit before you buy, not after a complaint)

This is the gate every "hotel was terrible" or "bus broke down" complaint traces back to. The vendor was booked on trust (a phone call, a rate card from six months ago) and never actually inspected before the client arrived. Fix it with two standing checklists, not a one-time gut check.

Hotel audit checklist, run before every new property goes into your master list and re-run once a year for repeat hotels:

• Rooms match photos currently on the property's own listing (ask for this month's photos, not stock images)
• Written confirmation of room count, category, and meal plan, not verbal
• Check-in/check-out times and early-check-in policy in writing
• Cancellation and no-show terms match what you'll quote the client
• A second contact number at the property besides the owner's personal number

Volume gives you leverage here: agencies that push roughly ten or more room-nights through a property over six months are commonly able to negotiate contracted rates and terms directly with the hotel, rather than working off a rack rate someone quoted once (source). If you're sending a hill-station property that volume every season, that's worth a direct conversation about a proper rate contract with allotments, not a fresh WhatsApp negotiation every time.

Transporter vetting is where hill routes bite hardest, and you don't need to invent a checklist. The Char Dham Yatra registration process has already built one. As of July 2026, its vetting requirement for any vehicle running hill routes covers a valid RC, current insurance, fitness certificate, PUC certificate, state road tax payment, permit, and a hill-driving endorsement on the driver's licence (source). These requirements are reissued each season, so confirm the current list on the official Char Dham Yatra registration portal before applying it. Borrow it wholesale for any transporter you use on a hill or ghat route, even outside Uttarakhand. It's the closest thing the industry has to an official benchmark, and asking a vendor for these seven documents before the season starts costs you one phone call.

Document	Confirms
RC + insurance	Vehicle is legally on the road
Fitness certificate + PUC	Vehicle is mechanically and emission-fit
Road tax + permit	Vehicle is licensed for the route/state
Driver's hill endorsement	Driver is certified for hill roads, not just any road

Keep photocopies or phone photos of all seven on file per vendor, dated. When a client asks "is this safe" the week before a Ladakh departure, you answer with a document, not a feeling.

Gate 4: Documentation (the tracker that replaces your memory)

Once vendors are booked and audited, one sheet should hold the entire trip's paper trail: passport/ID copies received, visa status if outbound, insurance issued, vouchers sent to hotels, and the vendor confirmation numbers. The rule: if it's not in the tracker, it didn't happen, no matter what someone remembers saying on a call.

Minimum columns: client name, trip dates, ID/passport received (Y/N + date), visa status, travel insurance issued (Y/N), hotel voucher sent (Y/N), transport confirmation number. One row per booking, one glance to see what's outstanding three days before departure.

Gate 5: The T-7 pre-departure pack

Seven days out, the client gets one message with everything they need, not four separate messages sent over three days as you remember pieces of it. That single pack is worth building properly once; the full pre-departure checklist covers the complete client-facing document list, so keep this gate's version to the essentials: final itinerary PDF, hotel and transport confirmation numbers, guide/driver contact, packing notes specific to the season and altitude, and an emergency contact number that isn't your personal phone.

Send it as one message, not a thread, and ask for a thumbs-up reply so you have confirmation it was read, not just delivered.

Gate 6: On-tour escalation (who does the guide call at 11 pm)

Every departure needs one written answer to "what happens if something goes wrong," decided before the bus leaves, not improvised mid-crisis. At minimum: a named on-call person for the duration of the trip (not necessarily the owner), a backup transporter's number for that specific route, and a rule for how fast a hotel complaint gets escalated to management rather than left with the front desk.

Careful: "Call me anytime" is not an escalation plan if "me" is the same person answering sales enquiries, chasing three other departures, and asleep by the time a flight gets cancelled at midnight. Name a specific on-call person per active departure and put their number in the pre-departure pack.

Gate 7: Post-tour (feedback and reviews before the memory fades)

The 48 hours after a client gets home is the only window where feedback is both fresh and honest. A short WhatsApp message asking for a rating out of 10, plus one open question ("what's one thing we could have done better"), catches problems before they turn into a public review and catches praise while it's easy to convert into a Google review or a referral ask.

Log every score against the trip in your tracker. A pattern of "hotel wasn't as described" against the same property across three trips is a vendor problem, not three unlucky bookings. Gate 3's audit checklist is what should have caught it the first time.

Vendor scorecards and the fire-or-keep rule

Every vendor (hotel, transporter, local guide) gets one row in a running scorecard, updated after every departure, not reconstructed from memory when a complaint arrives.

Example: A Manali transporter runs eight departures for you across a season. Score each on three things out of 5: punctuality, vehicle condition, driver conduct. After eight trips: punctuality 4.6, vehicle condition 3.1, conduct 4.8. The vehicle-condition score is the one to act on: average out below 3.5 on any single metric across four or more trips, and that vendor gets a documented warning before the next booking, not after the next complaint.

Set the same threshold for hotels: two independent client complaints about the same specific issue (room cleanliness, meal quality, check-in delays) in a season is your trigger to either renegotiate terms or drop the property from your master list.

Fire-or-backup rules should be decided per route, not per vendor, before peak season starts:

• Any hill or ghat route needs a second transporter's number on file, confirmed available, before the season opens, not sourced after the first vehicle breaks down.
• Any property that's a client's only hotel for a night (no same-night alternative in town) needs its allotment reconfirmed in writing within 72 hours of departure, not assumed from the original booking.
• Any vendor scoring below your threshold on two consecutive departures gets suspended from new bookings until you've personally re-audited them, not "we'll see how the next one goes."

Common questions

What do I do when a client complains about hotel quality mid-tour

Escalate immediately to the hotel's management contact, not the front desk. This is why Gate 3's audit collects a second number. Offer the client a concrete fix (room change, upgrade, partial refund) within the hour if possible, and log the complaint against the hotel's scorecard the same day, while it's fresh, not after the trip ends.

How do I manage tour operations staff without checking every booking myself

Give each gate a named owner other than yourself: one person always logs enquiries, another always confirms vendor bookings. Require sign-off in the tracker before a booking moves to the next gate. The SOP is what lets you step back; without it, delegation just means someone else is now the single point of failure.

What's a reasonable SOP format for a small travel agency

A shared sheet with one tab per gate (enquiry log, quote tracker, documentation tracker, vendor scorecard) beats a written policy document nobody reopens, whether that sheet lives in Excel or inside a WhatsApp CRM built for travel agents. The format matters less than the discipline of not skipping a gate: a one-page checklist that's actually followed outperforms a twenty-page manual that isn't.

The short version

• Run every booking through eight gates: enquiry, quote, confirmation, vendor booking, documentation, T-7 pack, on-tour escalation, post-tour feedback.
• Never vendor-book before the advance clears: held-not-confirmed bookings cause most double-booking complaints.
• Audit every hotel before it enters your master list: written room/meal confirmation, current photos, a second contact number.
• Borrow the Char Dham Yatra's transporter checklist (RC, insurance, fitness, PUC, road tax, permit, hill endorsement) for any hill-route vendor, everywhere.
• Send the pre-departure pack as one message seven days out, and get a read confirmation.
• Name a specific on-call person per departure: "call me anytime" isn't an escalation plan.
• Score every vendor after every trip; two bad scores in a season is your trigger to renegotiate or drop them, not wait for a third.