RTMS (SANS 1395) Compliance Checklist for Fleet Operators

The Road Transport Management System (RTMS) has become a commercial requirement for many South African carriers. Large consignors increasingly ask for it in their contracts, and it is a prerequisite for running Performance-Based Standards (PBS) “smart trucks”. Yet the hardest part of RTMS is not passing the audit — it is staying compliant in the eleven months between audits. This checklist breaks SANS 1395 down into the evidence an auditor will actually ask to see.

1. What RTMS and SANS 1395 are

RTMS is an industry-led, government-supported, voluntary self-regulation scheme. It encourages consignors, consignees and road transport operators to implement a management system that demonstrates compliance with road traffic legislation and contributes to protecting road infrastructure, improving road safety and lifting productivity.

The scheme is based on SANS 1395-1, a national standard published by the South African Bureau of Standards (the current edition referenced in industry is SANS 1395-1:2019). Like ISO management-system standards, it does not hand you a set of policies to copy. It requires leadership to set objectives and to run auditable processes and controls that achieve them — which is why two certified operators can look quite different on paper.

The practical requirements cluster around four areas you will hear repeatedly: load and payload management, driver wellness, vehicle maintenance and productivity, held together by management commitment, risk assessment, record-keeping and internal review.

2. How certification and audits work

Certification is done by an external, accredited certification body. The typical cycle looks like this:

• Stage one audit — an overview of your system and documentation, usually short.
• Remediation window — commonly around 90 days to close findings.
• Stage two audit — a detailed check of whether the system actually works, using samples of vehicles, drivers, trips and records.
• Annual surveillance — certificates are typically valid for twelve months, with the full stage one and two audits repeated on a three-year recertification cycle.

That sampling is the key insight. An auditor will pick, say, five vehicles and five drivers and ask to see their records for a period. If one roadworthy expired for three weeks in May, or one driver drove on a lapsed PDP, the sample finds it. Compliance is judged on your worst record, not your best.

3. Management system and risk

• ☐ Signed RTMS policy and measurable objectives (e.g. overloading incidents, crashes, breakdowns, fuel use).
• ☐ Named responsibilities: who owns vehicles, drivers, loads, records and internal review.
• ☐ Transport risk assessment covering route risks, speed management, accident management and traffic-fine management.
• ☐ Legal register: the road traffic legislation and permits that apply to your operation, and how you track them.
• ☐ Agreements with consignors/consignees that make load and safety responsibilities explicit.

4. Vehicles and maintenance

Most findings start here, because vehicle records are numerous and dates expire quietly.

• ☐ Nominated vehicle inventory: every truck, trailer and item of plant under the system, with registration, category, ownership and status.
• ☐ Vehicle fitness documents per vehicle: licence disc, roadworthy certificate, operating licence/permits where applicable, with expiry dates.
• ☐ Preventative maintenance schedule by kilometre, hour-meter or calendar — and evidence each service was done when due.
• ☐ Reactive repairs recorded as job cards, linked to the vehicle and the defect that triggered them.
• ☐ Pre-trip and periodic inspections (DVIRs) with defects captured and closed out before the vehicle is released.
• ☐ Tyre condition and replacement records — tyres are a frequent sample item.
• ☐ A rule, enforced, that a vehicle with an expired document or open safety defect does not go out.

5. Drivers and wellness

• ☐ Driver register with licence code, licence expiry and Professional Driving Permit (PDP) expiry for every driver.
• ☐ Medical fitness evidence where your system requires it, and a process for chronic-condition management.
• ☐ Fatigue management: driving and rest time rules, trip planning that respects them, and evidence of compliance.
• ☐ Induction and ongoing training records per driver (defensive driving, load securing, hazardous goods where relevant).
• ☐ Driver behaviour monitoring (speeding, harsh driving) and the coaching that followed.
• ☐ Alcohol and substance policy with testing records.

Driver medical records are special personal information under POPIA. Holding them in a shared drive with no access control or retention rule solves an RTMS problem by creating a POPIA one. Keep them in a system with role-based access and an access log.

6. Loads and payload

• ☐ Vehicle mass assessment: legal limits (GVM/GCM, axle and axle-unit limits) known per vehicle combination.
• ☐ Load planning and load control procedure — how you prevent overloading at the point of loading.
• ☐ Weighing evidence (weighbridge tickets or approved alternatives) and records of overload incidents and corrective action.
• ☐ Load securing standards and checks.

Load control is usually a physical process at the loading point, owned jointly with the consignor. Keep it documented, and keep the weighbridge data where the auditor can trace a sampled trip to its weight.

7. Operations, incidents and fines

• ☐ Trip records for sampled vehicles: who drove, which vehicle, route, dates.
• ☐ Incident register: crashes, breakdowns, speeding events, cargo loss — with root cause and corrective action.
• ☐ Traffic fine management: every fine logged, nominated to the driver, and analysed for trends.
• ☐ Productivity measures you actually track — utilisation, downtime, fuel consumption, cost per kilometre. (See our guide to calculating fleet cost per kilometre.)

8. Records, documentation and internal review

• ☐ Every document versioned and attributable — you can show what was current on a given date and who uploaded it.
• ☐ Records retrievable per vehicle and per driver without a hunt through email and shared drives.
• ☐ Internal audits on a schedule, with evidence attached and sign-off recorded.
• ☐ Management review minutes showing objectives were reviewed and actions assigned.
• ☐ A corrective-action log that closes the loop on audit findings and incidents.

9. Where operators usually fail — and how to avoid it

Expiries that lapse quietly

A licence disc, roadworthy, PDP or medical runs out on a Friday afternoon and nobody notices until the sample finds it. Fix: automated expiry alerts that reach the responsible person — on the channel they actually read, which in a depot is often WhatsApp, not email — and escalate if nothing happens.

Maintenance that was “done” but can’t be proven

The workshop serviced the truck, but the job card is in a box. Fix: preventative schedules that generate job cards, and job cards closed with evidence against the vehicle.

Evidence assembled the week before the audit

Folders built from three shared drives the night before tell the auditor the system only exists at audit time. Fix: keep evidence on the record as work happens, and export a structured pack per vehicle and driver when asked.

Internal review that never happens

Self-audits are the first thing dropped in a busy month. Fix: recurring self-audit workflows with a due date, an owner and a sign-off.

How SynchPlus ONE helps

SynchPlus ONE for transport operators supports operators working to SANS 1395 by holding the records an RTMS auditor samples, and warning you before they go stale:

• One register for vehicles, trailers and plant, with ownership, category and status.
• Vehicle fitness: roadworthy certificates, licence discs, operating licences and inspection records with automated expiry escalation — by email, SMS, WhatsApp and in-app.
• Maintenance: preventative schedules and reactive job cards with evidence and cost captured against the asset; DVIR inspections with photo evidence and sign-off.
• Driver documents: licences, PDPs and medical certificates tracked to expiry under POPIA-appropriate access controls.
• Incidents and fines linked to the vehicle and driver, feeding true cost-per-km.
• Internal review: recurring self-audit workflows with evidence and sign-off, and an audit evidence export pack your auditor can work through.

SynchPlus ONE complements your telematics rather than replacing it, and it does not perform load control or mass verification — keep your weighbridge and loading procedures for that. It runs in any country — on your servers or our cloud. See the fleet management module and pricing (the Compliance plan includes the audit evidence pack).

Frequently asked questions