01Plan the safety work.
Establish a practical approach to managing safety across a project. Connect the system, its lifecycle and the responsibilities of the people involved.
Possible focus: a safety program plan, management arrangements, or a review of an existing approach.
02Understand the hazards.
Examine what could go wrong, how it could happen and what needs to be done about it. Select analysis methods that suit your system and its stage of development.
Possible focus: preliminary hazard identification and analysis, requirements hazard analysis, or operating and support workshops.
03Build the safety argument.
Bring the claims, reasoning and supporting evidence together. Identify where an argument is clear, where evidence is missing and what needs further work.
Possible focus: safety case reports, evidence reviews, or an assurance review with prioritised findings.
04Connect software and safety.
Consider software as part of the wider system safety picture, including how safety engineering fits with an Agile development approach.
Possible focus: software safety planning, review of the safety approach, or focused guidance for an engineering team.
05Make operational risk visible.
Bring together engineering knowledge and the realities of use, maintenance and support. Explore work health and safety alongside the system’s operating context.
Possible focus: facilitated hazard discussions, operating and support analysis, or a review of safety management arrangements.
06Strengthen your team’s practice.
Build a shared understanding of the principles and methods your team needs to apply. Use the questions and challenges of your own work to focus the learning.
Possible focus: tailored team training, a method workshop, or a combination of training and project support.
The scope, deliverables and responsibilities are agreed for each engagement, based on your system, available evidence and project needs.