Parts, Workshops and Who Does the Work
Where maintenance is done determines what data you get back, and most fleets never make that a selection criterion.
Running it · Analysis
Condition data is only useful if something acts on it, and what acts on it is a workshop with its own systems and incentives.
The three arrangements
In-house workshop: full control of records, full cost of premises and staff, and the data stays yours.
A contracted network: national coverage, standard rates, and records in their system rather than yours.
Ad hoc local garages: cheapest per job, no consistent record, and no way to see a pattern across the fleet.
The third is common in small fleets and is why their whole-life cost figures cannot be assembled.
What to require whatever the arrangement
Job records returned in a usable form, per vehicle, with parts and labour itemised.
Fault codes recorded as found and as cleared, which is how the triage list improves.
Odometer at every visit, which is the check against the telematics reading.
Defect resolution dates, for the compliance record.
Put these in the contract. Asked afterwards, they arrive as PDFs.
Parts stocking
Holding stock costs capital and space; not holding it costs downtime.
Which is a comparison you can make once the downtime-by-cause figure exists — specifically the "waiting for parts" portion.
Stock what fails predictably and is cheap: filters, bulbs, wipers, common sensors.
Not: major components, which are better sourced when needed.
And review it against actual consumption annually, because stock lists accumulate items for vehicles disposed of years ago.
The data the workshop should receive
The fault code history before the vehicle arrives, so diagnosis starts from information rather than from a driver's description.
Usage since last service, which changes what to inspect.
Recurring issues, which is the difference between fixing a symptom and finding a cause.
Most workshops receive a vehicle and a sentence, and the diagnostic time that follows is billed to you.
Recurring failures
The same component failing repeatedly on one vehicle is a diagnosis failure, not a parts quality issue.
Across a model, it is a purchasing finding.
Track by component and by vehicle, which requires the itemised job records above and is the reason to insist on them.
The measure
First-time fix at the workshop: vehicles returning for the same fault within a period.
Waiting-for-parts days as a proportion of downtime.
And diagnostic labour as a proportion of total labour, which falls when the workshop gets the code history.
Send the code history ahead
Before the vehicle arrives.
Most workshops receive a vehicle and a sentence, and the diagnostic time that follows is billed to you.
Fault history, usage since last service, and any recurring issue.
It changes what they inspect and shortens what they charge for, and it costs an export.
Connect policy and data
The choices in this note can be compared with view the form-based example. Keep the written purpose in control and enable only the information needed at this boundary.