Knowella

Journey Risk Assessment Template

Most journeys do not need assessing. The ones that do share a characteristic: something about this trip is outside the pattern the fleet's standing controls were built for. A journey risk assessment applied to every delivery becomes a formality within a week; applied to the exceptions, it is one of the few controls that prevents road incidents rather than investigating them.

KnowFleetAssessmentFLT-037Full guide
Applies to
Exceptional journeys, not routine ones
Decides
Go, modify, or do not travel

Summary

In short

  • Road incidents are the largest cause of work-related fatalities in many economies, and the majority of exposure sits with organisations that do not consider themselves transport businesses.
  • The assessment is only useful where journeys vary. Where every trip is the same, standing controls and vehicle checks do the work and a per-journey form adds nothing.
  • The most valuable output is the option not to travel. An assessment whose only outcome is proceed has documented a departure rather than assessed a risk.
  • Weather and daylight are the conditions most often underweighted, because they are forecastable and therefore feel like background rather than a decision input.
  • Journey planning interacts directly with fatigue: schedule, distance and delivery windows determine whether a driver can complete the trip without impairment.
  • ISO 39001 provides the road traffic safety management framework, treating journey planning as a risk factor alongside vehicle and driver.

What it is

What it is

What is a journey risk assessment?

An assessment of a specific journey before it starts, covering the route, the conditions expected, the load and the vehicle, concluding with a decision to proceed, proceed with modifications, or not travel. It is used where the journey falls outside the pattern that routine fleet controls address.

When is one warranted?

Where something about the trip is exceptional: unfamiliar or remote route, severe weather forecast, abnormal load, long duration, night driving on unfamiliar roads, higher-risk territory, or a combination that no standing control covers. Applying it to routine deliveries dilutes it into a form.

When to use it

When to use it, and when not to

This assessment covers a specific journey. Routine driving is handled by standing controls rather than by a form per trip.

Use it for

  • Journeys on unfamiliar, remote or high-risk routes
  • Severe weather forecast, or seasonal conditions such as ice, flooding or high wind
  • Abnormal loads, oversize or hazardous goods requiring route restrictions
  • Long-duration journeys where fatigue or timing becomes a factor
  • Travel in territories with elevated security, infrastructure or medical response risk

Not for

  • Daily vehicle inspection, which checks the vehicle rather than the journey
  • Fatigue risk assessment, which addresses the driver's state and interacts with but does not duplicate this
  • Hours of service planning, which is a compliance activity with its own record
  • The load securement check, which verifies restraint rather than route suitability
  • Routine deliveries on known routes, where standing controls are the right mechanism

Standards

What it is built against

Journey risk sits under road traffic safety management and general duty obligations rather than a dedicated standard.

ClauseRequirementWhere it lands
ISO 39001 cl.6.1Risk factors and performance factors for road traffic safety, including journey planning and route selectionHeader
ISO 39001 cl.6.2Objectives and planning to achieve them across the road traffic safety systemOutcome
ISO 45001 cl.6.1.2Hazard identification covering work-related driving as an occupational exposureConditions
FMCSA 49 CFR 392Driving of commercial motor vehicles, including hazardous conditions requiring reduced speed or cessationConditions
FMCSA 49 CFR 397Routing requirements for hazardous materials transportationRoute
49 CFR 393 Subpart ICargo securement performance criteria, relevant where load characteristics affect routeLoad and vehicle
HSE INDG382Driving at work guidance, covering journey planning, route and schedule (GB)Route
ISO 45001 cl.8.2Emergency preparedness, including breakdown and incident response on remote routesOutcome

What it does not cover

  • Daily vehicle inspection, which examines the vehicle rather than the journey ahead.
  • Fatigue risk assessment, which addresses the driver's state and should be read alongside this.
  • Hours of service planning, a compliance activity with its own records and limits.
  • Load securement verification, which confirms restraint rather than route suitability.
  • Hazardous materials routing determination, which follows prescribed requirements rather than assessment.

Filling it in

Filling it in well

Four inputs and one decision, completed before departure rather than in a lay-by afterwards.

Assess the route rather than the destination

Road type, junction and crossing points, gradients, height and weight restrictions, availability of safe stopping places, mobile coverage and distance to assistance. A satellite navigation route optimised for time frequently uses roads unsuitable for the vehicle and offers nowhere to stop.

Treat forecast conditions as a decision input

Weather, daylight hours and seasonal road condition are known in advance, which paradoxically makes them easy to ignore. Where the forecast would change the decision, it should be recorded as part of the assessment rather than discovered en route.

Check the load against the route, not only against the vehicle

Height, weight, width and centre of gravity interact with bridges, gradients, roundabouts and lane widths. A load correctly secured for the vehicle can still be unsuitable for the route, and abnormal load routing is a separate exercise with its own permissions.

Include the option not to travel

Proceed, proceed with modifications such as a different route, a different time or a second driver, or do not travel. Where the form offers only the first, the assessment is a departure record. Recording the occasions when a journey was delayed or rerouted is the evidence that the process works.

Audit findings

Common audit findings

Findings here concern whether the assessment is applied where it can do something.

FindingClauseWhat fixes it
Journey assessment applied to every trip, including routine ones.ISO 39001 cl.6.1Define trigger conditions; universal application produces a tick exercise.
No option other than proceed on the form.ISO 39001 cl.6.2Include modify and do not travel; a single-outcome assessment is a record, not a decision.
Route taken from navigation software with no suitability check.HSE INDG382Check height, weight and width restrictions and stopping places against the actual vehicle.
Forecast severe weather not treated as a decision input.49 CFR 392.14Hazardous conditions require caution or cessation; forecast conditions should be assessed in advance.
Journey planned without regard to the driver's hours or fatigue state.ISO 45001 cl.6.1.2Read journey and fatigue assessments together; schedule determines both.
Remote route with no breakdown or emergency arrangement.ISO 45001 cl.8.2Establish communication, check-in and assistance arrangements before departure.
Delivery window making the safe route or safe speed impractical.ISO 39001 cl.6.1Schedule pressure is a journey risk factor; assess it rather than treating it as fixed.
Assessment completed after departure.ISO 39001 cl.6.1Complete before leaving; a retrospective assessment has assessed nothing.
Abnormal load moved without route survey or permissions.National abnormal load rulesAbnormal loads require route-specific permission; the general assessment does not substitute.
Records never reviewed to identify recurring high-risk journeys.ISO 39001 cl.9.1Read the accumulation; recurring exceptions indicate a scheduling or network problem.

Worked case

Case in point: the shortest route

A distribution operation sent a rigid vehicle to a rural customer using the route the navigation system offered, which was the shortest. It included a series of single-track lanes with passing places, a weight-restricted bridge the driver had to reverse away from, and no safe stopping point across a twenty-mile stretch.

The journey took two and a half hours against a planned ninety minutes. The driver arrived outside the delivery window, having reversed a rigid vehicle several hundred metres on a lane with a ditch on one side, in fading light.

No incident occurred. The route had been used four times in the previous month by different drivers, each of whom had discovered the same problems independently, and none of which had reached anyone who plans routes.

Definitions

Definitions and key terms

Journey risk assessment
Pre-departure assessment of a specific trip covering route, conditions, load and vehicle, concluding with a travel decision.
Abnormal load
A load exceeding normal dimension or weight limits, requiring route-specific permissions and often a survey.
Route suitability
Whether the roads on a route can accommodate the vehicle: height, weight, width, gradient and turning restrictions.
Safe stopping place
A location where the vehicle can stop safely for rest, checks or in an emergency, absent on many rural routes.
Journey management
The systematic planning, monitoring and support of journeys, used widely in energy and mining operations.
Check-in arrangement
Scheduled confirmation that a driver on a remote route is safe, with escalation if a check-in is missed.
Hazardous conditions rule
The requirement to exercise extreme caution or cease driving where conditions such as ice, fog or snow adversely affect safety.
Schedule pressure
The effect of a delivery window on driving decisions, a road traffic safety risk factor in its own right.

FAQ

Frequently asked questions

Should every journey be assessed?+

No, and doing so destroys the control. Where journeys are routine and the route is known, standing controls, vehicle checks and driver competence do the work. A form completed for every delivery produces identical answers, the driver stops reading it within days, and the assessment exists only in the records. Define trigger conditions instead.

What conditions should trigger an assessment?+

Unfamiliar or remote routes, severe weather forecast, abnormal or unusual loads, extended duration or night driving on unfamiliar roads, and travel in territories with elevated security, infrastructure or medical response risk. Any of those puts the journey outside what standing controls were designed for.

Can the route come from navigation software?+

As a starting point. Navigation optimises for time or distance and does not know the vehicle's height, weight or width, and does not consider whether there is anywhere to stop. Route suitability against the actual vehicle is a separate check, and it is where the practical problems on rural and industrial routes are found.

How does this relate to fatigue?+

Directly. The schedule, distance and delivery window determine whether the journey can be completed without impairment, and a route that takes substantially longer than planned converts a compliant duty period into an extended one. The two assessments should be read together rather than filed separately.

What should be done with completed assessments?+

Read them in aggregate. Where several drivers independently record the same restriction, difficulty or delay on a route, that is a planning finding rather than a journey finding. It is the cheapest output of the process and the one most often skipped, because the records are filed per trip and never revisited.

The agents

What the agents do with it

The assessment is short and pre-departure. What fails is universal application and the accumulation nobody read.

KnowFleet

Applies the assessment against defined trigger conditions rather than to every journey, and holds route findings against the route rather than the trip.

Ella

Reads recorded difficulties in aggregate and flags routes where several drivers independently encountered the same restriction.

KnowLogistics

Connects delivery windows and scheduling to the assessment, since schedule pressure is a road traffic safety risk factor.

KnowSafe

Links remote and lone journeys to check-in and escalation arrangements, so a missed check-in triggers something.

This template lives in KnowFleetfleet and transport. Drivers, vehicles, hours, cargo securement and operator licence compliance.

Sources

Sources

  • ISO 39001, road traffic safety management systems, clauses 6.1 and 6.2
  • 49 CFR Part 392, driving of commercial motor vehicles, including hazardous conditions, FMCSA
  • 49 CFR Part 397, transportation of hazardous materials, driving and parking rules, FMCSA
  • HSE INDG382, driving at work: managing work-related road safety (GB)
  • ISO 45001:2018 clauses 6.1.2 and 8.2
Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.