Duty of Care in Ground Transportation: The Complete Guide

Duty of care in ground transportation is an organization’s legal and ethical obligation to take reasonable steps to protect travellers in vehicles it arranged — which in practice means verifying that every performing operator holds valid commercial licensing, carries insurance that is in force on the day of travel, meets driver-safety standards, and can be identified after the fact, even when the trip was subcontracted. A program meets that obligation with evidence, not intentions: records that show what was known about the supplier, and when.

This is the complete guide to building that program. It covers what the obligation actually requires, why ground transportation is structurally harder to govern than air or hotel, the five capabilities a defensible program runs on, and how to put them in place — whether you manage travel for a corporation, run a TMC, or source ground for an agency or event business.

What duty of care requires — and what it doesn’t

Strip away the conference-stage language and duty of care is a negligence concept. An organization that arranges travel owes the people travelling a reasonable standard of care against foreseeable harm. The test applied afterwards is narrow and uncomfortable: would a reasonable, similarly situated organization have foreseen this risk and taken steps to address it?

Two things follow from that framing. First, the obligation is not discharged by choosing a booking tool, signing a large vendor, or collecting paperwork at onboarding. It is discharged by a process that stays current — and by the ability to show, after an incident, what the process knew. Second, the standard is reasonable steps, not perfect ones. No program can guarantee nothing goes wrong on the ground. What a program can do is make its selection and monitoring defensible, which is a bounded, achievable piece of work.

ISO 31030:2021, the travel risk management guidance most large programs now anchor to, formalizes this. It treats ground transport as a distinct risk category and moves supplier safety from a procurement nicety into the organization’s documented risk framework: assess the risk, treat it, monitor it, and keep records that prove you did. If your organization is aligning to ISO 31030 — or answering RFPs from clients who are — ground transportation is one of the categories where auditors now expect to see specifics rather than a general statement about preferred vendors.

Why ground transportation is the weakest leg of the trip

Road travel is where the physical risk actually concentrates. The WHO counts about 1.19 million road traffic deaths a year worldwide, and road crashes are consistently among the leading causes of non-natural death for travellers abroad. Yet ground transportation is the segment most travel programs govern least — not through negligence, but because three structural features make it genuinely harder:

• Licensing is local. Authority to carry passengers commercially is issued city by city or state by state — TCP authority in California, TLC licensing in New York City, PSV and operator licensing regimes across Europe, and hundreds of other local frameworks worldwide. There is no global register a travel manager can check.
• The supply base is fragmented. A program covering 40 cities is relying on dozens of independent companies, most of them small, each with its own insurer, renewal dates, and standards. Air has a few hundred credentialed carriers overseen by regulators who publish; ground has tens of thousands of operators overseen by nobody in particular.
• Subcontracting is built in. When an operator cannot cover a trip, it farms the trip out to an affiliate. This is normal, legitimate, and the only way global coverage has ever worked in this industry — but it means the company that meets your traveller may not be the company you vetted.

Air and hotel mostly survive a vet-once, file-the-certificate approach because their suppliers are large, consolidated, and publicly credentialed. Ground does not survive that treatment. A duty-of-care file built the procurement way quietly stops matching reality within months.

The five capabilities of a defensible program

A ground transportation duty-of-care program that holds up under scrutiny can do five things on demand. Most programs can do one or two.

1. Verify operating authority — for every performing operator

The baseline question is whether the company carrying your traveller is licensed to carry passengers commercially in the place the trip happens. Because licensing is local, this cannot be answered once at a global level; it has to be answered operator by operator, jurisdiction by jurisdiction. A defensible program records which authority was checked, what was found, and when — and it re-checks, because permits lapse and get revoked.

Note what this excludes: a rideshare platform does not answer the question. TNC drivers typically operate under transportation-network-company permits rather than commercial livery authority, and the platform assigns whoever is nearest rather than a vetted supplier. Rideshare has its place in many programs, but it cannot evidence operating authority for a specific trip, and a program that leans on it should say so explicitly in its risk assessment rather than treating the gap as covered.

2. Track insurance currency, not insurance history

A certificate of insurance proves a policy existed on the day the certificate was issued. It says nothing about the day of travel. Policies lapse, get cancelled mid-term, and renew with changed limits or excluded vehicles. A COI collected at onboarding and filed is a record of the past; what duty of care requires is knowledge of the present — commercial auto liability in force, at appropriate limits, on the date your traveller is in the vehicle.

The practical control is monitoring between renewals: expiry-date tracking, renewal confirmation, and a supplier list whose “approved” status actually decays when documents do. If your supplier file cannot tell you which of your operators’ policies expired last month, it is not tracking currency.

3. Hold suppliers to driver standards you can name

The driver is the single largest variable in passenger safety, and driver standards are where small operators vary most. A defensible program asks its suppliers to evidence four disciplines: screening before hire and a current driver qualification file; an active drug and alcohol program — in the US, 49 CFR 382.701 requires a full FMCSA Clearinghouse query before employing a CDL driver and at least annually after; license and medical-certification tracking with expiry management; and hours-of-service discipline, because fatigue is a foreseeable risk a court will ask about.

You do not need to audit every supplier yourself. You do need to ask the questions, keep the answers, and prefer suppliers who can answer them without improvising. Our companion piece, Duty of Care: What to Actually Ask a Ground Transportation Supplier, turns these four disciplines into a usable questionnaire.

4. See the chain of supply

Farm-out is where most programs’ evidence quietly breaks. The trip you booked with a vetted operator in London may be performed by that operator’s affiliate — a different company, with different insurance, a different licence, and a driver your file has never heard of. The obligation does not transfer with the subcontract: your traveller is still your traveller.

A defensible program does not prohibit farm-out — prohibiting it just means losing coverage. It makes the chain visible: the contracted operator discloses when a trip is farmed out, the performing affiliate is held to the same verification bar, and the program can identify, for any completed trip, which company actually performed it. If your current suppliers cannot tell you that, the gap belongs in your risk register, not in the dark.

5. Produce the evidence afterwards

Everything above converges here. When an incident, an audit, or a client RFP asks the question, a defensible program can produce — for a named past trip — the performing company’s operating authority, its insurance status on the travel date, the driver standards it attested to, and the chain of responsibility if the trip was subcontracted. A program that can only produce onboarding paperwork has evidenced the booking, not the trip.

This is the standard worth designing backwards from. Every policy choice, sourcing decision, and tool in the program either contributes to that after-the-fact answer or it doesn’t.

Building the program: a practical sequence

ISO 31030’s plan-do-check-act structure maps onto ground transportation cleanly. In practice the build looks like this:

Assess. Inventory where your travellers actually ride: cities, volumes, booking channels, and — the uncomfortable one — the bookings happening outside any channel you see. Unmanaged ground spend is invisible risk; you cannot evidence a trip you never knew about. Score each market by exposure: volume, local road risk, and how much visibility you currently have into supply there.

Set policy. Write down what your organization requires of a ground supplier — licensing verification, insurance minimums, driver standards, farm-out disclosure — and what travellers are required to use. A policy that names its standards can be audited against; “use preferred vendors where possible” cannot.

Source against the policy. Whether you contract operators directly, go through a TMC, or use a verified network, the sourcing question is the same: who does the vetting, what exactly do they check, and does the checking continue after onboarding? Ask to see the verification methodology in writing. Our guide to how travel agencies find and vet ground transportation suppliers compares the sourcing channels and what each one actually verifies.

Monitor continuously. Credentials expire on their own schedule, not yours. The program needs a mechanism — internal or supplied by a network — that tracks insurance and licence currency between renewals and flags decay. This is the piece that separates a duty-of-care program from a duty-of-care binder.

Prepare the incident path. Decide in advance who is called when something goes wrong on the ground, what information the program can produce within an hour, and how the traveller is reached and moved. Live trip visibility — knowing which vehicle, which driver, which company, right now — turns an incident response from reconstruction into action.

Review and evidence. On a set cadence, sample completed trips and run the audit question against them: could we produce the performing operator’s credentials for this trip as of its travel date? The percentage that pass is the program’s real coverage number, and it is a better KPI than supplier count.

Where technology fits — and where it doesn’t

No software discharges duty of care. What technology changes is the cost of doing the five capabilities properly, which is the difference between a program that is defensible on paper and one that is defensible in practice.

The pattern that works is a verification layer underneath whatever booking channels the program already runs. GNet, for example, maintains a network of 5,600+ verified operators across 80+ countries: insurance is checked against insurer systems rather than uploaded PDFs, operating licences are tracked by issue and expiry date, operators are reminded at 90, 60, and 30 days before documents lapse, and verified status reflects whether credentials are current today. Affiliates on the network are held to the same verification bar, which keeps the farm-out chain inside the evidence rather than outside it. It complements the booking tools and TMC relationships a program already has — the point is not another place to book, it is that the supplier list underneath stops decaying quietly. The methodology is public: how GNet verifies operators.

Whatever supplier or network you evaluate, the questions are the same three: What exactly is verified, and against what source? Does verification continue after onboarding, or happen once? And can it show me the evidence for a specific past trip? A vendor that answers all three in writing is carrying part of your program. A vendor that answers with a brochure is not.

What the obligation looks like by buyer type

The five capabilities are the same everywhere, but the pressure points differ by who is doing the arranging.

Corporate travel programs and TMCs carry the obligation most directly: the traveller is an employee, the trip is arranged by the program, and the selection process is squarely part of the record. The characteristic failure mode is scale — a global program cannot maintain market-by-market vendor files across 40+ cities, so files go stale and coverage gaps get papered over with rideshare. The fix is structural, not more effort: a verified network that carries the monitoring burden, layered under the booking channels the program already runs. The TMC-specific picture is at ground transportation for TMCs.

OTAs and travel platforms arranging transfers for consumers face the same question with a different label — supplier quality and liability exposure rather than employee duty of care. A platform reselling ground it cannot evidence is holding brand and legal risk on every trip. The requirement to write into supplier agreements is identical: verified operating authority, insurance currency, and farm-out disclosure from the network providing supply.

Travel agencies and advisors sit in between: they arrange for clients rather than employees, but the client relationship — and in some jurisdictions, agency law — makes “we booked a company we’d never checked” an uncomfortable position after an incident. The practical bar for an agency is lighter but real: source from channels where vetting is documented, and keep the record of what the channel verifies. Our agency sourcing guide compares those channels in detail.

DMCs and event buyers face the concentrated version: dozens of vehicles, one city, one date, often sourced under time pressure through layers of subcontracting. Volume sourcing is exactly where farm-out multiplies and where a single event can involve performing operators nobody in the chain has vetted. The discipline that matters most here is capability four — requiring the prime supplier to disclose the full performing list before the event, and holding every company on it to the same verification bar.

Quick reference: who licenses ground transportation where

Licensing regimes vary enormously; these are the patterns a program will meet most often. In the United States, interstate passenger carriers hold federal (FMCSA/DOT) operating authority, while intrastate livery is licensed at state or city level — TCP numbers in California, TLC licensing in New York City, and equivalents elsewhere. In the UK, operators hold PHV or PSV operator licences issued by local authorities or the traffic commissioners. Across the EU, national transport authorities license occasional passenger transport, frequently with EU-level rules layered on. In much of the Middle East, Asia, and Latin America, licensing sits with national or emirate/municipal transport regulators, and requirements can differ between cities in the same country. The operational takeaway is the same everywhere: verification has to happen at the level the licence is issued, which is why a global register does not exist and why continuous, operator-level verification is the only version of this that scales.

FAQs about duty of care in ground transportation

What is duty of care in ground transportation?
It is an organization’s obligation to take reasonable steps to protect travellers in vehicles it arranged — verifying the performing operator’s commercial licensing, confirming insurance is in force on the day of travel, holding suppliers to driver-safety standards, and being able to identify who performed a trip even when it was subcontracted.

Is duty of care a legal requirement?
The underlying obligation is a negligence standard that exists in most jurisdictions, though its exact shape varies by country and by employment relationship. ISO 31030:2021 is guidance rather than law, but it is increasingly the benchmark clients, insurers, and courts use to judge whether a program’s steps were reasonable.

Does booking through a TMC or booking tool satisfy duty of care?
Not by itself. A booking channel evidences that a trip was booked, not that the performing operator was licensed and insured on the day. The program still needs a verification layer under the channel — either the TMC’s own documented vetting or a verified supplier network.

How is ground transportation different from air and hotel for duty of care?
Air and hotel suppliers are large, consolidated, and credentialed by regulators who publish, so vet-once approaches mostly hold. Ground supply is fragmented across tens of thousands of locally licensed companies and routinely subcontracted, so evidence decays unless verification is continuous and covers the performing operator, not just the contracted one.

What should a ground transportation duty-of-care policy include?
Named standards for licensing verification, insurance minimums and currency tracking, driver screening and drug-and-alcohol programs, farm-out disclosure, and an incident response path — plus a review cadence that samples completed trips for evidence. If a standard is not named, it cannot be audited.

Who is responsible when a farmed-out trip goes wrong?
Responsibility is fact-specific and jurisdiction-specific, but the arranging organization’s selection process is always part of the record. What a program controls is whether the affiliate that performed the trip was held to the same verification bar and whether the chain of supply can be reconstructed. “We didn’t know it was farmed out” is an admission, not a defence.

Related reading: Ground Transportation Duty of Care: The 2026 Guide for Travel Buyers · What to Actually Ask a Ground Transportation Supplier

Last verified 31 August 2026. This article is general information about ground transportation risk practice, not legal advice — duty-of-care obligations vary by jurisdiction and by employment relationship, so confirm your program’s specific requirements with counsel.