Review OBD fault codes alongside the vehicle and reading date.
Open the vehicle’s fault indication and check the reading behind it. The summary shows recorded codes, their frequency and when they appeared in available driving data, giving you context to discuss with a workshop. Suitable OBD data is required.
Open the vehicle record before acting on a warning
A warning alone does not explain which vehicle or data reading it concerns. Open the vehicle from the fleet overview and review its stored OBD fault codes. The overview indication uses the most recent available drive that included a fault-code read. For example, check when that data was captured before making the next scheduling decision. Codes appear in their vehicle context. Suitable OBD data and correct vehicle association are required; an older indication is not continuous monitoring of the vehicle’s present condition.
Put recurring codes into their recorded context
When an instructor reports a familiar fault again, a single warning symbol offers little context. Open the fault-code summary and review the code, any available description, occurrence count, and first and last appearances in the analysed driving data. For example, check whether the same code appeared across several recorded drives before sharing the observation with a workshop. The summary provides a history within the available analysis. This requires repeated suitable readings; an occurrence count records observations and does not, by itself, establish the severity of a fault.
Review fresh readings after a workshop visit
After a repair, a previously captured code can still appear in the summary. Review the newest fault-code reading and distinguish it from earlier occurrences. For example, compare the time of the new drive with the last recorded appearance of that code. This lets you place the stored indication in context while retaining earlier observations. You need a new suitable reading after the workshop visit. The closed beta OBD view records codes that have been supplied; a qualified assessment is still needed to determine whether the vehicle is fit for use.
Requirements and boundaries
The view does not replace a complete vehicle diagnosis and provides neither a manufacturer connection nor a statutory inspection reminder.
Frequently asked questions
Does the absence of a warning mean the fault memory is empty?
A vehicle without a suitable read provides no evidence about stored codes. An available read containing no codes is a different case. Check the data available before interpreting the absence of a warning.
Does the overview warning use every code in the summary?
The fleet overview uses the newest available drive with a fault-code read. The summary combines occurrences across several analysed drives. A historically visible code therefore need not appear in the latest overview indication.
How do we get access?
Driving school management is in closed beta. Apply with your school; scope, setup and admission are discussed. No immediate access.
Help shape the management beta.
We discuss scope, setup and conditions before arranging participation. Applying does not activate access.