A hotel calls with a family request, a returning customer books by message and two people arrive at the office. None of those sales is inherently difficult. Problems begin when they remain outside the system that determines capacity, pickup and the guide's passenger list.
A guest manifest is the operational result of several decisions, not a substitute for making them. It should show who is expected and what the team must deliver, while the fuller booking record retains commercial details and the change history. This guide describes a practical manual process without assuming a particular platform includes manual-entry tools, document exports or automatic manifests.
Give manual sales a defined entry point
Decide who can accept a booking from each source and where they record it. Staff taking a phone request should know whether they can confirm immediately or must seek a capacity decision. A guide or hotel partner should have the same understanding before promising a guest a place.
Use a short intake sequence: identify the departure, capture the party and contact details needed to assess it, check capacity, record the decision and communicate the result. Do not begin with a payment request while the date or product option remains ambiguous. A completed form is useful only if the underlying request is understood.
For an out-of-office enquiry, establish a practical handoff to someone with the current capacity record. If that person is unavailable, give the customer a response time rather than an unsupported confirmation. The business can remain welcoming without allowing several independent seat reservations to exist in separate phones.
Keep a stable reference across every conversation
Assign one booking reference and record any hotel, agent or external-platform reference beside it. Use that reference when moving information between the intake record, payment record and departure list. A guest's name alone is not a reliable link, especially when one person books for several families.
Check for duplicates before creating another booking. Ask whether the traveler already has a confirmation and compare departure, contact and party details. A guest may contact the office after booking elsewhere because they want pickup advice, not because they intend to purchase twice.
If you discover duplicate records, identify the active one and link the other to it. Keep a brief explanation so the next staff member understands why the same family appears twice in the messages. Do not cancel one payment or release capacity until the booking and payment positions have been verified through the appropriate processes.
Separate the booking header from the passenger detail
The booking header should identify the product, option, date, departure, lead contact, channel, booking status and relevant payment status. Passenger detail describes the people covered by that booking and the resources they need. Keeping those levels distinct prevents one group's contact information being repeated unnecessarily on every operational list.
For a simple product, an adult count and child count may be sufficient for planning. Another product may require individual names or particular participant information. Determine those requirements from the actual service and the responsible provider before collecting them. Do not copy the most detailed supplier's form onto every unrelated tour.
Use consistent column labels and explain the unit. “Quantity” could mean people, private groups or equipment sets. “Children” could mean all minors or a specific ticket category. Write a small data dictionary describing what each field means and who completes it. This is especially useful when several people enter bookings during a busy shift.
Handle children through the product's actual rules
Record age information at the level the product needs for eligibility, pricing and resource preparation. Ask the parent or responsible adult for clarification when a category is uncertain. A child ticket, an infant ticket and a person who does not pay the adult price should never be assumed to consume the same resources.
Check seating, equipment and supervision arrangements with the person responsible for delivery. A reduced fare does not itself settle whether a separate place or specific equipment is required. Likewise, accepting children on one option does not establish that every option in your catalogue has the same suitability or participation rules.
Communicate the outcome clearly before confirmation. For example: “We have recorded two adults and two children aged [ages] for [option]. We are confirming the required [relevant arrangement] before finalizing your booking.” This is an original template, not a universal policy. Replace every bracket with verified details and avoid asking guests to diagnose suitability from a vague phrase such as family friendly.
Collect relevant information without building a dossier
For each requested field, identify the decision it supports. A guide may need a language preference or an agreed assistance arrangement. They rarely need the whole payment conversation. If a detail serves no current operational purpose, reconsider why it appears on the manifest.
The UK Information Commissioner's data-minimisation guidance explains the principle for organizations within the relevant UK data-protection framework. It is useful primary guidance on limiting information to its purpose; it is not a universal statement of every destination's requirements. Establish the requirements that actually apply to your business and service.
Where a provider requests identity or other sensitive information, verify the requirement, the receiving party and the appropriate collection route. Avoid putting document images or detailed personal disclosures into a general passenger sheet. Explain why information is requested and route special questions to a person qualified to handle them. The operational team needs actionable arrangements, not unnecessary private history.
Generate a departure view from the active records
The departure list should identify the date, product, departure or resource, issue time and person responsible. Include booking references, party quantities, meeting arrangements and any relevant delivery note. Show unresolved items explicitly rather than leaving a blank that staff may interpret as complete.
If using Google Sheets, filters and filter views can help isolate a particular departure. Test the criteria before relying on the result. A row excluded because of an inconsistent date or status can make the departure appear smaller than it is. Verify the total against the authoritative booking count and passenger quantities.
Do not assume hiding a column creates a suitably restricted copy for another recipient. Create an appropriate operational view or separate controlled document containing only the necessary fields, using the actual tools and permissions available. Keep the fuller booking register out of broad driver or guest groups.
Make check-in marks mean one thing
Define what each mark records. “Present” may mean the lead traveler has spoken to staff, the entire party has arrived or everyone has boarded. Those are different events. A single tick beside a group can conceal a missing family member unless the team understands its meaning.
Google Sheets checkboxes can record a defined yes-or-no task. Use them for a clear state such as “party count verified,” rather than an ambiguous field called “done.” If your departure requires more stages, use separate labeled fields or a short controlled status.
For a hypothetical four-person booking, staff may record that three people have arrived and one is still expected. Keep that quantity visible until the situation is resolved. Do not mark the booking fully present because the person carrying the confirmation is there. At the same time, avoid collecting a new full set of guest details at the meeting point when those details are already recorded and unnecessary to repeat.
Control access and issue versions deliberately
Decide who needs view access and who needs edit access. A driver may need the collection list but not permission to change the booking date or price. The office needs a clear route for corrections from the guide without allowing several conflicting copies to become authoritative.
Google Drive's sharing documentation explains viewer, commenter and editor permissions and sharing with specific people. Check the actual file and parent-folder access rather than assuming a restricted-looking sheet is private. The examples here do not require using Google tools; apply equivalent controls in your chosen system.
When a list is printed or sent as a snapshot, label its issue time. A later change must reach the person using that copy and be acknowledged. If several vehicles receive different lists, confirm which bookings belong on each. Sending everyone the entire manifest to avoid preparing appropriate views is an inefficient substitute for a clear allocation.
Reconcile late additions, moves and cancellations
Every late addition needs the same capacity and preparation checks as an earlier booking. Identify what has already been issued: pickup messages, equipment requests and guide lists. Update those outputs as part of the change, not as optional tasks someone may remember afterward.
A move between departures has two sides. Remove the commitment from the old departure through the correct status or change process and add it to the new one only after checking availability. Verify both totals. Otherwise, a booking can disappear from one operational list while still consuming capacity there, or appear on the new list without the required resource.
For cancellations, retain the record with a clear status and handle any payment action separately. An operational cancellation does not establish that a refund has been processed. If only part of a group cancels, update the passenger quantities and any associated resources, then communicate the revised booking to the guest.
Keep an exception note when a change cannot yet be resolved. For example: “Reference [X], one additional participant requested, not confirmed, capacity review assigned to [name] by [time].” This prevents an unanswered request from appearing as an accepted passenger on the list. The guest-facing reply should use the same distinction.
If internet access fails during preparation, nominate one person to maintain the temporary record and mark when the outage began. Record new commitments, attempted changes and decisions in sequence. When access returns, reconcile those events against the live record before issuing another list. Do not simply paste the final passenger total into a cell, because that can conceal which bookings created it. The recovery should restore the booking trail as well as the count, so later questions about payment or pickup still connect to a recognizable reference.
Close the manifest without losing the learning
After departure, reconcile expected and actual attendance and record material delivery exceptions. Distinguish a no-show from a canceled booking or a person moved to another departure. Those differences matter when reviewing communications and capacity use later. Avoid changing historical attendance simply to make the totals look tidy.
Have a defined retention and disposal process appropriate to the information and requirements involved. Operational copies should not accumulate indefinitely in car gloveboxes, personal downloads or unmonitored group chats. Determine what the business needs to retain and where, then make clearing unnecessary copies part of the closeout routine.
Review one sample manifest with a colleague. Can they identify the departure, understand every column, total the passengers and see what requires action? Ask them to trace a hypothetical child-category change and a late hotel booking from intake through the final list. If they need the owner's memory to finish, improve the instructions.
Use a short release checklist before each departure: correct date and option, all channels reconciled, passenger quantities checked, relevant child arrangements confirmed, pickup details current, unresolved cases assigned and issue time visible. Read the checks against the records rather than ticking them from habit. A checklist is valuable when each item has a specific piece of evidence behind it.
The capacity-management guide explains the resource side of this process. Tripnatic's operator area supports bookings and operational communication, while the exact handling of manual intake and manifests should follow the controls available in your account and business. A reliable list begins with a reliable commitment and ends with a team that knows precisely whom it is expecting.
