When a collection fails at a Pakistani airport, the risk is rarely the delay itself. It is the forty minutes that follow, when a tired employee with a laptop bag stands outside arrivals, a phone without data, and a queue of unofficial drivers offering a ride. Good corporate travel risk management in Pakistan decides that forty minutes in advance. The short version: one named person owns the incident from the moment the traveller cannot see their driver; the traveller stays inside the terminal and does not accept an unbooked ride; the supplier gets ten minutes to fix it; the local host or a second pre-approved operator gets the next ten; and by thirty minutes a replacement car is moving or the traveller is waiting somewhere controlled. Everything below is how to build that plan, who holds each step, and what to record afterwards so the same failure does not happen twice.
Corporate travel risk management in Pakistan: why a missed pickup is a risk event
In most markets a driver who does not turn up is an annoyance. In Pakistan the official advice changes the calculation. The UK Foreign, Commonwealth and Development Office tells visitors to “avoid using street taxis, e-taxis. or online apps for taxi services” and to use only “reputable, licensed companies where you call for a taxi and the operator contacts a taxi driver” (FCDO safety and security guidance for Pakistan). The same page advises against public transport, naming the Metro Bus between Rawalpindi and Islamabad.
Put those two lines together and a missed collection removes the traveller’s approved way out of the airport. The easy improvisations, a kerbside offer, a quick app booking, the airport metrobus, are exactly the options the advice steers people away from. Your plan has to supply a sanctioned alternative before anyone is tempted.
The FCDO also notes that terrorist attacks have taken place in Karachi, Islamabad and Lahore, and records that on 10 October 2024 a suicide attack near Karachi’s Jinnah International Airport killed four people. The US State Department, which rates Pakistan at Level 3 (reconsider travel), lists “transportation hubs” and “airports” among likely targets and tells travellers to have a plan to depart in an emergency that does not depend on US government help (US State Department Pakistan travel advisory). A missed pickup lengthens exactly that exposure: the wait outside and the approach road.
Check the destination, not just the airport
Before any trip, read the current FCDO travel advice for Pakistan for the onward destination. At the time of writing (the page was updated on 22 September 2026) the FCDO advises against all travel to Balochistan, to Peshawar and a long list of other Khyber Pakhtunkhwa districts, and to within 10 miles of the Afghan border and the Line of Control, and against all but essential travel to Azad Jammu and Kashmir and to Sindh north of and including Nawabshah, among other areas. If an itinerary touches any of those, involve your insurer and security provider before the ticket is issued. Islamabad, Lahore and Karachi are not on those lists.
The missed airport pickup escalation ladder: four owners, one lead
Failed collections go wrong when everyone helps and nobody is in charge. The traveller rings the driver, the assistant in London emails the supplier, the local office sends a colleague, and three cars arrive at once, or none do. A travel incident escalation plan fixes this by naming owners in advance and giving exactly one of them the lead.
| Rung | Owner | What they own | What they must not do |
|---|---|---|---|
| 1 | The traveller | Raising the alarm early, staying in a controlled area, sharing location and flight status | Leave the terminal with anyone not named in the booking |
| 2 | The ground supplier’s dispatch desk | Locating the assigned driver or reassigning the job, and giving a real arrival estimate | Send an unnamed substitute without telling the traveller the new driver’s name and vehicle |
| 3 | The local host (office, hotel or client contact) | A second, pre-approved transport option and a local voice who knows the city | Dispatch a car without telling the incident lead, which creates duplicate pickups |
| 4 | The UK or regional travel desk (the incident lead) | Decisions, the timeline, the log and every call to the insurer or security provider | Hand the lead to whoever happens to be awake |
The incident lead is rung 4 in the table because they sit furthest from the kerb, but they own the incident from minute zero. The traveller should not have to decide whether to escalate; the lead does that. If your business runs overnight arrivals, the lead role needs a rota with a named deputy, because flights into Pakistan from the UK and the Gulf often land in the small hours.
What each owner needs before the flight lands
- Traveller: the driver’s name and mobile number, the vehicle make, colour and registration if the supplier provides them, the supplier’s dispatch number, the local host’s number, and the incident lead’s number, written on paper as well as saved in the phone.
- Supplier: the flight number, the traveller’s full name as on the passport, and the incident lead’s number with an instruction to call it, not the traveller, if the driver is running late.
- Local host: the itinerary, the name of the second approved operator, and authority to book it without waiting for a purchase order.
- Incident lead: all of the above, plus the traveller’s hotel, the insurer’s assistance line and your security provider’s contact if you have one.
Timed fallbacks: what happens at 10, 20 and 30 minutes
A clock is kinder than judgement at 3am. Start it when the traveller has cleared immigration and customs and is at the agreed meeting point, not when the aircraft touches down. Baggage halls vary, and a clock that starts at touchdown punishes the supplier for a slow belt.
Minute 0 to 10: the supplier’s window
The traveller messages the incident lead with one line: “At meeting point, no driver visible.” The lead, not the traveller, calls the supplier’s dispatch desk. Dispatch has ten minutes to do one of two things: put the named driver on the phone with a believable position, or confirm a reassigned driver with name, vehicle and estimate. A vague “he is coming” does not count as either.
Meanwhile the traveller stays put, keeps bags close and declines ride offers. Assume that anyone who appears knowing their name is not their driver unless the name, phone number and vehicle match what the lead has.
Minute 10 to 20: the second option goes live
If dispatch has not produced a verifiable driver, the lead calls the local host and authorises the second pre-approved operator. The original booking is not cancelled yet; you run both until one car is physically confirmed. The cost of a duplicate car is small against the cost of a traveller stranded at a kerb for an hour, and your supplier agreement should say who pays for the duplicate when the original supplier failed.
At this point the lead also tells the traveller exactly which car to expect. One car, one name.
Minute 20 to 30: decide, then commit
By thirty minutes the traveller should either be in a verified car or have a firm plan for a controlled wait. If neither route is working, the lead moves to the contingencies you agreed in advance: a hotel near the airport that can send its own vehicle, a colleague collecting in person, or a supervised wait inside the terminal until daylight. What is off the table, at every minute, is a street taxi or an unvetted app booking, because that is the specific option the FCDO advice warns against.
Write the thirty-minute decision down as a rule, not a suggestion. For example, a policy might read: “If no verified vehicle is confirmed thirty minutes after the traveller reaches the meeting point, the incident lead books the pre-agreed airport hotel and the traveller remains in the terminal until its vehicle is confirmed.” That is an example, not a template; your insurer and security adviser may want different wording.
Where a stranded employee at the airport should wait
“Stay somewhere safe” is useless advice unless you say where. The general rule for all three major airports is the same: stay inside the terminal building or its immediate, supervised forecourt, in view of staff and security, and do not walk to a car park, a service road or the main road to meet a car. Airport forecourts in Pakistan are security-controlled, and a driver cannot always wait where the traveller expects. So agree the meeting point precisely beforehand; the traveller should not wander off looking for it.
Before each trip, ask your supplier where exactly its drivers meet arrivals at that airport and write the answer into the traveller’s brief. Layouts, forecourt rules and parking arrangements change with construction and security posture, so treat any description older than a few months as a starting point, not a fact.
Islamabad International Airport (ISB)
Islamabad’s airport is not in Islamabad. It sits at Fateh Jang in Attock District, roughly 25 km southwest of both Islamabad and Rawalpindi, and opened for full operations in May 2018 (Islamabad International Airport overview). The distance is the risk factor: a driver stuck on the Srinagar Highway is not five minutes away, and a replacement car dispatched from the city takes real time. That is why the ten-minute trigger matters most here. The terminal has a food court, so a traveller has somewhere indoors to sit while the lead works the phones. There is also a metrobus link to the twin cities, but given the FCDO’s advice against public transport, it should not appear in your fallback list. Our Islamabad airport transfer page covers how pickups from ISB are arranged.
Allama Iqbal International Airport, Lahore (LHE)
Lahore’s airport is about 15 km from the city centre, with the main Allama Iqbal Terminal handling passenger flights and a separate Hajj Terminal (Allama Iqbal International Airport overview). An expansion project that began in 2024 was targeted for completion by October 2026, so expect changes to forecourt and pickup arrangements around this period and reconfirm the meeting point shortly before travel. The terminal has bank branches, ATMs and porter services, which helps a traveller who arrives without rupees and needs to wait. Our Lahore airport transfer page sets out how pickups there are arranged.
Jinnah International Airport, Karachi (KHI)
Two things belong in any Karachi brief. First, confirm with the supplier exactly which arrivals exit your traveller will use and where the driver will stand, especially if they are connecting from a domestic flight, because a driver waiting on the wrong side turns a missed meeting into what looks like a missed pickup. Second, the October 2024 attack near the airport is a reason to keep the waiting time inside the terminal as short and as supervised as possible, not a reason to wait outside. See our Karachi airport transfer page for how collections there work.
When roaming fails: offline contact that still works
Every escalation ladder assumes the traveller can reach the incident lead. That assumption can break at the worst moment. A roaming plan may not connect on landing, a battery may be flat after a long-haul flight, and the FCDO warns that “during times of protest or civil unrest, mobile data coverage and internet connectivity may be cut without warning”. If your ladder runs entirely on a messaging app, it has a single point of failure.
Build redundancy that does not depend on data:
- A printed contact card. Driver, supplier dispatch, local host, incident lead, hotel and insurer, with international dialling codes. Paper does not run out of battery.
- Voice and SMS as the default escalation channel. An ordinary call or text may still get through when data does not. Tell suppliers that a missed-pickup alert will arrive by SMS or voice call, and that they must answer it.
- A pre-agreed silence rule. If the incident lead hears nothing from the traveller for a set period after the flight is shown as landed, the lead starts the ladder anyway and calls the supplier. Silence is a signal, not a reason to wait.
- A local fallback number. The local host’s landline or a hotel front desk can relay messages if the traveller borrows a phone from airport staff or an airline desk.
- Emergency numbers memorised. The FCDO lists 15 for police and 1122 for ambulance and fire in Pakistan, and 020 7008 5000 as the FCDO’s 24-hour line in the UK for people worried about someone abroad (FCDO getting help in Pakistan). US citizens should also be enrolled in STEP, as the State Department advises.
Putting it into your corporate travel risk management policy
A ladder that lives in one travel manager’s head is not a plan, and for any corporate travel risk management Pakistan programme that is the first gap to close. The corporate travel risk management policy should hold the rules, and your supplier contracts should hold the obligations that make the rules workable. Four clauses do most of the work.
1. Named driver and verification before landing
Require the supplier to send the driver’s name, mobile number and vehicle details to the incident lead ahead of arrival, and to tell the lead, not only the traveller, of any change. Unannounced substitution is how a traveller ends up getting into a car on trust.
2. A dispatch desk that answers at the hour you land
Ask the supplier which hours its dispatch desk is staffed and test the number before the first trip. If the supplier cannot cover the hours your people fly, you need a second operator for those hours.
3. A second approved operator, already vetted
Vet the fallback before you need it. The FCDO standard, a reputable licensed company you call where the operator assigns the driver, is a sensible minimum test for both your primary and your backup. Give the local host a standing authorisation to book the backup, with a spending limit, so that minute ten does not become minute forty while someone finds a purchase order.
4. Agreed consequences for a missed collection
Decide before the trip, in writing, what a failed collection triggers: a replacement journey at no charge, a credit against a future booking, or a refund, and how the cost of any duplicate car is shared. Do not assume a supplier’s standard terms cover a corporate account; read them and negotiate what you need. Suppliers who handle business travel should be willing to discuss this. If you are assessing iDrive for this role, our business travel car service page explains how corporate journeys are set up; hold us to the same four clauses you would ask of anyone else.
After the incident: the report, the credit and the risk register
The traveller is at the hotel, the car is paid for, and everyone wants to go to bed. This is exactly when the lesson gets lost. Give the incident lead forty-eight hours to close three things.
The post-incident report
Keep it to one page. Record:
- the timeline in minutes, from meeting point to verified car;
- which rung resolved it and whether any rung was skipped;
- the supplier’s stated reason, and whether it holds up against the flight’s actual arrival time;
- any moment the traveller was approached, felt unsafe or was out of contact;
- costs incurred, including the duplicate car and any hotel.
Also ask the traveller at what minute they started to feel uneasy. That answer is often more useful than the timeline.
The credit or refund claim
Submit the claim with the report attached, against the clause you agreed in advance. The aim is to establish whether the failure was a one-off or a pattern. If you booked through a platform, raise it through that platform’s own support channel so the record sits against the booking.
Updating the risk register
Each missed collection should change at least one line in the risk register, even if the change is only a note that the control worked. Useful entries include:
- Likelihood: did this supplier or airport produce a second failure within a set period? Adjust the rating.
- Control effectiveness: did the 10, 20 and 30 minute triggers fire on time? If the lead was slow, the fix is the rota, not the supplier.
- New controls: for example, a second meeting point at Karachi if the concourse confusion recurs, or an earlier driver confirmation deadline for night arrivals at Islamabad.
For the traveller’s side of the brief, our sister service Pakistan Taxi, the passenger brand run by iDrive, explains how to combine an airport pickup with business meetings in Pakistan, which is worth handing to a first-time visitor before the next trip.
Next step
Once the ladder, the backup operator and the thirty-minute rule are written down and the incident lead knows they are on duty, you can request a journey through iDrive and share the booking details with your incident lead. Treat every quote as a request until you receive confirmation of the driver and vehicle.
Questions people ask
How long should a traveller wait before escalating a missed airport pickup?
Escalation should start at once, but the traveller should not act alone. The incident lead calls the supplier at minute zero; the supplier gets ten minutes to produce a verifiable driver; a second approved option goes live at ten; and a firm decision is made by thirty.
Can a stranded employee just book a ride-hailing app at the airport?
The UK FCDO advises against street taxis, e-taxis and online taxi apps in Pakistan, and recommends reputable licensed companies where you call and the operator assigns the driver. A corporate fallback should follow that advice.
