Digital Manifests and Check-In for Tours
The list a guide carries is where your whole operation gets tested.
Bookings arrive from four channels, payments land at different times, a guide gets assigned, someone books at ten the night before — and all of it has to resolve into one accurate list held by a person standing in a square at nine in the morning.
The manifest is where operations either works or is quietly revealed not to. This covers what belongs on it, the genuine trade-offs between digital and paper, what guides should and should not be able to see, and why checking the tour in matters long after everyone has gone home.
What belongs on a manifest
Each field earns its place by answering a question a guide will actually face:
- Names and party size — who am I expecting, and how many.
- The exact option booked — which departure, which language, with or without pickup. Without this a guide cannot resolve a disagreement at the meeting point.
- A contact number for the lead guest — the single most useful field when somebody has not arrived.
- Special requirements — dietary, mobility, anything affecting the day.
- Pickup point and time, per guest, where pickups apply.
- Booking source — so the guide asks for a review on the right platform, and the team knows which cancellation terms apply.
- Outstanding balance, where money is still owed and collectable on the day.
- Total expected, stated plainly at the top, so the guide knows when to stop waiting.
The two most frequently missing are the option and the source. Both are invisible in the office and both matter at the meeting point — the first because a guest insisting they booked the English tour cannot be checked, the second because a review request sent to the wrong platform is wasted.
Digital vs paper, honestly
Software companies present this as settled. It is not, and pretending otherwise leads operators to abandon something that works in conditions where the replacement does not.
Paper is genuinely better at surviving a dead battery, working with no signal, being readable in bright sun, tolerating rain and gloves, and being handed to a second guide without any setup. It also never updates itself, which is precisely the problem.
Digital is genuinely better at being current at the moment it is opened, showing the office what is happening in the field, capturing check-in as data rather than pencil marks, and carrying details that would not fit on a printed sheet.
The failure modes are completely different, which is the argument for running both. Digital as the working record, a printed copy in the bag as the backup. Operators who treat paper as an embarrassment tend to rediscover its value on a mountain with 3% battery.
More useful than the digital-versus-paper framing is a single requirement: the manifest must work offline. Loaded before departure, readable without connectivity, able to record check-ins locally and sync when signal returns. Tours operate in valleys, on boats and underground — a system needing a connection at the meeting point will fail regularly rather than occasionally.
Special requirements and privacy
Requirements are worth capturing at booking rather than discovering on the day, and worth capturing specifically. "Dietary requirements" as a free-text box produces answers ranging from a preference to a serious allergy, and a guide cannot tell which is which.
Ask the questions your product actually needs — mobility on a walking tour, swimming ability on a boat, dietary detail where food is served — and flag anything safety-relevant so it stands out rather than sitting in a paragraph.
Which raises a question few operators consider: how much should a guide see?
The sensible principle is what they need to deliver the tour safely and well. A guide needs to know somebody has a severe nut allergy and needs a contact number for the lead guest. They do not need home addresses, full payment details, or notes unrelated to the day. Beyond being better practice, it limits the exposure if a phone is lost or a printed sheet is left in a café — which happens.
Paper manifests deserve a disposal habit for the same reason. A stack of old sheets with guest names and phone numbers in the back of a van is personal data nobody is managing.
Check-in in the field
A guide checking guests in is doing it one-handed, in daylight, with people talking to them, frequently in a hurry. Anything that requires care and attention will be skipped and reconstructed afterwards from memory, which defeats the purpose.
- One tap per guest. Not a form, not a confirmation dialogue.
- Large touch targets and high contrast, because outdoor screens are hard to read and hands are not always dry.
- Visible running count — how many arrived against how many expected, without needing to count rows.
- Somewhere to note the exception — a no-show, a late arrival, an extra person the lead guest brought.
- A way to close the tour at the end, confirming it ran and with how many.
That last step is the one most often left undone and the one carrying most of the downstream value. It takes a guide five seconds and is the only definitive record that the tour happened.
Staying current
The manifest's whole value is accuracy, and it decays fast. Bookings arrive late — this category runs on last-minute demand — and a list prepared at six in the evening is wrong by ten.
Two consequences worth designing around. The manifest should be generated from live bookings rather than assembled, so opening it produces the current version rather than a snapshot. And the guide should be told when something changes after they have looked — a late booking, a cancellation, a pickup amended — rather than discovering it by counting heads.
The office side matters too. Somebody taking a phone call at nine fifteen about whether a guest arrived should be able to answer without ringing the guide mid-tour. That is only possible when check-in flows back rather than living on the device until someone gets home.
What the data is for
Check-in feels like administration for its own sake right up until you need it. Four things depend on it:
- Payment disputes. A record that a named guest was present on a named date is the strongest evidence in a chargeback response.
- Reconciliation. Marketplaces pay on tours delivered rather than booked, so a confirmed-run record is what you match their remittance against.
- Your real no-show rate — the number that tells you whether prepayment or reminders are worth changing, rather than an impression.
- Guide hours, confirmed by the record of tours run rather than a separate timesheet nobody enjoys keeping.
None of those are available if the only evidence a tour took place is that nobody complained afterwards.
How Travelity helps
Travelity builds the manifest from live bookings as part of daily operations, with the option and booking source attached, so what a guide opens in the morning includes the reservation that arrived at ten the night before.
Because reservations from every channel land in one place, there is one list rather than a marketplace export reconciled against a spreadsheet — which is the difference between a manifest that is current and one that was current when somebody made it.
Frequently asked questions
What should be on a tour manifest?
Guest names and party sizes, the exact option each person booked, contact details, special requirements, pickup points and times, the booking source, and any outstanding balance. The two most often missing are the option and the source, and both cause problems at the meeting point that the guide cannot solve without them.
Are digital manifests better than paper?
Digital is better at being current, shareable and capturing check-in data. Paper is better at working with no signal, no battery and wet hands. Most well-run operations use digital as the working record and carry a printed copy as a backup, because the failure modes are completely different.
What information should guides be able to see about guests?
What they need to run the tour safely and well — names, party composition, requirements affecting the day, and a contact number for the lead guest. They generally do not need home addresses, full payment details or anything unrelated to delivery, and limiting what appears in the field is both good practice and lower risk if a device is lost.
How do guides check guests in without a mobile signal?
The manifest needs to work offline — loaded before departure and able to record check-ins locally, syncing once a connection returns. Signal is unreliable in exactly the places tours operate, so a system that requires connectivity at the meeting point will fail regularly rather than occasionally.
Why does checking a tour in matter after it has run?
A record that the tour ran with named guests present is the evidence that settles a payment dispute, the confirmation marketplaces settle against, the input to your real no-show rate, and the basis for paying guides accurately. Without it, the only proof a tour happened is that nobody complained.
Bottom line
Put the option and the booking source on the manifest, because those are the fields a guide needs and rarely gets. Generate it from live bookings rather than assembling it the night before. Make it work offline, and carry paper as the backup rather than treating it as a failure.
Then close the tour at the end. Five seconds from the guide produces the record that settles disputes, matches payouts, tells you your real no-show rate and confirms hours — none of which can be reconstructed later from the fact that nobody complained.
Related guides
See Travelity in action. Book a Personalized Demo.
30 minutes that can completely change the way you run your travel business. See how Travelity can help you work smarter, sell more, and operate with less stress.