Safety Message: Level Crossings and the Importance of Ongoing Risk Assessment - Part 2

1. Risk assessments

The Rail Safety National Law (RSNL) requires rail infrastructure managers to identify and assess, so far as is reasonably practicable, risks to safety at a level crossing. It is good practice in undertaking this risk assessment to ensure that:

• all participants in the risk assessment have the appropriate experience, knowledge, qualifications and competency to assess the risks.
• all parties that are accountable for the safety of the level crossing are represented, including road managers.
• the risk assessment covers both current and potential level crossing hazards.

Rail infrastructure managers must determine measures to manage so far as is reasonably practicable, the risks at a level crossing. It is good practice to record in the interface agreement:

• a specific, detailed and clear description of each control measure and who is responsible for maintaining it. For example, the distance in metres for which the road manager is responsible for maintaining the road approaches either side of the outside running rail.
• only one person or entity is responsible for each control measure.
• reasons for rejecting any control measures that were considered in accordance with section 100 of the RSNL.

2. Control measures: ongoing monitoring and review

As highlighted in our previous safety message, it is important to continually assess risks to ensure chosen controls are effective. ONRSR has observed the following good practice:

• ensuring all staff who undertake inspections and monitoring of the level crossing are suitably qualified, trained and competent.
• regularly inspecting the controls that are in place, such as sighting distances, signage and line markings, in line with the interface agreement and any maintenance plan, and sharing the results of any inspection with all parties to the interface agreement.
• ensuring that the review of control measures at a level crossing considers incidents and occurrences.
• sharing information about any changes to level crossing controls with all parties to the interface agreement, particularly any deficiencies such as:
  • missing or damaged signage and line marking.
  • changes to rail traffic, road vehicle or pedestrian utilisation.
  • temporary works.
  • urban development/infrastructure changes.
  • population growth.
  • changes to rail traffic or road traffic speed.
  • level crossing or road configuration change.

3. Updating interface agreements

Interface agreements need to be continuously monitored and reviewed to ensure that the risks to safety arising from a level crossing are appropriately managed. Any change to an interface agreement should also be reflected in the Rail Infrastructure Manager’s risk register and Safety Management System. ONRSR has observed the following good practice:

• updating the interface agreement as soon as is reasonably practicable after new or changed risks are identified (see also Safety Message - Management of Change).
• ensuring the interface agreement details how changes to control measures will be managed. For example, the interface agreement could provide for additional schedules to be added for any risk assessment and control measures associated with temporary works at the level crossing.
• documenting clear processes and procedures in the interface agreement for resolving any disputes that may arise particularly regarding responsibility for managing level crossing risks and controls.
• documenting when the interface agreement will be reviewed, including frequency and triggers, such as in response to incidents.
• documenting the process to review risk assessments, inspections and audits where they have been undertaken by contractors and third parties.
• maintaining and keeping an easily accessible register of all interface agreements.
• undertaking regular audits of interface agreements.

Key documents and actions

You are encouraged to review your interface agreements and safety management system to ensure the good practices raised in this safety message are taken into account.