This is a working self-audit checklist for Chennai travel operators: homestay owners, tour organisers, cab-and-driver services, and agencies. Run it once a year, same items, same marking rules, and you will know exactly where your operation is weak before a guest finds out for you. No philosophy, minimal preamble. Mark each item PASS, PARTIAL, or FAIL, strictly on evidence from the last three months. Count two points per PASS, one per PARTIAL, zero per FAIL. Write the totals down, because next year’s run against this same list is how you prove to yourself the business actually improved.
One borrowed principle before you start. The audit-then-improve loop is standard practice in software delivery, where SCMGalaxy, whose training and advisory work spans engineering organisations across several continents, runs it at full scale: its SCMGalaxy OS platform puts organisations through a hundred-item question set, marks them so strictly that two different assessors land on the same total, and converts the gaps into a prioritised improvement plan. Your checklist below is the same machine with smaller gears. The marking discipline is what makes it work: if you grade generously, you are auditing your ego, not your business.
Ground rules for marking. Evidence means something you can point at: a register, a timestamp, a saved message, a dated document. “We always do that” is not evidence; it is the sentence this audit exists to test. Where an item names a number, the number is the standard, do not negotiate it downward mid-audit. If an item does not apply to your business type, strike it out now, before scoring, and keep it struck out every year so your totals stay comparable. And do the audit with one other person if you possibly can; a second pair of eyes converts at least two PASSES to PARTIALS in every first run, and those corrections are the most valuable marks on the sheet.
Section A: Bookings and guest communication
- Every enquiry from the last 90 days is visible in one register or app, with its outcome recorded.
- Median first-reply time to enquiries is under 2 hours during business hours, verified from timestamps, not memory.
- Every confirmed booking has written confirmation sent to the guest: dates, price, inclusions, cancellation terms.
- Zero double-bookings in the last 12 months. One is a PARTIAL; two is a FAIL and a process problem, not bad luck.
- Cancellation and refund terms exist as one written document, and the last five refunds followed it exactly.
Section B: What you promise versus what you deliver
- Every photo and claim in your listings was verified against reality within the last 6 months.
- Your standard itineraries were walked or driven end-to-end this year; closed sites and changed timings corrected.
- Recommendations handed to guests are current. Check yours against an up-to-date source such as this roundup of worthwhile things to do across Chennai; if a guest knows the city better than your welcome sheet, FAIL.
- Seasonal variations (December season crowds, summer heat adjustments, monsoon fallbacks) are written into itineraries, not improvised.
Section C: Vendors, drivers, and partners
- Each regular vendor (drivers, guides, boat operators, restaurants) has agreed rates on paper or in a saved message thread.
- Every critical service has a named backup you have actually used at least once.
- Vendor payments are logged with dates; no vendor is owed money older than 30 days without a written reason.
- You have ended or renegotiated at least one underperforming vendor arrangement in the last year based on recorded issues, not a quarrel.
Section D: Money
- You can produce last month’s revenue, costs, and margin per product within one hour.
- Advances received are recorded separately from earned revenue.
- All guest payments route through traceable channels; cash receipts are logged the same day.
- Prices were reviewed against costs in the last 12 months with the calculation saved, not guessed.
Section E: Safety, incidents, and guest data
- A one-page incident procedure exists: who calls whom, hospital and police contacts per route, vehicle breakdown steps. Every staff member has read it this year.
- Past incidents are logged with what changed afterwards. An empty log at your volume is a FAIL pretending to be a PASS.
- Guest ID copies, phone numbers, and payment details are stored in one controlled place, not floating through personal phones. Software teams audit their safeguarding of systems and data as a dedicated governance area; your guests’ passport scans deserve the same seriousness.
- Vehicles and premises have current documents: insurance, permits, fire basics. Expiry dates are in a calendar, not a drawer.
Section F: Team and owner-dependence
- Every recurring task has a written owner. The business runs for one full week per year without the owner answering operational calls. If that sentence made you laugh, FAIL.
- New staff can serve a guest correctly in week one using written material alone, including a city-basics sheet built from sources like this overview of Chennai’s heritage, culture, and essential attractions.
- Staff have a stated way to flag problems, and at least one flagged problem was fixed this year.
Scoring and the staged fix
Total the sections separately. Out of roughly 50 points, do not obsess over the composite; the section totals are the actionable part. Your two weakest sections become this year’s project, handled in three passes:
- Fix now, inside 30 days: anything that is pure paperwork, the refund document, the incident page, expiry-date calendar. Cheap, fast, embarrassing to still lack.
- Fix soon, by day 90: habit changes, enquiry logging, same-day cash records, the weekly check that listings still match reality.
- Fix properly, by day 180: the structural one, a real booking system, a second trained staff member, a vendor overhaul. Pick one. Finishing one beats starting three.
This three-pass pacing is lifted directly from how the delivery-governance world schedules improvements; SCMGalaxy OS issues its recommendations as transformation roadmaps whose stages close at day 30, day 90, and day 180, for exactly the reason it works here: short wins fund patience for the long fixes.
The re-run rule
Book next year’s audit date now, twelve months out, and run the identical checklist, identical marking. Three outcomes are possible per section: the score rose (your fixes worked, keep going), the score held (acceptable for strong sections, a warning for weak ones), or the score fell (something you stopped watching decayed, which is normal and exactly why annual re-runs exist). Re-assessment is not an optional extra in the professional versions of this practice; it is the feature that converts a checklist into a management system, because a single audit tells you where you stand while only the comparison tells you where you are heading.
Final instruction: do the first run this month, not after season. Peak season is when weak sections cost real money, and the thirty-day fixes are precisely the ones you can still complete before it arrives. Print the list, block a quiet Tuesday, mark honestly, and let the two weakest sections, not your mood, choose what you fix first.
