DriverLog: A Digital Driving Assessment and Training Record System
Driving lessons and driving assessments create a lot of information.
A trainer may need to remember what happened during a session, where a mistake occurred, what the student needs to practise, whether the issue was minor or serious, and how progress has changed over time.
Traditionally, much of this is recorded by memory, paper notes, rough comments, or separate files. That can work for a small number of students, but it becomes harder when trainers need to manage multiple learners, prepare reports, support RTO candidates, or review long-term driving progress.
At ComplySA, we have been developing DriverLog, a practical digital record system designed around real driving training and assessment workflows.
Why DriverLog was created
DriverLog was created from a simple problem:
Driving trainers need a clearer way to record what actually happens during a lesson or mock assessment.
In a real driving session, information is created quickly. A trainer may notice:
- missed mirrors
- late or missing signals
- poor road position
- unsafe gap judgement
- issues at traffic lights, roundabouts, junctions or lane changes
- repeated errors across several sessions
- positive improvements that should also be recorded
These details are important, but they are easy to lose if they are not recorded properly at the time.
DriverLog is designed to make that process easier.
What DriverLog does
DriverLog allows a trainer to create student records, start a driving session, record events during the drive, and review the result later.
Each session can include:
- student name and profile details
- trainer or assessor name
- vehicle registration
- session date and time
- licence and pre-drive checks
- road situation, such as traffic light, junction, roundabout, lane change or manoeuvre
- recorded issue or positive observation
- severity level, such as positive, minor, major, failure or note
- GPS-based event location, where available
- session summary and practical feedback
The system then keeps these records connected to the student, so progress can be reviewed across multiple sessions.
Student records and long-term progress
One important part of DriverLog is the student profile system.
A trainer can create or update a student record with details such as:
- student name
- contact details
- student type
- assigned trainer
- licence background
- driving goal
- current ability level
- preferred language
- trainer notes
If a student’s name is entered incorrectly, it can be corrected later without breaking the link to previous driving records. This is important because training records should stay connected to the same student, even when profile details are updated.
DriverLog also helps summarise practical progress, including repeated issues and areas that may need further training.
Event map and session review
Where GPS permission is enabled, DriverLog can show recorded driving events on a map.
This is useful for reviewing where issues occurred during a session. For example, a trainer may be able to see that repeated errors happened around a particular intersection, road environment, or traffic situation.
The map is used as review support only. GPS accuracy can vary, and professional judgement remains essential.
Multi-user trainer access
DriverLog has been designed with trainer access in mind.
A trainer account should only see the student records and driving records assigned to that trainer. Admin users can manage the broader system and review platform-level information.
This matters because student training records contain personal and practical learning information. A digital system should not simply store records; it should also control access properly.
Practical use cases
DriverLog may be useful for:
- driving instructors recording normal student progress
- mock test preparation
- VORT-style assessment preparation
- RTO candidate training
- trainer supervision
- student progress review
- identifying repeated driving issues
- creating clearer records for follow-up lessons
It is not intended to replace professional judgement. It is a record-keeping and review tool that supports the trainer’s decision-making.
Designed from real training experience
A key difference with DriverLog is that it was not designed as a generic form system.
It was built around real driving training situations, including:
- traffic lights
- junctions
- roundabouts
- lane changes
- merging
- manoeuvres
- observation issues
- signalling issues
- road position issues
- judgement and safety-margin concerns
The aim is to make the system practical during or immediately after a lesson, rather than creating paperwork that only looks good in theory.
Privacy and responsible use
DriverLog is being developed with a privacy-conscious approach.
Users should not enter unnecessary sensitive identity information such as licence numbers, dates of birth, passport details, Medicare numbers, bank details, medical details, or copies of identity documents.
The purpose is to record driving training and assessment information, not to store excessive personal information.
DriverLog is also not designed to record or store audio or video. The focus is on structured session records, student progress, event notes and review information.
Current development status
DriverLog is currently being developed and tested as a practical beta system.
The current focus is on:
- improving the student record workflow
- strengthening account access controls
- refining the trainer interface
- testing trial account limits
- improving record search and review
- preparing the system for controlled beta users
Before wider public release, the system will continue to be tested in real training situations to make sure it is stable, clear and practical for trainers.
How ComplySA approaches digital tools
DriverLog reflects the broader ComplySA approach:
Practical systems should support real work, not create extra confusion.
Many small organisations, trainers and education-related businesses need better documentation, records and digital workflows. But those systems must be simple enough to use in real life.
ComplySA helps develop practical tools, forms, policies, workflows and digital systems that match how people actually work.
DriverLog is one example of that approach: a real-world problem, turned into a structured digital solution.
Final thoughts
Driving training is not only about what happens during one lesson. It is also about patterns, progress, repeated issues and clear communication between trainer and student.
A well-designed digital record system can help trainers see those patterns more clearly.
DriverLog is being built to support that goal.