A workable corporate travel cancellation policy for ground transport in Pakistan answers four questions before anyone needs them: who may cancel on the company’s behalf, by what deadline, what a late cancellation costs, and where the refund lands in the ledger. Most company policies answer them for flights and hotels and say nothing about the car. That is where money leaks: a driver held for a cancelled site visit in Lahore, a refund that returns to a card nobody reconciles, a return leg left live after the outbound was scrapped.
The short version: name one or two authorised cancellers per cost centre, cancel through the booking record rather than by phone to the driver, work to the cancellation window shown on each booking confirmation, treat every leg of a multi-city itinerary as its own line, and record the refund against the original cost centre with the booking reference. When a trip is cancelled for safety, the duty-of-care record matters as much as the refund. The rest of this guide turns that into a desk procedure your team can follow on a bad Monday.
The decision summary for a travel desk
Before the detail, here is how the common cancellation scenarios sort out. Treat the right-hand columns as the questions your policy must answer, not as fixed outcomes; the operative terms are always the ones on the individual booking.
| Scenario | Who should act | Cost exposure to check | What finance needs |
|---|---|---|---|
| Meeting postponed, date known | Travel desk, after line-manager approval | A change is not a cancellation, but change terms are set case by case; confirm first | Amended confirmation, same reference |
| Trip scrapped more than two days out | Travel desk | Check the free-cancellation window on the confirmation | Refund confirmation and date released |
| Trip scrapped inside the window | Travel desk, with budget holder sign-off | Late-cancellation fee as stated on the booking | Fee posted as a cost, refund balance recorded |
| One leg of a multi-city trip dropped | Travel desk | Depends whether legs are separate bookings or one | Leg-level record, not a trip-level note |
| Cancelled for safety (advisory change, unrest, flooding) | Security lead or duty-of-care owner, then travel desk | Ask whether the operator is cancelling on its side | Risk note filed with the refund |
| Traveller simply did not turn up | Nobody can cancel after pick-up time | Treat as a sunk cost | Incident note explaining the loss |
Who is authorised to cancel on the company account
If the traveller, their PA, the host office in Karachi and the travel desk can all cancel, you will eventually get two cancellations, one reinstatement and an argument about who owes the fee.
Set three roles, not one
- Requester — the traveller or their manager. They can ask for a cancellation, never make one.
- Authorised canceller — a named travel desk officer (and one deputy) who holds the booking reference and the email address the booking was made under. Only this person contacts the booking platform.
- Budget holder — signs off any cancellation that will cost money, meaning anything inside the late-cancellation window or any bespoke booking.
The reason for tying authority to the booking email is practical rather than bureaucratic. On iDrive, a cancellation request is raised from the booking page using the reference and the booking email, or by replying to a booking email quoting the reference. Whoever controls that inbox controls the booking. If bookings are made under a shared desk mailbox and managed through the iDrive customer account, authority stays with the desk even when staff change.
What the traveller should never do
Telling the driver “don’t come” by phone is not a cancellation. It creates no record, starts no refund and, if the driver waits at the pick-up point, is likely to be treated as a no-show. Put that sentence in the policy in plain words.
Cancellation windows and cancellation fees for company bookings
The single most useful line in any cancellation policy is the deadline. Everything else follows from it. For ground transport the deadline is measured backwards from the scheduled pick-up time, not from the date of booking and not from the end of the journey, and in Pakistan that clock runs on Pakistan Standard Time. A desk in London or Dubai that works in its own local time will misjudge the window by several hours; say in the policy which clock applies.
A note on status before quoting any figures. iDrive’s cancellation policy is currently published as a draft for legal review. It is marked as not in force and not a commitment, and the terms that govern a specific booking are the ones shown when that booking is made. With that caveat, the draft sets out the structure a desk should expect and plan around:
- A cancellation request received more than 48 hours before pick-up is proposed as free, with everything paid refunded.
- A request received 48 hours or less before pick-up is proposed to carry a fee of 10% of the total booking value, with the remaining 90% refunded.
- Once the pick-up time has passed, or the passenger is a no-show, the draft provides for no refund.
- Some services may carry a longer notice period shown at booking; the draft flags wedding convoy and security bookings as a case under review.
- What counts is when the request is received, not when someone replies to it.
A worked example (hypothetical)
Suppose, as an illustration only, a company books a chauffeured day in Islamabad for a visiting auditor, and the audit is pulled at 10:00 PST on the day before a 09:00 pick-up. That is 23 hours out, well inside a 48-hour window. Under the structure in the draft, the company would lose one tenth of the booking value and recover the rest. Had the desk sent the request at 08:00 two days before the pick-up day, 49 hours out, it would have been outside the window. The lesson: the budget holder’s sign-off must never be what delays the request. Send first, record the approval second.
Write your internal deadline earlier than the supplier’s
Set an internal cut-off at least a working day ahead of the supplier window. It absorbs weekends, public holidays in either country, time-zone gaps and the hour it takes to find the booking reference. If the platform’s free window is 48 hours, an internal rule of “request by 17:00 PST three days before pick-up” leaves room for everything that normally goes wrong.
Partial cancellations in multi-leg itineraries
A typical programme might be an Islamabad airport arrival, two days of meetings, an intercity run to Lahore and a departure from Allama Iqbal International. When one meeting falls away, only part of that changes, and the policy has to say how to cancel it without breaking the rest.
Know how the trip was booked
The first question is whether each leg is its own booking with its own reference, or one booking covering several legs. It matters because of the clock. The iDrive draft says that for a multi-day hire or multi-leg trip, the window runs from the pick-up time of the first leg unless the booking confirmation says otherwise. On a single multi-leg booking, dropping day four may therefore be treated as a late change as soon as day one has started.
For that reason, consider booking legs separately wherever the itinerary is not fixed. Separate references give each leg its own window and make a partial cancellation a clean, single-line event. Where a single multi-leg booking is the better choice (a driver kept for the whole week, for instance), write the plan B into the request: ask for a change to the booking rather than cancellation of a leg, and get the revised figure in writing before agreeing it.
Change, credit or re-quote: what to do with a cancelled booking
Travel managers used to airline credits often expect a cancelled car booking to leave a voucher behind. Do not assume it. The iDrive draft refund policy describes refunds as going back through Stripe to the original payment method, and says a refund cannot be sent to a different card, a bank account or a third party. It does not describe a credit balance. So the real choice is between two routes:
- Change the booking. If the trip has moved rather than died, ask for a new date, time or pick-up point before cancelling. The draft is explicit that a change is not a cancellation. How changes are priced, especially inside 48 hours, is still marked as undecided in the draft and is handled case by case, so get the position in writing first.
- Cancel and re-quote. If the new trip is materially different (another city, another vehicle class, different passengers), cancel the original and request a fresh quote through the iDrive booking page. Treat the new quote as a new purchase with its own approval; a rebooked journey is not guaranteed the same vehicle or price.
The policy should tell the desk to prefer the change route whenever the traveller, route and vehicle are the same. It keeps one reference and one invoice trail, and avoids a fresh approval cycle.
Business trip cancelled: recording the refund against the cost centre
When a business trip is cancelled, the refund is only half the job. A refund that finance cannot match to anything is worse than no refund, because someone will spend an afternoon looking for it. Build the record at the moment of cancellation, not when the card statement arrives.
The minimum record
| Field | Why it matters |
|---|---|
| Booking reference | The only key that links the platform, the card line and your ledger |
| Cost centre and project code | So the refund reverses the original charge rather than landing in suspense |
| Traveller name and trip purpose | For audit trails and repeat-cancellation reporting |
| Request time (PST) and requester | Proves whether the request was inside or outside the window |
| Amount paid, fee retained, amount refunded | The fee is a cost; the balance is a recovery. Post them separately. |
| Payment currency and card | Refunds return to the original method in the original currency |
| Refund release date | Starts the clock for chasing a missing statement credit |
Currency and timing
If the company paid in pounds, dirhams or dollars, the draft refund policy says the refund reverses the payment in the currency charged, and that the card issuer’s own exchange-rate or foreign-transaction charges are outside iDrive’s control. On a corporate card, that means the pound amount returned can differ slightly from what your expense system expects if the issuer converted at a different rate. Reconcile to the card statement, not the original quote.
The draft separates two stages: iDrive releasing the refund, and the bank posting it. It does not yet commit to a release time. Your policy should therefore not promise travellers a date. It should instead set a chasing rule, for example: “If a released refund has not appeared on the card statement after the period the refund email states, the desk raises it with the supplier quoting the reference.”
Duty-of-care checks when a trip is cancelled for safety
Safety cancellations are the ones an auditor, insurer or board will ask about later, so they need the fullest record.
Check the official advice for every place on the itinerary
For UK-based organisations, the reference point is the FCDO travel advice for Pakistan. It advises against all travel to Balochistan, to a long list of Khyber Pakhtunkhwa districts (including Peshawar and Swat), to within 10 miles of the Afghanistan border and the Line of Control, and to the Karakoram Highway between Mansehra and Chilas. It advises against all but essential travel to further districts, to Azad Jammu and Kashmir, to Dera Ghazi Khan and to Sindh from Nawabshah northwards. The lists change, so check the live page on the day of decision, not a copy saved in the policy. The FCDO also warns that travel insurance could be invalidated by travelling against its advice, which is a direct reason for a travel desk to cancel rather than “wait and see”.
US-linked staff should also be checked against the US State Department Pakistan travel advisory, which sets an overall level for the country and a stricter “Do not travel” level for some provinces. The two governments draw their lines differently. A multinational policy should state which advice governs, or require the stricter of the two.
Short-notice disruption
The FCDO’s safety and security guidance for Pakistan warns that during protests or unrest, major roads in and around cities may be shut or blocked and mobile data and internet may be cut without warning. The main advisory page, updated on 22 September 2026, also flags planned protests in Islamabad, Rawalpindi, Peshawar and other cities, with routes and timings liable to change at short notice. The safety guidance calls local driving standards erratic, especially at night. That has a quiet policy consequence: if an evening intercity leg is cancelled for safety, the replacement should be a daytime journey, not the same leg an hour later.
When the operator cancels instead
The iDrive draft lists weather, flooding, landslides, road closures, protests, security incidents and civil disturbance among the reasons iDrive may cancel a booking itself, and says an operator-side cancellation carries no fee whenever it happens, with a full refund or, where possible, a replacement offered first. If a route becomes unsafe close to pick-up, ask whether the booking is being cancelled on the operator’s side before you cancel on yours. The distinction may decide whether the late fee applies at all.
The duty-of-care record
ISO 31030:2021, the travel risk management guidance for organisations, treats travel risk as something an organisation manages through policy and a documented programme, not ad hoc calls. For a cancelled ground journey, that means a short file note kept with the refund record:
- Which advisory or event triggered the decision, with the date and a link to the source.
- Who decided, and at what time (PST and head-office time).
- Whether the traveller was already in Pakistan, and how they were contacted.
- What replaced the journey, if anything: a different route, a daytime run, a virtual meeting.
- Whether the cancellation was made by the company or by the operator.
The travel desk cancellation workflow, step by step
Put the following on one page and pin it where the desk works. It is written so that someone covering for a colleague can run it without context.
- Receive the request. Log who asked, when (PST), and why. A cancel employee travel booking request from anyone other than the traveller’s manager or the security lead goes back for confirmation.
- Pull the booking. Find every reference attached to the trip. Note the pick-up time of each leg and the cancellation terms shown on each confirmation.
- Ask: change or cancel? If the traveller, route and vehicle stay the same and only the timing has moved, request a change. Otherwise, cancel.
- Check the clock. Compare the request time with the window. If a fee will apply, alert the budget holder at once, but send the request now; approval can follow within the hour.
- If safety is the reason, check the FCDO (and State Department, where relevant) pages, record the trigger, and ask whether the operator is cancelling on its side.
- Send the request from the booking inbox or the customer account, quoting the reference and listing any legs that stay live.
- Tell the traveller that the journey is cancelled, and tell them not to contact the driver about it.
- Record the outcome when the decision arrives: approved amount, any fee, refund release date. Accept an offer only if it matches your expectation; otherwise ask for another look with reasons.
- Post to finance with the reference, cost centre, fee and refund as separate lines.
- Close the ticket only when the refund appears on the card statement, or when the fee is confirmed as the final cost.
Group moves need a variant of this. When the cancellation is a conference or delegation rather than a single traveller, the same steps run per vehicle, and the arrival-to-departure plan needs revisiting as a whole. Our sister service Pakistan Taxi, part of the iDrive network, publishes a planning guide to conference delegate transport from arrival to departure that is useful for mapping which vehicles a cancelled session actually releases.
Clauses worth writing into the policy
The wording below is an example to adapt, not legal advice. Have your own HR and legal teams approve the final text.
Authority. Only the travel desk may cancel or change a ground transport booking made on the company account. Travellers must not cancel by contacting the driver.
Deadline. Requests to cancel must reach the travel desk by 17:00 Pakistan Standard Time three working days before the first pick-up. Requests received later may incur supplier fees, which are charged to the requesting cost centre.
Change first. Where only the date, time or pick-up point has changed, the desk will request an amendment instead of a cancellation.
Safety. The company will cancel any journey to or through an area where the FCDO advises against all or all but essential travel, unless the security lead has approved it in writing as essential. Safety cancellations are never charged to the traveller’s team.
Records. Every cancellation is logged with the booking reference, cost centre, amounts and, for safety cancellations, the source of the advice.
If you are setting up ground transport for staff in Pakistan and want these rules built into how journeys are requested, start with iDrive’s business travel car service, check the terms shown on each confirmation, and run the cancellation workflow above from day one.
