<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//TaxonX//DTD Taxonomic Treatment Publishing DTD v0 20100105//EN" "../../nlm/tax-treatment-NS0.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:tp="http://www.plazi.org/taxpub" article-type="research-article" dtd-version="3.0" xml:lang="en">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">69</journal-id>
      <journal-id journal-id-type="index">urn:lsid:arphahub.com:pub:8D21F818-6EEF-540F-91C7-D50E3E5A13E0</journal-id>
      <journal-title-group>
        <journal-title xml:lang="en">Maandblad voor Accountancy en Bedrijfseconomie</journal-title>
        <abbrev-journal-title xml:lang="en">MAB</abbrev-journal-title>
      </journal-title-group>
      <issn pub-type="ppub">0924-6304</issn>
      <issn pub-type="epub">2543-1684</issn>
      <publisher>
        <publisher-name>Amsterdam University Press</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.5117/mab.99.148806</article-id>
      <article-id pub-id-type="publisher-id">148806</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Research Article</subject>
        </subj-group>
        <subj-group subj-group-type="scientific_subject">
          <subject>Accountantscontrole (Auditing)</subject>
          <subject>Organisatie en Management (Organisation and management)</subject>
          <subject>Overige vakgebieden (Other disciplines)</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>﻿An empirical model for root cause analysis in the audit profession</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Groot</surname>
            <given-names>Wendy</given-names>
          </name>
          <email xlink:type="simple">w.groot@vu.nl</email>
          <uri content-type="orcid">https://orcid.org/0000-0002-5949-7942</uri>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Meertens</surname>
            <given-names>Caroline</given-names>
          </name>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Winkelaar</surname>
            <given-names>Tom</given-names>
          </name>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
      </contrib-group>
      <aff id="A1">
        <label>1</label>
        <addr-line content-type="verbatim">Vrije Universiteit , Amsterdam, Netherlands</addr-line>
        <institution>Vrije Universiteit </institution>
        <addr-line content-type="city">Amsterdam</addr-line>
        <country>Netherlands</country>
      </aff>
      <aff id="A2">
        <label>2</label>
        <addr-line content-type="verbatim">PwC, Amsterdam, Netherlands</addr-line>
        <institution>PwC</institution>
        <addr-line content-type="city">Amsterdam</addr-line>
        <country>Netherlands</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding author: Wendy Groot (<email xlink:type="simple">w.groot@vu.nl</email>).</p>
        </fn>
        <fn fn-type="edited-by">
          <p>Academic editor: Barbara Majoor</p>
        </fn>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2025</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>23</day>
        <month>07</month>
        <year>2025</year>
      </pub-date>
      <volume>99</volume>
      <issue>3</issue>
      <fpage>155</fpage>
      <lpage>161</lpage>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/5B6CFEAC-8982-5DA9-B446-D59DFC7CA92A">5B6CFEAC-8982-5DA9-B446-D59DFC7CA92A</uri>
      <uri content-type="zenodo_dep_id" xlink:href="https://zenodo.org/record/16417733">16417733</uri>
      <history>
        <date date-type="received">
          <day>05</day>
          <month>02</month>
          <year>2025</year>
        </date>
        <date date-type="accepted">
          <day>23</day>
          <month>05</month>
          <year>2025</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>Wendy Groot, Caroline Meertens, Tom Winkelaar</copyright-statement>
        <license license-type="creative-commons-attribution" xlink:href="https://creativecommons.org/licenses/by-nc-nd/4.0/" xlink:type="simple">
          <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution License (CC BY-NC-ND 4.0), which permits to copy and distribute the article for non-commercial purposes, provided that the article is not altered or modified and the original author and source are credited.</license-p>
        </license>
      </permissions>
      <abstract>
        <label>﻿Abstract</label>
        <p>Audit firms conduct root cause analysis (<abbrev xlink:title="root cause analysis" id="ABBRID0EUC">RCA</abbrev>) to learn from errors and enhance future processes. This study aims to improve the effectiveness of these efforts by introducing a root cause taxonomy that categorizes underlying causes and develops a common language within the audit profession. Developed empirically and validated with data from an audit firm in the Netherlands, spanning from 2021 to 2024, the taxonomy includes six categories: Strategy and policy; Systems and procedures; Knowledge and understanding; Time and capacity; Human factors; and Client matters. Our findings reveal that the root causes frequently manifest in conjunction with one another rather than in isolation, indicating interdependencies. While the list of root causes is not exhaustive, this taxonomy offers a structured approach that can enhance consistency within the <abbrev xlink:title="root cause analysis" id="ABBRID0EYC">RCA</abbrev> practice.</p>
      </abstract>
      <kwd-group>
        <label>Keywords</label>
        <kwd>Root cause analysis</kwd>
        <kwd>taxonomy</kwd>
        <kwd>audit profession</kwd>
        <kwd>audit quality</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="﻿Relevance to practice" id="SECID0EAD">
      <title>﻿Relevance to practice</title>
      <p>Audit firms can use the taxonomy in their <abbrev xlink:title="root cause analysis" id="ABBRID0EGD">RCA</abbrev> practice to create more consistency both in identifying root causes and reporting on them. This approach not only facilitates the identification of broader patterns, rather than merely incidental issues, but also allows for organizational learning and fosters opportunities for cross-firm knowledge sharing. Furthermore, the use of the root cause taxonomy ensures that the <abbrev xlink:title="root cause analysis" id="ABBRID0EKD">RCA</abbrev> process produces more granular and precise insights, thereby reducing ambiguity in the outcomes. Such precision is crucial for effectively addressing root causes, preventing resource misallocation, and minimizing the recurrence of identified issues.</p>
    </sec>
    <sec sec-type="﻿1. Introduction" id="SECID0EOD">
      <title>﻿1. Introduction</title>
      <p>Root cause analysis (<abbrev xlink:title="root cause analysis" id="ABBRID0EUD">RCA</abbrev>) is an upcoming practice in the audit profession. <abbrev xlink:title="root cause analysis" id="ABBRID0EYD">RCA</abbrev> is based on the principle that the most effective way to resolve a problem is by identifying, addressing, and eliminating its underlying causes (<xref ref-type="bibr" rid="B17">NBA 2019</xref>; <xref ref-type="bibr" rid="B18">PCAOB 2024</xref>). Audit firms have been conducting some form of RCAs for several years, and with the establishment of <abbrev xlink:title="International Standard on Quality Management 1" id="ABBRID0EEE">ISQM1</abbrev> in 2022, the <abbrev xlink:title="root cause analysis" id="ABBRID0EIE">RCA</abbrev> practice has been further embedded (<abbrev xlink:title="International Standard on Quality Management 1" id="ABBRID0EME">ISQM1</abbrev>, <xref ref-type="bibr" rid="B11">IAASB 2020</xref>). However, current criticisms indicate that audit firms struggle to consider all the causal factors within their complex context and gain a sufficient in-depth understanding (<xref ref-type="bibr" rid="B1">AFM 2020</xref>; <xref ref-type="bibr" rid="B18">PCAOB 2024</xref>). Rather than identifying idiosyncratic root causes, leading to ineffective remediation, audit firms should aim to get an understanding of broader patterns and trends within their firm. To address these criticisms, the audit profession can benefit from fields which have a more established <abbrev xlink:title="root cause analysis" id="ABBRID0E3E">RCA</abbrev> practice, such as healthcare and aviation (e.g., <xref ref-type="bibr" rid="B2">Beaubien and Baker 2002</xref>; <xref ref-type="bibr" rid="B5">Dien et al. 2004</xref>; <xref ref-type="bibr" rid="B6">Ergai et al. 2016</xref>). Such standardization is particularly valuable as it fosters consistency and enables the identification of patterns and trends over extended periods, leading to a deeper understanding of underlying issues (<xref ref-type="bibr" rid="B2">Beaubien and Baker 2002</xref>; <xref ref-type="bibr" rid="B21">Runciman et al. 2009</xref>). Misuse of terminology, on the other hand, can lead to significant misunderstandings surrounding the language of safety and quality (<xref ref-type="bibr" rid="B3">Chang et al. 2005</xref>).</p>
      <p>The language of quality, specifically within the audit profession, is inherently ambiguous. There have been several studies which developed frameworks to capture audit quality (<xref ref-type="bibr" rid="B4">DeFond and Zhang 2014</xref>; <xref ref-type="bibr" rid="B8">Francis 2011</xref>; <xref ref-type="bibr" rid="B13">Knechel et al. 2013</xref>), providing different perspectives on what audit quality is and how it can be measured. However, producing audit services remains “highly complex, and service quality can be difficult to objectively define or measure” (<xref ref-type="bibr" rid="B14">Knechel et al. 2020</xref>, p. 2). Given the inherent ambiguity, the implementation of a taxonomy could be especially advantageous, as it allows for the consistent use of language for both the <abbrev xlink:title="root cause analysis" id="ABBRID0EKG">RCA</abbrev> team members and stakeholders. This consistency contributes to a more structured approach in addressing the complexities associated with improving audit quality. As such, a taxonomy can help create consistency and allow to identify patterns and trends over longer periods of time, paving the way for a better understanding (<xref ref-type="bibr" rid="B21">Runciman et al. 2009</xref>). However, taxonomies from other fields do not translate well to the audit profession given the profession specific nature of the taxonomies, requiring a root cause taxonomy tailored for the audit profession.</p>
      <p>In our study we empirically developed a root cause taxonomy for the audit profession, providing common language to increase the <abbrev xlink:title="root cause analysis" id="ABBRID0EUG">RCA</abbrev>’s effectiveness, increasing learning potential, and facilitating opportunities for cross-firm learning. Furthermore, we identified a non-exhaustive list of common root causes for each category to further enable consistency. Although we identified separate root causes, they typically manifest in conjunction with one another rather than in isolation.</p>
    </sec>
    <sec sec-type="﻿2. Root cause analysis in the audit profession" id="SECID0EYG">
      <title>﻿2. Root cause analysis in the audit profession</title>
      <p>The International Standard on Quality Management 1 (<abbrev xlink:title="International Standard on Quality Management 1" id="ABBRID0E5G">ISQM1</abbrev>, <xref ref-type="bibr" rid="B11">IAASB 2020</xref>) requires audit firms to conduct <abbrev xlink:title="root cause analysis" id="ABBRID0EGH">RCA</abbrev> in the case of adverse events, such as restatements in the financial statements after the audit sign off or quality findings from audit file inspections. <abbrev xlink:title="root cause analysis" id="ABBRID0EKH">RCA</abbrev> is the process of identifying the root causes of these events, so that remedial action can be formulated to prevent these root causes in the future (e.g., <xref ref-type="bibr" rid="B15">Leveson et al. 2020</xref>; <xref ref-type="bibr" rid="B20">Percarpio et al. 2008</xref>; <xref ref-type="bibr" rid="B22">Wu et al. 2008</xref>). <abbrev xlink:title="root cause analysis" id="ABBRID0E1H">RCA</abbrev>, therefore, aims to provide audit firms, regulators, and practitioners with the opportunity to learn from past mistakes and thus improve audit quality (<xref ref-type="bibr" rid="B18">PCAOB 2024</xref>). Although the audit firms have been conducting RCAs for several years in some capacity (<xref ref-type="bibr" rid="B17">NBA 2019</xref>), the <abbrev xlink:title="International Standard on Quality Management 1" id="ABBRID0EHAAC">ISQM1</abbrev> will further embed the <abbrev xlink:title="root cause analysis" id="ABBRID0ELAAC">RCA</abbrev> practice within the audit firms.</p>
      <p>In this paper we define root causes as those causal factors that, when addressed, prevent future occurrence of the issue at hand or reduce the risk or impact of its occurrence. The <abbrev xlink:title="root cause analysis" id="ABBRID0ERAAC">RCA</abbrev> process often starts with an adverse event but can also be triggered by good practices, as these can provide insights into underlying dynamics of audit quality as well. To identify the root causes, data on the adverse event (or best practice) is collected, for example through interviews with the audit team and data about the audit processes as it can be derived from internal systems. The collected data is then analyzed to identify the root causes, after which the remedial action can be formulated (<xref ref-type="bibr" rid="B10">Groot 2021</xref>). Although these steps seem straightforward, the <abbrev xlink:title="root cause analysis" id="ABBRID0EZAAC">RCA</abbrev> is a complex and subjective process (<xref ref-type="bibr" rid="B19">Peerally et al. 2016</xref>), and in the audit profession takes place in an environment of complex systems and processes. It is difficult to determine whether all the (relevant) root causes are identified, whether a sufficient level of depth is gained and whether there is a clear understanding of how the root causes interrelate. As it is not possible to determine whether addressing the identified root causes would have indeed prevented the initial occurrence, especially without the ability to revisit and alter the case, and it is often a combination of root causes that contribute to an issue, it is not surprising that regulatory oversight bodies emphasized the importance of acquiring a sufficient level of depth (<xref ref-type="bibr" rid="B1">AFM 2020</xref>; <xref ref-type="bibr" rid="B18">PCAOB 2024</xref>).</p>
      <p>In this paper, we focus on the development of a taxonomy to improve the effectiveness of RCAs through consistency in language. With the taxonomy developed in this study, we aim to help in achieving this consistency and aid in learning and improving audit quality.</p>
    </sec>
    <sec sec-type="methods" id="SECID0EKBAC">
      <title>﻿3. Research methods</title>
      <p>We collected proprietary data of RCAs conducted within a Big Four audit firm in the Netherlands between October 2020 and December 2023.<sup><xref ref-type="fn" rid="en1">1</xref></sup> RCAs were conducted on:</p>
      <list list-type="bullet">
        <list-item>
          <p>external quality findings from internal reviews;
</p>
        </list-item>
        <list-item>
          <p>external good practices from internal reviews;
</p>
        </list-item>
        <list-item>
          <p>consultations on restatements after the audit opinion sign off; and
</p>
        </list-item>
        <list-item>
          <p>RCAs on thematic matters.
</p>
        </list-item>
      </list>
      <p>RCAs were conducted by a dedicated, multidisciplinary <abbrev xlink:title="root cause analysis" id="ABBRID0E4BAC">RCA</abbrev> team. For each <abbrev xlink:title="root cause analysis" id="ABBRID0EBCAC">RCA</abbrev>, multiple root causes were identified, which formed the basis of the data collection.</p>
      <p>The collected data were coded separately by two of the authors of this article. The initial coding required interpretation of the identified root causes, as the description of the root causes varied across the time period in which RCAs were conducted and across the different team members who conducted them. Based on the knowledge of and experience with the <abbrev xlink:title="root cause analysis" id="ABBRID0EHCAC">RCA</abbrev> practice as an <abbrev xlink:title="root cause analysis" id="ABBRID0ELCAC">RCA</abbrev> team member, the authors were able to make this interpretation. After the initial individual coding, the authors compared the codes and aligned them through multiple discussions. After initial alignment, the authors compared the inductively derived codes with literature on (drivers of) audit quality (<xref ref-type="bibr" rid="B8">Francis 2011</xref>; <xref ref-type="bibr" rid="B7">FRC 2008</xref>; <xref ref-type="bibr" rid="B13">Knechel et al. 2013</xref>; <xref ref-type="bibr" rid="B16">NBA 2017</xref>, <xref ref-type="bibr" rid="B17">2019</xref>). No additional codes were identified based on this review. Subsequently, the codes were discussed with the author who was not involved in the initial coding process. Through these discussions, the six categories of the taxonomy emerged and common root causes per category were identified. Root causes were formulated when they recurred across multiple RCAs. Notably, the root causes are articulated in a neutral manner because they can serve both as drivers for high-quality audits and as drivers for audits of insufficient quality.</p>
      <p>After agreement amongst the three authors on the categorization and formulation of the root causes, the taxonomy was validated with the five other <abbrev xlink:title="root cause analysis" id="ABBRID0EFDAC">RCA</abbrev> team members who were not involved in the process of developing the taxonomy. This validation led to minor adjustments in the wording. To evaluate the usability of the taxonomy, the <abbrev xlink:title="root cause analysis" id="ABBRID0EJDAC">RCA</abbrev> team started to use the taxonomy in their RCAs from January to November 2024. Since its use in practice, a few new root causes were identified, but no further changes were made in the categorization of the taxonomy, suggesting the validity and usability of the model.<sup><xref ref-type="fn" rid="en2">2</xref></sup></p>
      <fig id="F1" position="float" orientation="portrait">
        <object-id content-type="arpha">AC0719F7-1C53-551F-9B7D-A937153905CE</object-id>
        <label>Figure 1.</label>
        <caption>
          <p>Root cause categories.</p>
        </caption>
        <graphic xlink:href="mab-99-155-g001.jpg" position="float" orientation="portrait" xlink:type="simple" id="oo_1380467.jpg">
          <uri content-type="original_file">https://binary.pensoft.net/fig/1380467</uri>
        </graphic>
      </fig>
    </sec>
    <sec sec-type="﻿4. Towards a root cause taxonomy" id="SECID0E4DAC">
      <title>﻿4. Towards a root cause taxonomy</title>
      <p>The taxonomy contains six overarching root cause categories, which subsequently consist of several underlying commonly identified root causes, creating a common language for the <abbrev xlink:title="root cause analysis" id="ABBRID0EDEAC">RCA</abbrev> practice. The taxonomy is developed on the premise that quality findings often arise from a combination of root causes, which can be attributed to distinct categories or within one category. The list of root causes is not exhaustive – new root causes might be identified, and current root causes might turn out to be less relevant over time. The taxonomy is therefore a dynamic model, tailored for its time and place. The taxonomy can be used during the analysis phase of the <abbrev xlink:title="root cause analysis" id="ABBRID0EHEAC">RCA</abbrev>, to determine whether the <abbrev xlink:title="root cause analysis" id="ABBRID0ELEAC">RCA</abbrev> team members have discussed all relevant topics with the <abbrev xlink:title="root cause analysis" id="ABBRID0EPEAC">RCA</abbrev>’s participants, and if they have a shared and sufficient in-depth understanding of the case at hand and its root causes. Also, the taxonomy can create consistency in the <abbrev xlink:title="root cause analysis" id="ABBRID0ETEAC">RCA</abbrev> reporting and monitoring of remedial actions.</p>
      <p>In this section, we elaborate on each of the categories: Strategy and policy, Systems and procedures, Knowledge and understanding, Time and capacity, Human factors, and Client matters. To illustrate the application of the model, we will highlight two root causes per category. Rather than aiming to address all potential root causes, our intention is to provide insight into how the model functions and can be applied in practice.</p>
      <sec sec-type="﻿4.1. Strategy and policy" id="SECID0EYEAC">
        <title>﻿4.1. Strategy and policy</title>
        <p>Root causes within this category refer to the application of broader organizational strategies and policies, and their influence within the firm. Root causes in this category lie within the scope of the strategic choices made by leadership and could be described as prioritization, tone from the top, and change management. We elaborate on the <italic>prioritization</italic> and <italic>change management.</italic></p>
        <p>The root cause prioritization might occur when leadership makes strategic decisions in prioritizing which lead to new goals or key performance indicators (KPIs). For example, an audit firm might decide to schedule the courses for the auditors in the fall while simultaneously committing to a KPI on a timely completion of the planning phase, which for the auditors coincides with the timing of the courses. Depending on which KPI is perceived as the most important in daily practice, this might lead to diverging outcomes. On the one hand, people might choose to prioritize fulfilling the firm’s training requirements, not meeting the deadline for completing the planning phase, pushing planning tasks into the execution phase and potentially leaving insufficient time for reflection later in the audit process. On the other hand, they might prioritize complying with the deadline for the completion of the planning phase, but fail to meet the training deadlines, potentially missing the latest knowledge updates needed for the audit. As such, leadership’s prioritizations, or lack thereof, might be a root cause for quality issues due to insufficient process management by not meeting the KPI of timely completion of the planning phase, or a root cause for quality issues due to insufficient knowledge.</p>
        <p>Another root cause in Strategy and policy could be change management, which refers to the approach surrounding organizational transitions to a desired future state. For example, let us consider the implementation of a revised standard. An audit firm might set up a change management program, including training, communication of the revisions and the impact on the daily practice, and adjustments of the working programs to ensure correct application of the new requirements. When the change program is not set up appropriately, for example because the need for behavioral change is not incorporated in the program sufficiently, it can lead to quality findings related to the revised standard. Although each element in the change program (i.e., training, communication, or working program) may serve as a root cause and fit into one of the established root cause categories, there might also be an overarching issue stemming from shortcomings in the change management approach itself, such as the absence of a coherent change management strategy. In the case of the latter, the root cause refers to a broader organizational strategy as it lies within the scope of the strategic choices made by leadership.</p>
      </sec>
      <sec sec-type="﻿4.2. Systems and procedures" id="SECID0EDFAC">
        <title>﻿4.2. Systems and procedures</title>
        <p>Root causes within this category lie within the systems and procedures in place, which includes the IT-systems, internal procedures, working programs and tools used, and their influence.​ Furthermore, root causes can refer, for example, to the way audit standards have been incorporated in the firm’s audit procedures manual. In this section we elaborate on <italic>the roles and responsibilities</italic> and <italic>the design of the systems and procedures</italic>.</p>
        <p>Regarding the root cause on roles and responsibilities, it can be the issue that there is a lack of clarity in who has which roles and responsibilities in a certain procedure. This problem can manifest in audit engagements, where ambiguous roles and responsibilities can lead to significant inefficiencies and misunderstandings. The responsibilities in the context of an audit entail a clear understanding of specific tasks that need to be performed, the designation of the team members to these tasks and the accountability of these individuals. Tasks can include execution and documentation of audit procedures, review of work performed, communications in the process of the audit, which also includes internal and external reporting. The ambiguity can lead to duplication of tasks, tasks being overlooked, inconsistent execution of tasks, confusion about who should be doing what. When tasks are overlooked, it could mean that work performed on a high risk element of the audit is not reviewed at the level needed, as each team member involved in the related review tasks has an assumption that another team member has covered the review at the expected level of depth.</p>
        <p>Another illustration of a root cause in this category relates to the design of processes and systems. For example, an auditor might use several systems in preparation of and during the audit (e.g., a system for the acceptance and continuance of clients and engagements, a system for the audit file, and a system for the creation of reports or engagement letters). However, it is possible that these systems do not have an interface, requiring manual work, as such that inconsistencies can emerge and lead to issues. For instance, an auditor documents their work in their audit files, but some information is also relevant for the acceptance and continuance process. When this process is documented in a different system, which is not connected to the audit file, difference might emerge between the latest insights in the audit file and the information required by the acceptance and continuance process.</p>
      </sec>
      <sec sec-type="﻿4.3. Knowledge and understanding" id="SECID0EPFAC">
        <title>﻿4.3. Knowledge and understanding</title>
        <p>Root causes in this category refer to the level of knowledge, experience, education, and understanding.​ Given the knowledge-intensive nature of auditing (<xref ref-type="bibr" rid="B14">Knechel et al. 2020</xref>), it is crucial for auditors to possess an appropriate foundation of knowledge and understanding in various areas, including audit standards and financial reporting (<xref ref-type="bibr" rid="B16">NBA 2017</xref>, <xref ref-type="bibr" rid="B17">2019</xref>) and sufficient understanding of the entity and its environment (ISA 315). Another example in this category can refer to the level of project management skills. Furthermore, to comply with the internal system of quality management, auditors must also be knowledgeable on internal (risk management) procedures and guidance. These knowledge areas are subject to constant change and development, necessitating the need to continuously update one’s knowledge (<xref ref-type="bibr" rid="B17">NBA 2019</xref>). This category, thus, gathers all root causes that refer to the auditor’s lack of <italic>know­ledge</italic> and <italic>understanding</italic>.</p>
        <p>An example of a root cause within this category might be an insufficient understanding of a accounting issue, which might be specific for the engagement, thus not common. Due to the insufficient knowledge of the specific accounting topic, the issue can become an ‘unknown unknown’ for the auditor and as such does not trigger consultation with accounting specialists, potentially leading to overseeing a material error in the financial statements.</p>
        <p>Furthermore, root causes: in this category might relate to internal procedures on, for example, the procedures in an audit firm’s system of quality management to ensure its independence (<abbrev xlink:title="International Standard on Quality Management 1" id="ABBRID0EMGAC">ISQM1</abbrev>). These procedures might consist of guidance and tools or systems that need to be used. However, when auditors have insufficient understanding of the applicable internal independence procedures or are unsure on where to find the relevant guidance, independence issues might occur.</p>
      </sec>
      <sec sec-type="﻿4.4. Time and capacity" id="SECID0EQGAC">
        <title>﻿4.4. Time and capacity</title>
        <p>Root causes in this category refer to matters regarding allocated resources and capacity, which are themes that have been defined as important drivers of audit quality in prior literature (<xref ref-type="bibr" rid="B16">NBA 2017</xref>, <xref ref-type="bibr" rid="B17">2019</xref>). Examples of root causes we identified in this category are availability, flexibility and continuity. In this section we elaborate on the root causes <italic>availability</italic> and <italic>continuity</italic>.</p>
        <p>Availability refers to the presence of the required number of team members, with the knowledge and experience needed for the specific audit. When there is insufficient availability of the right people for the audit, for example due to sickness or employee turnover, the remaining team members may pick up the tasks of the sick colleague within the allocated time. This can result in quality findings occurring in the form of material errors in the financial statements being overlooked or not meeting certain audit standard requirements. As with all root causes, the root cause availability often presents itself in combination with other root cause categories. If a client does not deliver the required information within the agreed-upon period (<italic>Client matters</italic>), an issue with the audit team’s time and capacity might arise when they have insufficient availability by the time the required information is received. On the positive side – when the availability of the team members is appropriate, the right people have sufficient time and capacity to make adequate judgments and decisions within the audit, and document those properly. Additionally, if the team does have sufficient availability of the needed level of experience, it might facilitate time and space for knowledge spillover effects within the team (<italic>Knowledge and understanding</italic>).</p>
        <p>Another root cause in this category is the continuity of resources, which relates to the prolonged assignment of team members to a client, enabling them to acquire specific client knowledge and understanding of its business, as well as building a good relationship with the client. As such, client specific knowledge can build up and subsequently contribute to high quality audits (<xref ref-type="bibr" rid="B16">NBA 2017</xref>). However, when the team is not stable over time, gaps can arise in the understanding of the client’s business and its environment, leading to quality findings. As with the previous example this root cause can also occur simultaneously with or cause other root causes. For example, when a client does not prioritize the audit of the financial statements and keeps failing to meet commitments to the audit team (<italic>Client matters</italic>), team members might not want to work for this specific client. In these cases, the team members might request to be scheduled for a different audit, increasing the turnover of this client’s team.</p>
      </sec>
      <sec sec-type="﻿4.5. Human factors" id="SECID0EQHAC">
        <title>﻿4.5. Human factors</title>
        <p>Root causes in this category refer to the various aspects related to human behavior and interactions within the audit teams. Within this category, we have identified several root causes that can be responsible for the occurrence of audit quality findings. We provide a discussion on the root causes <italic>collaboration</italic> and <italic>psychological safety</italic>.</p>
        <p>Collaboration can refer to issues arising from inadequate teamwork, coordination, or cooperation among individuals or departments. For example, within the context of hybrid working with international team members with distinct cultural backgrounds and time zones, teams might struggle more to achieve sufficient engagement, coaching and sense of goal alignment. On the other hand, appropriate collaboration results in better coaching, reviewing and thus improves audit quality. As such, audit teams might need to adapt their communication strategies and provide the necessary support and guidance to ensure successful collaboration in these dynamic environments.</p>
        <p>The second root cause, psychological safety, refers to the “sense of being able to show and employ self without fear of negative consequences to self-image, status, or career” (<xref ref-type="bibr" rid="B12">Kahn 1990</xref>, p. 705). Psychological safety influences the extent to which auditors are motivated to express their opinions during the audit process, such as during fraud brainstorming sessions (<xref ref-type="bibr" rid="B9">Gissel and Johnstone 2017</xref>). When team members observe a culture where questioning a manager’s judgment or pointing out potential errors is implicitly discouraged or even punished, they come to understand that it is not safe to speak up. As a result, they may withhold valuable observations or questions during team discussions or file reviews, potentially decreasing audit quality. Over time, this dynamic could even create a culture of silence and compliance, where team members focus more on avoiding conflict than on exercising professional skepticism.</p>
      </sec>
      <sec sec-type="﻿4.6. Client matters" id="SECID0EFIAC">
        <title>﻿4.6. Client matters</title>
        <p>Root causes in this category refer to the matters that reside on the client’s side, such as client’s knowledge (e.g., accounting standards), prioritization, availability of resources, and the relationship between the client and auditor. Even though these client matters are largely beyond the auditor’s control, it might still reveal opportunities for areas to address. For example, root causes regarding client matters might give rise to more selectiveness in accepting and continuing clients and engagements, pressing the client for improvements (e.g. through management letters), or taking additional quality measures in the audit process. In this section we briefly illustrate an example of the root causes <italic>prioritization</italic> and <italic>availability</italic>.</p>
        <p>The root cause of the client’s prioritization might occur in the case of subsidiaries of foreign group companies. These subsidiaries are required to publish statutory financial statements but might not prioritize the preparation of the statutory accounts due to a focus on their group reporting requirements. As the priority is somewhere else for the client, the statutory audit might not get the attention required to get the necessary information and documentation.</p>
        <p>The lack of priority might also be related to the availability of the client, as the client’s resources are allocated elsewhere. Due to this lack, deliverables might be delayed, and the quality of the information and underlying documentation might turn out impaired. The insufficient information and untimely documentation complicates the audit, and decreases they being delivered by the client. Issues regarding availability might then spill over to the audit quality.</p>
      </sec>
    </sec>
    <sec sec-type="﻿5. Concluding remarks" id="SECID0ERIAC">
      <title>﻿5. Concluding remarks</title>
      <p>In this study, we developed a root cause taxonomy, establishing a common language for the <abbrev xlink:title="root cause analysis" id="ABBRID0EXIAC">RCA</abbrev> practice within the audit profession. Some of the root causes were reported in prior literature (<xref ref-type="bibr" rid="B16">NBA 2017</xref>, <xref ref-type="bibr" rid="B17">2019</xref>) or were already identified as audit quality indicators (<xref ref-type="bibr" rid="B8">Francis 2011</xref>; <xref ref-type="bibr" rid="B7">FRC 2008</xref>; <xref ref-type="bibr" rid="B13">Knechel et al. 2013</xref>). However, as audit firms grapple with the challenge of identifying all the root causes in the complex environment of auditing and gaining a sufficient in-depth understanding (<xref ref-type="bibr" rid="B1">AFM 2020</xref>; <xref ref-type="bibr" rid="B18">PCAOB 2024</xref>) we hope to contribute to a more effective <abbrev xlink:title="root cause analysis" id="ABBRID0EXJAC">RCA</abbrev> practice by combining our empirical insights with these prior insights in a holistic taxonomy for root causes. As such, we subsequently aim to contribute to further improve overall audit quality within the audit firms.</p>
      <p>Our experience is that the taxonomy has proven to be valuable in our own <abbrev xlink:title="root cause analysis" id="ABBRID0E4JAC">RCA</abbrev> practice, both in gathering data for the <abbrev xlink:title="root cause analysis" id="ABBRID0EBKAC">RCA</abbrev> and identifying the root causes in analyzing the data. It provides a framework for conducting broad conversations within the <abbrev xlink:title="root cause analysis" id="ABBRID0EFKAC">RCA</abbrev> team and with the people involved in the case. For example, if an interviewee primarily focuses on the client’s matters, the taxonomy provides a topic list for the interviewer to also discuss other topics, thereby preventing tunnel vision. Also, the taxonomy aids in the analysis of the data, as it provides a broad spectrum for reflection on the case, whilst maintaining a consistent language, facilitating a shared understanding. Furthermore, due to the common language, the taxonomy contributes to consistency in identifying the necessary follow-up actions to address the underlying causes and facilitating the evaluation of ongoing actions. Lastly, the standardized language provided by the taxonomy provided consistency to the reporting of insights and progress to stakeholders and leadership.</p>
      <p>However, there are also limitations to this study, as it is empirically developed based on one audit firm, within the Netherlands. Although we expect there to be sufficient similarities between audit firms to be able to benefit from the taxonomy, the specificalities of another audit firm might require translation or adaptation. Furthermore, different countries may have varying needs to distinguish cultural characteristics and institutional contexts. Future research could contribute by examining these diverse contexts and their impact on the taxonomy. Lastly, the taxonomy should be viewed as a means to an end, a tool that supports the larger objectives of problem solving and continuous quality improvement. The focus should always be on using the taxonomy to identify and address root causes, rather than getting caught up in the taxonomy itself, using it as a checklist, and making it a goal to map identified root causes to the developed taxonomy.</p>
      <boxed-text id="box1" position="float" orientation="portrait">
        <p><bold>Dr. W. Groot RA – Wendy</bold>, Assistent Professor VU en Senior Manager PwC.</p>
      </boxed-text>
      <boxed-text id="box2" position="float" orientation="portrait">
        <p><bold>C.E.B. Jacobs-Meertens RA, Caroline</bold>, Senior Manager PwC.</p>
      </boxed-text>
      <boxed-text id="box3" position="float" orientation="portrait">
        <p><bold>Drs. T. Winkelaar – Tom</bold>, Senior Associate PwC.</p>
      </boxed-text>
    </sec>
  </body>
  <back>
    <fn-group>
      <title>Notes</title>
      <fn id="en1">
        <p>The proprietary nature of the data precludes providing detailed insights into the exact numbers.</p>
      </fn>
      <fn id="en2">
        <p>There are various tools available to understand the interconnections among different root causes. For example, <xref ref-type="bibr" rid="B10">Groot (2021)</xref> emphasizes the importance of moving beyond linear perspectives to gain a comprehensive understanding of the system and provides insights into several models that can assist in mapping these interrelations.</p>
      </fn>
    </fn-group>
    <ref-list>
      <title>﻿References</title>
      <ref id="B1">
        <mixed-citation xlink:type="simple">AFM [Autoriteit Financiële Markten] (<year>2020</year>) De kwaliteitsslag bij de Big 4-accountantsorganisaties onderzocht. Uitkomsten van het onderzoek naar de kwaliteitsgerichte cultuur, de kwaliteitscirkel en kwaliteitswaarborgen. <ext-link xlink:href="https://www.afm.nl/nl-nl/nieuws/2020/juli/rapport-kwaliteitsslag-big4" ext-link-type="uri" xlink:type="simple">https://www.afm.nl/nl-nl/nieuws/2020/juli/rapport-kwaliteitsslag-big4</ext-link></mixed-citation>
      </ref>
      <ref id="B2">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Beaubien</surname><given-names>JM</given-names></name><name name-style="western"><surname>Baker</surname><given-names>DP</given-names></name></person-group> (<year>2002</year>) <article-title>A review of selected aviation Human Factors taxonomies, accident/incident reporting systems, and data reporting tools.</article-title><source>International Journal of Applied Aviation Studies</source><volume>2</volume>(<issue>2</issue>): <fpage>11</fpage>–<lpage>36</lpage>.</mixed-citation>
      </ref>
      <ref id="B3">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Chang</surname><given-names>A</given-names></name><name name-style="western"><surname>Schyve</surname><given-names>PM</given-names></name><name name-style="western"><surname>Croteau</surname><given-names>RJ</given-names></name><name name-style="western"><surname>O’Leary</surname><given-names>DS</given-names></name><name name-style="western"><surname>Loeb</surname><given-names>JM</given-names></name></person-group> (<year>2005</year>) <article-title>The JCAHO patient safety event taxonomy: A standardized terminology and classification schema for near misses and adverse events.</article-title><source>International Journal for Quality in Health Care</source><volume>17</volume>(<issue>2</issue>): <fpage>95</fpage>–<lpage>105</lpage>. <ext-link xlink:href="10.1093/intqhc/mzi021" ext-link-type="doi" xlink:type="simple">https://doi.org/10.1093/intqhc/mzi021</ext-link></mixed-citation>
      </ref>
      <ref id="B4">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>DeFond</surname><given-names>M</given-names></name><name name-style="western"><surname>Zhang</surname><given-names>J</given-names></name></person-group> (<year>2014</year>) <article-title>A review of archival auditing research.</article-title><source>Journal of Accounting and Economics</source><volume>58</volume>(<issue>2–3</issue>): <fpage>275</fpage>–<lpage>326</lpage>. <ext-link xlink:href="10.1016/j.jacceco.2014.09.002" ext-link-type="doi" xlink:type="simple">https://doi.org/10.1016/j.jacceco.2014.09.002</ext-link></mixed-citation>
      </ref>
      <ref id="B5">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Dien</surname><given-names>Y</given-names></name><name name-style="western"><surname>Llory</surname><given-names>M</given-names></name><name name-style="western"><surname>Montmayeul</surname><given-names>R</given-names></name></person-group> (<year>2004</year>) <article-title>Organisational accidents investigation methodology and lessons learned.</article-title><source>Journal of Hazardous Materials</source><volume>111</volume>(<issue>13</issue>): <fpage>147</fpage>–<lpage>153</lpage>. <ext-link xlink:href="10.1016/j.jhazmat.2004.02.021" ext-link-type="doi" xlink:type="simple">https://doi.org/10.1016/j.jhazmat.2004.02.021</ext-link></mixed-citation>
      </ref>
      <ref id="B6">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Ergai</surname><given-names>A</given-names></name><name name-style="western"><surname>Cohen</surname><given-names>T</given-names></name><name name-style="western"><surname>Sharp</surname><given-names>J</given-names></name><name name-style="western"><surname>Wiegmann</surname><given-names>D</given-names></name><name name-style="western"><surname>Gramopadhye</surname><given-names>A</given-names></name><name name-style="western"><surname>Shappel</surname><given-names>S</given-names></name></person-group> (<year>2016</year>) <article-title>Assessment of the human factors analysis and classification system (HFACS): Intra-rater and inter-rater reliability.</article-title><source>Safety Science</source><volume>82</volume>: <fpage>393</fpage>–<lpage>398</lpage>. <ext-link xlink:href="10.1016/j.ssci.2015.09.028" ext-link-type="doi" xlink:type="simple">https://doi.org/10.1016/j.ssci.2015.09.028</ext-link></mixed-citation>
      </ref>
      <ref id="B7">
        <mixed-citation xlink:type="simple">FRC [Financial Reporting Council] (<year>2008</year>) The audit quality framework. <ext-link xlink:href="https://media.frc.org.uk/documents/The_Audit_Quality_Framework_and_initial_feedback_-_February_2008.pdf" ext-link-type="uri" xlink:type="simple">https://media.frc.org.uk/documents/The_Audit_Quality_Framework_and_initial_feedback_-_February_2008.pdf</ext-link></mixed-citation>
      </ref>
      <ref id="B8">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Francis</surname><given-names>JR</given-names></name></person-group> (<year>2011</year>) <article-title>A framework for understanding and researching audit quality.</article-title><source>Auditing: A Journal of Practice &amp; Theory</source><volume>30</volume>(<issue>2</issue>): <fpage>125</fpage>–<lpage>152</lpage>. <ext-link xlink:href="10.2308/ajpt-50006" ext-link-type="doi" xlink:type="simple">https://doi.org/10.2308/ajpt-50006</ext-link></mixed-citation>
      </ref>
      <ref id="B9">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Gissel</surname><given-names>JL</given-names></name><name name-style="western"><surname>Johnstone</surname><given-names>KM</given-names></name></person-group> (<year>2017</year>) <article-title>Information sharing during auditor’s fraud brainstorming: Effects of psychological safety and auditor knowledge.</article-title><source>Auditing: A Journal of Practice &amp; Theory</source><volume>36</volume>(<issue>2</issue>): <fpage>87</fpage>–<lpage>110</lpage>. <ext-link xlink:href="10.2308/ajpt-51519" ext-link-type="doi" xlink:type="simple">https://doi.org/10.2308/ajpt-51519</ext-link></mixed-citation>
      </ref>
      <ref id="B10">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Groot</surname><given-names>W</given-names></name></person-group> (<year>2021</year>) Root cause analysis – What do we know? Maandblad voor Accountancy en Bedrijfseconomie 95(1/2): 87–93. <ext-link xlink:href="10.5117/mab.95.60778" ext-link-type="doi" xlink:type="simple">https://doi.org/10.5117/mab.95.60778</ext-link></mixed-citation>
      </ref>
      <ref id="B11">
        <mixed-citation xlink:type="simple">IAASB [International Auditing and Assurance Standards Board] (<year>2020</year>) International Standard on Quality Management 1. <ext-link xlink:href="https://www.ifac.org/system/files/publications/files/IAASB-Quality-Management-ISQM-1-Quality-Management-for-Firms.pdf" ext-link-type="uri" xlink:type="simple">https://www.ifac.org/system/files/publications/files/IAASB-Quality-Management-ISQM-1-Quality-Management-for-Firms.pdf</ext-link></mixed-citation>
      </ref>
      <ref id="B12">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Kahn</surname><given-names>WA</given-names></name></person-group> (<year>1990</year>) <article-title>Psychological conditions of personal engagement and disengagement at work.</article-title><source>Academy of Management Journal</source><volume>33</volume>(<issue>4</issue>): <fpage>692</fpage>–<lpage>724</lpage>. <ext-link xlink:href="10.2307/256287" ext-link-type="doi" xlink:type="simple">https://doi.org/10.2307/256287</ext-link></mixed-citation>
      </ref>
      <ref id="B13">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Knechel</surname><given-names>WR</given-names></name><name name-style="western"><surname>Krishan</surname><given-names>GV</given-names></name><name name-style="western"><surname>Pevzner</surname><given-names>M</given-names></name><name name-style="western"><surname>Bhaskar</surname><given-names>LS</given-names></name><name name-style="western"><surname>Velury</surname><given-names>U</given-names></name></person-group> (<year>2013</year>) <article-title>Audit quality: Insights from the academic literature.</article-title><source>Auditing: A Journal of Practice &amp; Theory</source><volume>32</volume>(<issue>1</issue>): <fpage>385</fpage>–<lpage>421</lpage>. <ext-link xlink:href="10.2139/ssrn.2040754" ext-link-type="doi" xlink:type="simple">https://doi.org/10.2139/ssrn.2040754</ext-link></mixed-citation>
      </ref>
      <ref id="B14">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Knechel</surname><given-names>WR</given-names></name><name name-style="western"><surname>Thomas</surname><given-names>E</given-names></name><name name-style="western"><surname>Driskill</surname><given-names>M</given-names></name></person-group> (<year>2020</year>) Understanding financial auditing from a service perspective. Accounting, Organizations and Society 81: 101080. <ext-link xlink:href="10.1016/j.aos.2019.101080" ext-link-type="doi" xlink:type="simple">https://doi.org/10.1016/j.aos.2019.101080</ext-link></mixed-citation>
      </ref>
      <ref id="B15">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Leveson</surname><given-names>N</given-names></name><name name-style="western"><surname>Samost</surname><given-names>A</given-names></name><name name-style="western"><surname>Dekker</surname><given-names>S</given-names></name><name name-style="western"><surname>Finkelstein</surname><given-names>S</given-names></name><name name-style="western"><surname>Raman</surname><given-names>J</given-names></name></person-group> (<year>2020</year>) <article-title>A systems approach to analyzing and preventing hospital adverse events.</article-title><source>Journal of Patient Safety</source><volume>16</volume>(<issue>2</issue>): <fpage>162</fpage>–<lpage>167</lpage>. <ext-link xlink:href="10.1097/PTS.0000000000000263" ext-link-type="doi" xlink:type="simple">https://doi.org/10.1097/PTS.0000000000000263</ext-link></mixed-citation>
      </ref>
      <ref id="B16">
        <mixed-citation xlink:type="simple">NBA [Koninklijke Nederlandse Beroepsorganisatie van Accountants] (<year>2017</year>) Naar de kern. Een sectoranalyse van drivers van controlekwaliteit. <ext-link xlink:href="https://www.accountant.nl/siteassets/accountant.nl/in-het-publiek-belang/sectoranalyse_drivers_controlekwaliteit_november_2017.pdf" ext-link-type="uri" xlink:type="simple">https://www.accountant.nl/siteassets/accountant.nl/in-het-publiek-belang/sectoranalyse_drivers_controlekwaliteit_november_2017.pdf</ext-link></mixed-citation>
      </ref>
      <ref id="B17">
        <mixed-citation xlink:type="simple">NBA [Koninklijke Nederlandse Beroepsorganisatie van Accountants] (<year>2019</year>) Rapport oorzakenanalyse OOB accountantsorganisaties. <ext-link xlink:href="https://www.nba.nl/siteassets/tools-en-ondersteuning/publicaties/2019/nba-sgpb_oorzaakanalyse-jun19-04.pdf" ext-link-type="uri" xlink:type="simple">https://www.nba.nl/siteassets/tools-en-ondersteuning/publicaties/2019/nba-sgpb_oorzaakanalyse-jun19-04.pdf</ext-link></mixed-citation>
      </ref>
      <ref id="B18">
        <mixed-citation xlink:type="simple">PCAOB [Public Company Accounting Oversight Board] (<year>2024</year>) Spotlight. Root cause analysis – An effective practice to drive audit quality. <ext-link xlink:href="https://assets.pcaobus.org/pcaob-dev/docs/default-source/documents/root-cause-spotlight.pdf" ext-link-type="uri" xlink:type="simple">https://assets.pcaobus.org/pcaob-dev/docs/default-source/documents/root-cause-spotlight.pdf</ext-link></mixed-citation>
      </ref>
      <ref id="B19">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Peerally</surname><given-names>MF</given-names></name><name name-style="western"><surname>Carr</surname><given-names>S</given-names></name><name name-style="western"><surname>Waring</surname><given-names>J</given-names></name><name name-style="western"><surname>Dixon-Woods</surname><given-names>M</given-names></name></person-group> (<year>2016</year>) <article-title>The problem with root cause analysis.</article-title><source>BMJ Quality and Safety</source><volume>26</volume>(<issue>5</issue>): <fpage>417</fpage>–<lpage>422</lpage>. <ext-link xlink:href="10.1136/bmjqs-2016-005511" ext-link-type="doi" xlink:type="simple">https://doi.org/10.1136/bmjqs-2016-005511</ext-link></mixed-citation>
      </ref>
      <ref id="B20">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Percarpio</surname><given-names>KB</given-names></name><name name-style="western"><surname>Watts</surname><given-names>BV</given-names></name><name name-style="western"><surname>Weeks</surname><given-names>WB</given-names></name></person-group> (<year>2008</year>) The effectiveness of root cause analysis: What does the literature tell us? Joint Commission Journal on Quality and Patient Safety 34(7): 391–398. <ext-link xlink:href="10.1016/S1553-7250(08)34049-5" ext-link-type="doi" xlink:type="simple">https://doi.org/10.1016/S1553-7250(08)34049-5</ext-link></mixed-citation>
      </ref>
      <ref id="B21">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Runciman</surname><given-names>W</given-names></name><name name-style="western"><surname>Hibbert</surname><given-names>P</given-names></name><name name-style="western"><surname>Thomson</surname><given-names>R</given-names></name><name name-style="western"><surname>Van Der Schaaf</surname><given-names>T</given-names></name><name name-style="western"><surname>Sherman</surname><given-names>H</given-names></name><name name-style="western"><surname>Lewalle</surname><given-names>P</given-names></name></person-group> (<year>2009</year>) <article-title>Towards an international classification for patient safety: key concepts and terms.</article-title><source>International Journal for Quality in Health Care</source><volume>21</volume>(<issue>1</issue>): <fpage>18</fpage>–<lpage>26</lpage>. <ext-link xlink:href="10.1093/intqhc/mzn057" ext-link-type="doi" xlink:type="simple">https://doi.org/10.1093/intqhc/mzn057</ext-link></mixed-citation>
      </ref>
      <ref id="B22">
        <mixed-citation xlink:type="simple"><person-group><name name-style="western"><surname>Wu</surname><given-names>AW</given-names></name><name name-style="western"><surname>Lipshutz</surname><given-names>AKM</given-names></name><name name-style="western"><surname>Pronovost</surname><given-names>PJ</given-names></name></person-group> (<year>2008</year>) <article-title>Effectiveness and efficiency of root cause analysis in medicine.</article-title><source>JAMA - Journal of the American Medical Association</source><volume>299</volume>(<issue>6</issue>): <fpage>685</fpage>–<lpage>687</lpage>. <ext-link xlink:href="10.1001/jama.299.6.685" ext-link-type="doi" xlink:type="simple">https://doi.org/10.1001/jama.299.6.685</ext-link></mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>
