Small fleets miss PMIs for ordinary reasons. The planner is on a wall chart, the service sheet is in a cab, the workshop is full, a unit is out on a week’s work, and the person who normally chases dates is covering traffic. By the time anyone notices, the vehicle is already late, the file is incomplete, and the explanation to DVSA sounds thinner than it did in your own head.
Good HGV service schedule software for a small fleet is not about dashboards. It is about making it hard to miss the next preventative maintenance inspection, easy to prove what happened, and practical for the workshop that has to do the work. If it cannot hold inspection intervals properly, warn early, show missed visits clearly, and produce records that stand up when the O-licence is under scrutiny, it is not doing the job.
What small fleets actually need from service scheduling software
For a five to one-hundred-vehicle operator, the minimum requirement is simple. The system must know every vehicle, every trailer if applicable, every agreed PMI interval, and the date of the last completed inspection. It then needs to calculate the next due date correctly and keep doing that without manual rework every week.
That means the basics need to be solid.
First, each asset record should hold:
- Registration or fleet number
- Vehicle type and axle configuration where relevant
- MOT due date
- Odometer or kilometre reading
- Engine hours if you use them for some assets
- Planned PMI interval
- First-use date or in-service date where that affects planning
- Maintenance provider, if some work is in-house and some contracted out
Second, the software must schedule by date, not just by mileage. In UK HGV maintenance, PMI control is usually date-led because that is what gets examined first in a compliance review. Mileage can inform the interval, but the planner must make the due date obvious.
Third, it needs alerts that start early enough to be useful. A warning on the due date is not an alert. It is a post-mortem. We need to see upcoming inspections with enough notice to book workshop time, move loads, order parts if recurring defects are expected, and deal with access issues on customer sites.
Fourth, it must cope with reality. Vehicles go off road. Drivers hand defect reports in late. A trailer is still out when it should be in the bay. A system that assumes every inspection happens on the planned day with no exceptions is a system built for demos.
For that reason, the minimum jobs include:
- Forward planning of PMI dates and workshop slots
- Recording completed inspections against the planned event
- Carrying over the actual completion date into the next schedule
- Flagging missed or overdue inspections as exceptions, not hiding them
- Linking defects found at PMI to rectification work
- Keeping a service history that can be produced quickly
- Showing who signed off the inspection and when
If you run your own workshop, or rely on a local commercial workshop, the software also needs to handle the admin around the inspection. Job cards, technician notes, parts used, and sign-off are not extras. They are the record of how roadworthiness was managed.
This is where workshop-led systems tend to differ from generic fleet tools. We built ours from a working HGV workshop because the maintenance record is not finished when the date turns green on a planner. It is finished when the inspection sheet is complete, the defects are either rectified or controlled, and the paperwork is there if DVSA asks for it. That is the practical standard. If you want more on planning vehicle downtime around maintenance, our guide to vehicle off road planning for haulage fleets goes into the day-to-day side of it.
Spreadsheet, generic fleet system or workshop-led tool
Most small operators start in one of three places.
The first is the spreadsheet. It is cheap, familiar, and quick to set up. For a handful of vehicles with stable inspection intervals, it can work for a while. A decent sheet can list due dates, MOTs, tyre checks, tachograph inspections, and service bookings. The problem is not that spreadsheets are useless. The problem is that they rely on one careful person doing the same small tasks correctly every week.
They start to break down when:
- Dates are updated manually after each PMI
- More than one person edits the file
- Vehicles move between depots or maintenance providers
- You need an audit trail
- A missed inspection has to be explained months later
- Defect sheets and invoices sit in separate folders with no link back to the planned inspection
The second is the generic fleet system. This usually gives a cleaner planner and better reminders than a spreadsheet. It may also include fuel, driver records, fines, or telematics integrations. That can be useful. But many generic systems are strongest in fleet administration, not workshop process.
That matters because the weak point in small-fleet compliance is often the handover between planner and workshop. The vehicle is shown as booked, but where is the inspection sheet? Were the brake readings entered? Which defects were found? Was the repair done at the same visit or deferred? Who signed it off? A lot of generic systems lose detail here, or push it into attachments and free text.
The third option is the workshop-led tool. This starts from the maintenance event itself. The planned PMI becomes a job. The job has an inspection record. Defects become repair work. Parts, labour and sign-off sit with the vehicle history. That is usually a better fit where roadworthiness is the main risk, especially for operators in the five to one-hundred-vehicle bracket who do not have a separate compliance department to tidy things up afterwards.
That does not mean every workshop-led system will suit every operator. Some are built for large dealer groups and are too heavy for a small fleet. Some are really garage software with HGV labels stuck on. The point is simpler. If the maintenance process is what can damage your O-licence, then the software should be strongest there.
We have written before about why fleet software breaks down in a busy workshop, because that is exactly where many systems start to show the gap between a clean demo and a working day.
How to judge PMI scheduling without trusting the demo
Demos are tidy. Workshops are not. So judge the system by the awkward cases.
Start with alerts. Ask to see exactly how upcoming PMIs are flagged. Can we set warning periods by days in advance? Can different users receive different alerts? Can the system show what is due this week, next week, and already overdue, without exporting to Excel to make sense of it?
Then check inspection history. Pick one vehicle and ask to see:
- Planned PMI dates
- Actual completed dates
- Any missed or moved visits
- Copies of inspection records
- Defects found
- Rectification status
If that history is split across several screens, or depends on someone uploading PDFs by hand after the event, you are looking at more admin than the sales call suggests.
Planner views matter as well. The right question is not whether the calendar looks nice. It is whether a transport manager and a workshop controller can both use it. We need to see due inspections by vehicle, by week, by maintenance provider, and by status. If some assets are inspected in-house and others by an external workshop, that should be obvious.
Missed-visit handling is one of the best tests. Ask what happens when a vehicle does not attend its booked PMI. A weak system will simply let the date pass and show the vehicle as late. A better one will preserve the missed booking, record why it was missed, and make the overdue status impossible to ignore until a new date is arranged and the work is done.
That matters for O-licence compliance. When DVSA or the Traffic Commissioner looks at maintenance control, they are not only interested in the inspections that happened on time. They want to understand exceptions. Why was it missed? Was the vehicle used? What action did you take? A proper system helps us answer those questions with records, not memory.
Also check how the next PMI is calculated. Some operators plan the next date from the scheduled due date to preserve the inspection frequency. Others work from the actual completion date within the agreed tolerance and policy. The software should support the maintenance regime you operate and make that rule clear. If it is vague on this point, be careful.
Finally, ask for evidence output. Can the system produce a clear maintenance history for one vehicle over a chosen period? Can it show the inspection interval used, the inspections completed, and the exceptions? Our own operator compliance software for HGV maintenance records is built around those practical outputs because they are what people need when the questions stop being theoretical.
The records that matter when DVSA asks questions
When DVSA asks for maintenance records, speed matters, but clarity matters more. You want to be able to produce a file for a vehicle that shows a sensible, consistent story of roadworthiness management.
The key records are usually:
- The PMI schedule
- Completed preventative maintenance inspection sheets
- Repair records linked to defects found
- Driver defect reports and the action taken
- MOT history where relevant to the issue
- Brake test results, where they form part of the maintenance record
- Evidence of safety inspections for trailers as well as units
- Records of any third-party maintenance visits
- Details of vehicles off road, if that explains missed use or changed scheduling
For UK operators, this needs to fit the expectations around the O-licence regime. That is the practical framework most small fleets are working under. If someone is reading material from a wider EU source, be careful. The broad idea of maintaining commercial vehicles is shared, but the compliance evidence expected by UK authorities is tied to UK operator licensing and DVSA enforcement.
The useful question is not just whether the software stores documents. Plenty do. The question is whether it links them properly.
For example, if a driver reports a brake issue in a daily defect check, can that report be tied to the workshop job where it was inspected and repaired? If a PMI notes tyre damage and a lamp defect, can we see whether both were rectified before the vehicle returned to service? If a vehicle later attracts attention because of a roadside prohibition or poor OCRS performance, can we pull the relevant maintenance trail without digging through emails and filing cabinets?
Service history also needs to be readable by someone outside your business. A printout or export full of internal abbreviations and half-complete notes does not help when you are trying to show control. The record should show dates, odometer readings where relevant, inspection type, outcome, defects, rectification, and sign-off in plain terms.
The same applies to tachograph related workshop events if you record them in the same system. Not every maintenance platform handles them, and they are not the same as PMIs, but if the system is your operational record it should at least make related dates and documents easy to find.
Choosing software that works in a real workshop
A workshop-friendly system starts with job creation. If a planned PMI becomes a job in one click, with the vehicle details and inspection type already there, admin stays under control. If someone has to re-enter the same information into a second screen, errors creep in and booked work goes missing.
Technician input is the next test. Can the fitter record findings quickly from the bay? Can they mark pass, monitor, repair, or further action needed without writing a novel? Can they add measurements, notes and photos where needed? If the only practical way to complete the record is to scribble on paper and have someone retype it later, you are back to a broken chain of evidence.
Parts handling matters too, even in a small operation. Not because every fleet needs a full stock control system, but because recurring maintenance work often needs basic traceability. If brake components, lamps, filters or other common items are fitted, the job record should show what was used. Otherwise the workshop history tells only half the story.
Sign-off is another place where software often looks better in sales material than in daily use. We need to know:
- Who completed the inspection
- Who checked or authorised the work
- When the vehicle was released
- Whether outstanding defects remained
- Whether the vehicle was stopped from use pending repair
That last point is important. Real workshops sometimes find something that means the vehicle should not go back out. The system should make that status obvious. It should not depend on a verbal message and a sticky note.
For operators using external maintenance providers, the same principles still apply. You may not need technicians logging directly into your system, but you do need a clean way to bring completed inspection records and rectification details into the vehicle history without chasing paperwork for weeks.
This is exactly why our software came out of Woolpit Truck Repairs. We did not start with a product brief. We started with jobs coming through the door, inspections to complete, defects to fix, and customers who needed records that made sense months later. That background tends to show in the details.
What a small fleet should ask before buying
Before buying, keep the questions practical.
Ask how the system is set up. Who loads the vehicles, trailers, PMI intervals, MOT dates and existing history? If the answer is effectively "you do it all in your spare time", budget for a slower start than the brochure implies.
Ask how support works. When a planner date looks wrong, a completed inspection does not attach properly, or a user cannot sign off a job, who answers the phone or email? Software for roadworthiness control is not something you can leave broken until next quarter.
Ask how pricing changes as you add vehicles, users, trailers or workshops. The cheapest option at ten vehicles is not always the cheapest at forty. Equally, do not pay enterprise money for functions you will never use.
Ask about data ownership and export. If you leave, can you take your maintenance history, inspection records and attachments in a usable format? "Usable" matters. A pile of unnamed files is not a proper export.
Ask whether the system fits your maintenance arrangement. A fleet with one depot workshop needs something different from an operator that subcontracts all PMIs. A mixed arrangement needs both. If the software only works neatly in one model, that will show up quickly.
Finally, ask to see one complete vehicle story, not a feature tour. We want to see an asset created, a PMI scheduled, a job raised, an inspection completed, a defect repaired, the vehicle signed off, and the next visit planned. If the supplier cannot show that cleanly, the gaps will land on your desk later.
For many small operators, the right choice is not the system with the longest feature list. It is the one that makes missed PMIs less likely, overdue inspections more visible, and maintenance records easier to defend. That is the standard we work to, because it is the standard a real workshop has to live with.
Can small fleets manage HGV service schedules in Excel?
Some do at first. It usually works until vehicles, trailers, defects and PMI dates start moving at once. The weak points are missed reminders, poor audit trail and no clear workshop history.
Does service schedule software help with O-licence compliance?
It can help by keeping maintenance planning and records in order. It does not remove the operator’s responsibility. You still need suitable inspection intervals, proper repairs and evidence that the system is being used properly.
What should PMI software show at a glance?
Due dates, overdue vehicles, completed inspections, vehicles off road, linked defects and a clear history by unit. If you cannot see that quickly, the software will create admin rather than remove it.
Do workshops and operators need the same software?
Not always. An operator needs control of schedule, records and roadworthiness. A workshop also needs job flow, technician input and sign-off. The best fit depends on who actually runs the maintenance process day to day.
Is a bigger fleet platform better for a small operator?
Not by default. Large platforms often carry cost and setup work that small fleets do not need. If PMI planning and maintenance records are the main problem, a simpler workshop-led system may fit better.
