Relief Drivers and Vehicle Swaps: Keeping the Manifest Right Mid-Route

The run leaves the depot clean. One coach, one driver, a manifest everyone agrees on. Then reality arrives. The driver hits a mandated rest break down the line and a relief driver takes the wheel at a roadside changeover. A coach throws a warning light at the lunch stop and the only spare in the yard seats fewer than the one it replaces. A vehicle gets pulled onto a Saturday charter and the scheduled run it was rostered to needs a substitute. The booking was correct at 06:40. The question is whether it is still correct when the people and the vehicle change underneath it.

This article is for operators running scheduled and charter coach services where the driver and the vehicle don't always stay the same from origin to terminus — interurban and regional express lines long enough to need a driver changeover, school-and-charter fleets sharing vehicles across two booking models, depots where a breakdown means whatever is parked and serviceable goes out next. If the asset on the road at the last stop isn't always the one you planned at the first, the continuity problem below is one you already know.

It is a different problem from selling the seats in the first place. Pricing a multi-stop route so the same seat sells twice on one run, and metering each leg so you never oversell, is its own discipline — covered in multi-leg coach routes. This piece starts after the seats are sold: what happens to the manifest, the capacity, and the boarding record when the driver hands over and the vehicle gets swapped — and why that handover is where a lot of coach software quietly goes stale.

Why a stale handover costs more than a stale spreadsheet

A manifest that drifts out of date at the depot is annoying. A manifest that drifts out of date mid-route, at the moment a new driver takes responsibility for the passengers on board, is something else. The relief driver is accountable for a coach full of people they did not load. If the list in their hand was printed before the morning's last intermediate-stop boardings, they are accountable for a count they cannot verify and passengers they cannot account for. That is not a clerical problem; it is a safety and duty-of-care problem with the operator's name on it.

The cost shows up in three places. First, in the time the depot and the office spend reconciling by hand — survey work by Time etc found small-business owners spend more than a third of a 45.5-hour working week on administrative tasks (Time etc, 2023), and at a depot a large slice of that is rebuilding lists the system should already hold. Second, in capacity that goes unsold or oversold because nobody can see the real picture during a swap — the same blindness that left Washington State Ferries running an average 61% vehicle-deck utilisation in 2023, varying route by route from 39% to 79% (WSDOT Multimodal Mobility Dashboard). Different mode, same lesson: capacity you can't see during a change is capacity you can't manage. Third, in the customer left on the kerb because the substitute coach was smaller and nobody worked out who lost a seat until the doors were closing.

These are not edge cases an operator can design out. Mandated rest limits mean a long enough route needs a relief driver by law; a fleet of any size loses a vehicle now and then. A platform that treats these as exceptions to be patched up by hand fails on exactly the days the operation is already under pressure.

What "keep the manifest right" actually demands

The live manifest is the single list of who is travelling on a service — what they booked, where they board and alight, what fare and concession they hold, what state they're in (expected, checked in, boarded). Keeping it right through a handover means it stays one authoritative list no matter how many devices read it or how many times the responsible person changes.

The first demand is that the manifest is genuinely live and genuinely shared, not a snapshot. JetSetGo's manifest is live across every device — a walk-up sale at the depot kiosk lands on the driver's tablet the moment the card clears, a no-show triggers re-allocation, and the office, the depot supervisor, and the driver all see the same picture in the same second (the mechanics are in the check-in and boarding capability doc). That property is what makes a handover safe. The relief driver doesn't inherit a printout; they sign into the same service on their own device and pull the same authoritative list.

The relief driver picks up the live list, including the boardings since the last handover. Picture a regional express that changes drivers at a midpoint town three stops into a six-stop route. Between the depot and the changeover, eleven passengers boarded at intermediate stops, two no-shows were marked, and one walk-up bought a ticket at a kiosk. On a printed-list operation the relief driver starts the back half holding a roster that predates all of that — blind to fourteen changes on a coach they are now responsible for. With a live manifest, the relief driver signs in and the list already reflects every boarding, no-show, and walk-up to that minute. The boarding states carry across; the people already marked boarded stay boarded. The handover is a sign-in, not a re-keying exercise.

Last-minute boardings reach the incoming driver immediately. The riskiest window is the few minutes around the swap itself, when a passenger buys at a roadside stop or the depot kiosk just as the changeover happens. If that sale lands only on the outgoing driver's device, or has to be relayed by phone, the incoming driver starts out of date from the first metre. Because the kiosk POS, the website, and the boarding app all draw from one shared inventory pool and one manifest, a sale made at any channel in that window appears on whichever device is signed into the service — including the relief driver's, the moment they sign in. There is no stale printed list to work from, because there is no printed list at all.

When the vehicle changes size mid-plan

A driver changeover keeps the same vehicle and the same capacity; only the responsible person changes. A vehicle substitution is harder, because the capacity itself can change — and that is where most coach software is at its weakest.

A smaller coach swapped in has to reconcile already-sold seats against reduced capacity. A 57-seat coach breaks down at the lunch stop and the only relief vehicle the depot can get there is a 49-seater, with 53 passengers booked across the run. On a paper-and-phone operation, somebody at the gate works out the overflow with a pen and a forming queue — deciding who travels, who waits, and who gets a call, under pressure, on the day. The platform should do that reconciliation instead: recognise that the substitute carries fewer seats than the bookings already sold, flag the overflow explicitly rather than silently overbooking the smaller coach, and offer a bulk action — move the affected passengers to the next service, re-seat those who fit, notify everyone in one workflow. JetSetGo handles a coach substitution as exactly this: a smaller coach replacing a larger one flags the affected passengers automatically and offers rebooking onto the next service or a refund, with SMS and email in the same workflow, before the departure leaves the depot (the bus and coach pillar covers the substitution flow).

A subtlety worth naming: when the swap happens mid-route, the seats that matter are the seats on the legs the substitute coach will actually run. A passenger who alighted before the lunch-stop swap is not competing for a seat on the smaller coach; a passenger boarding after it is. A platform that meters seats per leg — the per-sector model behind multi-stop coach inventory — works out the real overflow on the remaining legs rather than a crude headcount against the whole run, the difference between flagging the three people who genuinely lose a seat and panicking the whole manifest.

A swap to a different seat layout invalidates assigned seat numbers. Operators who sell reserved seats hit a second problem the moment a substitute coach has a different floor plan. Seat 14A on a 57-seat three-axle coach may not exist on a 49-seat substitute, and where it does it may be a different position entirely. A platform that treats the seat map as part of the booking has to do one of two things cleanly: re-map the assigned seats onto the substitute's layout where they fit, or — where they can't be preserved sensibly — drop the affected legs to unreserved and tell the passengers their reserved seat could not be carried across. What it must not do is leave stale seat numbers pointing at seats that don't exist on the coach now running, which sends two passengers to the same row and the driver into a dispute at boarding. Operators running unreserved seating sidestep this; for those who sell specific seats, how the platform handles the re-map is worth asking before signing.

Charter and scheduled work share one fleet, so a charter pull forces a scheduled substitution. School-and-charter operators run both models on the same vehicles — the 54-seat coach on Tuesday's school run is Saturday's wedding charter. When a charter pulls a vehicle rostered to a scheduled service, the scheduled run needs a substitute, and that run's manifest inherits the same size-reconciliation problem above if the only spare is smaller. The two models are not separate systems with a wall between them; they draw on one fleet and one availability picture. JetSetGo holds charter inventory alongside scheduled inventory in one pool, so a vehicle committed to a charter is visibly unavailable to the scheduled roster, and the substitution it forces surfaces when the charter is confirmed — not at 06:00 on the day the scheduled coach fails to show.

The boarding record has to survive the change, because the audit depends on it. Operators on a council, transport-authority, or school-district contract need a defensible record of who travelled, on what vehicle, under which driver — and a mid-route swap is precisely where a weak system loses the thread. JetSetGo's audit trail captures every boarding scan, state change, and override with a timestamp and the crew member who made it, attributed to the resource the action sits against (check-in and boarding). A driver swap re-points the manifest to the new driver in one action, and that re-pointing is itself a logged event — so the audit reads as one continuous, attributable record (coach A under driver one, then coach B under driver two) rather than two half-manifests the contract manager has to staple together.

What to ask a platform before you commit

Demos run the clean run — one coach, one driver, origin to terminus. The handover and the swap are the brittle path, where you find out whether the platform was built for the day everything goes to plan or the day it doesn't. Put these to any vendor and watch whether the answer is a live screen or a story.

Hand the service to a relief driver mid-route. Ask them to board passengers at intermediate stops on a device, mark a no-show, take a kiosk walk-up, then sign in a second driver on a different device at a changeover point. The relief driver's manifest should already carry every one of those changes, boarding states intact. If the answer involves printing or phoning, the platform doesn't hold one live list.

Swap in a smaller coach against already-sold seats. Substitute a 49-seat vehicle into a run with 53 bookings. The platform should flag the overflow explicitly, identify who is affected on the legs the substitute actually runs, and offer a bulk move-or-notify action — not silently confirm 53 onto 49, and not leave the overflow for the depot to solve by hand.

Break the seat map. If you sell reserved seats, substitute a coach with a different layout. Assigned seats should be re-mapped where they fit, gracefully dropped to unreserved where they can't — never left pointing at seats the new coach doesn't have.

Pull a vehicle for a charter. Confirm a charter on a vehicle rostered to a scheduled service and show that the scheduled run's substitution surfaces as a known conflict at confirmation, from one shared fleet picture — not a surprise on the day.

Read the audit across the change. Ask for the audit record of a service that changed driver and vehicle mid-route. It should read as one continuous, attributable record, not two half-manifests. (For the full evaluation framework across charters, depots, channels, and reporting, the companion piece how to choose a bus and coach booking system runs the ten-question version.)

Where JetSetGo fits

JetSetGo holds one live manifest that the office, the depot, and the driver all see in the same second, so a relief driver taking over mid-route signs into the same authoritative list — every intermediate-stop boarding, no-show, and walk-up since the last handover — rather than inheriting a printout. A coach substitution flags the affected passengers automatically and offers rebooking or refund with SMS and email in the same workflow, before the departure leaves the depot; a driver swap re-points the manifest to the new driver in one logged action. Charter and scheduled inventory sit in one shared fleet pool, so a vehicle pulled for a charter surfaces the scheduled substitution it forces at confirmation rather than on the day. Every scan, state change, and override lands in an audit trail attributed to vehicle, driver, and time, so the record reads as one continuous account across the change. Channel rules sit on top, capping how much of each run resellers can sell (the channel management capability doc covers the allocation mechanics).

Where to go next

The broader segment overview — scheduled routes, charters, depot scheduling, POS, and live manifest — is the bus and coach booking software pillar. The mechanics behind the live manifest, the boarding states, and the audit trail are in the check-in and boarding capability doc; the per-leg route model that makes mid-route reconciliation leg-aware is in durational and multi-sector services; the seat-selling side of multi-stop routes is in multi-leg coach routes. When you're ready to see a handover and a swap modelled the way they happen on the road, book a demo.