Guest Numbers, Sessions and Timings — Event Park and Ride Shuttle
The transport brief becomes workable only when every passenger wave has a route, time and owner. For Event Park and Ride Shuttle, the relevant users are event visitors, staff, volunteers and guests using remote or overflow parking. The organiser should estimate confirmed, likely and contingency numbers separately, then divide them by arrival time, destination and service priority. This creates a demand profile that can be checked against the programme without treating the headline attendance figure as the number travelling on every run.
The movement pattern may include continuous loops between approved parking areas, assembly points and the event entrance. Reporting time should be earlier than the passenger-facing departure time so the driver, coordinator and group leader can resolve access or boarding questions. Each trip should state whether it is a fixed transfer, a continuous shuttle, a vehicle waiting on standby or a split duty that returns later.
For Event Park and Ride Shuttle, the busiest points are usually connected to the opening arrival rush, programme intervals and concentrated end-of-event egress. Capacity should therefore be planned by wave, not only by the total day. A small operational margin can be reviewed for approved guest additions, but it must not replace an accurate passenger forecast or become an unpriced promise of unlimited capacity.
Demand profile — Event Park and Ride Shuttle
- Purpose and passenger profile
- Timing and movement pattern
- Approved operating margin


