The short answer: in event transportation management, one named person owns the transport schedule, and nobody else changes it. Anyone may ask for a change. Only that owner approves it. Only the operator’s dispatcher tells drivers. When those three jobs sit with three clearly named people, a late change is a controlled edit with a timestamp and a cost. When they blur, the same change reaches drivers through a keynote speaker’s assistant, a hotel concierge and two family WhatsApp groups, and three vehicles end up at the wrong gate.
This guide sets out a change-control rule you can adopt for a conference, a corporate offsite, a delegation visit or a multi-day wedding in Pakistan: who may request, who approves, who broadcasts, which cut-offs apply, what each kind of change tends to cost, and what the audit trail should look like. It is written for the organiser or procurement lead who will later be asked who agreed to the extra coach.
Decision summary
- One owner. A single client-side transport lead holds the live schedule. A deputy covers named hours, not “whenever”.
- Three roles. Requesters ask, the owner approves, the operator’s dispatcher broadcasts. Drivers take instructions from the dispatcher only.
- Cut-offs. Agree in writing when a change is routine, when it is late, and when it is only possible if a spare vehicle exists.
- Costs are part of the approval. The owner approves the change and its cost consequence in the same step, not a week later on the invoice.
- One log. Every change gets a line: who asked, who approved, when drivers acknowledged, and what it changed on the bill.
Event transportation management starts with one schedule owner
Most event transport plans are strong on vehicles and weak on authority. The run sheet lists the Coaster for the gala dinner and the Land Cruiser for the chief guest, but it does not say who is allowed to move them. That gap is where late changes go wrong.
The schedule owner is usually the client’s conference transport coordinator, or on a family event, the one relative everyone already phones. What matters is not seniority but reachability and a clear mandate. The owner should be able to say yes or no without checking with three other people, and should be awake and on a charged phone for every operating hour.
What the owner holds
- The master run sheet, with a version number and the time it was last changed.
- The passenger manifest per movement: names, pickup points, flight numbers where relevant, and a contact number for each group lead.
- The approved vehicle list, with the operator’s reference for each vehicle and driver.
- The budget envelope for changes, or a named person who can extend it.
What the owner is not
The owner is not a dispatcher. They should not be messaging drivers directly, however tempting that is at 11pm when a speaker’s flight lands early. A driver who receives instructions from two directions will follow whichever arrived last, and the operator’s dispatcher then plans the next job around a vehicle that is no longer where the plan says it is.
If a deputy covers night shifts or a second venue, write the handover time into the run sheet. A line such as (example names) “Sara owns the schedule until 18:00 PKT, then Imran” is a rule. “Either of us can approve” is how two conflicting approvals reach the dispatcher within the same ten minutes.
Request, approve, broadcast: the three roles
Every late change passes through three hands. Naming them in the transport brief, before the first guest lands, removes most of the arguments later.
| Role | Typically held by | May do | May not do |
|---|---|---|---|
| Requester | Speakers’ handlers, delegation liaison, hotel desk, family group leads, venue manager | Ask for a change through the single agreed channel, with the details the owner needs | Contact drivers to move a vehicle, or promise a guest a pickup that has not been approved |
| Approver (schedule owner) | Client transport lead or named deputy on shift | Accept, refuse or modify the request; accept the cost consequence; update the master version | Brief drivers directly, except in a genuine safety emergency |
| Broadcaster (dispatcher) | The transport operator’s dispatch desk | Re-plan vehicles, send the change to each affected driver and marshal, collect acknowledgements | Act on a change that has not come from the approver, however senior the person asking |
The last cell is the one that gets tested. A minister’s protocol officer or the bride’s uncle will ring a driver directly. The driver’s correct answer is polite and short: the request is passed to dispatch, and the car stays on its current job until dispatch confirms otherwise. Brief the client’s senior people on that answer too, so nobody takes it as rudeness.
The single request channel
Pick one channel for requests and publish it on the guest information sheet: a named phone number, a shared inbox, or a form. What it must not be is “any of the WhatsApp groups”. A request should carry enough to act on without a follow-up call:
- Which movement it affects (use the run-sheet reference, not “the morning bus”).
- What should change: time, pickup point, drop point, passenger count, vehicle.
- Who the passengers are and a reachable contact for their group lead.
- Why, in one line. “Speaker’s flight now lands at 14:40” (an example) is useful; “plans changed” is not.
The why matters because it tells the owner whether the change is final or likely to move again. A flight that has slipped once often slips twice.
Cut-off times for changes
A cut-off is not a refusal. It is an agreement about what kind of change is still cheap. Before a vehicle is assigned, moving a pickup costs a keystroke. Once the driver has been rostered, has planned fuel and has another job booked afterwards, the same move can cost a second vehicle.
The windows below are an example framework to adapt with your operator, not a published iDrive tariff or rule. Your contract and the operator’s written terms decide what actually applies.
| Window (example) | Status of change | What the owner should expect |
|---|---|---|
| More than 72 hours before the movement | Routine | Re-planned in the next schedule version; cost change, if any, shown on the revised quote |
| 72 to 24 hours before | Planned change | Usually workable; vehicle size changes depend on what the operator can still source |
| 24 to 4 hours before | Late change | Driver and vehicle may already be committed; extra hours, repositioning or a substitute vehicle become likely |
| Under 4 hours, or on the day | Live change | Handled only if a spare vehicle or slack exists; the owner accepts that it may be refused |
Use one clock
Write every cut-off and every log entry in Pakistan Standard Time. PKT is UTC+5 and, according to the record of Pakistan Standard Time, Pakistan has not used daylight saving since 2009. That matters when the client’s head office is in London, which moves between four and five hours behind Pakistan across the year. A cut-off written as “Thursday 6pm” with no zone will be read two ways, and the difference decides whether the change was on time.
Last minute shuttle changes: pushing a change to every driver and marshal
An approved change is worthless until the right drivers have it, have understood it and have said so. This is the part that group chats handle worst. A message in a busy group is “delivered” to forty phones and read properly by nobody in particular.
The broadcast sequence
- Approver sends the change to dispatch in the agreed format, quoting the movement reference and the new schedule version number.
- Dispatch re-plans and identifies every affected vehicle, including knock-on effects. Moving the 09:00 pickup to 09:45 may make the same Hiace late for its 11:00 job.
- Dispatch messages each affected driver individually, with the new time, the pinned pickup point and the passenger contact.
- Each driver acknowledges with a read-back, not a thumbs-up: “Coaster 2, Serena main porch, 09:45, 22 pax, contact Ali” (an example).
- Marshals and gate staff get the same change, because they are the ones directing guests to the kerb.
- Dispatch confirms to the owner that all acknowledgements are in, and the owner marks the log line closed.
If one driver has not acknowledged within an agreed time, dispatch phones. Silence is not consent; it is usually a driver on the road with the phone face down, which is exactly where you want it.
Plan for the network going quiet
The UK government’s FCDO safety and security advice for Pakistan says protests can start with little warning, that major road networks in and around cities may be shut or blocked during unrest, and that mobile data and internet connectivity may be cut without warning. Two consequences for event transport:
- Keep a voice-call and SMS fallback for every driver and marshal. An app-only broadcast plan fails the moment data drops.
- Pre-agree an alternative route and a secondary pickup point for each venue, so a closure triggers a known Plan B rather than a fresh round of improvisation.
For events in the capital, the Islamabad Capital Territory Police site lists the Islamabad Traffic Police helpline, 1915; put it on the dispatch sheet alongside the venue’s own security contact.
Check the destination itself
If any movement leaves the main cities, check the FCDO travel advice for Pakistan before the programme is fixed. At the time of writing it advises against all travel to Balochistan, to parts of Khyber Pakhtunkhwa including Peshawar city, and to areas within 10 miles of the Afghan border or the Line of Control. It advises against all but essential travel to further areas, including the rest of Azad Jammu and Kashmir and parts of Sindh and Punjab. A late change that re-routes a delegation into one of those areas is not a scheduling question, and it should go back to whoever owns the client’s security decisions.
Event transportation logistics: what late changes do to the bill
Late changes rarely cost what people expect. The visible part is the extra hour. The larger part is usually what the change does to the vehicle’s next job and the driver’s rest. When the owner approves a change, they should see its likely cost category at the same moment, even if the exact figure comes later on a revised quote.
| Type of change | Where the cost usually comes from | Question the owner should ask before approving |
|---|---|---|
| Pickup moved later | Waiting or extra hours; the vehicle may miss its next assignment | Is this vehicle booked straight after, and who covers that job? |
| Pickup moved earlier | Driver may need to start before the rostered time; possible repositioning the night before | Is the driver’s rest period still respected? |
| Extra passengers | Upsizing from an MPV to a Hiace or Coaster, or adding a second vehicle | Is a larger vehicle actually free, or are we splitting the group? |
| New pickup point | Dead mileage and time across the city | Could the group come to an existing pickup point instead? |
| Event overruns | Overtime for every vehicle held at the venue | Release some vehicles and hold only what the late group needs? |
| Movement cancelled late | The operator may still have committed the vehicle and driver | What do the written cancellation terms say for this window? |
Overtime and driver hours
Driver fatigue is the cost nobody itemises. A driver who has done the airport run at dawn, the venue shuttles all day and then waits for a dinner that overruns by two hours should not also do the late return to Rawalpindi. A good operator will swap drivers rather than stretch one, and that swap is a real cost. Approving the overrun means approving the swap.
Put the rules in the contract, not the chat
Cut-offs, waiting time, overtime and late cancellation belong in the written agreement. For bookings made through iDrive, read the iDrive terms of hire and the cancellation policy before the programme is locked, and ask for anything event-specific to be written into the quote. An operator can only honour a late change if it can still source the vehicle and driver, so treat every late request as a request, not a guarantee.
A transport change log the client can audit
After the event, finance will reconcile the invoice against the original quote, and somebody will ask why the numbers differ. A transport change log answers that in five minutes instead of five days of scrolling through chats. It also protects the operator and the owner: a change that was approved and acknowledged is visibly different from one that was never passed on.
Fields worth keeping
| Field | Example entry |
|---|---|
| Log number and schedule version | CH-017, run sheet v9 to v10 |
| Time received (PKT) | Wed 21:12 |
| Requested by | Delegation liaison, by the agreed request number |
| Movement affected | M-14, hotel to venue, Thursday 08:30 |
| Change | Pickup 08:30 to 07:45; passengers 18 to 23 |
| Window | Late (under 24 hours) |
| Approved by and time | Transport lead, 21:25 |
| Cost consequence | Second vehicle added; revised quote to follow |
| Drivers and marshals acknowledged | Both drivers and gate marshal by 21:50 |
| Outcome | Ran as changed; closed |
The entries above are illustrative. The discipline is the point: the log is written as the change happens, not reconstructed afterwards.
Keep the personal data lean
A change log is tempting to fill with passport numbers and guests’ private phone numbers. It does not need them. If the client or organiser is UK-based, the ICO’s guidance on data minimisation sets the test: personal data should be adequate, relevant and limited to what is necessary for the purpose. For a transport log, a group lead’s name and a work contact usually meet it. The same regulator’s guidance on storage limitation expects a retention period you can justify, so decide when the manifest and log are deleted or anonymised once the invoice is settled.
Drivers need less still: pickup point, time, passenger count and one contact. Keep the log in one place, owned by the schedule owner. If you book through iDrive, copy each booking reference from your iDrive customer account onto the matching log lines, so finance can match every change to a booking without asking anyone.
What the conference transport coordinator does on the day
With the rules agreed, the coordinator’s day becomes a loop rather than a scramble. A workable rhythm:
- Morning check. Confirm with dispatch that every vehicle for the first wave has checked in, and that the run-sheet version on the dispatch desk matches the owner’s.
- Flight watch. For airport movements, check arrivals against the manifest in batches rather than reacting to each message from a delayed guest.
- Batch non-urgent changes. Collect routine requests and send them to dispatch at set times, for example on the hour. Live changes still go immediately.
- Venue walk. Before each big movement, stand at the pickup point. The best-planned porch is useless if the hotel has put a floral delivery van in it.
- End-of-day reconciliation. Close open log lines, note overtime, and issue the next day’s run sheet with a new version number.
Guest communication should also come from one voice. If a shuttle moves, the guest information sheet or the event app changes once, and group leads repeat that version. For large family events with guests arriving from abroad, our sister service Pakistan Taxi, which runs on the iDrive network, has a practical guide to building a pickup manifest for an event with several vehicles that pairs well with the change rules here.
When the three-role rule bends
Two situations justify short-cutting the chain, and both should be written into the brief so nobody invents a third.
- Immediate safety. A driver who meets a blocked road, a crowd or an incident acts to keep passengers safe first and reports to dispatch as soon as it is safe to do so. The log records it afterwards.
- Owner unreachable during a live change. If the owner and deputy cannot be reached within an agreed time, dispatch may make the least-cost change that keeps passengers moving, and flag it for approval. The brief should name that time and set a cost ceiling for it.
Everything else waits for the owner.
Setting this up with iDrive
If you are planning conference shuttles, delegation movements or wedding convoys, start with the iDrive events and weddings booking page and send the draft run sheet, the named schedule owner and your proposed cut-offs with the enquiry. Quotes are prepared against the programme you describe, and vehicle availability is confirmed by the operator, so the more complete the brief, the fewer late changes you will need. For single journeys around the event, the iDrive booking page handles individual requests.
Questions people ask
Who should own the transport schedule at a conference?
One named person on the client side, usually the conference transport coordinator, with a named deputy for set hours. The operator’s dispatcher runs the vehicles, but approval of changes stays with the client’s owner.
Can the transport operator refuse a late change?
Yes, if no suitable vehicle or rested driver is available. A late change is a request. Agree cut-off windows in advance so everyone knows which changes are routine and which depend on spare capacity.
Why not just use one WhatsApp group for all drivers?
Group messages get lost, and a reaction is not an acknowledgement. Send each change to the affected drivers individually, ask for a read-back, and keep voice and SMS as a fallback in case mobile data is disrupted.
