If you hire in a vehicle and put it on your O-licence, the record keeping duty sits with us as the operator for the period we use it. That is the point many fleets get wrong. The hire company may own the vehicle. Their workshop may inspect and repair it. But if DVSA asks who controlled its maintenance, defects and roadworthiness while it was working under our licence, the answer needs to be clear, documented and backed by records we actually hold.
So when people ask us how to keep O licence maintenance records for hired in vehicles, the practical answer is this. Treat every hired-in unit or trailer as if it were one of our own from the moment it goes into service. Build a file for it on day one. Agree responsibilities in writing before the keys move. Then make sure every PMI, defect, repair, MOT and off-road period can be followed in date order without chasing three different businesses for missing paperwork.
What records you need for a hired-in vehicle
For a hired-in vehicle used under our O-licence, we need the same core roadworthiness records we would keep for an owned vehicle, plus the hire documents that explain who had control and when.
At minimum, the file should contain:
- the hire agreement, with start date, end date, registration, fleet number if used, and who is responsible for maintenance
- the vehicle details, including VIN, make, model, axle configuration and plating details where relevant
- the current maintenance planner entry, showing the inspection frequency we have set
- copies of each preventative maintenance inspection record completed during the hire
- evidence that defects were reported, assessed and rectified
- repair records for safety related work and other maintenance carried out during the hire
- MOT history and current test certificate details, where applicable
- calibration or service dates for items relevant to compliance if they sit with the vehicle, including tachograph dates where that is part of the hire arrangement
- records of periods off the road, including why the vehicle was unavailable
- any prohibition, roadside encounter, DVSA inspection or other event affecting roadworthiness
- handback notes at the end of hire, especially where defects or damage were identified
For trailers, the same principle applies. If a hired trailer runs under our operation, we need the maintenance history for the period we control it, including PMI records, brake performance evidence where applicable, defects and repairs.
What catches operators out is assuming the hire company will hold everything and send it over if needed. Sometimes they will. Sometimes they will send half of it. Sometimes the workshop did the work but the paperwork stayed in a depot inbox. That is no use when DVSA asks us for records by a deadline.
In the UK, the expectation is straightforward. The operator using the vehicle under the O-licence must be able to produce the maintenance and roadworthiness trail. This is not a case where saying "the rental company has it" gets us very far. If we are called to a Public Inquiry before the Traffic Commissioner, that answer tends to sound worse out loud than it did in the yard.
If you are reviewing your wider setup, our guide to fleet maintenance records that stand up to DVSA covers the standard DVSA will usually expect across the fleet, not just hired-in vehicles.
Who is responsible for what during the hire period?
This needs agreeing before the vehicle turns a wheel for us. Not after the first defect. Not when a PMI date is missed. Before use.
There are usually three parties involved:
- us as the operator
- the hire company or vehicle owner
- the maintenance provider, if different from the hire company
The written agreement should cover five points.
First, who schedules and carries out the PMI. If the hire company says they maintain the vehicle, we still need the inspection interval agreed and recorded. For example, a six weekly or eight weekly cycle, depending on use, age, mileage and our own maintenance policy. We also need to know where the inspections will be done and how quickly the inspection sheets come back to us.
Second, who handles driver defects and daily reporting. In practice, drivers report to us, not to the hire company. So we need a process for logging nil defects and reported defects, deciding whether the vehicle stays in service, and passing jobs to the repairer. If the hire company wants defects reported through its own portal as well, fine, but that does not replace our own record.
Third, who authorises repairs. This matters because a vehicle can sit with a dangerous defect while people argue over cost approval. The agreement should say who can instruct safety critical work immediately, who must be notified, and what happens out of hours.
Fourth, who keeps each document. Our rule is simple. If a document relates to roadworthiness during our period of operation, we keep a copy. The hire company can keep the original if it wants. We still keep the copy.
Fifth, who manages statutory dates. That includes MOT where applicable, tachograph inspection dates, and any manufacturer or safety inspection dates the vehicle arrives with. A hired vehicle can arrive with only a short period left before a test or inspection is due. If nobody checks, the problem becomes ours the moment the vehicle enters service.
Put this in writing, by email or in the hire terms, and keep it in the vehicle file. A verbal understanding with the depot manager is not a system.
How to set up a record pack from day one
The cleanest way is to create a hired-in vehicle pack the same day the booking is confirmed, then complete it before first use.
We use a checklist. It stops the usual gaps.
Start with identity and control:
- registration number
- VIN or chassis number
- hire company name
- hire start date and expected end date
- date the vehicle comes onto our O-licence operation
- internal fleet reference
- operating centre used
- person responsible for compliance on our side
Then add the baseline documents:
- copy of the hire agreement
- copy of the latest PMI record before the hire start, if the vehicle arrives part way through an inspection cycle
- current MOT status or booking date
- tachograph inspection date if relevant
- any open defects, restrictions or pending jobs declared at handover
That last point matters. We want a handover condition record. If the hire vehicle arrives with a warning light on, body damage, a tyre close to limit, or a booked workshop visit next week, note it before it disappears into traffic. Otherwise, every issue found in the first few days gets treated as an argument.
Next, put the vehicle onto the maintenance planner immediately. Do not wait for the first workshop visit. The next PMI date should be visible from day one, based on the agreed interval, not guessed later from memory.
Then set up the live record sections:
- defect reports
- PMI sheets
- repair orders and invoices
- brake test or roller brake test evidence where used
- off-road periods
- correspondence on maintenance decisions
We also recommend a simple front sheet that shows, in one place:
- hire dates
- next PMI due
- MOT due
- tachograph due
- last defect reported
- current status, on road or off road
This is where small fleets usually come unstuck. The records exist, but in four places. Some are in email. Some are in a workshop folder. Some are with the hire desk. Some are in a driver's photo gallery. That is how a straightforward audit turns into a two day paper chase.
If you are still trying to run this on ad hoc spreadsheets and shared drives, our piece on small-fleet maintenance records without spreadsheet risk covers the practical failure points we see most often.
How to handle PMI, defects and unscheduled repairs
A hired-in vehicle should follow the same daily and periodic discipline as the rest of the fleet. The fact that we do not own it changes the contract, not the compliance duty.
For PMI, make sure every inspection sheet shows:
- vehicle identity
- inspection date
- odometer reading if available
- the inspection standard used
- defects found
- rectification details
- who inspected it
- who checked the repair and return to service, where relevant
If the inspection is carried out by the hire company or an external workshop, get the completed sheet promptly. Not at the end of the quarter. Not only when asked. Promptly. Review it. If it is illegible, incomplete or missing rectification details, send it back at once. A poor PMI record is still our problem once the vehicle is on our licence.
For driver defects, keep the same process you use for owned vehicles. Drivers complete a daily walkround check. Nil defects should be recorded if that is your system. Reported defects must show:
- date and time reported
- who reported them
- what the defect was
- whether the vehicle was taken off the road
- who assessed it
- what action was taken
- when it was rectified
- who signed it off
Where a defect goes to the hire company, record that handoff as well. "Emailed hire desk at 07:42, instructed not to use until tyre changed" is far better than "told rental company".
Unscheduled repairs need the same traceability. If the vehicle breaks down on the road, keep:
- breakdown report
- recovery details if used
- diagnosis
- repair authorisation
- job card or invoice
- parts replaced
- date and time returned to service
This matters for repeat faults. If a hired tractor unit has three brake related callouts in six weeks, we need to see that pattern. We also need to decide whether it stays in service. A hired vehicle with a weak maintenance trail can damage OCRS just as effectively as one we own.
Be careful with replacement vehicles during breakdowns. A common scenario is this. Vehicle A is hired in, fails on the road, and the hire company swaps it for Vehicle B by lunchtime. Good operationally. Dangerous administratively. If Vehicle B goes straight to work, we still need its hire record, inspection status, MOT status and maintenance plan from the moment it takes over. "It was only for two days" does not help if something goes wrong.
When a vehicle is off the road, record that properly as well. Dates matter. If a PMI falls due while the vehicle is unavailable, the file should show whether the inspection was completed on time, moved with justification, or whether the vehicle remained out of service until inspected. We covered that wider point in our guide to keeping maintenance plans right when vehicles go off the road.
What DVSA will expect to see at audit or investigation
DVSA will usually want a clean audit trail. Not a story. Not a pile of emails with gaps. A trail.
If a hired-in vehicle is checked at audit, roadside follow-up, desk-based enquiry or investigation, expect to show:
- when we took control of the vehicle
- under what agreement we used it
- how it was added to our maintenance system
- what inspection interval applied
- each PMI completed during the relevant period
- all driver defect reports and rectification records
- evidence of repairs carried out
- MOT status
- any prohibition, encounter or serious defect history
- when the vehicle left our control
Dates need to line up. If the hire started on 3 March and the first defect report in our records is 10 March, DVSA may ask what happened in between. If the PMI sheet says defects found but there is no repair evidence, they may ask whether the vehicle went back into service unrectified. If a roadside stop found a tyre defect and our file shows an inspection three days earlier with no note, they may question the quality of the inspection itself.
This is where hired-in vehicles often look untidy. The records are split between businesses, so the sequence is broken. One document uses the registration, another uses the hire company asset number, another has the wrong date, and the workshop invoice turns up weeks later. DVSA will not tidy that up for us.
The practical standard is that someone should be able to open the file and follow the vehicle through its time with us, from handover to handback, without needing a separate explanation meeting.
If the vehicle is involved in an incident, complaint or maintenance investigation, keep everything. Emails, photos, authorisations, recovery notes, tyre reports, warning lamp diagnostics, all of it. A narrow view of "maintenance records" can become a problem later. At Public Inquiry, the Traffic Commissioner may look beyond the PMI sheet and ask how we exercised control in real life. That includes decisions to keep using a vehicle, delays in rectification, and whether defect reporting was active or just nominal.
There is also a UK specific point worth stating plainly. EU level transport rules are not the same thing as UK operator licensing practice. In Great Britain, the O-licence regime and DVSA enforcement expectations are what matter here, alongside the Traffic Commissioner system. If you operate across borders, that does not reduce the need to hold a UK ready maintenance file for any vehicle used under your licence in Great Britain.
The safest approach is boring. One vehicle, one file, one clear responsibility chain, and no assumptions that somebody else will have the paperwork later. That is the real answer to how to keep O licence maintenance records for hired in vehicles. Decide control before use. Capture every document as you go. Make the file make sense to somebody outside the business. If it would take us half an hour to explain the record, it is not in good enough order yet.
Do hired-in vehicles need their own maintenance file?
Yes. Even on short hire, each vehicle should have its own record trail covering hire dates, PMI, defects, repairs and MOT position while it is used under your O-licence.
Can I rely on the hire company to keep the records?
Not on its own. If the vehicle is operating under your O-licence, you need access to the records and a clear way to produce them to DVSA without delay.
What if the vehicle arrives with recent PMI paperwork?
Keep a copy and check the next due date fits your maintenance system. Do not assume the paperwork will stay with the vehicle or be easy to retrieve later.
Do I need to keep driver defect reports for hired-in vehicles?
Yes. Daily defect reporting still matters on hired-in vehicles, and the reports should show what was found, what action was taken and when the vehicle returned to service.
What happens if maintenance records are split between several parties?
That is common, but it creates risk. If DVSA cannot see a complete history quickly, the gap sits with the operator using the vehicle, not with the paperwork arrangement.
