Safety comes before the record

When a vehicle strikes a gate, barrier, bollard, wall or another vehicle, the first task is not completing the digital register. Stop movements if that can be done safely, protect people from further traffic, call the site's emergency response and arrange first aid or emergency services where needed. Damaged equipment may introduce a second hazard: a gate could move unexpectedly, a barrier arm could obstruct a route, or debris could put pedestrians and tyres at risk. Follow the site's emergency and traffic-management arrangements and do not ask a guard to stand in a live vehicle path to obtain a photograph.

HSE's investigation workbook puts prompt emergency action and making the area safe before the initial report. Its workplace-transport guidance also requires traffic routes to be arranged so pedestrians and vehicles can use them without danger. Those principles matter even after an apparently minor scrape. The person in charge should decide when the area may reopen and whether a competent inspection is needed; a tidy-looking barrier is not proof that its supports, controls or locking mechanism are sound.

Treat the gate log as supporting evidence, not the investigation

A vehicle movement record can establish useful parts of the timeline: the registration observed, the photographed vehicle, the site and gate, the guard account and the recorded IN or OUT time. It may also show the permit or visit category used in the normal workflow. It does not by itself establish speed, fault, mechanical condition, driver competence, the position of pedestrians, the sequence of impacts or why the event happened.

Keep the formal incident process separate. The appointed incident owner should bring together the vehicle record, the site's incident form, witness accounts, photographs taken under the approved procedure, equipment inspection, relevant CCTV and any contractor or insurer information. This prevents a manager from treating one gatehouse screen as a complete finding. It also lets the ordinary vehicle history remain understandable for operational reporting.

Preserve the original movement before adding context

Identify the relevant visit without altering it to fit an early theory. Check the registration against the plate and available photograph, confirm which gate and direction were recorded, and preserve the associated IN or OUT details. If the record contains a genuine registration mistake, use the organisation's correction process and retain an intelligible account of what was changed. Do not replace the original vehicle with a different one simply because a witness initially named the wrong registration.

Priority Service's published features include a vehicle photograph, guard-checked registration, time-stamped IN and OUT records linked to the site, gate and guard, searchable visit history and CSV reporting for authorised administrators. Those fields can support identification and chronology. The site does not advertise a dedicated accident-investigation module, evidence lock or legal-hold function, so buyers should not assume those controls exist. Decide how the responsible manager will preserve relevant records and restrict changes within the actual product and the organisation's wider incident system.

Record observations separately from conclusions

Write what was seen, heard or done, with the observer, time and source. Examples include: the barrier arm was down when the guard looked up; the driver stopped beyond the marked line; a warning light was flashing; the guard closed the lane at 14:18. Avoid converting those observations into conclusions such as reckless driving, defective brakes or guard error unless a competent investigation supports them. If someone gives an opinion, identify it as their account rather than an established fact.

The ICO accuracy principle requires reasonable steps to prevent personal data being incorrect or misleading, to keep its source and status clear, and to distinguish matters of opinion appropriately. A later correction should not make the history more confusing. If a witness changes their account, record the clarification through the incident procedure instead of silently rewriting the first note. That is useful both for fairness and for anyone who must later understand the sequence.

Preserve the scene and evidence proportionately

HSE's investigation workbook advises preserving the scene and noting the people, equipment and witnesses involved. In practice, the incident lead should decide what must remain untouched, what can be photographed or measured, and what must be moved immediately to prevent further harm. Record why safety-critical changes were made. Do not delay emergency access or leave a dangerous obstruction in place merely to protect a scene.

Secure relevant material early because normal systems may overwrite it. That can include CCTV clips, gate-control logs, maintenance records, contractor bookings, radio or control-room notes and the relevant vehicle visit. Preserve only what is connected to the event and document where the authoritative copy sits. A screenshot passed through several personal phones is harder to govern than an export or controlled copy held by the incident owner.

Give reporting decisions to the responsible person

A guard should escalate promptly, but should not be expected to decide the legal reporting category at the roadside or gatehouse. HSE states that RIDDOR reports are submitted by responsible persons, including employers, self-employed people and people in control of work premises. Not every accident is reportable: an injury event must be work-related and result in a reportable outcome, while reportable dangerous occurrences are the specific high-potential incidents listed in Schedule 2.

Vehicle or gate damage on its own does not automatically answer the RIDDOR question. The responsible health-and-safety person should check the current HSE criteria, the people affected, injury outcome and event type, then make and retain any required report without waiting for a finished investigation. Other notifications may be required by the client, landlord, contractor, insurer, equipment maintainer or police depending on the circumstances. Put those contact and decision routes in the site procedure before an incident.

Control access and set an incident-specific retention decision

Vehicle photographs, registrations, guard identities and witness details can be personal data in context. Give access to people who need it for the operational response, investigation, legal duties or a properly assessed claim. Avoid circulating a complete gate register when one visit and a narrow time window are enough. The ICO's data-minimisation guidance requires data to be adequate, relevant and limited to what is necessary.

An incident may justify keeping a relevant record longer than the routine gate-log period, but 'keep everything indefinitely' is not a retention policy. The ICO says organisations should not keep personal data longer than needed and should establish appropriate time limits based on purpose. Document the incident hold, scope, owner and review point; release or delete the additional copy when the purpose ends, while preserving any records still required under another justified schedule. Protect exports and photographs with appropriate organisational and technical security.

Investigate causes rather than stopping at driver error

Once the immediate response is complete, examine why the event was possible. Consider layout, visibility, lighting, stop-line position, pedestrian separation, vehicle dimensions, queue pressure, signage, instructions, guard workload, barrier controls, maintenance and supervision. HSE says accidents and near misses should prompt review of risk controls, and its guidance for horizontal swing barriers specifically recommends reviewing risk assessments and considering whether the hazard can be eliminated.

The action should match the finding. It may involve repairing equipment, changing the traffic route, moving the stopping point, improving lighting, altering delivery instructions, separating pedestrians, revising the barrier procedure or retraining relevant staff. 'Remind drivers to be careful' is weak if the route or equipment made the event predictable. Close the investigation only when actions have owners and due dates, and check later that they worked.

Test retrieval and escalation before buying

Use a realistic demonstration scenario: a contractor van records IN at the service gate, clips the barrier ten minutes later and leaves through another gate after the lane is made safe. Ask the supplier to show exactly how an authorised manager finds the original visit, confirms the registration and vehicle photograph, identifies the recording gate and guard, reviews the later OUT and exports the relevant history. Ask what can be corrected, what audit information remains after a correction, and which roles can view or export the records. Treat any feature not demonstrated or contracted as unavailable.

Priority Service publishes the vehicle-capture, permit, approval, IN and OUT, role, visit-history and CSV capabilities that can support this exercise; it does not claim to replace your accident book, risk assessment, RIDDOR decision or incident-management system. Review the published workflow at https://priorityservice.co.uk/#features and request a live demonstration at https://priorityservice.co.uk/#demo. Bring your own escalation map and retention rules so the test covers the whole response, not only the app screen.

Sources & further reading

Vehicle logging for your operation

Explore the workflow, plans and demo options for your team.

    Explore gatehouse management software

    Compare gate management plans

    SEE THE WORKFLOW IN PRACTICE

    Explore Priority Service at your gate.

    See vehicle capture, permits, approvals and reporting in a demonstration built around your requirements.

    Request a demoExplore the app features