Preferred supplier policy for business travel in Pakistan

A preferred supplier policy for business travel in Pakistan should do one thing well: tell a traveller, before they land, which journeys must go through the company’s approved transport channel and which they may arrange themselves. The short version is this. Airport arrivals and departures, intercity road journeys, any journey after dark, and every journey made by a first-time or foreign visitor go through the mandated travel booking channel, pre-booked with a named driver and vehicle. Short daytime hops inside the main cities, for staff who live in Pakistan and know the city, can be left to the traveller’s judgement. Anything outside those lines is an exception, and exceptions get logged, not argued about at month-end.

That split is not arbitrary. The UK government’s own advice for Pakistan tells visitors to avoid street taxis, e-taxis and online taxi apps, and to use reputable, licensed companies where you call and the operator assigns the driver. A policy that ignores that sentence will be hard to defend if something goes wrong. The rest of this guide sets out the journey categories, the exception rules, the expense treatment of out-of-policy bookings, and how to review whichever supplier you appoint.

Why a preferred supplier policy for business travel matters more in Pakistan

In most markets a travel policy is mainly a cost control. In Pakistan it is also a duty-of-care document, and the order of those two priorities should be written into the first paragraph of the policy itself.

Three facts shape the policy:

• The official advice is specific about taxis. The FCDO’s Pakistan safety and security page says to avoid street taxis, e-taxis and online apps for taxi services, and to use reputable, licensed companies where you call for a taxi and the operator contacts the driver. It also names business travellers among the groups seen as targets, and advises varying routes and timings for regular journeys.
• Some destinations are off the table for ordinary business trips. The FCDO travel advice for Pakistan advises against all travel to Balochistan, most of Khyber Pakhtunkhwa including Peshawar city, the Afghanistan border area and the area near the Line of Control, and against all but essential travel to further districts, including Azad Jammu and Kashmir, parts of Sindh north of Nawabshah and Dera Ghazi Khan. The US State Department advisory places Pakistan at “Reconsider Travel” with its own do-not-travel areas. These lists change; the policy should link to the live pages rather than copy them.
• The ride-hailing market has shifted. Careem announced in June 2025 that it would suspend its ride-hailing service in Pakistan from 18 July 2025, as Dawn reported. Travellers returning after a gap may find the app they relied on is no longer an option for rides, which is one more reason to decide the channel for them.

There is also the employer’s side. UK health and safety law treats work-related road journeys like any other work activity. The HSE’s guidance for employers on work-related road safety frames the assessment as safe journey, safe driver, safe vehicle, and lists fatigue, distraction and time pressure among the hazards. A traveller hailing whatever car arrives at 2am outside Allama Iqbal International is the opposite of an assessed journey.

Journeys that must use the mandated travel booking channel

Write these as a closed list. If a journey matches any line, the traveller books through the approved channel or asks for an exception before travelling.

1. All airport transfers. Arrivals are the moment a visitor is most tired, most visible and least oriented: luggage, a phone that may not have a local SIM yet, and a crowd of drivers at the kerb. Departures matter too, because a missed flight after a long meeting day is a cost the company pays twice.
2. All intercity road journeys. Islamabad to Lahore, Lahore to Faisalabad, Karachi to Hyderabad: these are hours on the road, where driver fatigue and vehicle condition are the whole risk. A pre-booked car lets you check both in advance.
3. Any journey that starts or ends after dark. The FCDO notes that local driving standards are erratic, especially at night, and that road quality off the major motorways is variable.
4. Every journey for a first-time or foreign visitor for the whole trip, not just the first day.
5. Journeys carrying a senior executive, a client or a group, where the reputational cost of a no-show is high.
6. Any journey to or through an area on the FCDO’s advise-against lists, which in practice should not reach the transport stage without written sign-off from your security lead. If the FCDO advises against all travel to a place, a transport booking is not the control that makes the trip acceptable.

What the traveller should receive for every mandated journey: the driver’s name and phone number, the vehicle make, colour and registration, the pickup point in plain words (not just a map pin), and a named contact at the supplier who answers outside office hours. If your supplier cannot send that before the day, it is not the right supplier for this list.

For corporate accounts, iDrive’s business travel car service in Pakistan is set up around exactly this kind of pre-booked, documented journey; quotes are confirmed by the operations team rather than generated instantly, and a vehicle is only committed once a booking is accepted.

Where ride hailing on business trips can be acceptable

A policy that bans every app ride will be ignored by resident staff, and ignored rules are worse than no rules because nobody reports the breach. The better approach is a narrow, explicit permission.

A reasonable permitted zone looks like this:

• The traveller is a resident employee, or a returning visitor your security lead has cleared for independent movement.
• The journey is inside one city (Islamabad and Rawalpindi, Lahore or Karachi are the usual cases), in daylight, and between known addresses: office, hotel, client premises.
• The traveller shares the trip with a colleague or the travel desk, and sits in the back.
• No journey in the mandated list above is being substituted.

Be honest in the policy wording about what this permission is. The FCDO’s advice to visitors is to avoid online taxi apps altogether, so allowing them for resident staff on short daytime hops is a risk decision your organisation is taking, not something the official advice endorses. Record who made it and when it will be reviewed.

Many companies also allow app rides as a fallback when the booked car is late beyond an agreed threshold. That is fine, provided the fallback is treated as an exception (next section) and the late supplier is recorded against its service levels.

Decision table: which channel for which journey

Emergency exceptions: a rule finance can enforce

Exceptions are where most policies collapse, usually because they are written as “use your judgement” and audited as “why didn’t you follow the policy?” Give the traveller a fixed sequence instead.

1. Safety first, always. If a traveller feels unsafe, they leave, by whatever means is safest in the moment. No policy clause overrides that, and the policy should say so in bold.
2. Call the supplier’s out-of-hours line if the problem is a late or missing car. Give them a fixed window before moving on. Thirty minutes for an airport pickup is one example; set your own number and publish it.
3. Call the travel desk or duty manager if the supplier cannot recover the journey. The duty manager can authorise an alternative on the spot.
4. Use the least risky alternative available: a hotel-arranged car, an airport’s official transport desk, or, as a last resort, an app ride with the trip shared.
5. Log the exception within 24 hours using a short form: date, time, planned journey, what failed, what was used instead, cost, who authorised it.

The log is the part that makes the rule enforceable. A logged exception is paid without argument. An unlogged one is queried. Over a quarter, the log also tells you whether the failure is the traveller, the supplier or the policy itself.

Out of policy bookings and expense claims

Finance needs three categories, not two. “In policy” and “out of policy” is too blunt, because it treats a traveller who took an app ride after a two-hour airport no-show the same as one who simply could not be bothered to book.

A few practical rules keep claims clean:

• Receipts must show date, time, pickup and drop-off, and amount. App receipts usually do; cash payments to a hotel-arranged driver usually do not, so the traveller should ask for a written receipt or note the details straight away.
• Record the currency and the conversion. Claims mixing Pakistani rupees, sterling and card charges are the ones that take longest to settle. Agree whether you reimburse at the card statement rate or a published rate, and state it.
• Do not reward the out-of-policy ride by paying it faster. Supplier invoices for pre-booked journeys should be settled centrally, so the traveller never needs to claim them at all. That alone removes most of the incentive to go around the system.
• Keep the tax position with your payroll team. For UK employers, HMRC’s position is set out on GOV.UK in its guidance on employer travel expenses and benefits and on employee tax relief for travel. How a particular journey is treated is a question for your payroll or tax adviser, not the travel policy.

Travel policy compliance starts before the visitor flies

The breach that matters most is the one at the airport on day one, and it usually happens because nobody told the traveller the rule. So the policy has to reach the visitor before departure, in a form they will actually read on a phone in an arrivals hall.

What to send, and when

• At approval: a one-page summary, not the full policy. Four lines: which journeys are pre-booked for you, when you may use an app, who to call if a car fails, and how to claim.
• Five to seven days out: the confirmed transport schedule with booking references, and a reminder to check the live FCDO page for any change since the trip was approved.
• The day before: driver and vehicle details for the airport pickup, the meeting point in words, and the out-of-hours number saved as a phone contact rather than buried in a PDF.
• On arrival: a short message from the travel desk confirming the car is at the airport, or telling the traveller what to do if it is not.

Visitors who are not your employees

Clients, contractors and guest speakers are often the least briefed and the most exposed. If your company is paying for their trip, the transport part of the policy should apply to them in full; there is little point protecting your own staff at Islamabad arrivals and leaving the keynote speaker to find a car alone. Say so in the invitation letter, and book their journeys centrally.

Returning Pakistani diaspora staff deserve a specific line too. They may know Lahore far better than the travel desk does, and resent being told how to get home from the airport. The honest framing is that the rule protects the company’s duty of care, not their local knowledge, and that a permitted-zone exemption for resident-style movement can be granted by name.

For operational detail on stitching an airport pickup onto a meetings day, our sister service Pakistan Taxi has a practical guide to combining an airport pickup with business meetings in Pakistan, written for the traveller rather than the policy owner.

Choosing and reviewing the preferred supplier

A preferred supplier earns the title by being measurably better than the alternative the traveller would otherwise use. Put the measures in the contract or service schedule, then check them.

Before appointment

• Dispatch model. Does the supplier assign a named driver and vehicle before the day, in line with the FCDO’s “call and the operator contacts the driver” description, or does it simply forward your request to whoever is free?
• Coverage. Which airports and cities can it serve directly, and where does it rely on partners? Ask for the list in writing.
• Vehicle standards. Age, condition and class of vehicle by booking type. An executive sedan for a single visitor is a different specification from a van for a delegation with equipment.
• Driver hours. How the supplier prevents the same driver doing an early airport run, a full city day and a late intercity return. HSE’s safe-driver principle applies whether the driver is your employee or the supplier’s.
• Out-of-hours contact. A real person, reachable by phone and messaging, around the clock on travel days.
• Invoicing. Central monthly invoicing with booking references that match your travel records, so reconciliation is a lookup, not a detective job.

Quarterly review

Keep the review short and data-led. Five numbers usually tell the story:

1. On-time pickup rate against the agreed window, split by airport and city.
2. Failed or substituted journeys, taken straight from your exception log rather than the supplier’s own report.
3. Details-sent-in-time rate: the share of bookings where driver and vehicle details reached the traveller by the agreed deadline.
4. Out-of-policy spend as a share of total ground transport spend. If it is rising, find out whether travellers are avoiding the supplier or the policy.
5. Traveller feedback, collected with one or two questions after each trip, not an annual survey nobody fills in.

Agree in advance what happens when a number misses: a remediation plan at the first miss, a formal review at the second, and the right to move volume to a second supplier after that. Keeping a secondary approved supplier on the list, even at low volume, is cheap insurance for the day the first one cannot cover a city.

Putting the policy to work

A workable rollout takes weeks, not months, if you keep the scope tight:

1. Write the closed list of mandated journeys and the permitted app-ride zone, and have security and finance both sign it.
2. Publish the one-page traveller summary and the exception form.
3. Appoint the preferred supplier and a secondary, with the service levels above.
4. Set up a corporate account so bookings, traveller details and invoices sit in one place. iDrive business customers can create an account for the booking team, and travellers can follow their confirmed journeys in the iDrive app, which is for pre-booked journeys rather than street hailing.
5. Run the first quarterly review after three months, and adjust the permitted zone if the log shows it is too tight or too loose.

When a trip is approved, the travel desk can request the journeys through iDrive’s booking page, starting with the airport leg, for example an Islamabad airport transfer for a visitor landing for meetings in the capital. Availability and the final price are confirmed by the operations team before the booking is accepted.

Questions people ask

Should visitors to Pakistan be allowed to use ride-hailing apps on company trips?

The FCDO advises visitors to avoid online taxi apps and use licensed companies where the operator assigns the driver. A defensible policy therefore mandates pre-booked transport for visitors and limits app rides to resident staff on short daytime journeys within a city.

What counts as an emergency exception?

Any situation where the traveller feels unsafe, or where the booked car has failed beyond the published waiting window and the supplier cannot recover it. The traveller uses the safest available alternative and logs it within 24 hours.

Can we mandate one supplier for every city in Pakistan?

You can, but confirm in writing which cities the supplier serves directly and keep a secondary supplier approved. Trips to areas on the FCDO advise-against lists need security sign-off before any transport is booked.

How should out-of-policy rides be treated in expense claims?

Separate logged exceptions from genuine breaches. Pay logged exceptions on normal approval, query unlogged out-of-policy rides, and escalate repeat cases. Settle supplier invoices centrally so travellers rarely need to claim ground transport at all.