Charter Pre-Departure Passenger Headcount Sheet

Use it before the initial departure and again after every scheduled or unscheduled stop where passengers may board or exit. It is especially useful on charter, tour, shuttle, and group trips where the driver needs a repeatable count check. The form is not meant for ticketing or full passenger manifests; it is for confirming who is physically aboard at each checkpoint. If your operation has multiple vehicles, use one sheet per vehicle and trip.

The driver should complete the core count fields because the driver is usually the person responsible for the final departure check. A group leader, escort, or dispatcher can confirm the count when your process requires a second set of eyes. If your operation uses a manifest or boarding assistant, they can help verify names, but the sign-off should still clearly identify who made the final count. Keep the assignment consistent so the audit trail is easy to review later.

The actual headcount is the number of passengers physically on the vehicle at the stop. The manifest count is the expected number based on the trip roster or boarding list. Matching the two confirms that no one is missing, but a mismatch should trigger the discrepancy section rather than being ignored. This is the main control that helps prevent passengers from being left behind.

At minimum, verify the count before departure and after each stop where the passenger load can change. Many operators also require a second verification before leaving busy pickup points, rest stops, or attractions. The form includes a field for count_verified_twice so you can document a double-check when your policy calls for it. If your route is simple and nonstop, you may only need the departure check.

Only collect missing passenger names when there is a discrepancy or when your process requires identification for a specific count issue. That keeps the form aligned with data minimization and avoids collecting unnecessary PII. For ordinary headcounts, the total number is usually enough. If you do collect names, add clear disclosure language about why the information is needed and who will review it.

Use the discrepancy section to record the count gap, the reason, and any missing passenger names if known. Then note whether a supervisor was notified and what resolution status applies, such as resolved, pending, or escalated. Do not leave the discrepancy as a blank field or free-text note only, because that makes the audit trail harder to review. The form should make the next action obvious.

Yes, it can be adapted for school charters, airport transfers, sightseeing tours, employee shuttles, and private group outings. You can rename fields like tour_operator_or_group, add route-specific stop types, or include escort fields when minors or assisted passengers are involved. Use conditional logic so extra fields appear only when they apply. That keeps the form short and easier to complete on the road.

A notebook or chat thread can confirm a count in the moment, but it is easy to lose, hard to standardize, and difficult to audit later. This template creates a consistent record with required fields, timestamps, and sign-off so the same information is captured every time. It also reduces ambiguity by separating the count, the discrepancy, and the resolution. That makes reviews, incident follow-up, and route audits much easier.