Fleet Sat Nav Policy Checklist UK

A fleet sat nav policy should standardise how devices are mounted, how vehicle profiles are set, how routes may be changed, and how problems are reported. It is not a complete legal compliance system, and it does not stop bridge strikes on its own. Keep driver judgement and escalation in the document, then fit the hardware around that.

What should a fleet sat nav policy cover?

Cover the decisions that currently vary from driver to driver. If those decisions stay informal, two vans on the same round will mount screens differently, store different heights and handle a wrong turn in different ways.

• Which vehicles carry a portable unit, a built-in unit, a phone app, or more than one of those.
• Who may change a mount, a vehicle profile or a stored destination.
• When a route must be entered or changed only while parked.
• How signed restrictions override a digital route.
• What must be reported after a near-miss, a refused site or a device failure.
• How agency and night drivers receive the same briefing as regular drivers.

HSE's work-related road safety pages put driving for work on the employer and the worker. A one-page navigation policy is one control among others, not a substitute for training, scheduling and vehicle information. The Highway Code section on using the road expects drivers to stay in control once moving, including using both hands on the wheel where possible; the policy should repeat that as a parked-setup rule rather than writing a private version of the law.

Which settings should be standardised and which remain vehicle-specific?

Standardise the behaviour, not every millimetre of every cab. Vehicle-specific facts still have to be measured on that vehicle. Keep mounting, parked route edits, failure reporting and update ownership the same across the fleet. Keep the exact dash position, the measured height of that combination, the duty contact number and the spare-unit arrangement vehicle-specific.

The Department for Transport bridge-strike good practice guide expects operators and drivers to know running height and to treat signs as decisive. Standardising a sat nav profile without a measured height simply copies an error into every duty that vehicle covers.

How should route changes be handled while driving?

They should not be handled while driving. The policy should say that destinations, via points and profile edits wait until the vehicle is safely parked. Hands-free voice prompts can continue, but a driver who has to look down to tap a new postcode is no longer keeping both hands available for control.

If traffic or a customer demand forces a change, the next step is to park, then call the operator if the new road is unsigned in the briefing or disagrees with a restriction sign. Do not write a policy that tells drivers to “just keep the screen updated” in motion.

What should drivers report after a navigation problem?

Report anything that would send the next driver into the same hole. That includes a mount that creeps, a profile that showed the wrong height, a route that ignored a signed limit, a unit that died without a satellite fix, and a customer site whose gate did not match the postcode.

Keep the report short: date, vehicle, combination, what the device showed, what the road or site actually required, and what the driver did instead. The point is a fleet memory, not a blame note. If a bridge, a weight limit or a refused access was involved, escalate the same day so the route library can be changed before the next booking.

When is a device policy insufficient without wider risk controls?

A device policy is insufficient when drivers do not have measured heights, when schedules have no delay margin, when agency staff receive no briefing, or when a refused site has no agreed holding place. Navigation equipment does not remove road risk and does not prevent a bridge strike if the height on the screen is wrong or the driver is told to follow the magenta line anyway.

In those cases fix the information, the schedule and the training first. Buying another unit, or forcing every driver onto the same model, will not repair a missing height gauge or a customer slot that only works at illegal speed.

Completed one-page policy template

Use this completed template as a starting text, then replace the example names with your own. It is an operational draft, not a solicitor's compliance pack.

• Scope: all company vans and HGVs that carry a portable or built-in navigation unit, including agency cover.
• Mounting: set the unit only while parked; keep it off the central windscreen sightline; never hold it in motion, in a queue or at lights.
• Profiles: enter the measured combination before departure; after any trailer or load change, update the written height first, then the device.
• Route edits: park, then change; if a roadside sign disagrees with the screen, obey the sign and call the transport office.
• Failure: park, report on the same duty, and do not continue on an unconfirmed restricted road.
• Review: transport manager reviews reports weekly and updates the shared route notes the same day a restriction incident is logged.

Who this article is not for

This article is not for owner-drivers looking for a product review, and it is not a complete operator-licence compliance manual. It is also not a claim that standardised devices will eliminate bridge strikes or other road risk.

Stop conditions

Stop rolling out a device-only policy if measured running heights are missing. Stop if drivers are still expected to type destinations in motion. Stop if there is no named person to receive a restriction report. Put those controls in place before you print a laminated sat nav sheet.

If the fleet still needs a shared portable unit after those controls exist, you can review the 7-inch automotive navigation system. Match any purchase to the policy above, not the other way around. Cab layout rules that drivers will actually follow are in where to mount a sat nav in a lorry.