Policy

Here is what drivers need to know about Zimbabwe’s draft e-hailing rules

📲 Join our WhatsApp Channel for Breaking News! Follow on WhatsApp Drivers who earn a living through inDrive, Bolt, Tap & Go and other ride-hailing…

Here is what drivers need to know about Zimbabwe’s draft e-hailing rules
Zimbabwe’s coat of arms is flanked by Tap & Go, inDrive and Bolt vehicles in a collage illustrating the country’s proposed regulations for e-hailing services.

📲 Join our WhatsApp Channel for Breaking News!

Follow on WhatsApp

Drivers who earn a living through inDrive, Bolt, Tap & Go and other ride-hailing apps would need a dedicated e-hailing permit under draft regulations released by Zimbabwe’s Ministry of Transport and Infrastructural Development. A vehicle operator would need an endorsed licence listing each car used for the service, while the company running the app would need its own accreditation.

📰 For this and more exclusive stories, read our weekly digital print edition.

Read E-Paper

The proposals would also affect the cost of getting on the road and the amount drivers take home. The draft sets out a vehicle age limit, proposes a ceiling on platform commission and introduces a road user charge on each completed trip. Some of the figures that matter most to drivers, including the amount of the road charge and the fees for several approvals, remain open.

The Ministry released the document for public consultation. Cabinet directed that the regulations be promulgated by 31 December 2026. The final statutory instrument will determine which provisions take effect and when. The explanation below follows the November consultation draft.

Three approvals would apply to an app booked ride

The draft covers commercial passenger trips arranged through an e-hailing platform and starting in Zimbabwe, even if the app is hosted abroad. It would treat qualifying vehicles as unmetered taxicabs and limit them to seven passenger seats, excluding the driver. Conventional taxi trips arranged outside an e-hailing platform, organised tours and genuine cost-sharing arrangements for journeys the driver would make anyway are excluded from the draft’s scope.

The platform’s accreditation would authorise it to make the app available. The operator’s endorsement would authorise the service using the vehicles named on the licence. The driver’s permit would authorise the individual behind the wheel. Someone who runs their own car and drives it would need both the operator and driver approvals. Where a fleet operator provides the car, the draft requires a written agreement setting out the terms on which the driver can use it.

Read the draft e-hailing regulations

Who would qualify to drive

The draft puts the minimum age at 21 and requires applicants to have held the appropriate class of driving licence continuously for at least five years. A 23-year-old who obtained the relevant licence two years ago would meet the age threshold and fall short of the experience requirement.

Applicants would also need a valid defensive driving certificate, a recent medical fitness certificate and any additional driving credentials required for public service vehicles.

The draft also lists Zimbabwean citizenship as a condition, with an unfinished statutory reference. It specifies a two-year driver’s permit and says the Commissioner would have to give written reasons for refusing an application. Drivers would have to carry the permit and produce it on request to a passenger, police officer or inspecting officer.

How the 10 year vehicle limit would work

Section 12 measures a car’s age from the date of manufacture to the date it is first listed on an e-hailing endorsement. A vehicle manufactured more than 10 years before that first listing would fall outside the proposed limit. A driver weighing up a purchase would therefore need to check the manufacture date. The section gives no automatic removal date for a vehicle that crosses the age threshold after its first endorsement.

The vehicle would also need a valid certificate of fitness, third-party insurance and passenger liability cover. The draft leaves the minimum passenger liability amount blank. Every seat would need a working seat belt, and window tint would have to comply with existing road traffic rules. The operator would display a vehicle-specific identification disc on the inside of the front windscreen, visible from outside. Satellite tracking could be provided through the driver’s device, as long as it transmits the vehicle’s location during the trip.

An operator using more than one app would have to register the vehicle with each platform. A driver could use only the vehicle linked to their profile on the app. If a driver’s phone is unavailable or the nominated car breaks down, borrowing a colleague’s account or switching to a car that the platform has yet to verify would fall outside the proposed rules.

What the draft says about delivery riders and NSSA

An editing note calls for the inclusion of goods vehicles and motorcycles carrying goods only. The draft sets out detailed rules for passenger services, while the note gives no operative requirements for deliveries. Motorcycle couriers and businesses that move parcels would need to see the final wording to know what permits, vehicle standards or charges would apply to them. The note refers specifically to carrying goods.

Another editing note calls for an NSSA certificate in the vehicle operator’s application. It leaves open which certificate would be accepted, which operators would need it and how the requirement would apply to someone who owns and drives a single vehicle. The application text separately calls for a valid ZIMRA tax clearance certificate or presumptive tax clearance certificate. The draft would require platforms to verify that clearance before activating a vehicle on the app.

How a driver would handle a trip

Drivers would have to take bookings through an accredited app, verify passengers using the code or other method the app provides, and keep the app and location tracking active from acceptance to the end of the trip. The draft would prohibit using an e-hailing vehicle to pick up unbooked passengers at a rank or on the roadside under the e-hailing service. It would also bar drivers from moving an app-introduced passenger to a private booking or demanding a fare above the amount displayed. Cash could still be used for a trip booked and recorded through the app.

How fares and driver payouts would work

Before a passenger confirms a ride, the app would show an estimated fare or, where the service uses offers and acceptance, the fare agreed by the parties. It would also have to show the basis of any surge pricing. The draft proposes that the final fare be no more than 15% above the estimate unless the passenger requests a different route or destination, or causes the vehicle to wait beyond the period disclosed in the app. On a US$10 estimated fare, the proposed ceiling would normally be US$11.50.

The draft also proposes a surge pricing ceiling of twice the fare that would otherwise apply and would ban surge pricing during declared public emergencies or disasters. Platforms would have to lodge their fare methodology with the Commissioner and submit changes at least 14 days before they take effect.

Platform commission or service fees would be capped at a proposed 18% of the fare, exclusive of VAT and the road user charge. On a US$10 fare base, that would put the maximum commission at US$1.80. A driver’s final payout would also depend on any road user charge, applicable tax deductions and other charges agreed in writing and disclosed in the platform’s standard terms. The draft would require a monthly statement showing the fare, commission, road charge, any tax deducted and the net amount paid for each trip.

The proposed seven-day payout deadline applies to amounts due on fares paid electronically. Platforms would also have to provide an electronic payment option through an authorised provider, record cash fares and issue receipts. Where the platform or operator is registered for VAT, the receipt would have to be fiscalised. The 15% fare tolerance, the surge multiplier, the 18% cap and the seven-day payout period appear in square brackets in the draft.

What the ZINARA charge would mean

The vehicle operator would owe a road user charge on each completed trip. The app would collect it by deducting the amount from the fare and would send the money to ZINARA for the Road Fund. The draft offers two possible methods, a flat amount per trip or a percentage of the fare excluding VAT, and specifies neither rate. The distinction matters on short trips. A flat charge would take a larger share of a low fare than of a high fare, while a percentage charge would rise with the fare.

Platforms would submit monthly returns to the Commissioner, ZIMRA and ZINARA, and would give the Commissioner and ZIMRA secure, read-only electronic access to specified trip data. If an authority gives written notice of overdue tax, an unpaid road charge or an expired authorisation covered by the draft, the platform would have 24 hours to deactivate the affected vehicle or driver and give the affected person a reason. Reactivation could follow written confirmation from the issuing authority that the issue had been resolved.

Safety checks and passenger privacy

Passengers would register with their full name and a verified mobile number registered in their own name. A verified national ID or passport number would be required for cash trips or trips starting during the proposed 9 pm to 5 am window. People under 18 could travel on a trip booked by a registered adult, who would be responsible for the booking and payment.

The app would have to verify a driver’s face before they first go online each day and carry out further checks at intervals set by the Commissioner. The platform would also have to provide an emergency alert and operate a safety response centre in Zimbabwe around the clock. If an alert indicates danger to life or personal safety, the centre would notify police within a proposed 15 minutes and provide the vehicle’s location and relevant details. That deadline concerns the platform’s notification to police. Drivers would have a separate duty to report serious incidents to police and the platform as soon as possible and within 24 hours.

Trip records would generally be retained for at least six years. A current copy would ordinarily be kept in Zimbabwe, although an alternative could be approved under the conditions in the draft. Section 23 would allow police to obtain relevant records under a warrant or court order, or through a written request from an officer of at least Inspector rank in specified emergencies. The platform would have to log disclosures and limit emergency disclosures to information strictly necessary for the stated purpose.

What platforms would have to put in place

A foreign company would have to register locally and appoint a Zimbabwean-incorporated representative with a physical office in Zimbabwe. Platform applicants would need a data controller licence, an independent security assessment and proof of tax registration. They would also have to disclose how fares and commissions are calculated and show how they handle complaints. Once accredited, providers would be subject to annual independent security assessments and would have to display their accreditation number on the app and in advertising in Zimbabwe.

Enforcement and the proposed transition

Police or inspecting officers would be able to check the driver’s permit and licence, the endorsed operator’s licence and the trip or profile in the app. A car could be detained if, for example, it had no valid disc, the driver lacked a permit or the provider was unaccredited. An officer would have to give written reasons for detention. The draft proposes fines of up to level four for specified offences, including certain failures involving operating documents, driver duties and platform obligations. Where a listed contravention continues after conviction, each additional day could be treated as a separate offence. The draft also provides for appeals to the Administrative Court within 30 days of notification of a decision by the Commissioner under the regulations.

The draft also preserves local rules on parking, taxi ranks and traffic. Its proposed restriction on additional municipal passenger licences is still bracketed.

Drivers, operators and platforms already operating lawfully would have a proposed 60 days from commencement to apply. Their temporary compliance status would end when their application is decided or on the proposed date of 8 February 2027, whichever comes first. Specified safety, data and revenue duties would apply to platforms from commencement. For drivers assessing the cost of staying on the road, the final Gazette text will resolve several questions the draft leaves open, including the permit fees, the ZINARA charge and the date on which the new requirements would begin.

Breaking News Alerts

Get instant news updates delivered straight to your WhatsApp.

Leave a Comment