2026-10-17 · Shuttle Roster

Who Should Be Allowed on a Corporate Shuttle in Shanghai? Passenger Rosters, Ad-Hoc Rides and Driver Checks

Six months into a shuttle service, the problems are rarely mechanical. They concern who is allowed on board: a colleague who left two months ago is still on the list, a contractor crew boards alongside employees, someone working until ten at night does not know whether a seat exists, and the driver recognises faces at the door, offending someone by being too strict and someone else by being too loose. The common cause is that the service was designed around routes and timetables but never around people and eligibility. Six questions and answers work through the riding population, roster maintenance, ad-hoc rides, removing access, driver checks and exceptions for outsiders, so administration has a workable basis. General management method only; your own policy governs the specifics.

1. Defining Who Rides

Q1: Who should be allowed to use a corporate shuttle?

Sort people into four groups and the rules stop being ambiguous. Permanent and probationary employees are included by default, boarding on a badge or roster check. Interns and agency staff are usually included, but name the department that registers them and the date cover starts. On-site suppliers, outsourced teams and construction crews are better kept on a separate list tied to specific routes and time windows, because they come and go with a project and distort headcount if mixed into the employee roster. Visitors and family members are not part of the daily service; where genuinely needed, they go through an ad-hoc request that states who is responsible. The point of the classification is not simply permission but a different registering department, validity period and basis of responsibility for each group. Put the four categories in a table inside the riding rules and drivers no longer have to judge from memory at the door.

2. Building and Maintaining the Roster

Q2: How should the passenger roster be built and kept current?

The roster must answer three questions: who is on it, which route they use, and from when it applies. Fields can stay few: name, employee number, department, route and stop, effective date, expiry date for leavers or transfers, and who registered them. Maintain it with a monthly full check plus event-driven updates: departments report additions and removals at the start of each month for reconciliation, while joiners, leavers, transfers and long absences are updated as they happen rather than waiting for month end. Keep versions traceable, with time and operator recorded, so nobody argues that a person was added last week and has now vanished. One point often missed is the link between person and route: the same employee may take route A in the morning and route B in the evening, and the roster has to show both or the driver check will not reconcile. A solid roster also simplifies ad-hoc rides, access removal and cost allocation later.

Q3: How should access be handled for leavers, transfers and long absences?

Removal should follow the HR action rather than the driver noticing a stranger. Three points. For leavers, the last working day is the expiry date: remove them from the roster from that day and collect the badge and any travel pass; if they still need a ride on the final day, log a one-off with route and time. For transfers, a change of workplace usually means a change of route, so adjust before the transfer takes effect, or the employee waits at the old stop. For long absences such as sick leave, maternity leave or an overseas posting, keep the person on the roster marked as suspended and restore on return, instead of deleting and re-adding. If all of this sits with one administrator it will be missed; a better arrangement is a linked form where HR ticks whether a shuttle is involved when processing a change, and administration acts on the tick. Missing one person is cheap; a leaver holding a seat while someone who needs it cannot board is a management problem.

3. Ad-Hoc Rides and Driver Checks

Q4: How should ad-hoc rides be requested?

Ad-hoc rides (late overtime, returning from a trip, a meeting at another site, taking a different route) are the least controlled part of shuttle management because they are inherently retrospective. Keep the path as short as possible: the passenger submits through one fixed channel by a cut-off such as 15:00 the same day, with name, employee number, boarding stop, time and reason; a department contact or administrator confirms and the name enters that day list, so the driver sees an added passenger rather than an approval chain. For genuine emergencies, allow boarding first and recording the next day, but limit the frequency and keep the record, or emergency becomes the norm. Capacity needs a limit too: hold a few flexible seats per vehicle and say no clearly when they are gone, rather than leaving the driver to grant favours at the door. Once the route in is clear, most friction turns out to have been people not knowing whom to ask rather than the company refusing.

Q5: How can drivers check passengers without delaying departure?

The purpose is not policing but confirming that those expected are on board and those not expected are not. Three practices keep it quick. Check by stop rather than by name: the driver holds a list ordered by stop, compares expected boardings with actual boardings at each stop, and departs when the numbers reconcile, looking at names only when they do not. Use a visible credential instead of scrolling a list: a badge, a travel card or a unified boarding code is recognised at a glance. Handle exceptions in one place: ad-hoc riders, forgotten badges and colleagues asking on someone else behalf are noted in the day remarks and resolved at the terminus or back at base, not in a long conversation at the door. Importantly, the driver should not be deciding eligibility; the roster does that, and the driver checks and records. For anyone not on the list, the agreed step is to contact the coordinator rather than admitting or refusing on personal judgement.

4. External Passengers and Exceptions

Q6: Can family members, visitors and external people ride?

Not as a rule, and exceptions need conditions. Requests usually appear after late overtime, bad weather or a company event, and refusing outright is hard, but a commuter shuttle is designed around registered employees: seats, route, stops and cover are all set for the roster, and adding people affects punctuality and other passengers. A workable approach is a defined exception channel rather than an open door: confirmed in writing by the department head or administration, limited to that trip and that day, limited to available seats, and with no extra detour, all recorded. Visitors and external people such as clients, suppliers or candidates are better served by a separate vehicle, because their timing does not match the commute and the arrangement raises information and responsibility questions. Whatever the exception, state in the riding rules that prior confirmation is required, so employees know the rule exists instead of negotiating at the door. Cover and responsibility follow your company policy and the service agreement.