InnerWeb
Skip to main content

Reconstructing the driver route after an incident: a guide for OHS and security

After an incident on plant grounds the first questions are which way the driver went, where they stopped and when they left the site. The delivery route preview on the online map answers these without reviewing footage from several cameras. This guide shows how to read the route, the stops and the proof for the incident documentation.

60 s
minimum time after which a series of readings counts as a stop
Source: karta
89 s
signal gap that ends a stop
Source: karta
3 s
live refresh of route points
Source: karta

When you reconstruct the route and why

The route is reconstructed after a road incident on plant grounds, after a driver enters a zone without authorisation, after a complaint about a delayed unloading, or after a report that a vehicle stood in a prohibited place. The aim is twofold: to establish the facts for the documentation and to draw conclusions, for example about gaps in road markings or in the navigation matrix.

The delivery route preview on the online map shows the locator's path from entry to the plant up to the current moment. These are data on the locator's movement in the vehicle, not on the driver's movement outside the vehicle, and they should be described that way in the documentation.

Step by step: how to read the route

The order below works for most reports.

  • Find the delivery by its number, the notice card code or the time of entry.
  • Open the delivery route preview on the online map.
  • Read the entry point and the point of the last position or departure.
  • Review the route for sections outside the intended approach to the target warehouse.
  • Check the marked stops and their duration.
  • Note the times of the incident and compare them with the record from other sources.
  • Record your conclusions and attach the route description to the documentation.

How the system counts a stop

A stop in the route preview is a series of readings at the same location lasting longer than 60 seconds. A gap in the signal longer than 89 seconds ends the stop, so a long stop with a signal gap may look like two separate stops. The practical conclusion: when reading the stop time, pay attention to signal gaps next to it.

Time thresholds in the route preview

Time thresholds in the route previewBar chart: refresh every 3 seconds, a stop longer than 60 seconds, a signal gap longer than 89 seconds ends a stop.020406080100secondsPoint refresh: 3 seconds3Point refreshMinimum stop: 60 seconds60Minimum stopSignal gap ending a stop: 89 seconds89Signal gap ending a stop
Source: Feature card for the delivery route preview

Archived deliveries and data freshness

Route points of a delivery are stored separately with every signal from the active locator, so the route can be reconstructed even for an archived delivery. An incident reported several days later therefore does not require reviewing camera footage, provided the delivery has not been removed earlier under the plant's retention policy.

For current deliveries the route points refresh together with the vehicle position every 3 seconds, so the dispatcher sees the course almost live. For an investigation it is best to take a screenshot or a route description at the moment the facts are established, before the data is changed under the retention policy.

Limitations to keep in mind

Location relies on signals from several BLE beacons averaged on the map, without GPS. Accuracy therefore depends on beacon density: on plant roads they are placed about every 100 m, and indoors one beacon is assumed per 100-200 m2. On stretches without coverage the route will be approximate.

The locator route confirms the vehicle's passage but does not determine the cause of the incident. In the documentation, cross-check it with statements, cameras and road markings. InnerWeb provides evidence for analysis, and the assessment of the incident belongs to the incident investigation team.

Conclusions after the analysis: what to improve

If several drivers turned into the same spot, the problem most likely lies in the road markings or in the navigation matrix. The administrator corrects the matrix in the panel on the fly, without deployment, so the fix applies from the next delivery.

If stops repeat at one point, it is worth checking the organisation of the ramp or the queue. Such data feeds the vehicle traffic safety review and the risk assessment, because it is based on actual journeys, not assumptions.

Video

Frequently asked questions

Can the route be reconstructed for a completed delivery?

Yes. Route points are stored separately with every signal from the active locator, so the route is available for an archived delivery too.

After how long does the system count a stop?

A stop is a series of readings in the same location lasting longer than 60 seconds. A signal gap longer than 89 seconds ends the stop.

Does the route show who is to blame for the incident?

No. The route is proof of the locator's passage, to be compared with other sources. The assessment of the cause belongs to the incident investigation team.

Let's show the route preview on your plant

We will reconstruct a sample delivery route and go through how to use it in an incident investigation.

Let's talk