Incident and near-miss reporting for haulage offices
How haulage offices can record incidents and near misses clearly, preserve evidence, follow up actions and learn without relying on memory or message threads.
Incidents and near misses are easy to handle badly. A driver calls, the office solves the immediate problem, and the details end up split between phone notes, WhatsApp, photos and memory. A week later, nobody can clearly explain what happened or what changed.
HSE guidance covers workplace transport and work-related road safety. RIDDOR may apply to some reportable workplace incidents, depending on the facts. This article is a practical office workflow and not legal advice.
Define what should be reported
Drivers and office staff should know what counts as an incident or near miss in your operation. Examples may include:
- collision or contact with another vehicle, structure or object
- bridge or overhead-structure near miss
- load shift or load-security concern
- unsafe loading or unloading event
- injury or dangerous occurrence
- serious site access problem
- vehicle defect discovered during work
- aggressive customer or site behaviour
- fuel spill, environmental concern or property damage
The definition should encourage early reporting. A near miss is valuable because it gives the business a chance to improve before harm occurs.
Capture facts first
The first record should be factual. Avoid blame, guesswork or emotional wording. Capture:
- date and time
- driver and vehicle or trailer
- job or customer reference
- location
- what happened
- immediate action taken
- whether anyone was injured
- whether the vehicle continued, stopped or was recovered
- who was informed
- photos or documents where safe and appropriate
If the event may need formal reporting or insurance involvement, follow the relevant process and preserve evidence.
Keep evidence proportionate
Photos, GPS notes, POD, messages and driver statements can be useful. They can also include personal data. Collect what is relevant, store it securely and avoid sharing it casually.
Evidence should be attached to the incident or job record, not left in a phone gallery. The office should know who can access it and how long it is needed.
Turn reports into actions
An incident report is not complete until the follow-up is clear. Actions might include driver briefing, route-note update, customer-site note, maintenance inspection, defect creation, training, insurance notification or a change to dispatch instructions.
Record the action owner and due date. Otherwise the report becomes an archive rather than a control.
Review trends
Once a month, review incident and near-miss reports for patterns:
- same site or customer
- same route problem
- repeat vehicle or trailer issue
- repeated load type
- repeated driver confusion
- delays creating pressure
- missing site instructions
The review should be practical. If drivers repeatedly struggle with the same site, update the site instructions. If near misses involve vehicle height, review route planning.
Decide what must be escalated immediately
Not every incident needs the same response, but drivers and office staff should know what requires immediate escalation. Examples may include injury, collision, suspected dangerous defect, bridge strike, load shift, spill, security incident, customer refusal involving safety, or any event where the driver is unsure whether it is safe to continue.
The escalation note should say who to call first, what information to collect, and what not to do. For example, do not ask a driver to continue with a vehicle or load concern until the right person has assessed the situation. If formal reporting, insurer notification or customer escalation may be required, the office should preserve the facts and avoid speculative comments.
Protect the driver report
Drivers are more likely to report near misses when the process is fair. If every report is treated as blame, the business will hear about fewer problems. Make it clear that factual reporting is expected and useful. The office can still investigate performance, training or disciplinary issues where appropriate, but the first step is to understand the event accurately.
Connect incidents to existing records
An incident may also need a defect record, job note, customer-site update, driver briefing or maintenance action. Do not duplicate everything manually, but do link the records. If a vehicle was damaged, the fleet record should show the follow-up. If a site instruction was wrong, the customer location should be updated. If a driver needs a briefing, the driver record should show it happened.
Frequently asked questions
Does every incident need to be reported under RIDDOR?
No. RIDDOR applies to specific reportable work-related incidents. Operators should check current HSE guidance and get competent advice where needed.
Should near misses be recorded if nothing was damaged?
Yes, as good practice. Near misses help the office spot risk before an incident causes harm or cost.
Can drivers submit incident photos from a mobile app?
They can where it is safe and appropriate. The office should still control what is stored, who can access it and how it is linked to the job or incident record.
Final takeaway
A useful incident routine is simple: report early, record facts, attach evidence, assign actions and review patterns. Do not let important learning disappear into phone calls and messages.
Related pages
Sources & further reading
Manage checks, defects and records digitally
HauliK gives UK transport operators digital walkaround checks, defect tracking, job management and driver compliance — built around DVSA-aligned workflows.