If defects are being missed, the problem is usually not that nobody cares. It is that the workshop cannot see, in one place and in the right order, what has been reported, what has been inspected, what parts are waiting, what is safe to defer, and what must not leave the yard. Good job tracking in a commercial vehicle workshop is not a nicer booking sheet. It is the control point between defect reporting, repair, PMI, MOT preparation, vehicle off road time and the evidence you need if DVSA asks questions later.
For HGVs and vans, the standard is higher than in a car garage. A missed advisory can become a prohibition. A job left half closed can break the chain of evidence for roadworthiness. A vehicle can look booked in on a diary, while still having no signed inspection record, no technician notes and no clear decision on whether it is fit to return to service. That is the gap proper commercial vehicle workshop job tracking has to close.
What job tracking needs to do in a commercial vehicle workshop
A workshop system for trucks and vans has to do more than show that unit 123 is booked in on Thursday.
It needs to hold the whole life of the job.
That starts with the trigger. A job may begin from a driver defect report, a PMI schedule, a brake issue found during a road test, an MOT failure, a tachograph fault, a tyre inspection, or a phone call from traffic saying a vehicle has gone down at a customer site. Those are different types of work. They need different priorities, different records and often different approval routes.
A proper tracking process should show at least these points:
- what the vehicle is in for
- who reported the issue
- when it was reported
- whether the defect affects roadworthiness
- whether the vehicle is off the road, restricted, or still in service
- what diagnosis has been done
- what work has been authorised
- what parts are needed
- who is doing the work
- what is still outstanding
- what checks were completed before release
- who signed the vehicle back into service
That sounds basic. In practice it is where workshops lose control.
Take a common example. A unit comes in for a preventative maintenance inspection. During the inspection, the technician finds a worn brake chamber, a marker light out, and damage to an airline. The PMI itself is one record. The remedial work is another. If the parts are not in stock, the workshop needs to decide whether the vehicle stays off road, whether a temporary control is possible, or whether the issue is non-safety related and can be planned. If that decision lives in somebody's head, or on a whiteboard that gets rubbed off, you do not have job tracking. You have memory.
The system also needs to cope with linked jobs. A booked PMI may uncover repairs. A reported defect may need a road test. A failed MOT may create several remedial tasks and a retest booking. A trailer and unit may be coupled operationally but need separate records. Vans have the same problem on a smaller scale. The moment one booking turns into four pieces of work, simple diaries start to fail.
Job tracking also has to reflect workshop reality. Technicians get interrupted. Vehicles arrive late. Parts do not turn up. A roadside job gets dragged into the middle of the day. If your system assumes every job starts and finishes exactly as planned, it is not built for commercial use.
This is why we built from workshop practice first. At Woolpit Truck Repairs, the question was never "can we list bookings?" It was "can we tell, right now, which vehicles are waiting diagnosis, which are waiting parts, which have open safety defects, and which can legally and safely go back out?"
If you want a wider look at the difference between booking and control, our piece on truck workshop booking systems that stop missed jobs goes into that in more detail.
Whiteboards, spreadsheets and generic job systems compared
Most UK workshops have used all three.
Whiteboards are fast. Everyone can see them. You can change the day in seconds. For a small operation with one or two fitters and a handful of vehicles, they can work well enough for planning space in the bay.
Their weakness is everything after that.
A whiteboard does not keep history. It does not show what was found on the job. It does not prove who decided a vehicle was fit to return to service. It cannot separate booked work from safety critical defects unless somebody writes that clearly every time. It also depends on people being in the same room. Once the transport manager is on the road, or the workshop controller is off, the board stops being a reliable source.
Spreadsheets usually come next. They are better for history and filtering. You can list due dates, job numbers, defect categories and parts on order. For a while, they feel like control.
Then the pressure starts.
One person edits the wrong line. Another filters the sheet and forgets to clear it. A PMI gets entered as complete before the rectification is done. A defect report is copied into the planner but never into the vehicle file. A technician updates paper notes, but nobody transfers them back. The spreadsheet becomes a planning list, not a workshop record.
The bigger problem is that spreadsheets do not manage workflow well. They show data. They do not enforce process. They do not stop a job being treated as closed when there are still outstanding safety items. They do not naturally link inspections, defects, authorisation and release checks.
Generic job systems, often borrowed from car repair or general service software, fix some of that. They usually give you a digital job card, customer record, parts lines and labour entries. They can be a step up from manual methods.
But many break under real workshop pressure because they are not built around commercial vehicle maintenance.
The warning signs are easy to spot:
- the system is customer invoice led, not roadworthiness led
- inspections are bolted on, not central
- there is no clean link between defect reporting and workshop action
- trailer records are awkward
- vehicle off road status is unclear
- recurring PMI schedules are weak
- there is no practical oversight for the person managing the O-licence
- job closure does not require the records you would want to see after a DVSA stop
That last point matters. In a car garage, an untidy closed job is usually an admin problem. In a truck workshop, it can become a compliance problem.
We see this often with systems that look good in a demo. They can create jobs, assign labour and print invoices. But when a vehicle has an open driver defect, a scheduled PMI, a delayed part and an MOT due next week, the software has no clear operational view. That is where why good fleet software breaks down in a busy workshop becomes very real.
How to compare workshop software without buying the wrong thing
The safest way to compare systems is not to start with features. Start with your actual jobs.
Take ten recent examples from your workshop. Include a PMI with rectification, a reported defect that took two visits to fix, a roadside breakdown, an MOT fail, a van service, a trailer brake issue, and a job delayed for parts. Then ask each software supplier to show exactly how those jobs are created, updated, paused, reopened and closed.
If they stay in slideshow mode, you have your answer.
For commercial vehicle job tracking, we would compare software against these practical points.
First, can it separate job types properly?
A PMI is not the same as a service. A safety defect is not the same as a cosmetic repair. A roadside breakdown is not the same as a booked inspection. You need to sort, prioritise and report on those differences.
Second, can it show live workshop status without guesswork?
You should be able to see what is booked, what is in progress, what is waiting parts, what is awaiting authorisation, and what is complete but not yet released. If the only status options are open and closed, it will not be enough.
Third, does it support vehicle based history?
When DVSA or a Traffic Commissioner looks at maintenance, they are not interested in whether your invoice process was neat. They want to know what happened to that vehicle, when, why, and with what follow up. The record needs to stay with the asset.
Fourth, can it handle recurring inspections and planned maintenance?
For UK operators, PMI control is central. The workshop system needs to work with inspection intervals, due dates and planning windows. If it treats every inspection as a one-off booking, you will end up managing schedules elsewhere.
Fifth, what does closure actually mean?
A closed job should mean the work is done, the findings are recorded, any safety decision is clear, and the vehicle's release is documented. If a job can be closed with no notes, no defect outcome and no sign-off, you are storing risk.
Sixth, can it deal with parts delay without losing the thread?
This is where many systems become messy. The job should remain visible, with the reason for delay, expected next action and vehicle status clear. Otherwise the workshop starts keeping a second list on paper or WhatsApp.
Seventh, is the system usable from the workshop floor?
If technicians cannot update it quickly, they will not. If every note needs an office user to retype it later, the records will drift. Workshop software has to survive dirty hands, interruptions and short bursts of input.
Eighth, does it support management oversight, not just workshop admin?
The person carrying the O-licence responsibility needs a view of overdue work, open defects, missed inspections, repeat issues and vehicles spending too long in a compromised state. That is different from a service receptionist view.
Ninth, can it work at your size?
A five vehicle fleet does not need enterprise complexity. A hundred vehicle fleet cannot live on a digital whiteboard. The software should fit that middle ground properly.
If you are comparing options now, our overview of workshop software that keeps HGV repairs under control, which includes insights from Woolpit Truck Repairs, sets out the points that matter when the workshop is already busy, not just when somebody is selling to you.
The records that matter for DVSA and O-licence control
In the UK, workshop records do not sit apart from compliance. They are part of it.
For an operator running under an O-licence, the maintenance record has to support roadworthiness and show proper systems of control. The exact format can vary. The standard of evidence cannot.
The records that matter most are these.
A clear inspection history. That means each PMI or preventative maintenance inspection recorded against the vehicle, with the date, mileage or kilometres where used, the findings, the rectification required and the sign off. If inspections are done by an external provider, the operator still needs control of the record.
Defect reporting and rectification records. Driver reported defects, workshop found defects and any follow up action all need to be traceable. It should be obvious whether the issue was safety related, what happened next and when it was put right.
Evidence of repair completion. It is not enough to know that a vehicle came in. You need to know what work was done. Technician notes, parts fitted, test results where relevant, and release checks matter.
MOT related records. A fail sheet on its own is not enough. The useful record is the link between the failure items, the remedial work, and the retest outcome. That gives a proper picture of maintenance control.
Scheduling and missed inspection oversight. If a PMI is moved, there should be a reason. If it is missed, that needs to be visible. A pattern of late inspections is the sort of thing that can damage confidence quickly if DVSA reviews the operation.
Vehicle off road decisions. If a defect affects roadworthiness, the system should show when the vehicle was restricted or stood down, and when it was returned to service. This is often one of the weakest points in manual systems.
Repeat defects and trend visibility. If the same issue appears again and again on the same vehicle, or across several vehicles, management should be able to see it. That is not just good engineering practice. It is evidence of oversight.
This is where workshop data and compliance software need to speak to each other. If the workshop closes jobs one way and the compliance record is updated another way, gaps appear. That is why we link workshop activity with operator compliance records for maintenance control, rather than treating the workshop as a separate island.
A quick point on UK versus wider EU practice. Operators sometimes read general fleet advice written for the EU and assume the same record expectations apply everywhere. The broad principles are similar. The UK compliance context is its own one. O-licence undertakings, DVSA enforcement, OCRS impact and the expectations of the Traffic Commissioner shape what good evidence looks like here. A system that is acceptable in a general European fleet setting may still be weak for a UK goods vehicle operator if it does not support those controls properly.
What changes first when a five to hundred vehicle fleet gets this right
The first change is not usually dramatic. It is quieter than that.
People stop asking where things are.
The transport manager can see which jobs are still open. The workshop knows what is waiting parts. The person responsible for compliance can see whether a defect has actually been rectified or just booked. The phone calls and walk-backs across the yard drop because the answer is in the record.
After that, the next improvements tend to come in a predictable order.
Fewer jobs disappear between report and repair. This is the biggest one. Defects that used to sit in notebooks, texts or memory now stay visible until somebody deals with them.
PMI follow up gets tighter. The inspection itself is only half the job. When the rectification work is linked properly, there is less chance of an item being noted and then lost.
Vehicle off road time becomes easier to plan. Not always shorter, because some jobs really do take as long as they take, but easier to control. You can see the blockers. You can make cleaner decisions on substitute vehicles, outside repair support or rebooking.
Release decisions get safer. Instead of "I think that was done", you have a record of what was found, what was repaired and what checks were completed before the vehicle went back out.
Management sees weak spots earlier. That may be one technician carrying too many interrupted jobs, one vehicle generating repeated defects, or one category of work always slipping. You cannot fix a pattern you cannot see.
Smaller fleets often feel the benefit fastest. At five to twenty vehicles, one missed defect or one poor PMI follow up can upset the whole week. At fifty to a hundred vehicles, the issue is different. The problem is volume. Manual methods no longer hold the moving parts together. In both cases, proper tracking gives control back.
It also makes outside scrutiny less painful. If DVSA visits, or if you need to review your systems after a prohibition, the difference between a proper workshop record and a pile of part-complete notes is enormous.
That is the standard we work to because we run the workshop as well as writing the software. The job has to make sense to the fitter using it, the workshop controller planning the day, and the operator carrying the O-licence responsibility. If it does not hold up on the floor, it will not hold up when somebody asks for the records later.
Is workshop job tracking the same as a fleet maintenance system?
No. A fleet maintenance system may schedule PMI and hold vehicle records. Workshop job tracking controls the live job: defect, parts, labour, status, sign-off and what is still waiting.
Can a spreadsheet work for a small commercial vehicle workshop?
It can for a while. It usually fails when jobs pass between people, vehicles have multiple defects, or someone needs a clear audit trail of what was reported, done and signed off.
What should be attached to a workshop job record?
At minimum: vehicle details, reported defect, dates, technician notes, parts used, outcome, and who signed work off. Many operators also need inspection sheets, images and linked PMI records.
Does job tracking software help with DVSA visits?
It can help if it gives clear, consistent records. Software does not make an operator compliant on its own, but it can make it much easier to show how defects and maintenance were controlled.
What is the biggest mistake when choosing workshop software?
Buying for features on a demo instead of checking how the system handles real workshop interruptions, incomplete jobs, waiting parts, repeat defects and handover between office and workshop floor.
