From manifest read-through to post-trip debrief: a time-ordered checklist covering every admin and gear item that decides how a departure goes before anyone arrives.
Two hours into a food walk, a guide learns that one guest is severely allergic to nuts. The information existed. It sat in a booking note added after the manifest was printed, or in an inbox nobody reopened before the van left. The same morning, another departure goes out with a guest whose final balance hasn't cleared, and a third has a boat promised to two groups at once.
None of that is a gear problem. All of it was decided in the office, days earlier. That's why a tour guide checklist works better ordered by time than by topic: the night before, the meeting point, the trip itself, and the debrief after. It sits alongside the broader duties and responsibilities of a tour guide, but it covers the part that fails quietly: what the guide needs to know before anyone shows up.
The sequence below holds at both ends of the market. A four-hour city walk and a ten-day trek use the same order at different depth. Admin items and gear items sit on separate lines, so neither gets folded into a vague tick box marked "prepared."
Volume makes the point sharper. UN Tourism recorded about 1.4 billion international tourist arrivals in 2024, an 11% rise on 2023 and 99% of the 2019 level, with Europe alone at 747 million, according to its 2024 recovery figures. More departures means more languages and more special requests landing on the same operations desk.
A headcount tells you how many people are coming. The manifest tells you who they are, what they need, and what they've agreed to. Only the second check catches anything.
Read every line the night before: names, dietary needs, medical notes, emergency contacts, waiver status, and any notes added after the booking was made. A count that matches the manifest can still hide a swapped name, a new allergy, or a guest moved across from a departure that was canceled.
Illustrative: a 12-seat kayak departure where the count is right, but a participant's medical note went in yesterday and never reached the printout in the guide's dry bag.
Ten minutes with the right document covers it.
A food allergy isn't a preference, and "just a little" isn't safe. The FDA states that it has not established a threshold level for any food allergen, meaning there is no recognized amount below which a reaction is unlikely, per its food allergy guidance. Treat that as the operating rule for every tasting, picnic, and set menu.
Check each declared need against the actual menu, the route, and the first-aid kit. A nut allergy, a heart condition, or medication needed mid-afternoon should change the plan on paper, not just fill a field in a form.
Illustrative: the picnic lunch is pesto and a nut allergy was added after the menu was locked. The night-before read catches it while the kitchen can still swap the dish.
Accessibility tends to get handled as a separate topic and then dropped. Asking about walking distance, surfaces, stairs, gradients, handrails, toilet access, and vehicle boarding at the same time as dietary needs costs nothing extra.
Inclusive-guiding training, such as this inclusive tourist guiding handbook from the European Network for Accessible Tourism, treats access as something the guide checks in advance rather than takes on trust. Step-free isn't the same as usable: an entrance can be flat and still sit at the end of a long approach with no rest points.
A name without a working number is not an emergency contact. Every participant needs someone reachable during the trip, with a number that works and a person who knows they're listed.
The U.S. National Park Service advises always leaving a trip plan with an emergency contact, checking the forecast on the day, and carrying supplies in case you have to wait out a storm, as its winter weather safety guidance explains. For an operator, that means recording the itinerary, the expected return time, access limits, and the person responsible for escalating a missed check-in.
Illustrative: a guest is injured on a ridge with no signal. The contact page is in the guide's waterproof sleeve, so a family member gets a call from the trailhead instead of a message three hours later.
The fields that belong on that form (name, relationship, number, and a backup) are covered in this emergency contact forms guide. Personal-safety teams apply the same test: their guide to building emergency contact lists that work treats a contact list as a communication plan rather than paperwork, and the measure is whether someone answers on the worst day.
An unsigned waiver is a problem to find at home, not at the put-in. Confirm every participant has signed the form that applies to the activity and the jurisdiction, and that signatures are stored where you can produce them on request. If you're unsure what the form should cover, start with what a liability waiver is and isn't.
Borders, national parks, permits, and hut bookings also need passport or ID details, with names spelled exactly as they appear on the document. A missing middle name on a permit list stops a guest at a desk.
Illustrative: a hut requires passport numbers 48 hours ahead. One guest's passport was never collected, so the guide spends the evening asking for an exception instead of checking the route.
If signatures are still collected on a clipboard at the meeting point, online waiver software is the cheapest fix on this whole list.
An unpaid balance should never become a conversation at the trailhead. Check payment status for every participant the night before, and decide in advance what happens if it's still open: the guest pays before departure, or the place is released.
Deposits and installments make that manageable, because each due date is a known point rather than a surprise. The failure mode is a final installment on an expired card, discovered at 7 a.m. with a van idling outside.
Illustrative: a trekking guest's third installment fails the day before departure. The reminder goes out automatically, the guest updates the card that evening, and the guide never hears about it.
Some departures need a minimum number to run: a boat with a crew, a charter with a skipper, a trek with two guides. Check the count against the minimum the night before, and make the call with a stated reason attached.
There's a second minimum worth knowing. The U.S. Forest Service says a group entering a remote area should have at least four people, so that if one is hurt, another can stay with them while two go for help, per its outdoor safety guidance. A commercial minimum of two and a safe field party are different numbers, and the gap between them is a decision you make, not a technicality.
Illustrative: a sailing charter has a minimum of four and, three days out, two guests. The operator consolidates into a later departure and tells both guests that evening in writing.
The mechanics of scheduling this (recurrence, cutoffs, and capacity) are set out in this guide to departure management.
Set cancel and reroute thresholds before the morning, not while the group stands around in jackets. Wind on a lake, river flow, rain on a scree slope, heat on a bike route, visibility on a safari drive: each one gets a number and an alternative.
Forecasts also move under you. Australia's Bureau of Meteorology notes that forecasts are updated at least twice daily and become more accurate as the date approaches, and advises reviewing them regularly and watching for thunderstorm and strong-wind warnings, in its weather guide for land activities. That argues for staged reviews: at booking, the day before, the morning of, and again before an exposed section.
Illustrative: a rafting outfit sets a flow threshold for one river section. The gauge reads above it the night before, the group moves to a calmer section, and guests get a message that evening rather than at the put-in.
Boats, bikes, vehicles, radios, and gear are capacity. The same 12-seat kayak can be promised to two overlapping departures without anyone noticing until both groups are on the beach.
Before leaving home, confirm which equipment is assigned to the departure, check its condition, and confirm it isn't also assigned to an overlapping one. Count seats against the vessel's rated capacity. Match bike sizes to the guest list. Check the driver and the seating on vehicles.
Illustrative: two day departures share one boat. The office spots the overlap the night before and one departure moves to a later slot, which costs an hour instead of a morning.
Anything outside your control gets confirmed twice: when it's booked and the night before it's used. That means permits and park passes for the right date and headcount, transport with drivers or partners, restaurant, lodge, and hut reservations, gate codes, and pickup times.
The number on the permit is the usual failure. Groups change after booking, and a permit issued for ten doesn't become twelve.
Illustrative: a hut booking was made for ten and the manifest now shows twelve after two late bookings. The reconfirmation call adds two beds while there's still room.
For food and wine tours, reconfirming means checking the venue has the group size and the dietary notes, not just a table for twelve.
A kit is only worth carrying if it works when it's opened. Safety management for adventure tourism has its own international standard: ISO 21101:2014 sets out requirements for a provider's safety management system, as recorded in the ISO standard listing. Equipment inspection and briefing records sit inside that kind of framework.
Confidence is the weak link. A 2025 study of 38 white-water rafting guides at five companies in Jinja, Uganda, found that 71.1% reported low confidence handling rafting emergencies, 78.9% lacked CPR or basic first-aid knowledge, 65.8% had never conducted rescue drills, and 52.6% reported first-aid kits were never available, according to the study. It's one river and a small sample, but the lesson travels: carrying a kit and being able to use it are separate qualifications.
The core kit doesn't cover everything, and the gaps are activity-specific. The Adventure Travel Trade Association's Adventure Travel Guide Standard expects guides to manage risk to participants and to be trained in first aid and incident-response protocols, and those protocols only work when they match the activity. The addendum below is where that lands in practice.
Illustrative: a cycling tour takes two punctures on day one. The kit and correct spare tubes cost ten minutes instead of an afternoon.
Keep one addendum per trip type and staple it to the master. A generic kit gets packed. A specific one gets used.
The meeting point is where the manifest meets the actual group. Count heads against the list, never from memory.
Brief from a script so every guide covers the same ground. Guide performance isn't only personality: a systematic literature review identifies communication, managerial skill, and leadership as core performance factors and links guide performance with tourist satisfaction, the visitor experience, behavior at the destination, and intention to revisit, according to the guide performance review. The briefing is where communication shows first.
Illustrative: a guest is 15 minutes late to a kayak launch. The published wait is 20 minutes, so the guide calls the emergency contact, and the guest walks up just after the call connects.
Once the group moves, the risk is on the terrain, not in the office. Set turnaround times for hikes, river sections, and rides, and tell the group what they are. A turnaround time only the guide knows is a plan nobody can follow.
Count at transitions: after a stop, before a crossing, after a viewpoint, before leaving a venue. Run a lead guide ahead and a sweep guide last, so the group has a defined front and back.
Log incidents as they happen: time, who was involved, what was done, who was told. Small ones included. A near-miss written down on the spot becomes a checklist change; the same near-miss remembered over dinner becomes an anecdote.
Illustrative: on a trek, the sweep sees a participant stopped 300 meters back. The lead is told by radio, the group pauses at a safe point, and the participant is checked before continuing.
The end of a trip is when information is most valuable and most likely to evaporate. Write up incidents and near-misses while details are fresh, flag damaged or missing gear so it's pulled from the next departure, and pass the office what it needs for follow-up.
There's commercial weight in this. GetYourGuide survey data reported by TravelPress found that 94% of leisure travelers who booked a guided tour in 2023 planned to book one again in 2024. Guests who had a good trip are the cheapest bookings available, and the guide is the only person who heard them say so out loud.
Illustrative: a near-miss on a river section shows the throw bag was out of reach. The fix is a new line item, bag clipped to the guide's vest and checked at every put-in, not a memo nobody reads.
Version every change with a date and a name. An undated checklist can't tell you whether last season's fix is in the copy the new guide is holding.
This item sits between the office and the field, so by default nobody owns it, and that's where a good share of field problems begin. Someone has to confirm the manifest is final, at a stated time, and there has to be a defined route for late changes after that point.
Late bookings, a medical note added after the printout, a dietary edit from a traveler who finally opened the confirmation email: all of it arrives in the window between printing and departure.
Illustrative: a traveler adds a nut allergy the day after the guide printed the manifest, and the picnic lunch is pesto. A handoff rule gets the change flagged the same day, and the guide checks the live list instead of the paper.
Write the rule into the master checklist so it doesn't depend on who's working that week. It also helps when guides can open the current manifest themselves without being handed payment admin rights, which is what role-based team access is for.
| Item | When It Happens | Who Owns It | Problem It Prevents |
|---|---|---|---|
| Read the Full Manifest, Not Just the Headcount | Night before departure | Guide, using the current manifest | Missed guest changes or needs |
| Check Dietary Needs, Allergies, and Medical Notes | Night before departure | Guide and relevant food or lodging partners | Health risks and unprepared meals or routes |
| Confirm Emergency Contacts for Every Participant | Before the trip starts | Operator or office; guide carries the details | Delays reaching family when there is an emergency |
| Collect Waivers and Passport or ID Details | Before departure; ahead of permit or border deadlines | Operator or office | Missing signatures and document-related access problems |
| Settle Balances Before the Meeting Point | Night before departure | Office or payment administrator | Payment disputes distracting the guide in the field |
| Confirm Minimum Group Size or Make the Go/No-Go Decision | Night before departure, by the booking cutoff | Operator or departure manager | Last-minute cancellations and unviable departures |
| Check Weather and Conditions; Apply Set Cancel or Reroute Thresholds | Night before, with an additional check on trip day | Operator and designated decision-maker | Unsafe or inconsistent weather decisions |
| Assign and Check Shared Equipment | Night before departure | Office or equipment manager, with the guide | Double bookings, capacity mismatches, or faulty gear |
| Reconfirm Permits, Transport, and Reservations | Night before departure | Office or trip coordinator | Access, transport, or booking failures |
| Check the Core Guide Kit | Night before departure | Guide | Missing, uncharged, or unusable essentials |
| Check Activity-Specific Equipment and Supplies | Before departure | Guide and relevant equipment partner | Activity-specific equipment gaps |
| Take a Headcount, Brief the Group, and Handle No-Shows | At the meeting point | Guide | Missing participants, inconsistent briefings, and unclear follow-up |
| Set Turnaround Times, Count at Transitions, and Log Incidents | During the trip | Lead guide and sweep guide | Separated participants and incomplete incident records |
| Record Incidents, Flag Gear, and Update the Checklist | After the trip | Guide and office or checklist owner | Repeat problems and damaged gear returning to use |
| Confirm the Final Manifest and Route Late Changes to the Guide | Before departure, at a fixed cutoff; as changes occur | Named office confirmation lead and guide | The guide relying on an outdated manifest |
The short version, to print and keep by the van keys:
Seven lines, one page. If the list runs longer than that, it stops being usable at 6 a.m. in a parking lot and goes back to being a document nobody opens.
Most of the important work sits in the admin half, and that's the half most checklists handle worst, because the information is scattered: passports in one inbox, dietary notes in a booking comment, waivers in a folder, emergency contacts on a form nobody reopened. Pulling it into one manifest, and asking travelers for missing details well before departure, means a missing waiver turns up on Tuesday rather than at the put-in. If you're still running departures from spreadsheets and email, the pre-departure checklist covers the office side of that week in more detail.
Shared resources matter just as much. Boats, bikes, vehicles, and gear that can't be double-booked across overlapping departures remove an entire category of morning phone call. Minimum group sizes and booking cutoffs stop the manifest changing at an unknown hour. Deposits and reminders get payments sorted before anyone stands at a meeting point.
None of that replaces judgment on the day. It just means the judgment starts from a list that's current.
Run the list once on your next departure and fix whatever it catches. Then run it again next week, because the second pass is where the habit forms.
Samba runs the admin half of this list in one place: manifests with passports, dietary needs, waivers, and emergency contacts, a tasks library that collects missing details before departure, and shared boats, bikes, and vehicles that can't be double-booked across overlapping departures. Guides get their own access and a calendar feed, while deposits, automatic balance reminders, and a traveler portal settle payments long before the meeting point. Take a look at Samba and run your next departure from a manifest that's live rather than printed.
Read the full manifest, not just the headcount: names, dietary needs, medical notes, emergency contacts, waiver status and any notes added after booking. Then confirm balances are settled, the minimum group size is met, weather thresholds are set, shared equipment is not double-booked, and permits, transport and reservations are reconfirmed. Fix a time, such as 8 p.m., so the read-through never happens in the van.
Decide with thresholds set in advance, not at the meeting point. Give each condition, such as wind on a lake, river flow or heat on a bike route, a number and an alternative plan. Review the forecast at booking, the day before, the morning of and before exposed sections, and record the forecast, any warning, the go or no-go call and the backup plan.
The U.S. Forest Service says at least four, so that if one person is hurt, another can stay with them while two go for help. That is separate from a commercial minimum. A departure can be viable at two guests and still be too small for safe field practice, so set both numbers before the season and publish the minimum and booking cutoff on the departure page.
Set a fixed wait per activity, write it down and apply it the same way every time: for example, ten minutes for a walking tour and twenty for a boat. If a guest runs past the wait, the guide calls the emergency contact on file for that participant. Publishing the wait time keeps guests, guides and the office working from the same rule.
One named role, not a vague reference to the office. That person confirms the manifest at a stated time, usually tied to the booking cutoff, and any change after that goes to the guide as a timestamped message saying what changed and who sent it. Writing the rule into the master checklist means it does not depend on who is working that week.
Founder & CEO
Related posts
Duties and Responsibilities of a Tour Guide: 15 Key Tasks
The real work of guiding is mostly invisible: headcounts, manifests, timing, supplier confirmations, incident logs. Here's what the job actually contains, and what the office must own.
Emergency Contact Forms That Work When Signal Fails
Emergency contacts fail in the field because they're incomplete or the named person is on the same trip. Here's how to collect, verify, and carry them properly.
What Is a Liability Waiver? A Plain Guide for Tour Operators
A liability waiver isn't a force field—it allocates risk and documents informed consent. Here's what it covers, where it breaks down, and how to collect every signature before departure.
Keep the 20–30% you would hand an OTA
Samba gives tour and activity operators direct bookings on their own website, so you stop paying a marketplace 20–30% of every booking.