Mpumalanga’s safety department announced on 13 August that eight municipal areas had implemented AARTO from 1 July 2026, covering provincial and local traffic authorities there. The areas named were City of Mbombela, Nkomazi, Thaba Chweu, Steve Tshwete, Emalahleni, Thembisile Hani, Govan Mbeki and Lekwa.
The department said these authorities would use AARTO infringement notices instead of the specified Criminal Procedure Act notices. Earlier notices issued before 1 July remained outstanding where unsettled. Its guidance also described an initial 32-day response period. This is a geographically scoped implementation update, not a claim that every part of AARTO—or a demerit scheme—started everywhere on that date.
The fleet problem is often a handover problem.
Our practical assessment: a notice can pass between a vehicle owner, a transport office and a driver before anyone takes responsibility. A change of process makes that gap worth checking. A shared vehicle needs records that identify who was driving and when; an email inbox needs an owner who actually monitors it.
Do not build a response around a headline or a remembered deadline. Read the actual notice and the issuing authority’s current guidance. The right procedure depends on the document and circumstances. This article summarises a government announcement and is not personalised legal advice.
An admin check worth doing now.
- Identify who receives infringement notices for each vehicle and who acts when that person is away.
- Keep accurate driver-allocation and journey records, with access limited to people who need them.
- Log the issuing authority, notice reference, service details and response deadline; retain proof of the action taken.
- Keep pre-change notices separate from new notices. Do not assume a new process cancels an older obligation.
- Check current RTIA or issuing-authority instructions, and seek qualified advice where a notice or deadline is disputed.
Mpumalanga Department of Community Safety, Security and Liaison · 13 August 2026 ↗︎
Checked 12 Sept 2026. Original reporting summary and clearly labelled editorial interpretation. Operational information reflects the source date, not live status.
Part of the six-week launch retrospective, first published 12 Sept 2026.