A clause-by-clause guide to what belongs in a ground transport service level agreement — measurement definitions, escalation windows, duty of care, insurance, data handling and invoicing — written for travel managers and procurement teams.
Most ground transport contracts describe intentions rather than obligations. The difference between the two is measurement: an SLA is only meaningful when it states what is guaranteed, how the number is calculated, who produces the report, what happens when the target is missed, and when the parties sit down to review it. A supplier that will commit to those five things in writing is a materially different proposition from one that will not, regardless of how the two fleets compare.
Start with performance. On-time performance needs a definition before it needs a target — for airport arrivals the benchmark is the chauffeur in position relative to actual touchdown, and for scheduled pickups it is the agreed time. A realistic contracted target for a well-run urban operation is 97–99%; a supplier offering 100% is not counting exceptions. Attach the sample (all rides, not a selected subset), the reporting frequency, and a remedy for sustained under-performance, which in practice is usually a service credit plus a corrective action plan.
Escalation is the clause that gets used. It should name the contact and channel, guarantee availability across the hours the business actually travels rather than office hours, and set maximum times for acknowledgement and for dispatching a replacement vehicle. It should also place the notification burden on the operator: the traveller and the booker are told about a problem before they discover it themselves. Escalation language without time limits is decorative.
Duty of care is increasingly the clause that legal reviews hardest. Expect to specify verified chauffeur licensing, documented background and medical checks, driving-hour limits, a maximum vehicle age with a maintenance and inspection schedule, insurance limits with certificates on file, an incident reporting procedure with timelines, and a lone-traveller policy that addresses late-night journeys and female travellers. Passenger data — itineraries, addresses, names — should be covered by an explicit confidentiality and retention clause, with a stated position on whether trip data is shared with the employer.
Commercial terms deserve the same precision. Net-30 payment, VAT-compliant tax invoices carrying the TRN, per-ride cost-centre or project tagging, a consolidated monthly statement exportable as CSV and PDF, a dispute window, and an explicit commitment that the fare confirmed at booking is the fare invoiced, with only the published exception rates (extra waiting, extra stops) able to change it. This is where a fixed-fare operator has a structural advantage over a dynamic-pricing supplier: the reconciliation is trivial.
Close with governance. Monthly reporting against the agreed metrics and a quarterly business review covering incidents and root causes, spend against budget, and changes to routes, vehicle mix or coverage. Chauffeurr operates corporate accounts on this framework across the UAE — Net-30 invoicing, cost-centre tagging, a named account manager and 24/7 escalation — and will supply the SLA annexe for review before any commitment is made.
| Clause | What it must specify | Benchmark |
|---|---|---|
| On-time performance | Measured against actual events | 97–99% target |
| Escalation acknowledgement | Named 24/7 contact | Minutes, not hours |
| Replacement vehicle | Reserve car per shift | Defined max window |
| Chauffeur vetting | Licence, background, medical | Documented, on file |
| Invoicing | VAT invoice with TRN, cost-centre tags | Net-30 |
| Reporting cadence | Metrics, incidents, spend | Monthly + QBR |
Multi-traveller booking, cost-centre tagging, traveller profile library, policy compliance flags.
One monthly VAT invoice across every emirate, with bank transfer, corporate card, or PO settlement.
Multi-car, multi-day scaling for IPO roadshows, board offsites, event shuttles. SLA-backed.
One-day onboarding, dedicated relationship manager, 24/7 escalation line, monthly SLA report.
An SLA is the contractual annexe that converts service promises into measurable commitments: what performance is guaranteed, how it is measured, who reports it, what happens when it is missed, and how the relationship is reviewed. Without measurement definitions and a remedy clause, an SLA is a marketing document.
Eight: on-time performance with a stated measurement definition; vehicle and chauffeur standards; escalation and replacement windows; duty-of-care and incident reporting; insurance limits and licensing evidence; data protection and passenger confidentiality; invoicing, VAT and expense-format requirements; and a scheduled performance review with defined reporting.
For a well-run urban chauffeur operation, 97–99% on-time is realistic when measured against actual events (touchdown for arrivals, agreed pickup time otherwise). Anyone contracting to 100% is either not measuring or not counting the exceptions. What matters more than the headline number is that the definition, the sample and the reporting frequency are written into the agreement.
Specify a named contact and channel available at the hours the business actually travels, a maximum acknowledgement time, a maximum time to dispatch a replacement vehicle, and a proactive notification obligation — the operator informs the traveller and the booker before they discover the problem. Escalation clauses without time limits are unenforceable in practice.
Verified licensing for every chauffeur, documented background and medical checks, driving-hours limits, maintained and inspected vehicles within a stated age, real-time trip visibility for the employer where the traveller consents, an incident reporting procedure with defined timelines, and a lone-traveller policy covering late-night and female-traveller journeys.
Payment terms (Net-30 is the corporate norm), a VAT-compliant tax invoice with the TRN, cost-centre or project tagging on each ride, a consolidated monthly statement, CSV and PDF export, a dispute window, and a commitment that fares are those confirmed at booking with no post-hoc adjustment other than the agreed exception rates.
Monthly reporting with a quarterly business review is the standard cadence for programmes above roughly fifty rides a month; quarterly reporting is adequate below that. The review should cover the agreed metrics, incidents and root causes, spend against budget, and any changes to routes, vehicle mix or coverage.