Vehicle compliance records for GB goods fleets: the evidence chain

Organise daily checks, defects, repairs, safety inspections and annual tests in one vehicle evidence trail using current DVSA guidance.

A vehicle compliance record should tell a clear story. The operator acquired or hired the vehicle, checked its condition before use, carried out the scheduled inspections, received and resolved defects, arranged any repairs and annual tests, and kept the evidence accessible. A folder containing an MOT certificate and a few workshop invoices cannot tell that story by itself.

This guide focuses on goods vehicle operators in Great Britain. GOV.UK says an operator must keep its vehicles safe and in good condition and keep records of safety inspections and maintenance for at least 15 months. The DVSA roadworthiness guide explains the checks and records in more detail. It includes passenger-carrying vehicles, but the examples here are deliberately goods-focused. Vehicles below operator licensing thresholds, exempt vehicles and Northern Ireland operations need their own scope check.

The aim is a usable evidence chain, not a stack of forms. Record what happened, when, to which vehicle, who decided what to do, and whether the vehicle was released back into service. Keep legal duties, DVSA guidance and your own management choices distinct. The DVSA guide expressly says its “must” statements identify direct legal requirements or operator licence undertakings, while “should” marks strongly recommended practice that may have an alternative approach.

Identify the vehicle and its operating basis

Begin with a reliable vehicle inventory. Give each vehicle and trailer a unique record linked to its registration or other identifier, the business responsible for operating it, its relevant test category, date placed into service, maintenance provider and planned inspection arrangement. Record the person who owns the file inside the business. An invoice without a vehicle identifier is hard to connect to the right asset later.

Do not assume every vehicle follows the same annual test route. The GOV.UK HGV and trailer MOT overview lists the vehicle and trailer categories covered, exemptions and due dates. Covered HGVs usually need an annual test, but first-test dates and trailer rules vary. Certain zero-emission goods vehicles fall into a different MOT class. Check the individual vehicle's category and current service record before adding a universal “HGV MOT due” field.

The operator should also know whether a vehicle is owned, leased, hired or borrowed. A short-term hire can still have a maintenance history and a first-use question. DVSA's roadworthiness guide says an operator is responsible for the roadworthiness of hired, leased or borrowed vehicles in its possession and must have available copies of relevant inspections. The supplier's responsibility to maintain the asset does not eliminate the operator's need to know whether it is safe for the work.

Vehicle compliance records should follow the vehicle through changes in assignment and provider. If a vehicle moves to more arduous work, review whether its existing inspection plan remains suitable. If a trailer is coupled to different tractors, maintain an identifiable trailer file. These are practical controls that make the DVSA evidence easier to retrieve; they are not an official file format.

Capture the first-use decision separately

A newly acquired vehicle should not enter service merely because it has an MOT certificate. The DVSA roadworthiness guide's first-use section says operators must conduct a first-use inspection before using newly acquired equipment on a public highway to satisfy themselves that it is roadworthy. It describes circumstances in which sufficient recent inspection evidence may mean a separate first-use inspection is not needed, such as a comprehensive pre-delivery or pre-rental inspection record.

Record the decision: what evidence was received, which vehicle it covered, its inspection date, who reviewed it, and whether a further inspection was arranged. Keep the evidence with the vehicle file. A supplier's assertion that the vehicle was “checked” is less useful than an identifiable report showing the checks and outcome. A first-use inspection is distinct from the driver's daily walkaround; one cannot simply be relabelled as the other.

The same question arises when a vehicle has been out of service for some time. DVSA says vehicles used only part of a year or brought back after a period off road must be inspected before returning to use. The operator should record the return-to-service condition, inspection and approval, not merely switch the status from inactive to active in a register.

Connect the daily check to defect action

The daily walkaround is the beginning of the day's evidence, not the end of it. GOV.UK's goods operator guidance says drivers must carry out a walkaround before driving a vehicle for the first time each day. DVSA's HGV walkaround guide tells drivers to record and report defects found during the check or noticed during the journey. It identifies core report details including vehicle, date, defect symptoms, assessment, driver and recipient.

A useful daily record links the check to a driver, vehicle, time and outcome. Where no defect is found, a clear nil-defect confirmation can show that the check occurred. Be careful with retention language: DVSA calls at least three months for nil-defect reports a recommendation, while defect reports and their rectification evidence sit in the longer maintenance history. Do not present one period as the universal rule for all check records.

When a defect is reported, route it to a person with authority to assess and act. The record should show the symptom, severity assessment, whether the vehicle was taken out of service, the repair or other resolution, the person who confirmed it, and the return-to-service decision. A defect ticket marked “closed” without a repair or decision record breaks the evidence chain. If a dangerous defect is found during a journey, DVSA says it must be fixed before the journey continues.

Drivers and dispatchers need a simple stop rule. They should know who receives a defect report, who may remove the vehicle from service and who may authorise its return after the appropriate work and review. This is a proposed operating process. It does not replace a competent assessment of the defect or the official roadworthiness standard.

The DVSA's roadworthiness guidance covers the broader fleet maintenance duties. A driver-level record has its own logic, while this page owns the vehicle-level evidence trail.

Give safety inspections their own schedule and reports

Safety inspections are not the same as servicing. The DVSA roadworthiness guide explains that they assess safety-critical and other roadworthiness items and should be planned independently of routine servicing, even when the activities are combined in one workshop visit. A service invoice that says “oil and filters” does not by itself demonstrate a complete safety inspection.

The inspection interval should follow the vehicle and the work. DVSA says to consider age, type, manufacturer's recommendations, load, terrain, mileage and operational conditions. The guide gives usual examples between four and thirteen weeks, with special discussion for older vehicles and trailers. Those examples are guidance, not a single statutory interval for every fleet. A licensed operator's stated safety inspection frequency is part of its own maintenance commitment, and DVSA says it must be met.

For each vehicle, record the declared interval, why it was chosen, the last inspection, next due window and any change made after a review. If one vehicle's use becomes harsher, review that vehicle instead of waiting for a fleet-wide policy refresh. If an inspection is missed or delayed, record the reason, immediate safety decision and corrective action. Do not hide a missed interval by changing the planned date after the fact.

The report needs to be usable. GOV.UK's operator guidance identifies vehicle details, inspected items, date and inspector, results, work carried out and a declaration that defects were fixed. DVSA's guide adds that the transport manager or responsible person must have access to and review the completed report before the vehicle returns to service, with a written confirmation exception if that review cannot be arranged. Record the review and release decision rather than leaving a report in an inbox.

An inspection can reveal no defect and still matter. Its value is the dated check against the planned programme. It can also reveal a pattern, such as recurring brake or tyre findings. Review patterns across inspections so the maintenance plan can be changed when evidence shows it is ineffective. That is a management practice drawn from the purpose of DVSA's guide, not a guarantee that a dashboard will detect a problem.

Keep repairs and contractor work connected

Outsourcing inspection or repair does not outsource the operator's roadworthiness responsibility. GOV.UK's goods operator page says the operator remains responsible even if someone else maintains the vehicles and trailers. The DVSA guide expects a written maintenance contract that defines vehicles, inspection frequency, checks and repair policy, with provider details kept current where required.

The record trail should join a driver's defect report to the workshop job, findings, parts or work, final inspection and return-to-service decision. If the work was not completed, retain the open issue and prevent an unjustified green status. If a different provider completes the repair, link both pieces of evidence. A purchase order and paid invoice show commercial activity; they do not necessarily show that the vehicle was checked and safe for use afterward.

When a contractor sends electronic reports, agree a format that retains the vehicle, date, items checked, defects, repair outcome and responsible person. Make sure reports are retrievable in the operator's system, including after a provider contract ends. DVSA says safety inspection and repair records must be available for at least 15 months whether work was carried out by the operator or contracted out. A portal login that disappears when the contract ends is not a durable evidence plan.

It is worth testing the handover. Ask a member of the operations team to find a particular vehicle's last safety inspection and the closure record for a defect. If the answer depends on a workshop employee forwarding an email, identify how the process will work when that person is absent.

Treat the annual test as one event in a continuous system

An HGV or trailer MOT is important evidence, but a pass on test day does not replace daily checks, scheduled safety inspections or repair records between tests. GOV.UK explains the annual test categories and usual due dates. The exact vehicle classification matters, so do not use a standard car MOT date or a blanket “all fleet vehicles annually” assumption.

The vehicle file can show the relevant test type, due date, booking, result, any failure items, retest and resulting action. An annual test failure is useful information for the maintenance system: was the item visible on a recent safety inspection, was it reported by a driver, and did the inspection interval still fit the work? The questions should be asked without assuming a single failure proves a particular person was negligent.

Keep the actual test evidence with the vehicle's maintenance trail and review the next date against the official record. If a vehicle changes class or exemption position, recheck the requirement at source. A reminder can help prompt that review; it cannot classify the vehicle correctly by itself.

Retain records without flattening different rules

For a licensed goods vehicle operator, GOV.UK states a minimum 15-month period for safety inspection and maintenance records. DVSA's guide applies that period to repair work and defect reports with rectification evidence, and says safety inspection records remain available even after the vehicle is sold or removed from the operator licence. Preserve the records according to their proper category and any longer obligation that applies to your operation.

Do not turn this into “everything is deleted after fifteen months.” Nil-defect reports have a distinct DVSA recommendation, and insurance, contractual or investigation needs may affect other material. Set a records policy that identifies the source, category, owner, retention trigger and disposal process. Avoid keeping personal information indefinitely simply because the fleet file has no cleanup routine.

Electronic records need the same integrity as paper records. DVSA's electronic-record guidance discusses complete, available records, clear identification of who checked what, an audit trail, access and backup. Test whether you can produce reports on request, including records from a hired vehicle or former provider. A screenshot of a green fleet summary is less useful than the underlying dated inspection and decision.

Use access controls appropriate to the work. A driver should be able to submit a defect, but a responsible person should assess and close it. An inspector's report should remain attributable. A later correction should have a visible explanation rather than silently replacing the original result. These are proposed process controls to keep the evidence trustworthy; they are not a claim about what a particular software platform currently provides.

Example: a leased vehicle with a reported defect

Consider a GB goods operator taking a leased vehicle for a short contract. At delivery, the operations lead obtains the supplier's recent inspection report and checks whether it is sufficient for the first-use decision under DVSA's guidance. They record the vehicle identifier, the report date, the reviewer and the reason for accepting it or booking an additional inspection. The vehicle is added to the appropriate safety inspection programme, with the agreed maintenance provider recorded.

On a later daily walkaround, the driver reports a brake concern. The report records the symptom, date, vehicle and recipient. The vehicle is removed from service while a competent person assesses it. The provider examines and repairs it, issues a report, and the responsible person reviews the evidence before return to service. The file links the original defect, repair and release decision. A later safety inspection can then be read in context.

If the operator cannot produce the delivery inspection, it should not assume the lessor retains a copy forever. If the workshop invoice omits the defect and repair outcome, ask for a complete report. If the vehicle is returned to the supplier, preserve the operator's required maintenance history for the applicable period. This example shows an evidence workflow, not a decision that every leased vehicle follows identical inspection arrangements.

Make retrieval part of the operating routine

Once a month, a transport manager or other responsible person can sample a vehicle file: one daily check, one defect if any occurred, the last safety inspection, repair closure, annual-test position and next planned inspection. Confirm that dates and vehicle identifiers match. Check overdue actions and reasons for any interval change. This is suggested quality control, not a statutory monthly audit requirement.

A useful dashboard asks specific questions. Which vehicles are due for inspection under their declared plan? Which defect reports have no closure evidence? Which contractor reports have not been reviewed? Which vehicles are inactive and need a return-to-service decision? Which records cannot be retrieved without calling a provider? Those questions help people act; they should not be collapsed into an unqualified “fleet compliant” score.

If you are evaluating software, ask Complys for a demonstration of its current vehicle records, check and follow-up workflow against a real example. Compare other vendors against the same task. Confirm which features are available in your edition and whether they can support your own maintenance arrangements. Do not assume any system certifies roadworthiness, validates MOT status or makes the release decision for you.

The strongest vehicle compliance record is one a new responsible person can read without guessing. It connects the vehicle, schedule, daily observations, inspection, repair and decision. The DVSA roadworthiness guide remains the primary reference when you design and review that system. Recheck it when the vehicle, use, provider or regulatory guidance changes.

Next step: Choose one active vehicle and retrieve its complete evidence chain. Note any missing report, ambiguous status or decision with no named reviewer. Then ask Complys to demonstrate its current workflow against those concrete gaps.