If the workshop and the transport office keep different versions of the same vehicle history, you do not have a record system. You have an argument waiting to happen. One side thinks a defect was repaired. The other thinks it is still open. A PMI sheet sits in a tray in the workshop while the transport office is asked for proof of roadworthiness. A vehicle goes out because the planner can only see availability, not the missing sign-off.
The practical answer to how to keep workshop and transport office using the same records is simple in principle and harder in discipline. There must be one master record for each asset, one place where defects live from first report to final sign-off, and one timeline that shows what was found, what was done, who did it and when the vehicle was returned to service. Everyone can have access. Not everyone gets to keep their own version.
Why split records cause real trouble
Separate records usually start for innocent reasons. The workshop keeps job cards because that is how repairs are managed. The transport office keeps a maintenance planner because that is how bookings, MOT dates and PMI intervals are managed. Drivers hand in defect reports on paper. A fitter writes notes on the bench. Someone updates a spreadsheet later. None of that feels unusual until you need to prove what happened.
That is where the trouble starts.
For an O-licence holder, the issue is not whether the repair happened in real life. The issue is whether you can show a clear, consistent maintenance history when DVSA asks for it. If the workshop file says the brake defect was rectified on Tuesday, but the transport office defect log still shows it open on Thursday, you have created doubt around roadworthiness. If the PMI inspection sheet is signed but the follow-up repair evidence is somewhere else, you have made a simple question slow to answer.
Slow answers matter. At a roadside stop, at an investigation, or during a visit to your operating centre, you do not get credit for meaning well. You need to show a joined-up record. That means defect report, assessment, repair action, sign-off and return to service all lining up.
Split records also cause operational damage before compliance damage. Vehicles get booked twice. Parts are ordered twice. Defects are chased by the office after the workshop has already fixed them, or worse, assumed fixed when they are waiting on parts. Drivers lose faith in reporting because they keep seeing the same issue come back. Fitters waste time answering calls about jobs that should be visible on the screen already.
Then there is the effect on OCRS. A missed defect, poor record trail, or vehicle presented in a condition that suggests weak maintenance control can have consequences well beyond one day’s inconvenience. The Traffic Commissioner will not be interested in whether your spreadsheet was current but the workshop whiteboard was not. They will be interested in whether your systems actually controlled maintenance.
This is also one of those areas where small fleets get caught because they rely on memory. With five vehicles, people think they can hold the full picture in their heads. Sometimes they can, until someone is off sick, on holiday, or leaves. Once that happens, all the gaps show at once.
Decide what counts as the master record
If you want the workshop and transport office to work from the same source, decide first what the master record is, and what must be attached to it. Not in theory. In actual fields and actual documents.
For each vehicle and trailer, the master record should hold the identity of the asset and the full maintenance history. At minimum, that means registration, fleet number, VIN or chassis number, make and model, PMI schedule, MOT due date, odometer history, and any manufacturer inspection regime you are following if it affects frequency or scope.
For each defect, the master record needs one live entry that stays with that defect until closure. Not one note in the driver app, one note on a job card and another note in the office diary. One entry. It should include:
- Date and time reported
- Who reported it
- Vehicle or trailer concerned
- Defect description in the driver’s own words where possible
- Whether the defect makes the vehicle unroadworthy, safety related, or suitable for deferred repair
- Decision taken, off road, repair now, monitor, or book in
- Workshop booking date
- Work carried out
- Parts used if relevant
- Name of fitter or technician
- Inspection or quality sign-off
- Date and time returned to service
That same record should also hold the documents that support it. Driver walkaround report. Photos if you use them. Job card. Parts note if needed. Final sign-off. If there was a road test, note it. If the repair was subcontracted, attach the external invoice or worksheet. If the vehicle was prohibited from use internally until repair, record that clearly.
The same approach applies to PMI and preventative maintenance inspection records. A PMI sheet on its own is not enough if it raised defects. The inspection result, the repair work arising from it, and the release back into service need to sit together. Otherwise you are making someone reconstruct the story from several places.
This is where digital systems help, but only if you are strict about the record being the record. If the workshop software is updated properly but the office still keeps a separate spreadsheet "just in case", you have not solved the problem. You have duplicated it.
We built our systems from workshop use because this exact gap causes daily grief. If you want a wider view of transport software that stops the spreadsheet sprawl, that is the point to focus on. Not more places to type, one place to trust.
Give each job a clear owner
Shared records do not mean shared responsibility for everything. In fact, the opposite is true. The record stays in one place, but each stage needs an owner.
Start with defect reporting. The driver owns the initial report. That means the defect is recorded at the time it is found, with enough detail to act on it. If it is a nil defect check, that belongs in the same reporting flow. If your drivers use phones or tablets, the process has to work when they are busy, wet, rushed and parked badly. If it does not, you will get poor reports and late reports.
Next comes triage. Usually this sits with the transport office, traffic office, fleet controller or transport manager, depending on your size. One named person, or one role per shift, decides whether the vehicle is stood down, booked in, or can continue pending repair. This decision must be visible to the workshop and to planning. If nobody owns triage, defects drift.
Booking belongs to the workshop controller or the person running the diary. That person owns date, bay allocation, parts requirement and labour planning. They should not be deciding whether a safety defect can wait. They are booking the work once the operational decision has been made.
Inspection sign-off belongs to the competent person who completed or checked the work. That may be the fitter, a workshop supervisor, or an external repairer if work is subcontracted, but it must be clear. "Done" is not a sign-off. A signature, name, date and outcome is a sign-off.
Document checks belong to the transport office or compliance lead. Their job is not to re-run the repair. Their job is to confirm the record is complete. Was the PMI signed? Are the repair notes attached? Does the MOT certificate match the vehicle? Is the tachograph calibration date where it should be? Are there open defects older than your policy allows?
This matters because overlap creates blind spots. If both workshop and office think the other side is checking missing signatures, nobody checks them. If both think they can close a defect, one will close it before the evidence is in place.
Write the ownership down. Keep it short. For example:
- Driver reports defect
- Transport manager decides use or stand down
- Workshop books and completes repair
- Workshop supervisor signs off
- Compliance admin checks record completeness
- Planner only releases vehicle once status shows fit for service
That is enough to stop most confusion.
Build one timeline from defect to repair
The best way to keep everyone aligned is to make the process follow one timeline. A defect should move through stages, not between disconnected systems.
A practical workflow looks like this.
The driver reports a defect at the end of shift or when found. If it is safety critical, the report triggers immediate review. The vehicle is marked not available until someone with authority changes that status. This is important. Availability should flow from maintenance status, not from wishful thinking in the traffic office.
The transport office reviews the report. If more detail is needed, they get it while the driver is still reachable. They decide whether the vehicle is off road, can be moved to the workshop, or can continue under a controlled deferred repair if the issue is not affecting roadworthiness. That decision is recorded on the defect itself.
The workshop receives the same defect entry, not a retyped summary. The job is booked against that record. If parts are needed, the status changes to waiting for parts. If an inspection shows the fault is different from first reported, the original report stays visible and the diagnostic findings are added beneath it. You do not overwrite history.
Once repaired, the fitter records what was done. Not a novel, just enough to show the work. Replaced nearside trailer marker lamp. Repaired airline chafe at rear crossmember. Adjusted headlamp aim and tested. If the defect was not confirmed, note that too and explain the check carried out.
Then comes sign-off. The sign-off should confirm either that the vehicle is fit to return to service, or that further work is needed. If further work is needed, the defect stays open or a linked follow-on task is created. What must not happen is a job card marked complete while the original defect quietly remains unresolved.
Finally, the vehicle status changes back to available. That change should only happen once the repair record and sign-off are in place. Not because the bay is needed. Not because the planner is under pressure.
This single audit trail is what lets you answer real questions quickly. Why was this vehicle off the road yesterday? Who authorised it back out? Was this defect reported before? Did it arise at PMI? Was the repair completed before the MOT? Those answers should come from one record, not from a phone call chain.
If your current process still depends on whiteboards and memory, it is worth looking at which workshop diary actually keeps a fleet on the road. The diary is not just a calendar. It is where workshop reality meets transport planning.
Keep PMI, MOT and roadworthiness records together
A lot of operators are reasonably good at keeping PMI sheets. Fewer are good at keeping the evidence around them together.
For roadworthiness purposes, the transport office needs to be able to show more than a list of inspection dates. They need the preventative maintenance inspection record itself, any defects found during that inspection, the repairs completed because of it, and the sign-off that returned the vehicle to service. If there was a brake test, keep the result with the PMI. If there was a laden brake test schedule you follow, the evidence needs to be easy to retrieve. If there was an MOT failure and retest, keep both outcomes and the remedial work together.
The same applies to trailers. Trailers are often where record systems become patchy because they move between units and sites. But DVSA will still expect a clear maintenance trail.
A good folder structure helps if you are paper based. A good asset record helps if you are digital. Either way, the rule is the same. For each vehicle or trailer, one place should show:
- Next and previous PMI dates
- PMI inspection sheets
- Defects raised at PMI
- Repair evidence linked to those defects
- Brake test results where applicable
- MOT booking and result
- Any prohibition, repair and clearance evidence if that has occurred
- Supporting certificates that affect legal operation, such as tachograph calibration where you keep those with the vehicle file
In the UK, the expectation around maintenance records sits within the O-licence system and DVSA enforcement practice. If you also operate across Europe, do not assume that a UK style vehicle file is the formal requirement everywhere in the same shape. The legal framework differs by country. But for a UK operator defending roadworthiness, being able to produce one coherent file quickly is the safe standard to work to.
This is one reason we put workshop history at the centre. If you want more on workshop software that keeps fleets roadworthy, start with the records question, not the screens. A neat dashboard is useless if the supporting documents are missing.
Check the system before DVSA does
Do not wait for an annual review to find out your records are drifting apart. Check the process every week.
These checks do not need to be complicated. They need to be consistent.
First, run an open defects report. Look for anything older than your expected repair window. Ask why it is still open. Waiting for parts may be valid. Forgotten may not. Pay special attention to repeat defects, because they often show a closure problem rather than a repair problem.
Second, compare vehicle availability against workshop status. Any vehicle shown as available with an open safety defect needs immediate attention. Any vehicle off road with a completed repair but no sign-off needs chasing.
Third, sample a few completed jobs from the week. Check that each one has the original defect report, the repair note, the sign-off and matching dates. You are looking for gaps like undated repairs, unsigned PMI sheets, or a vehicle returned to service before the recorded completion time.
Fourth, check upcoming PMI and MOT bookings against actual workshop capacity. This is where split systems often show themselves. The office diary says six inspections next week. The workshop diary has space for four. Better to find that on Monday morning than after a missed booking.
Fifth, review document consistency. Registration numbers, trailer numbers, dates and odometer readings should make sense across the file. If a PMI says 412,000 km and the next one says 398,000 km, somebody needs to explain it. If an MOT pass certificate is stored against the wrong vehicle, fix it now, not when asked for it.
Finally, test retrieval. Pick one vehicle and ask a simple question. Show me the last PMI, all defects arising from it, what was done, and when the vehicle went back into service. If that takes twenty minutes and three people, your system is not ready.
This is not glamorous work. It is routine control. But routine control is what protects an O-licence. It is what keeps OCRS from being made worse by avoidable record failures. And it is what gives you a straight answer when a customer, an examiner or the Traffic Commissioner wants to know how you manage maintenance.
The aim is not to create more admin. The aim is to stop the workshop and transport office telling different stories about the same vehicle. Once there is one master record, clear ownership and one timeline from defect to repair, the arguments reduce quickly. More importantly, so do the risks.
What records should both the workshop and transport office see?
At minimum: vehicle details, defect reports, repair status, PMI history, MOT dates and outcomes, and documents that support roadworthiness decisions. If one side cannot see them, you do not have one record.
Can we keep some records on paper and some digitally?
Yes, if the process is controlled. The problem is not paper on its own. The problem is when paper in the workshop and digital notes in the office stop matching.
Who should close a defect?
The person authorised in your process to confirm the vehicle is fit to return to service. That usually needs workshop input, and the transport office must be able to see the evidence behind the decision.
Do PMI sheets and repair jobs need to be linked?
Yes. If a preventative maintenance inspection finds defects, the repair record should show what was done, when, and by whom. Otherwise the inspection file is incomplete.
How often should we check record quality?
Weekly is sensible for most small and mid-sized fleets. Check a sample of vehicles, open defects and recent PMI files. The aim is to catch gaps early, not to create another pile of admin.
