How to vet corporate transport vendors that claim all-Pakistan coverage

Most corporate transport vendors in Pakistan can show you a clean car and a confident driver in Islamabad, Lahore or Karachi. That tells you almost nothing about the phrase that sits on page one of their proposal: “all-Pakistan coverage”. The only reliable way to vet a transport supplier is to test the claim before you sign. Place paid or dry-run bookings in cities where the vendor is least likely to have its own cars (Multan and Sialkot are good first tests), ask for documents you can check against government registers, time how they answer at 2am, and make them write down who actually owns the vehicle that turns up. If the answers only arrive after the contract is signed, you have already bought the claim rather than the service.

What follows is that method, written for procurement, travel and admin teams who have to sign off a supplier and then live with the result.

The decision in brief

• Treat “nationwide” as a hypothesis. Ask the vendor to split its city list into three columns: own fleet, contracted partners, and “on request”. Expect much of the map to sit in the second and third.
• Test the edges, not the centre. A booking at Islamabad International proves little. A 5am pickup in Multan or a same-day request from Sialkot proves a lot.
• Verify documents yourself. Company registration, tax status and vehicle registration can be checked on official portals in minutes. Do not rely on scanned certificates alone.
• Put subcontracting in the contract. Partner networks are normal and often sensible. Undisclosed ones are not.
• Separate safety from coverage. A vendor offering cars in areas where the UK and US governments advise against all travel is not a selling point for your duty-of-care file. That is a security decision, not a transport one.

What “all-Pakistan coverage” usually means

There are three honest business models behind nationwide coverage claims, and one dishonest one. Knowing which you are dealing with changes every question that follows.

1. Owned fleet in a few cities

The vendor owns or leases vehicles, employs or directly contracts drivers, and runs its own dispatch in one to three metros. Service quality in those cities can be excellent and consistent. Outside them, the vendor is either sending a car long-distance (with the empty return leg priced in somewhere) or quietly calling someone else.

2. Managed partner network

The vendor sets standards, onboards local fleets and independent drivers in each city, and takes responsibility for the booking end to end. This is how most platforms reach secondary cities sensibly. Its quality depends on onboarding checks, how partners are monitored, and whether the vendor will stand behind a failure that happened in someone else’s car.

3. Broker or agency

The vendor takes your booking and places it with whoever is available, with lighter standards and little ongoing oversight. This can work for occasional trips, but it is a different product and should be priced and contracted as one.

4. The phone-book model

One owner, a handful of cars in a home city, and a list of phone numbers everywhere else. The proposal says “nationwide”. The reality is a series of calls made after your booking arrives. The tests below are designed to surface this model before it surfaces itself at an airport kerb.

None of the first three is wrong. The problem is only ever a mismatch between what is sold and what is delivered.

Before you test: where coverage and duty of care collide

Some of the cities that sit on a typical vendor’s list are ones your own travel policy may not allow. As of the update published on 22 September 2026, the UK FCDO travel advice for Pakistan advises against all travel to Balochistan Province, which includes Quetta, and against all travel to a list of Khyber Pakhtunkhwa districts that includes Peshawar, city included. It also advises against all but essential travel to Dera Ghazi Khan in Punjab and to all areas of Sindh north of and including Nawabshah. The FCDO notes that travel insurance could be invalidated if you travel against its advice.

The US State Department advisory (issued 16 June 2026) rates Pakistan overall at Level 3, Reconsider Travel, with Balochistan, Khyber Pakhtunkhwa (including the former FATA) and the vicinity of the Line of Control at Level 4, Do Not Travel.

What that means for procurement:

• A vendor’s ability to put a car in Quetta or Peshawar does not make travel there safe or insurable for foreign staff. Do not let a coverage map drive a travel decision.
• If your organisation has locally based employees who do travel in these areas, the question is no longer “can the vendor cover it?” but “what does our security team require?” Journey management, route approval and communications plans belong with specialists.
• You can still test a vendor’s paperwork and response for those cities without anyone travelling. Ask how they would handle the request, who the local partner is, and what they would refuse. A vendor that says yes to everything without asking a single question is telling you something useful.

Advisories change. Re-check both official pages before each contract review and before any trip, rather than relying on this article.

Evidence to request, and how to check it

A proposal pack full of logos and a fleet photo is not evidence. Ask for the items below in writing, then check what you can against official sources.

Two practical notes. First, spot-check rather than audit. Pick five registrations at random from the fleet list, including at least two from outside the vendor’s home city, and see whether the details match. Second, a mismatch is not always fraud. A car can be registered to a director personally or to a leasing company. What matters is whether the vendor explains the mismatch clearly when you ask.

Run test bookings in secondary cities

Coverage claims break at the edges: smaller airports, early flights, short notice, and cities where the vendor has no office. Design a test programme that goes there deliberately. A few real journeys cost less than one failed airport pickup for a visiting director.

Pick the right test cities

• Multan. A major southern Punjab city with its own international airport, and far enough from Lahore that a vendor without local supply has to improvise. Book a real airport pickup and a half-day in town, or compare what the vendor offers against a local taxi and car hire option in Multan.
• Sialkot. Its airport, built by the local business community and described as Pakistan’s only privately owned airport, is mainly served by Gulf and Middle East routes, so arrivals cluster around flight banks rather than office hours. Test an early-morning arrival and a transfer onward; set it against what a dedicated Sialkot airport pickup service would expect you to provide.
• A city in a different province from the vendor’s base. If the vendor is Karachi-based, test Islamabad or Lahore; if it is Lahore-based, test Karachi or Hyderabad. The transport company in Islamabad, Lahore or Karachi that you already know works may be a very different operation at the other end of the country.
• Quetta and Peshawar, on paper only. Given the FCDO and US positions above, do not send anyone just to test a vendor. Run a desk test instead: ask for a written plan for a hypothetical request, named partner, vehicle type, and what the vendor would decline.

Make each test count

1. Book through the channel your travellers will use. If staff will book by app or portal, test the app or portal, not a sales manager’s WhatsApp.
2. Vary the lead time. Book one journey two days ahead, one the evening before, and one with three to four hours’ notice.
3. Include one out-of-hours slot. An arrival between midnight and 6am is where thin coverage is most visible.
4. Change something mid-journey. A flight delay or an added stop tests whether dispatch is live or whether your booking was simply passed on.
5. Record what arrived. Note the registration, the driver’s name against what was confirmed, vehicle condition, and whether the car matched the class booked.
6. Compare the paperwork. Check that the invoice entity matches the contracting entity, and that the registration matches the fleet list or partner list you were given.

Example scoring (illustrative, not a benchmark): give each test journey a pass or fail on five points: confirmation received with driver and vehicle details before pickup; vehicle matched the booked class; driver on time or proactively updated; change request handled without a new booking; invoice consistent. A vendor that fails the same point in two cities has a process gap, not bad luck.

Response time and out-of-hours cover

Ask vendors to describe, in writing, what happens when a traveller calls at 3am because the driver is not at the arrivals exit. Then test it.

• Who answers? A staffed operations desk, an on-call manager’s personal mobile, or a voicemail? All three exist. Only one scales.
• What can they do? Can the person answering see the driver’s location, reassign the job and call a replacement, or can they only promise to “check”?
• How is the traveller updated? By SMS, app notification or a call back? At what interval?
• What is the escalation path? Named roles, not “the team”. Include what happens when the out-of-hours contact is unreachable.
• What languages? Visiting colleagues may need English; drivers may be more comfortable in Urdu, Punjabi or Pashto. Ask who bridges that gap on the phone.

Run two unannounced calls during your test period: one in office hours asking to amend a booking, and one late at night with a simple question. Time the answer and note whether the person could actually act. Do not ask vendors for a guaranteed response time you cannot measure; ask for their target, then measure it yourself.

Subcontracting: disclose it, then contract for it

Subcontracting is not the problem. In secondary cities it is usually the only efficient way to get a well-maintained local car rather than one that has driven for half a day to reach you. The problem is subcontracting you do not know about, because it quietly moves the risk without moving the price.

Write these into the contract or service schedule:

• Disclosure. The vendor names its partners per city, or at minimum tells you in the booking confirmation when a partner is fulfilling the job.
• Standards flow down. Vehicle age, condition, driver checks and insurance requirements apply to partners exactly as to owned fleet.
• Single point of responsibility. The contracting vendor handles complaints, refunds and incident reports, whoever drove the car.
• No onward chains. A partner may not pass your booking to a third party without the vendor’s approval.
• Data handling. Traveller names, phone numbers and flight details go only to the driver who needs them, not into a group chat of available drivers.
• Audit right. You can request the fleet and driver records for any journey fulfilled on your account.

A vendor that runs a proper partner model will usually accept these terms because it already operates this way. One that resists every clause is likely running the phone-book model described earlier.

Ask every shortlisted vendor for the document that tells partners how to join. For comparison, the iDrive partner programme sets out publicly how fleets and independent drivers apply. Read each one the way a partner would.

Reference checks that actually tell you something

Every vendor has three happy clients. Ask for references that match your risk, not their marketing.

• A client that uses the same cities you need, particularly the secondary ones. A Karachi-only reference says nothing about Multan.
• A client with a similar volume and pattern. Occasional executive trips and daily staff shuttles stress a vendor very differently.

Questions worth asking the referee:

1. What went wrong in the last six months, and how was it handled?
2. Did you ever discover a journey had been passed to another operator without being told?
3. How did out-of-hours support perform the times you actually needed it?
4. Would you give them your most senior visitor’s airport pickup tomorrow?

Questions to ask a ground transportation provider before signing

Use this as the core of your request for proposal or the agenda for a final clarification meeting. Ask for written answers.

Coverage and supply

• For each city on your list, is supply owned, leased, contracted partner or on request only?
• How many vehicles of each class are based in each city, not merely “available”?
• What notice do you need in each city for a standard car, an executive car and a people carrier?
• Which cities or routes will you decline, and why?

Commercial terms

• How are quotes built: distance, time, waiting, tolls, parking, night charges, empty return legs?
• Which elements are fixed at booking and which can change, and on what evidence?
• What are the cancellation and no-show terms, and do they differ for partner-fulfilled journeys?

Finally, ask whether they will accept the subcontracting clauses above, and what insurance covers passengers in partner vehicles.

Red flags that should pause a contract

• The city list grows every time you ask about a new place, but the fleet list does not.
• Test bookings are confirmed quickly, yet driver and vehicle details arrive only minutes before pickup, or not at all.
• The car that arrives is registered to a name nobody at the vendor recognises.
• The invoice comes from a different entity than the one you contracted with.
• The out-of-hours number is a sales manager’s mobile that goes to voicemail.
• The vendor promises a fixed, guaranteed price and availability everywhere, without asking about timing, luggage or passenger count. Pricing in Pakistan moves with fuel, tolls and demand; a serious vendor explains how its quotes are built rather than promising that nothing will change.
• Insurance documents cover private use only, or name an insurer you cannot find on SECP’s licensing pages.
• The vendor offers cheerful service in areas under an all-travel advisory without mentioning the advisory at all.

One red flag is a question. Three is an answer.

A sensible shortlist-to-contract sequence

1. Issue the questions above to three or four vendors, with a two-week reply window.
2. Verify documents for the two strongest: SECP, FBR and a random sample of vehicle registrations.
3. Run test bookings over two to three weeks, covering at least one secondary city, one out-of-hours slot and one mid-journey change.
4. Take references matched to your cities and volume.
5. Negotiate the service schedule, including subcontracting disclosure, escalation contacts and incident reporting.
6. Start with a pilot period and a review point, rather than a long exclusive term.

For teams that need a reference point while benchmarking, iDrive publishes how its business travel car service in Pakistan is set up, and you can place a request through the iDrive booking page as one of your test journeys. As with any vendor, a request is not a confirmed booking until a driver and vehicle are assigned and the price has been confirmed to you, so judge the process by what actually arrives. For individual travellers who would rather plan a day of meetings step by step, our sister service Pakistan Taxi, an iDrive brand, has a practical guide to planning transport for several business meetings in one day.

Questions people ask

Is a partner network worse than an owned fleet?

Not necessarily. Owned fleets tend to be more consistent in their home cities; well-managed partner networks usually reach secondary cities faster and with local cars. What matters is disclosure, flowed-down standards and a single point of responsibility.

Can I check a vendor’s vehicles myself?

Partly. Punjab and Sindh excise departments run online vehicle verification services, and you can spot-check registrations from the vendor’s fleet list. Treat mismatches as questions to ask, not automatic proof of wrongdoing.

Should we test bookings in Quetta or Peshawar?

Not with travellers. The UK FCDO advises against all travel to Balochistan, including Quetta, and to Peshawar. Run a desk test of the vendor’s plan instead, and refer any genuine travel need to your security team.

How many test bookings are enough?

There is no fixed number. Cover each city type you rely on, at least one out-of-hours journey and one change request. Consistent failures on the same point matter more than volume.