A workshop diary keeps a fleet on the road when it does more than fill bays. It needs to show what is due, what has been missed, what has gone off the road, what can wait until the weekend, and what must be acted on before the vehicle turns a wheel again. In a UK fleet, that means it is part planning tool, part control system, and part evidence file.
For small operators, almost anything works for a while. A wall planner, a whiteboard, a spreadsheet, a shared calendar. The problem starts when the diary stops being a simple booking sheet and becomes the place where PMI intervals, defect repairs, MOT preparation, parts delays and roadworthiness decisions all meet. That is usually the point where the wrong system starts costing days, not minutes.
What a workshop diary needs to do in a UK fleet
The practical job is simple to describe. A workshop diary for commercial vehicle maintenance should tell us three things at a glance.
First, what work is due and when. That includes PMI, servicing, MOT preparation, brake testing, tachograph inspections where relevant, and any manufacturer or in-house scheduled work.
Second, what is booked and what has not been completed. A due date is not the same as a completed job. If a vehicle was scheduled for a preventative maintenance inspection on Tuesday and the job slipped to Friday, the diary must show that clearly. Not buried in a note. Not assumed because the fitter was off sick. Clearly.
Third, what affects roadworthiness right now. A vehicle with an open safety defect is not just another line on a planner. It needs a status that changes the transport decision. Can it go out, yes or no. If not, who made that call, when, and what evidence sits behind it.
Under the O-licence regime, this matters because maintenance planning is not separate from operator compliance. The person named on the licence, or the transport manager acting for the operator, needs control over inspection intervals, repair follow-up, and the records that show the system is actually working. If DVSA asks questions, a diary that only shows bookings is not enough.
A proper diary also needs to handle missed dates honestly. In the real world, jobs move. Parts do not arrive. Drivers bring vehicles back late. Agency cover turns up and the workshop loses a bay to urgent defects. None of that is unusual. The issue is whether the diary shows the original due date, the reason for the move, the rebooked date, and whether the vehicle remained in service in the meantime. If it did, someone should be able to justify that decision.
That is where many systems fail. They are good at booking. They are weak at control.
Wall planners and whiteboards
Manual workshop diaries still have their place. We know why workshops use them, because they are quick. A whiteboard by the office door can show this week’s bookings in ten seconds. A wall planner can help the foreman balance bays, fitters and mobile jobs. If you run five or six vehicles, keep everything in one yard, and the same two people make every maintenance decision, manual planning can work.
It works best when the diary is only doing one job, workshop loading. It is visible. Nobody needs a login. If a vehicle arrives with a blown air line or a lamp defect, the board gets changed there and then.
But manual systems break down fast once the fleet grows, the work gets split across sites, or responsibility sits with more than one person. The first problem is version control. The board in the workshop is current only for the people standing in front of it. The transport office may be working from yesterday’s photo. The owner may be looking at a notebook in the pickup. None of them are wrong on purpose. They are just looking at different truths.
The second problem is history. When a PMI date is moved on a whiteboard, the old date is gone unless somebody writes it down elsewhere. If a vehicle misses an inspection interval, you need to know what happened. “It was on the board” is not a maintenance record.
The third problem is roadworthiness control. A board can say “do not use” in red marker. It cannot stop that message being wiped off, missed on a night shift, or ignored by someone who thinks the defect is minor. Once your workshop diary is also part of your compliance process, manual systems rely too heavily on memory and discipline.
There is also a practical risk with MOT preparation and defect work. Workshop boards tend to get crowded. Planned jobs and urgent jobs end up mixed together. The result is that the urgent work shouts loudest, while scheduled maintenance quietly slips. That is exactly how fleets drift into overdue PMI, poor follow-up on defects, and rising OCRS pressure.
For a single workshop with a tight team, a board is still useful as a visual layer. As the master record, it is weak.
Spreadsheets and shared calendars
The next step up is usually Excel, Google Sheets, Outlook calendars, or some mix of all three. This often feels like a grown-up solution because it is searchable, shareable and cheap. For a fleet beyond a handful of vehicles, it can be better than a whiteboard. It can also fail in ways that are harder to spot.
Spreadsheets are good at listing due dates. They are less good at reflecting what happened in the workshop. Someone has to keep them current, and that job usually falls between roles. The workshop thinks the traffic office updates it. The traffic office assumes the workshop has done it. Then a vehicle gets a PMI a week late, the job sheet is in a tray, and the spreadsheet still shows it as due tomorrow.
Shared calendars have a similar problem. They are built around appointments, not maintenance control. A calendar event can say “Unit 27 PMI 08:00”. It does not naturally show whether the inspection was completed, whether defects were raised, whether those defects were safety critical, whether the vehicle was returned to service, or whether the paperwork was signed off.
The common failure points are predictable.
One is hidden overdue work. In spreadsheets, overdue items often sit on a tab nobody checks daily, or in a conditional format that stops standing out once everything is amber. In calendars, yesterday’s missed job simply disappears into the past unless somebody manually rebooks it.
Another is no proper link between planned work and actual records. You may have one sheet for due dates, another for completed inspections, another for defects, and a folder full of scanned sheets. That is not one system. It is a patchwork held together by habit.
Another is poor visibility of vehicle off road time. A transport manager needs to know not just what is booked, but what is unavailable and why. Is the vehicle in for PMI, waiting for parts, away for MOT, or parked with a prohibition risk defect? If you want a clearer view of that side of planning, our piece on vehicle off road planning for haulage fleets goes into it in more detail.
Spreadsheets also struggle with evidence. When DVSA asks how you control inspection intervals, how you handle missed inspections, or how you ensure defects are repaired before use, you need more than cells and colour coding. You need a trail. We covered the record side of that in what DVSA checks in maintenance records.
For very small fleets, spreadsheets can hold for a while. Past that, they usually survive because people are used to them, not because they are doing the job well.
Generic garage software versus commercial vehicle reality
A lot of garage software looks convincing in a demo. Jobs, bookings, parts, labour, invoices. For car workshops, much of it is perfectly decent. The gap appears when you try to use it for HGV and commercial vehicle maintenance in a business operating under an O-licence.
The first gap is inspection structure. A general garage system often treats every job as a repair order. Commercial vehicle maintenance needs recurring inspection schedules tied to fleet policy, usage, and stated intervals. A PMI is not just another booking. It sits inside your declared maintenance system and links directly to roadworthiness.
The second gap is defect handling. In a commercial fleet, defects come in from walkaround checks, driver reports, roadside events and workshop findings. Some need immediate action. Some can be monitored. Some take the vehicle off the road. Generic systems often record the repair, but not the decision path around use, deferment, authorisation and return to service.
The third gap is evidence for the regulator. Under UK rules, operators of goods vehicles need to be able to show effective maintenance control. In some EU contexts the structure around road transport maintenance records is different, and the operator licensing framework is not the same. In the UK, the O-licence and the expectations of the Traffic Commissioner make that control framework specific. A garage package built for retail servicing does not usually understand that.
Then there is workshop reality. HGV jobs overrun. Parts are back ordered. A trailer inspection turns into brake work. A planned service loses a bay to an urgent unit with a steering issue. Generic systems often assume a neat start and finish. Busy commercial workshops do not work like that. We see this constantly, which is why we wrote about why fleet software breaks down in a busy workshop.
There is also the difference between customer communication and operator control. Many garage systems are built to text a retail customer, build an estimate, and close an invoice. Useful features, but they are not the heart of fleet maintenance. The heart is knowing what is due, what is safe, what is late, and what can be proved.
Workshop-led maintenance software
Purpose-built workshop diary software should be judged on whether it reflects how a commercial vehicle workshop actually runs.
Start with PMI visibility. We need to see due dates by vehicle, trailer and asset. We need to know what is already booked, what is coming due, and what has crossed the line. We also need the original due date to remain visible if the booking moves. Otherwise there is no honest record of slippage.
Then defects. A proper system should link defects to inspections, driver reports and repair jobs. It should show status clearly. Open, in progress, awaiting parts, completed, checked, returned to service. Safety defects should stand out without anyone having to read a paragraph of notes.
MOT preparation matters too. In practice, that means seeing test dates, pre-test work, outstanding defects and whether the vehicle is actually ready to present. Plenty of systems can remind you an MOT is due. Fewer help the workshop manage the work that gets it there in a passable state.
Parts and labour need to be inside the same picture, not off in separate software if that creates blind spots. If a vehicle is waiting for a brake chamber, the diary should tell us that. If a fitter has spent six hours on a job booked for two, that should be visible as well, because it affects capacity for the rest of the week.
Most important is evidence. If DVSA asks how we know vehicles received inspections on time, how missed inspections are controlled, how defects are closed, or why a vehicle was used between dates, the answers should come from the system without a scavenger hunt through folders and inboxes. That is one reason we built maintenance evidence for operator compliance around workshop records, not just office reports.
This is also where workshop-led software differs from software written from a distance. Because we run Woolpit Truck Repairs every day, we know the diary cannot be a polished front end sitting on top of messy reality. It has to survive late returns, fitter shortages, waiting parts, failed brake tests, interrupted PMIs and the constant question from traffic, “Can I have that unit back today?”
How to choose without buying the wrong thing
If you run between five and a hundred vehicles, do not buy on screens alone. Buy on control. A practical shortlist helps.
First, can it show due, booked, overdue and completed work separately, by vehicle and by date? If overdue work is hidden or overwritten, walk away.
Second, does it keep the original due date when a job is moved? Missed dates happen. Losing the evidence of them is worse.
Third, can it link PMI, defects, repairs, MOT preparation and return to service in one trail? If those sit in separate modules that do not talk to each other, you will be back to chasing paperwork.
Fourth, does it support workshop reality, not just planned jobs? Ask how it handles interrupted inspections, vehicles waiting for parts, mobile repairs, and jobs that uncover more work halfway through.
Fifth, what does the transport manager see that the workshop controller sees differently? Both need visibility, but not the same screen. The workshop needs loading and status. The transport side needs availability, compliance risk and roadworthiness decisions.
Sixth, what happens when DVSA asks questions? Ask the supplier to show missed PMI reporting, defect history, sign-off records and evidence of completion. Not slides. Actual records.
Seventh, how hard is it to use on a bad day? That is the real test. A good system on a quiet Tuesday is easy. The better question is whether it still works when three vehicles come back defected, one MOT slot gets pulled forward, and the parts supplier says tomorrow instead of today.
Finally, check whether the software was built from workshop use or from product assumptions. That sounds like a soft point. It is not. It affects every screen, every status, every missing field that somebody in a real workshop would have asked for in week one.
The right workshop diary for commercial vehicle maintenance is the one that helps us keep vehicles legal, available and properly recorded, without relying on memory or heroics. That is not glamorous. It is the job. And once the fleet is beyond the stage where one person can hold it all in their head, the diary stops being admin and becomes part of how we keep the O-licence safe.
What is a workshop diary in commercial vehicle maintenance?
It is the system used to plan and track workshop time for inspections, repairs, defects, MOT preparation and vehicles waiting for parts or authorisation.
Can a spreadsheet work as a workshop diary?
Yes, for a very small operation. It usually starts to struggle when jobs move often, more than one person updates it, or you need a clear history of what changed and why.
Does a workshop diary help with DVSA compliance?
It can help show control of maintenance and roadworthiness, but only if it is used properly and backed by the right inspection records, defect handling and follow-up.
Is generic garage software good enough for HGV workshops?
Sometimes for basic booking. Often not for PMI planning, O-licence expectations, fleet visibility and the level of control needed for commercial vehicle maintenance.
What should a transport manager look for first?
Start with visibility. You need to see what is due, what is late, what is off the road and what has moved, without hunting through tabs, emails and paper.
