Afghan-owned · Operating nationwide

Guide · Vehicles and fleet

Vehicle rental for UN and NGO field operations in Afghanistan: what to specify

Most vehicle-rental problems in field programmes are written into the request for quotation. A specification that names the routes, the working pattern, the driver requirements and what happens when a vehicle stops is what turns a set of guesses into quotations that can be compared.

Operating profile

34provinces covered
District reach
250+
Regional zones
5
View coverage
ZHIKAL / BEYOND BOUNDARIES / EST. 2011Explore this page

Start from the work, not the vehicle

A request for four 4x4 vehicles with drivers for six months invites four different interpretations. One supplier prices a vehicle parked in Kabul and driven on demand; another prices a vehicle stationed in a province with its driver living nearby; a third assumes daytime city driving; a fourth assumes long interprovincial trips with overnight stays. All four quotations are honest, and none of them can be compared with the others.

The remedy is to describe the work the vehicles will do. Where does each team start the day, and where does it go? How many people travel, carrying what equipment? Are the trips inside a city, between districts or between provinces? Does the team stay overnight in the field, and does the driver stay with it? A supplier who knows the pattern can price the vehicle class, the driver arrangement and the fuel realistically, and can say honestly where it cannot.

The pattern also decides which vehicle is right. The Logistics Cluster's road network assessment (opens in a new tab) records that many unpaved rural roads become impassable in heavy rain or winter months, which is where a 4x4 earns its cost; on a paved corridor a van may carry an enumeration team more efficiently than two pickups.

What should the request for quotation specify?

These are the items that most often decide whether quotations can be compared, and whether the deployment runs as planned once it starts.

  • Vehicle class and condition

    4x4, pickup or van; seating and load space; and any age or condition requirement your organisation applies, stated rather than implied, with how it will be checked at handover.

  • Geography and routes

    Base locations, provinces and districts, typical daily routes, and whether interprovincial or overnight travel is expected.

  • Working pattern

    Days per week, hours, on-call expectations, and how Fridays and public holidays are handled.

  • Drivers

    Licence category, experience on the routes, languages, conduct requirements, and whether a driver stays with the vehicle overnight.

  • Duration and flexibility

    Start date, minimum period, and the notice needed to add a vehicle or release one early.

  • Fuel, maintenance and distance

    Who pays for fuel and how it is recorded, and whether there are distance limits — the terms behind most invoice disputes.

  • Replacement and downtime

    What happens when a vehicle breaks down or a driver is absent, the replacement you expect, and how downtime is treated on the invoice.

  • Liability for loss and damage

    Who bears it, written into the contract. The Logistics Cluster reports that insurance services, including vehicle insurance, were suspended in March 2022, so check the current position rather than assuming cover exists.

  • Records

    Trip logs, fuel records and the usage report you need for your own reconciliation and donor reporting.

Conduct, safeguarding and security belong in the request

A driver is often the programme's most visible representative in a community, and on many deployments the person who spends most time with field staff and beneficiaries. Conduct requirements belong in the request, not in an induction after award: the code of conduct drivers must sign, the PSEA briefing they must receive, and how a complaint about a driver is raised and handled.

Security arrangements belong there too. State whether movements must be reported to your security focal point, whether any routes are off limits, and who has authority to stop a trip. A supplier with regional teams should then be able to show how that decision is taken locally. At Zhikal, routes and field risk are assessed before deployment, the go/no-go decision is held at zone level, and access or security disruptions are reported to the client within 24 hours with a proposed alternative.

Compare quotations on what they include

Once the specification is fixed, ask every supplier to price against it in the same format: vehicle cost, driver cost, fuel basis, overnight allowances, and what is excluded. A lower daily rate that leaves out fuel or overnight costs is not cheaper; it moves the cost onto the invoice.

Ask for evidence rather than assurances. Registration and tax documents, references for comparable deployments that can actually be called, and an account of how a recent multi-province deployment was coordinated say more than a fleet list. As a point of comparison, Zhikal's largest documented deployment kept rental vehicles working in all 34 provinces at once for more than seven months in support of an education-supply survey, with regional coordinators managing driver rotation, fuel, maintenance and route changes as access conditions shifted.

When one supplier should hold the whole deployment

Splitting a multi-province deployment across local vendors can look cheaper per vehicle, but it moves the coordination onto the programme: several contracts, several invoice formats, and nobody accountable when a vehicle in one province stops. A single supplier with coordinators in each zone gives one escalation line and one set of records, which matters most on surveys and monitoring rounds, where a stranded team loses days.

Where the need is goods rather than people, the service is a different one: see road transport and freight and the road transport planning guide. For project vehicles with drivers, Zhikal's vehicle rental service sets out vehicle classes, coverage and how deployments run.

Sources

External sources are cited for the facts they report and were checked when this guide was last updated. Citing them implies no relationship with, or endorsement by, their publishers.

Related services.

Who this is written for.

Further reading.

  • Guide · Road transport

    Road transport across Afghanistan: route, load and proof-of-delivery planning

    Most failed road movements in Afghanistan were decided before the truck was loaded: a route chosen by distance rather than access, a load that did not suit the vehicle, or a delivery with nobody authorised to sign for it.

  • Guide · Field operations

    Last-mile delivery in remote Afghan provinces

    Reaching a provincial capital is a freight problem with known answers. Reaching a district beyond it is a coordination problem — a different vehicle, a narrower access window, a named person to sign and proof of delivery captured on the day — and it is where most distribution plans lose their schedule.

  • Guide · Distribution

    Winter pre-positioning and remote-area delivery in Afghanistan

    Winter does not close Afghanistan, but it closes enough of it to decide a distribution plan. The work that matters happens in autumn: finding the destinations that lose access, moving stock close to them while roads are open, and agreeing what happens when the plan meets snow.