Carry a driver’s reported defect through assessment, repair evidence and the next dispatch decision. Keep one cleared fault from hiding another unresolved problem on the same vehicle.
A workshop message says the lamp has been repaired. The transport desk marks the lorry available, overlooking a second report that still needs assessment. The problem is not the absence of a repair record; it is the missing connection between individual defects and the vehicle being dispatched.
This HGV defect report form template is an inline resource for goods-vehicle operators in England, Scotland and Wales. Copy its sections into a controlled document, spreadsheet or form system. It supports recordkeeping and handoffs; it is not a technical inspection checklist, a roadworthiness certificate or a substitute for your operator’s maintenance system.
Set the boundary before using the form
The DVSA HGV walkaround guidance explains the actual checks and written reporting to the person responsible for resolving defects. Use that guidance and your approved vehicle-specific procedures—not this administrative form—to define inspection work.
The DVSA roadworthiness guide covers written defect reports, assessment and rectification records. It specifies at least 15 months for reports listing defects and associated assessment, repair and repairer details. It recommends retaining nil-defect reports for at least three months. Keep those record types distinct.
The workflow rules below are a recommended design. Your transport manager or responsible person must establish competence, decision authority, response arrangements and applicable requirements. This resource does not cover Northern Ireland, other countries, PSV incident reporting or the full safety-inspection programme. The existing company vehicle policy template addresses broader use rules; it does not replace this defect record.
Copy the report header
Create one report for a reporting event, with one defect line per distinct symptom. Record the vehicle and trailer separately when both are involved. Keep identifiers stable even when the unit moves to another workshop or driver.
REPORT HEADER Report ID: [unique text] Operator / operating centre: [name / location] Vehicle registration / fleet ID: [registration / internal ID] Trailer ID: [identifier / not coupled] Odometer and unit: [number / miles or km / unavailable + reason] Observed at: [date / time / time zone] Reported at: [date / time / time zone] Reporter / role / work contact: [name / role / contact] Discovery: [walkaround / in service / return to base / other] Daily-check record reference: [ID / not applicable + reason] Vehicle’s current location: [location; update if moved] Reported to: [named responsible person] Notification time / method / acknowledgment: [details / pending] Current dispatch status: [held pending assessment / held for repair / awaiting release evidence / authorized for dispatch] Status set by / at: [name / timestamp] Coordinator / backup: [named people / work contacts] Next action / owner / review due: [action / person / timestamp] Related report or work-order references: [IDs / none known]
Do not wait to finish the document before using your urgent reporting route. A digital “held” value does not itself prevent dispatch: the coordinator must also update the operational availability record and notify the people controlling assignments.
Defect lines: record observations, not an assumed diagnosis
Repeat this block for every defect. If a symptom affects a trailer, attach the line to that trailer rather than only to the tractor currently towing it.
DEFECT LINE Defect ID: [report ID + unique suffix] Affected unit: [vehicle registration / trailer ID] Component / location: [plain-language description] Observed symptom: [what happened or was seen] Circumstances / recurrence: [when / first or repeat / unknown] Earlier related defect: [reference / none known] Evidence reference: [notes or file reference / unavailable + reason] Immediate action actually taken: [action / person / time] Assessment pending with: [authorized competent person / due time]
Use short, factual descriptions. “Left rear lamp did not illuminate during the check” records an observation. “Wiring failed” asserts a cause that the reporter may not know. Do not recreate a dangerous condition or approach a hazard to obtain a photo.
Copy the assessment and rectification record
Give each defect its own decision and history. The DVSA maintenance-investigation guidance, questions 5b–5c, calls for reports to reach a responsible person with sufficient authority to act. It also says to keep the reason when a defect does not need immediate repair. Recording a deferral is not permission to operate an unsafe vehicle.
ASSESSMENT — ONE PER DEFECT Defect ID: [linked line] Assessed by / role / at: [competent authorized person / timestamp] Findings: [facts; suspected and confirmed cause distinguished] Road-use decision: [hold / repair before use / assessed non-safety item deferred with documented basis] Decision basis / applicable procedure: [reference and explanation] Restrictions or conditions: [specific terms / none] Assigned repairer / work-order reference: [name / ID / pending] Next action / owner / review due: [details] If deferred: [reason / authorized decision-maker / action due / review trigger / affected people informed] RECTIFICATION AND VERIFICATION Defect ID: [linked line] Work performed: [actual work / not yet performed] Repairer / completed at: [name or business / timestamp] Repair evidence: [work-order or service-report reference] Required verification: [competent reviewer’s specified checks] Result / evidence / checked by / at: [details / pending] Defect state: [reported / assessed held / repair in progress / repair complete awaiting verification / deferred non-safety / rectified verified] Outstanding actions: [details / none]
Preserve earlier entries and add dated updates. A repair invoice establishes neither the assessment of every other defect nor the next driver’s readiness to depart. If the required verification is missing, leave that line awaiting verification.
Review the whole vehicle before changing availability
Use this separate block whenever a held vehicle is proposed for dispatch. It is a record of the authorized review, not an automatic release certificate. Safety defects must not be bypassed with a deadline, manager override or a “deferred” label.
DISPATCH REVIEW Review ID / time: [unique ID / timestamp] Vehicle / coupled trailer: [current identities] All relevant open reports checked: [report IDs / checked by / time] Each defect’s current disposition: [defect IDs + states + evidence] Any unassessed symptom or unresolved safety defect? [yes / no] Any missing required repair or verification evidence? [yes / no] Any deferred non-safety item? [no / IDs + current basis, conditions, owner, review date and authorized decision] Other required maintenance / inspection records reviewed: [references / reviewer / time] Prohibition or other operating restriction checked: [result / reference / responsible reviewer] Decision: [remain held / authorized for dispatch] Decision-maker / authority / at: [name / role / timestamp] Availability record updated by / at: [name / timestamp] Dispatcher notified / acknowledgment: [name / time / reference] Next driver informed / acknowledgment: [name / time / reference] Outstanding follow-up / owner / due: [details / none]
Any “yes” to an unassessed symptom, unresolved safety defect or missing required evidence blocks dispatch authorization in this design. The responsible reviewer must also confirm other applicable operating restrictions have been addressed through their proper process. A single defect form cannot lift a prohibition.
A deferred non-safety item stays open with its reason and follow-up. Its label alone cannot satisfy the review. If its basis, conditions or review point no longer hold, return it to assessment and keep the availability decision from relying on the old assessment.
Field validation and follow-up rules
| Point | Required entry | Block or follow up |
|---|---|---|
| Report received | Unit identity, symptom, reporter, time and named recipient | If identity is uncertain, hold the affected unit pending confirmation; do not silently select a similar registration. |
| Assessment | Named competent assessor, decision, basis and next action | An unanswered report is not a non-safety assessment. |
| Repair completed | Repairer, work, completion time and evidence reference | Do not automatically change dispatch status. |
| Dispatch review | All relevant defect lines, required evidence and authorized decision | One verified repair cannot cancel another open safety concern. |
| Open follow-up | One owner and a dated review point | Escalate a missed review to the backup; preserve the missed deadline and record the new action. |
Use fixed-choice status fields, date-times with a consistent zone and unique text IDs. Allow “unknown” for an observation the reporter cannot establish, but route it to a named person. Do not use “not applicable” to hide missing release evidence.
As an example local policy, review the open queue at each staffed handover and before any affected dispatch; assign the next review timestamp to every open item. Urgent safety concerns use the immediate-response route, not the queue. An item is overdue when the current time exceeds its recorded review due time and it is not rectified and verified. This is follow-up logic, not a statutory repair interval.
Worked example: two defects, only one cleared
Fictional recordkeeping example: names, identifiers, times and outcomes below are invented. It illustrates the handoff, not a diagnosis or a test procedure. The operator’s actual competent reviewers determine the necessary checks.
| Record | Completed entry |
|---|---|
| Header | DR-041; North operating centre; HGV fleet unit V-12, registration recorded in the live register; no trailer coupled. November 23, 2026, 06:10 Europe/London; driver Alex reports to transport coordinator Maya. Daily check DC-041 linked. Vehicle held at North yard; dispatcher acknowledgment recorded at 06:15. |
| Defect A | DR-041-A: rear lamp failed to illuminate during the check. Authorized assessment and repair instruction recorded by Sam at 06:30. Workshop report WO-811 records repair completion at 08:20. Required verification result and reviewer evidence recorded at 08:40. State: rectified verified. |
| Defect B | DR-041-B: a separate warning indication was reported. Assessment still pending with authorized reviewer Jordan; next review due 09:00. No technical cause or road-use decision has been asserted. State: reported. |
| 08:45 dispatch review | Maya links both lines. Unassessed symptom: yes. Decision: remain held. V-12 stays unavailable; dispatcher informed. Clearing A does not clear B. |
| Next action | Jordan owns assessment of B; Maya owns follow-up and records the result. If Jordan is unavailable at the review point, the named backup receives the escalation. No departure time is promised. |
The report remains a useful record even when the correct outcome is “not ready.” Do not fabricate a completed repair or an authorizing signature merely to make the example or the queue look finished.
Handle the cases that break a simple log
- No defect found during the daily check: preserve the nil result in the daily-check record. Do not turn an older unresolved report into nil because today’s driver did not reproduce it.
- Repeat or intermittent symptom: link the earlier report, record the new observation and obtain a fresh assessment. “Could not reproduce” is a finding, not automatic clearance.
- Third-party trailer: retain its actual identifier, relevant report references and the responsible contact. Changing tractor or ownership does not erase the reported trailer issue.
- Workshop handover: record the new location, custodian and work-order reference. Keep the transport desk’s availability record aligned with the authorized decision.
- Unavailable electronic system: use the approved paper fallback, preserve the original time and reporter, and reconcile it into the controlled record once available. Do not let an offline report disappear from the dispatch review.
Where Workhint fits
The form is usable without software. A controlled document works when a named coordinator maintains the queue and the transport desk checks it.
For a multi-role process, Workhint’s Workflow Engine describes routing approvals to defined roles and requiring details, files or notes before progression. Its Workflow Automation Software solution describes structured forms and tracking stages, owners and next actions. Those capabilities are relevant to coordinating report intake and review.
Treat this resource as configuration requirements to discuss, not as evidence of a prebuilt HGV application, a certified maintenance record system or automatic roadworthiness assessment. Competence, technical decisions, retention implementation and actual dispatch controls remain the operator’s responsibility.
Frequently asked questions
Is this a replacement for the daily walkaround sheet?
No. The walkaround sheet records the applicable checks and their results. This form follows reported defects through the people and evidence needed for assessment, rectification and the next availability review. Link the two records.
Can a driver decide that a defect is safe to defer?
Do not give that authority merely because someone can submit the form. The operator must define competent decision-makers and applicable procedures. An unassessed symptom remains pending; it is not automatically minor.
Can one report contain several defects?
Yes, with distinct line IDs, decisions and evidence. The dispatch review must consider all relevant open reports for the actual vehicle and trailer combination, not only the most recently repaired line.
When can the coordinator close a defect line?
In this design, only after its rectification and required verification are recorded. Keep a deferred non-safety item open for follow-up. Closing a line is not, by itself, authority to dispatch the vehicle.
Put the resource into operation
Before first use, name the coordinator, backup, competent assessors and authorized dispatch reviewers. Link the form to your official check procedures and maintenance records, establish retention and retrieval, and rehearse the two-defect example. The useful test is whether the transport desk can see why a vehicle remains held even after one repair is complete.

Leave a Reply