If your units and trailers work with different partners through the week, you need one maintenance trail that links them without pretending they are one asset. The unit keeps its own history. The trailer keeps its own history. What joins them is the evidence of when they ran together, what defects were reported on each, what inspections were due, and what work was carried out. That is the practical answer to how to keep trailer and unit maintenance history together.
In UK operation, that joined history matters for more than tidy records. It affects roadworthiness evidence, PMI planning, MOT preparation, defect control, and what you can put in front of DVSA when someone asks how you manage maintenance on an O-licence. If the unit file says one thing, the trailer file says another, and the daily defect report sits somewhere else, you do not have a maintenance system. You have three piles of paper.
Why split histories cause trouble
Most operators start with separate files because the assets are separate. That part is right. A tractor unit has its own service schedule, MOT history, brake test record, tyre work, tachograph events, and defects. A trailer has its own PMI pattern, brake performance evidence, ABS or EBS faults, bodywork issues, and annual test history. The problem starts when those records never meet.
A common example is a driver reporting a trailer lighting fault on a daily check sheet against the unit they happened to be driving. The workshop fixes the trailer lamp, but the job card is filed under the unit registration because that is what was on the defect report. Three months later, the trailer has another electrical issue. Now the trailer file does not show the previous repair, the unit file shows work that was not on the unit, and nobody can see whether this is a repeat defect.
The same thing happens with brake complaints, ABS warnings, tail lift issues, and tyre damage. If the report starts on the combination but the repair ends up on one asset without a clear link to the other, the history breaks.
That causes trouble in three places.
First, roadworthiness evidence. If DVSA asks how a defect was identified, assessed, repaired, and signed off, you need a straight line from report to rectification. If the defect was found while unit A pulled trailer B, but trailer B's file does not show the report and unit A's file does not show the repair properly, that line is broken.
Second, workshop planning. If you cannot see which trailer has had repeated brake imbalance notes across different units, you miss patterns. If a trailer has been through three different depots and each one logged small defects in isolation, nobody sees the trend until the annual test failure or roadside prohibition.
Third, O-licence paperwork. The Traffic Commissioner and DVSA are not interested in whether your filing problem came from a busy yard or a software limitation. They want to see effective maintenance control. Split histories make you look less in control than you may actually be.
This is worse for operators between five and a hundred vehicles, because that is the point where combinations change too often for memory to cover the gaps, but the business may still be relying on spreadsheets, whiteboards, and emailed PDFs. If you want a clearer structure for inspection planning as well, our guide on planning trailer and unit inspections without missed defects covers that side of it.
What a joined maintenance record needs to show
A joined record does not mean one merged file. It means linked records with enough common fields that the story still makes sense when the unit and trailer part company.
At minimum, each asset needs its own master record. For a unit, that usually means registration mark, fleet number, VIN, make and model, O-licence operating centre if relevant, PMI interval, MOT due date, tachograph inspection dates where applicable, and status such as in service, off road, sold, or hired out. For a trailer, use registration mark where plated, fleet number, chassis number or VIN, trailer type, axle configuration, PMI interval, MOT or annual test due date, and status.
Then each event needs to carry enough detail to stand on its own. In practice, that means:
- event date and time
- asset type, unit or trailer
- asset identifier, registration and or fleet number
- linked partner asset at the time, if there was one
- driver name or ID
- depot or location
- odometer for unit, where relevant
- hubodometer or estimated usage marker for trailer, if you use one
- event type, defect report, PMI, preventative maintenance inspection, repair, brake test, MOT prep, annual test outcome, tyre work, breakdown, safety inspection
- defect description in plain language
- severity or roadworthiness decision
- action taken
- parts used if relevant
- fitter or technician
- sign off, including whether the defect was cleared, deferred, or requires monitoring
- supporting documents, images, brake test printouts, inspection sheets, invoices where needed
The important link is the pairing record. When unit AB12 CDE pulls trailer T45 for a shift, that pairing should be recorded as an operational event. It does not need a novel written around it. It does need a start time, and ideally an end time or at least the next known swap. Without that, later defect reports float free.
This is where many systems fall down. They store inspections nicely, but they do not store the real life relationship between assets on the day a defect was found. We built our tools from workshop use because that pairing matters on the floor. A fitter trying to understand a trailer brake complaint wants to know which unit was attached, whether the complaint repeated with another unit, and whether the issue points to the trailer, the unit, or both.
The joined record also needs document discipline. One source document, one home, linked where needed. A trailer PMI sheet belongs to the trailer record. If that inspection arose from a defect reported while coupled to a specific unit, the defect entry on the unit side should link across to the trailer PMI or repair, not duplicate it.
How to record work when units and trailers swap daily
Daily swaps are where good intentions usually collapse. The only way through is a simple process that people will actually follow on a wet Wednesday at 5:30 in the morning.
We use a four step approach.
Step one, capture the combination in use. Every shift, or every movement if your operation changes often enough, record which unit is on which trailer. This can come from traffic planning, gate control, yard checks, driver app entries, or workshop allocation. It does not need to be fancy. It does need to be timely.
Step two, record defects against the asset that is defective, while also preserving the combination. If a driver reports a marker light out on the trailer, log the defect on the trailer record. Also attach the current unit pairing so you know where and when it was found. If the defect is uncertain, for example poor braking with no clear cause, create linked defect entries on both assets or one combined incident that spawns asset-specific tasks after assessment.
Step three, assess and route the work. The workshop decides whether the issue is unit side, trailer side, both, or no fault found. That assessment must be recorded. Otherwise the original report stays vague forever. If you use digital job control, this is where linked jobs help. One defect can create a unit job and a trailer job without retyping the story.
Step four, sign off the rectification on the correct asset. The repair lives on the asset repaired. The cross link stays in place so anyone reviewing the original report can see the outcome.
This matters for PMI outcomes too. If a trailer comes in for a preventative maintenance inspection after being used behind three different units that week, the PMI result belongs to the trailer. But any defects noted by drivers during those pairings should already be linked into the trailer history. The PMI should confirm, clear, or expand on them. It should not be the first time the workshop hears about them.
A practical rule helps here. Do not let the driver defect report become the permanent workshop history. Drivers report symptoms. Workshops diagnose causes. Keep both. Do not overwrite one with the other.
Where a trailer is hired in, subcontracted, or borrowed, keep the same structure. Mark ownership clearly, keep your own defect and usage evidence, and store external maintenance documents against that trailer record. If the trailer leaves your control, close the pairing and status cleanly. For vehicles going off the road, the planning side is covered in our article on keeping maintenance plans right when vehicles go off the road.
How to handle PMI, MOT and defect records without duplication
Duplication usually starts with a good motive. Someone wants the unit file complete, the trailer file complete, and the workshop file complete. So they save the same PDF three times, type the same defect in two places, and email a fourth copy to transport. Six months later, none of the copies match.
The better approach is one primary record per event, with references from the other places that need to see it.
For PMI, keep the inspection sheet, technician notes, brake test evidence where applicable, and sign off in the asset's own maintenance record. A unit PMI goes on the unit. A trailer PMI goes on the trailer. If the inspection found a linked issue with the other half of the combination, note the reference and create the related job there. Do not turn one PMI into two inspection records.
For MOT and annual test work, do the same. The test booking, prep work, failure items, rectification, and pass evidence belong to the tested asset. If the trailer failed on a brake issue after several in service complaints, the trailer history should show that chain clearly. The unit file may refer to those complaints where they were first raised, but not as duplicate repair records.
For defects, decide your rule once and stick to it. Ours is simple:
- report the defect on the defective asset
- capture the paired asset and driver at the time of report
- if diagnosis is uncertain, open linked assessments
- complete the repair only on the asset repaired
- keep a visible link between report, assessment, and rectification
That keeps each asset's traceable history intact.
It also helps with OCRS exposure. Poor record control will not improve your score, and if roadside encounters raise questions, you need to show a clear maintenance process. Clean records do not guarantee a clean outcome, but confused records make every outcome harder to defend.
One more point for UK operators. Rules and terminology often get blurred online between UK and wider EU practice. Here, the focus is your O-licence undertakings, DVSA expectations, annual test and MOT arrangements as applicable, and evidence of roadworthiness. If you run internationally, you may have additional document and operational requirements, but they do not replace the UK maintenance record you need to show at home.
If your workshop is still juggling paper sheets, spreadsheets, and wall planners, our piece on workshop software that keeps HGV maintenance under control sets out what a workable system needs to do without creating extra admin.
What to do before a DVSA visit or O-licence audit
Before a DVSA visit or an internal O-licence audit, do not start by printing everything. Start by testing whether the story holds together.
Pick a sample of units and trailers. Include one busy unit, one busy trailer, one recently failed or deferred item, and one hired or less regularly used asset if that applies. Then check the following.
First, can you see the PMI schedule and completed inspections in date order for each asset? Look for missing sheets, missing signatures, and unexplained gaps.
Second, where a defect was reported during daily use, can you identify which unit and trailer were paired at the time? If not, your linking process is not strong enough.
Third, can you trace each serious or safety related defect from report to assessment to repair to return to service? Watch for defects closed with vague notes such as "done" or "ok now". That is not evidence.
Fourth, where repeat defects appear, can you see the pattern? A DVSA examiner may ask why the same trailer had repeated lamp faults or brake notes. If your records scatter those events across whichever unit was pulling it at the time, the answer will be weak.
Fifth, check readability. Scans need to be legible. Dates need to make sense. Registrations and fleet numbers need to be consistent. If trailer T045 is also written as TR45 and 45 in different places, someone reviewing the file will miss links that you assumed were obvious.
Sixth, confirm off road periods. If an asset was parked up, hired out, waiting parts, or away for body repair, the maintenance plan should show what happened to its inspection schedule and how you controlled return to service. Gaps without explanation look like missed maintenance.
Seventh, make sure supporting records line up. Brake test evidence, PMI sheets, job cards, parts issues, contractor invoices, and defect sign off should point to the same asset and the same event dates.
Finally, do a cold read. Hand a sample file to someone who was not involved in the jobs, and ask them to explain what happened. If they cannot follow it in five minutes, DVSA will not either.
This is also the point to check workshop and transport are not holding rival versions of the truth. There should be one live maintenance history per asset, not one in the office and another in the bay. If you need a checklist for the broader evidence side, our article on how to prove maintenance was planned for a DVSA visit goes into that in more detail.
Keeping trailer and unit history together is not about combining everything into one giant file. It is about preserving each asset's own record while linking the moments when they worked together. That is what lets you show control. It is what helps the workshop diagnose repeat issues. And it is what stands up when someone asks you to prove how you manage roadworthiness across the fleet.
Should a trailer have its own maintenance file?
Yes. A trailer needs its own history for PMI, defects, repairs and MOT. The point is not to merge it into the unit file, but to link both records so the working history stays clear.
What is the best way to link a unit and trailer record?
Use the registration or fleet number for the unit, the trailer ID for the trailer, and record the dates they worked together. That gives you a traceable link without losing each asset's own history.
Do I need to record every trailer swap?
You need enough evidence to show which unit and trailer were in use and when, especially where defects, repairs or incidents are involved. If swaps are frequent, the record needs to be routine, not guessed later.
Can I keep this in spreadsheets?
You can, if the fleet is small and the discipline is good. The problem starts when trailers move often, paperwork arrives late and nobody can quickly prove what was attached to what on a given date.
Why does this matter for DVSA?
Because maintenance control has to be demonstrable. If records are split, missing or contradictory, it becomes harder to show roadworthiness, defect follow-up and whether the maintenance system is actually working.
