Sales 0333 577 5016

Support 0333 577 5017
Developed in Partnership

InPractice is a medico-legal consultancy. Who primarily provide training on law and ethics to the NHS, private healthcare providers, professional associations and pharmaceutical companies.

No. of licences % saving
10-19 10%
20-49 20%
50-99 25%
100-149 30%
150-199 35%

For discounted prices on 200+ licences, please email us at or call us on 0333 577 5016.

Root Cause Analysis for Incident Investigation (Level 1)

Duration: 1-2 hours
Cost: £30+VAT

This InPractice online training will make you aware of the purpose of, and the process followed, during a Root Cause Analysis (RCA) investigation. It will give you a better understanding of the RCA methodology, the role of the investigation team and what is expected of employees who are asked to provide witness statements, or are called to interview, during an investigation.

The approximate duration of this training is 1-2 hours.

We also offer the Root Cause Analysis for Incident Investigation (Level 2) training course.

When do I get my certificate?

When you have successfully passed the course you will be able to download and print your certificate straight away.

As this course has been accredited by the CPD Certification Service, your certificate will contain the CPD logo and can be used to provide evidence for compliance.

What does the course cover?

The course contains the following 11 topics and includes an assessment at the end:

What is Root Cause Analysis?

  • The purpose of an RCA investigation
  • The focus on improvement and avoidance of blame
  • The twelve steps in an RCA investigation
  • The three phases of an RCA investigation

The Timetable

  • What the timetable covers
  • Why a timetable is needed
  • How time should be allocated

Removing Bias and Opinion

  • The problem with bias and opinion in incidents reports
  • How incident reports can be ‘neutralised’
  • How you can help the investigation team by avoiding opinion and bias when you report an incident


  • What scoping involves and why it is necessary
  • A simple exercise to help the team identify potential sources of evidence
  • The four categories of evidence
  • How the evidence gathered is indexed and filed

The Timeline

  • The information included in a simple timeline
  • Why a simple timeline is produced
  • The difference between the simple timeline and tabular timeline
  • How a tabular timeline is produced

Additional Information

  • When more information may be required
  • The two categories of missing information


  • Why interviews are sometimes needed
  • Why two people will conduct the interview
  • The need for the witness to agree the written record of the interview during the interview
  • What happens to the agreed written record of the interview

Identifying Good Practice

  • What is meant by ‘good practice’
  • Why the investigation team look for good practice

Identifying Care Delivery Problems

  • What is meant by the term ‘Care Delivery Problem’
  • The precision needed when describing CDPs
  • Examples of well worded and badly worded CDPs

Contributory Factors, Systems and Recommendations

  • What is meant by ‘Wagon-Wheel Analysis’
  • What a ‘contributory factor’ is
  • How missing or failing systems are identified
  • How recommendations are identified
  • Why the team will avoid identifying a definite root cause that led to the CDP

Report, Debrief and Follow-up

  • What goes into the final report
  • The feedback given to staff involved in the incident


The assessment is generated from question banks so that the questions change each time a candidate takes the assessment – making the training suitable for initial and refresher training.

There is no limit on the number of attempts at the assessment and informative feedback is given so candidates can learn from their incorrect responses.

Can’t find the training you want? Just email us at or call us on 0333 577 5016 to discuss what you are looking for. We regularly add to our training portfolio and adapt existing training to specific end user requirements.