How to choose an employee transport vendor in India

Employee transport is one of the few facilities line items where the cheapest quote and the biggest headache are usually the same vendor. Most contracts are won on rate and lost on everything that happens after the rate is agreed. This is a practical guide for the HR, admin or facilities team running the selection, built around the questions that actually separate a good operator from a cheap one.

Start with the shape of your operation, not the price

Before you talk to a single vendor, write down what you are actually asking them to move. A good brief has four things:

• Headcount to be transported, and how it splits across shifts.
• The shift pattern, including any night shifts and rotational timings.
• The corridors your people live along, drawn from real home locations, not a template.
• The office locations and the times people must arrive and leave.

A vendor who quotes without asking for this is quoting a number, not a plan. The right first response to your brief is a site survey and a route study, because the cost and the safety of the operation are decided by the routes, and the routes are decided by where your people actually live.

Cars or buses: let the routes decide

The instinct to standardise on one vehicle type usually costs money. The right vehicle is a function of density. Scattered residential pickups across a township are a job for cars. A corridor where twenty or more people board within a few kilometres of one another is a job for a bus, and an electric bus at high occupancy is the cheapest seat you can buy. A vendor worth hiring will size the mix from the route study and show you the cost-per-seat trade, so the choice is yours to check rather than theirs to assert.

Treat compliance as a floor, and audit it

Every serious vendor will claim their drivers are verified and their vehicles are legal. The words are cheap. What you are checking is whether the machinery behind them exists. At a minimum, ask to see how they track each vehicle document to its expiry, how a lapse pulls a vehicle off your routes, and what "verified" means in one redacted driver file. If you run night shifts for women, the compliance floor is higher, and the rules that changed with the Labour Codes in November 2025 are worth reading before you write the tender.

How they bill, and whether you can check it

The month-end invoice is where most transport relationships go sour. The question is not which billing model a vendor uses. It is whether every billed line traces back to a trip that actually ran. Ask for a sample invoice with its trip ledger attached: each trip, its date, its distance, its vehicle. If the vendor cannot produce a bill that reconciles to a record, you are being asked to pay on trust, and trust is what fails at scale.

What happens when a vehicle fails

A vehicle will break down, and it will happen at the worst time. The honest thing to ask is what is contracted to happen when it does. A serious answer has three parts: a defined number of standby vehicles held in reserve, a response window, and a penalty if the window is missed, all written into the contract rather than promised in a meeting. A buffer fleet that exists only as a reassurance is worse than none, because you will discover it does not exist on the one night you need it.

Safety you can see, not safety you are told about

Night-shift safety is where a vendor is really tested. The controls matter, no first pickup or last drop for a woman travelling alone, a trained escort below a threshold, live tracking to a named person, an SOS in every vehicle, geofence alerting. But the controls are only real if the roster is built so they hold on their own, and if you can check, the next morning, that last night's route was actually run to them. Ask for that evidence, not the policy.

Do you get data, or a spreadsheet?

The difference between a modern operator and a legacy one shows up in the monthly pack. You should receive the trip ledger, the invoice reconciled against it, pickup-variance reporting, and, if your sustainability team wants it, a measured commuting-emissions statement built from the same trips. If the reporting is a spreadsheet someone typed up after the fact, the numbers are only as good as the person who typed them.

The new-vendor question

A newer operator will have a shorter client list, and if the length of that list is your deciding factor, they will lose. But the things that actually de-risk a transport contract are not the logos on a wall. They are the buffer fleet, the metered ledger, the verified drivers and the go-live process, and those are written down and checkable. A newer vendor who can show you all four is often a safer bet than an established one who cannot.

The one-page checklist

Area	What to ask for
Scope	A site survey and route study before any quote.
Fleet	A car-versus-bus mix justified by density, with the cost-per-seat trade shown.
Compliance	Document-expiry tracking, and one redacted driver verification file.
Billing	A sample invoice with its trip ledger attached.
Continuity	Buffer-fleet count, response window and penalty, in the contract.
Safety	Written night protocol, plus evidence a recent route was run to it.
Reporting	A monthly pack drawn from primary data, not a typed summary.
Go-live	A staged plan from signing to running, with dates you can hold them to.

Run every shortlisted vendor against the same eight rows and the comparison stops being about price alone. It becomes about which operator can prove what they promise, which is the only comparison that survives contact with a real month of operations.