HGV maintenance planner to garage handover
An HGV booking is more than a date in a calendar. The garage needs to know which vehicle is coming, what inspection is due, what defects have been reported and which work must be authorised. The operator needs a timely, complete record back before deciding how the vehicle will be used. A reliable handover makes these two directions explicit.
This page addresses the transfer between an operator's maintenance planner and an external garage. It is not a generic guide to selecting an inspection interval. The DVSA Guide to Maintaining Roadworthiness sets out the wider maintenance-system expectations for commercial vehicles and trailers.
Send a useful booking instruction
Identify the vehicle or trailer unambiguously, the planned safety inspection, due date, current mileage or usage information where relevant, known faults, outstanding recalls and any other work requested. Include the latest defect reports and prior inspection findings that need follow-up. If a specialist test or brake assessment is needed, say so before the slot is booked.
State the vehicle's expected arrival and release window, depot contact, driver contact and who may authorise additional work. A workshop can discover a defect that changes the plan; it should not have to guess whether it may order an expensive repair or return the vehicle unrepaired. The operator should also tell dispatch that the vehicle is committed to maintenance, so it is not allocated for work before the evidence is back.
Agree how defects will be escalated
The handover should define how the garage reports a safety-related finding, what evidence it sends and who can make the operational release decision. A telephone call may be appropriate for urgent action, but the finding, response and repair must also enter the written record. If a part is unavailable, the operator needs the current condition and a plan for where the vehicle will remain; “garage has it” is not a useful status.
Driver-reported defects should retain their identity in the garage workflow. When work is completed, the record should link the original report to assessment, repair, recheck or reason no repair was needed. If several reported issues are grouped into one invoice line, the operator still needs to see what happened to each safety concern.
Receive the completed work as evidence
On return, obtain the inspection record and any relevant brake-test or repair evidence, not only an invoice. Check the vehicle identity, date, inspector or repairer, findings, work done and unresolved restrictions. Confirm that the garage's “complete” status means what the operator expects. Technical repair sign-off, receipt of documents and permission to dispatch are separate actions.
If an inspection is missed or rescheduled, record why and what happens to planned use. Do not change a maintenance date retrospectively to make a report appear on time. The operator's responsible person should decide the response from the current roadworthiness and licence requirements.
Keep a single timeline across systems
Many operators and garages use different software. Agree a shared reference for the asset and booking so records can be matched. Save the original instruction, changes, garage findings, approvals and final documents in a location the operator can retrieve. Check that attachments and photographs are legible and tied to the right vehicle. The GOV.UK goods-vehicle operator guidance states a minimum 15-month retention period for safety-inspection and maintenance records; confirm current scope and local record policy.
Audit a recent completed handover: could a new transport manager reconstruct why a defect was closed and when the vehicle returned to use? If not, improve the agreed exchange rather than adding another status label.
For software evaluation, Complys HGV compliance software is a relevant starting point. Ask to see the current asset and defect record flow. Do not assume the product schedules preventative inspections or integrates with a garage without a demonstrated implementation.
Example: the booked inspection becomes a repair job
The maintenance planner books a vehicle for a safety inspection and sends the latest driver reports. The garage discovers a defect requiring a part that will not arrive until the next day. It sends the finding to the named operator contact with the vehicle ID, condition and proposed repair. The operator takes the vehicle out of the dispatch plan, records the revised availability and tells the garage who can authorise the extra work. After repair, the garage returns the inspection and repair evidence; the operator checks that the original defect is closed before it makes a release decision. If the driver picks up the vehicle on a different shift, they still receive the current condition and carry out their own check. Each of these decisions belongs to a named person, not a vague “garage completed” status.
A two-way handover checklist
Before the booking, confirm asset identity, date, known defects, requested tests, authorisation limit and contact. On return, confirm findings, repairs, supporting test evidence, unresolved restrictions and the person who accepted the record. Keep changes to the appointment visible. This compact checklist makes the handover auditable without forcing the garage and operator into the same software.
At shift change, compare the planner’s due list with the garage booking and any vehicle still out of service. A booking is not evidence that an inspection occurred. If the garage returns a vehicle with outstanding defects, require a named operational decision before allocation. Keep the evidence linked to the correct vehicle and inspection date. Confirm the planner has received the final workshop response before the vehicle is shown as available.