EnglishEN
Contact us

Services

ISO 39001 Road Traffic Safety Management: Review People, Vehicles, and Journey Decisions

Fewer crashes may indicate lower risk, or simply less transport activity. Road safety management should consider the traffic context together with people, vehicle condition, and journey planning to identify decisions the organization can control or influence.

Fewer crashes may indicate lower risk, or simply less transport activity. Road safety management should consider the traffic context together with people, vehicle condition, and journey planning to identify decisions the organization can control or influence.

Discuss this need

Who may need this and when

Organizations using their own fleet, commissioning transport, or able to manage or influence other road activities can review the system when routes, shifts, or carrier relationships change. Vehicle ownership alone does not determine applicability.

Common business challenges

Dispatch focuses on delivery time, maintenance on service schedules, and procurement on freight rates, leaving safety risks between departments. If incident analysis omits traffic volume and working conditions, changes in workload may be mistaken for improved management.

Approach and applicable requirements

ISO 39001:2012 and Amendment 1:2024 set requirements and guidance for a road traffic safety management system. They address organizations interacting with the road traffic system that can control or influence relevant activities, with the aim of reducing deaths and serious injuries. A draft under development should not be treated as a published new edition. See the ISO overview.

Possible project scope, subject to agreement:

  • Activities, risks, and performance basis: define road activities, vehicles, and partners; align data definitions for exposure such as distance, incidents, and indicators so trends can be compared meaningfully.
  • Drivers, vehicle condition, and journeys: connect competence, fatigue, maintenance anomalies, and route conditions to dispatch, vehicle stand-down, and change decisions; flag matters needing specialist review.
  • Carriers, reporting, and improvement: set carrier selection and safety expectations, clarify incident and emergency contacts, and use event reviews to guide training and internal review.

Support and work stages

  1. Define owned and outsourced road activities, responsibilities, performance data, and consistent denominators.
  2. Review information exchange among dispatch, maintenance, and route planning; assign authority for stand-down, adjustment, and escalation.
  3. Pilot carrier and reporting interfaces using representative work; review vehicle checks, partner reports, and route-change records.
  4. Interpret incident trends alongside activity volume and context, track measures, and present resource decisions to management.

Possible deliverables include a road-activity and responsibility map, safety-performance definitions, driver/vehicle/journey controls, carrier requirements, and incident-improvement records. Confirm whether safety information informs dispatch, maintenance, and outsourcing decisions.

Information to prepare

  • Road activities, owned and outsourced vehicles, and carrier responsibilities.
  • Summaries of personnel qualifications, shifts, training, and routes.
  • Vehicle inspection, maintenance, and stand-down records.
  • Activity volumes such as distance, and de-identified incidents and improvements.

Start with an information index and de-identified examples. Share project data only after purpose, access, and retention are agreed.

Schedule and fees

Scope depends on fleet, carriers, routes, and shift differences. Vehicle inspections, driver qualifications, specialist training, traffic engineering, and third-party certification require separate confirmation of provider and fees.

Frequently asked questions

Can we review the system without an owned fleet?

Yes. Review outsourced transport or other road activities the organization influences; ownership is not the only criterion.

Can existing shift and maintenance data be used?

First check periods, scope, and whether the data can be compared; then fill information gaps relevant to safety decisions.

How can carriers be included?

Use selection, contracts, and necessary safety information to define the management interface, including anomaly reporting and improvement responsibilities.

What is the limit of tracking crash counts alone?

Pair counts with activity volume and context, using consistent denominators and periods, to avoid confusing volume changes with control effectiveness.

Does system planning replace vehicle inspections?

No. System management tracks responsibilities and records; competent providers handle technical inspections and qualifications.

Can certification promise zero crashes?

Third-party assessment has a defined scheme and scope and cannot guarantee that crashes will never occur.

Prepare a summary of transport activity and carrier arrangements, along with the data and indicators currently used for safety follow-up. Contact Captain International.