> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/quality-managers/action-item-application/creating-and-managing-scars/execute-scar-investigation.md).

# Execute SCAR Investigation

Investigate the reported supplier issue, document root cause findings, and submit the SCAR for review.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Execute SCAR Investigation

<i class="fa-user">:user:</i> **Performed By:** Assigned Supplier Representative

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

***

## Accessing the Task <a href="#accessing-the-task" id="accessing-the-task"></a>

The **Execute SCAR Investigation** task is accessed through the **direct link** provided in the email notification.

***

## Completing the Task <a href="#completing-the-task" id="completing-the-task"></a>

After the SCAR has been initiated, review the issue and complete the investigation.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

{% hint style="success" %}
For guidance on common form features and functions, see [**Working with Forms**](/interfacing-help-files/end-users/exploring-apps/working-with-forms.md).
{% endhint %}

***

{% stepper %}
{% step %}

### Review Issue Assessment

Review the issue assessment provided by the SCAR creator.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

***

{% endstep %}

{% step %}

### Investigate Root Cause

Examine and expand on the root cause investigation.

#### <i class="fa-magnifying-glass">:magnifying-glass:</i> Investigation

Review the initial investigation performed by the SCAR creator and update or expand the findings as necessary.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

* **Problem Statement:** Describe the problem clearly and concisely, including what occurred, where it occurred, and its impact.
* **Detailed Investigation:** Select to perform and document a detailed root cause investigation.
  * If selected, complete the **3 x 5 Why Analysis** section to support identification of the underlying root cause.

<details>

<summary><mark style="color:blue;"><strong>3 x 5 Why Analysis</strong></mark></summary>

The **3 × 5 Why Analysis** applies the 5Ws (**What**, **Where**, **When**, **Who**, **Why**) across three types of causes:

* **Direct Cause**
* **Detection Cause**
* **Systemic Cause**

***

* **Direct Cause**

Use this tab to examine and identify the immediate or specific cause of the problem. This is often the initial factor that directly led to the issue.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

***

* **Detection Cause**

Use this tab to examine the factors that allowed the issue to pass through without detection. This involves understanding how the problem reached the customer or end-user without being intercepted.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

***

* **Systemic Cause**

Use this tab to explore how the broader system, including business processes, contributed to the problem. This involves identifying any systemic failures or weaknesses that may have played a role in the emergence of the issue.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

</details>

* **Root Cause Description:** Provide a detailed explanation of the identified root cause.
* **Root Cause Documents:** Upload supporting root cause analysis documents, investigation reports, or related evidence.
* **Unable to Determine Root Cause:** Select to indicate that a root cause could not be conclusively identified after investigation.

<p align="center">━━━━━━━━━━━━━━━━━━━━━━━━━━━</p>

#### <i class="fa-bullseye">:bullseye:</i> Root Cause Findings

Identify and analyze the underlying factors contributing to the non-conformance.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

* **Direct Cause:** Identify the root cause for the technical problem leading to the non-conformance.
* **Detection Cause:** Examine how the non-conformance escaped detection.
* **Systematic Cause:** Assess how product development, production, and support processes contributed to the problem.

***

{% endstep %}

{% step %}

### Add Comments

Use the **Comments** field to provide additional investigation details, clarification, or supporting information related to the SCAR investigation.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>

***

{% endstep %}

{% step %}

### Submit Investigation

From the **Task Resolution** dropdown, select **Submit**, then click **Submit.**

→ Next Step: [Review SCAR](/interfacing-help-files/quality-managers/action-item-application/creating-and-managing-scars/review-scar.md)

***

{% endstep %}
{% endstepper %}

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://interfacing.gitbook.io/interfacing-help-files/quality-managers/action-item-application/creating-and-managing-scars/execute-scar-investigation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.