Why instruction-use vehicles need a different tracking approach
Standard fleet driver-behaviour tracking is built on the assumption that drivers are licensed adults responsible for their own driving signatures. Harsh-braking and harsh-acceleration events typically mean a driver is operating outside expected discipline. Speeding events mean the driver chose to speed.
Driving school vehicles invert this assumption. Harsh braking is sometimes the instructor intervening with the dual-control pedal to prevent an incident. Stalling, jerky starts, and uneven acceleration are normal in a learner’s first hours behind the wheel. Wide cornering and over-cautious lane changes are part of the learning process. A standard fleet alert profile would generate dozens of events per lesson, drowning out the genuinely meaningful signals.
Driving school tracking platforms adjust the alert profile to ignore the noise. The thresholds for what counts as a "harsh event" are widened. Per-vehicle aggregate scoring matters more than per-event spike alerts. The tracking record becomes a lesson-by-lesson log of the learner’s progress rather than a daily fire-hose of exception events.
Managing multiple learners per vehicle and per day
A typical driving school vehicle runs six to eight lessons per day, each with a different learner. The tracking system needs to identify which learner was behind the wheel for each lesson — both for the instructor’s lesson-quality records and for any post-lesson incident attribution.
Driver-identification on driving school fleets typically works through RFID tags, mobile-app sign-in, or simple instructor-input at the start of each lesson. The platform associates the lesson period with the named learner, captures all driving data for that period under that learner’s file, and resets at the next lesson.
The learner-by-learner data over time becomes the digital record of the school’s instruction quality. Schools can demonstrate that their learners progressed through a specific curve of competency over their lessons. This matters both for the school’s brand and for any quality-assurance review by the relevant licensing authority.
The AARTO attribution problem in driving school operation
AARTO infringement notices attach to the driver named in the notice. For driving schools, the driver behind the wheel at the time of any infringement is typically the learner, not the registered owner (the school). Without a documented record of who was driving when, infringement points and demerits can default to the registered owner.
Tracking-based driver-identification solves this. Every infringement notice received by the school can be cross-referenced against tracking records: which learner was in which vehicle at the recorded time and location. The learner is correctly identified to the licensing authority and the points attach to the appropriate party, not the school.
Where the infringement occurred during instructor-control of the dual-control vehicle (the instructor genuinely was driving), the tracking record supports the instructor’s account. Without it, the school is reliant on lesson-record paperwork that may or may not be available years later when an infringement is being contested.
Speed limiters and the school-zone overlap
Some driving schools run their fleet vehicles with installed speed limiters set well below the legal limit — typically 80 km/h for learner-licence vehicles and 100 km/h for code-08 instruction vehicles. Speed limiters are particularly common on motorcycles used for learner-licence instruction.
Tracking-based speed monitoring complements physical speed limiters. The platform records every speed event with timestamp and location; the per-learner record builds a clear picture of how the learner handles speed limits over the course of their lessons. Driving instruction in school zones (frequently a feature of urban lesson routes) attracts particularly strict speed compliance.
Some platforms support virtual speed-cap policies — even where the vehicle has no physical limiter, the platform notifies the instructor in-cab when speed exceeds a configured threshold. This becomes a teaching moment rather than an after-the-event scolding, and the alert frequency teaches the learner where their speed-management discipline is weakest.
The operator licence question
Driving schools in SA operate under various licensing regimes depending on the type of instruction offered. Code-08 (light motor vehicle) instruction typically requires registration with the Department of Transport and adherence to standardised curriculum requirements. Code-10 / code-14 (medium-and-heavy commercial) instruction requires additional certifications and is subject to RTMC oversight.
Most provinces require driving school operators to maintain documented records of vehicle conditions, instructor certifications, lesson durations, and incident logs. The volume of paperwork is meaningful for any school operating more than 3-4 vehicles.
Tracking platforms produce the records automatically. Each lesson generates a digital file: vehicle used, instructor on duty, learner identified, route taken, duration, speed signature, and any harsh events. The audit trail is built without separate operational effort.
Insurance for driving school vehicles
Driving school motor cover is a specialist commercial product. The named insured is the school; the regular drivers are the instructors; the learner drivers are accepted as additional named drivers under specific instruction-use conditions. Premium pricing is higher than general commercial motor cover, reflecting the elevated accident frequency on instruction-use vehicles.
Typical cover requirements: comprehensive motor cover on every vehicle, public liability cover (essential — third-party damage during a learner’s incident is common), passenger liability cover for the instructor while in the vehicle, and (in some structures) specific learner-driver damage waiver products.
Tracking is usually required as a condition of cover. Most insurers want approved active tracking on every vehicle in the fleet, driver-behaviour data continuity, and demonstrated operator discipline around incident management. Some insurers require specific instruction-use endorsements — without these, a learner-related claim may be disputed on the basis that the vehicle was being used for instruction without explicit cover acceptance.
Tracker product features that matter for driving schools
Hardware: hardwired installation, ignition-sensing, driver-identification capability (RFID, mobile-app sign-in, or simple instructor-input UI), and panic capability. Battery backup that survives overnight standby is essential — the vehicle sits in the depot overnight between instruction days.
Software: learner-identified lesson records, adjustable harsh-event thresholds (so the alert profile suits instruction-use rather than fleet-use), per-learner progression reports over time, geofenced school-zone speed policies, and integration capability with school-management platforms (lesson booking, billing, instructor scheduling).
Compliance: full export of lesson records for DOT and RTMC audits, driver-identification records for AARTO attribution, retention of data for the periods required by the licensing authority (typically 3-5 years for instruction-use records).
The OneCompare view
Driving schools sit in a regulatory and operational segment that doesn’t map cleanly to general fleet tracking. The right tracking platform recognises this and adjusts the alert profile, the driver-identification flow, and the reporting structure to suit instruction-use. Schools that try to run consumer-grade trackers on instruction-use vehicles typically end up either with alert fatigue or with insurance complications. Pricing and product fit reflected here is based on publicly-published data at the time of writing.