> 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/create-new-scar.md).

# Create New SCAR

Create and submit a new SCAR to initiate the SCAR Management workflow.

## Workflow Overview

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

<i class="fa-user">:user:</i>  **Performed By:** SCAR Creator (e.g., Quality Manager, Procurement Manager, Operations Manager)

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

***

## Completing the Form

Use the **New SCAR** form to document and initiate a Supplier Corrective Action Request (SCAR).

<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 %}

### Enter Basic Information

Complete the required fields to define the issue, affected supplier, and response expectations.

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

* **Initiation Date:** Verify the date the SCAR was initiated.

{% hint style="info" %}
This field defaults to the current date; modify it if the SCAR is being entered retroactively.
{% endhint %}

* **Response Due Date:** Select the date by which the supplier must provide a response.
* **Supplier:** Select the supplier associated with the issue.

{% hint style="warning" %}
When a supplier is selected, the following read-only fields are automatically populated with available information.

* **Supplier ID:** The unique identifier assigned to the selected supplier.

* **Supplier Representative Name:** The name of the representative associated with the supplier.

* **Supplier’s Phone:** The phone number of the supplier’s representative.

* **Supplier’s Email:** The email address of the supplier’s representative.
  {% endhint %}

* **Issue Description:** Provide a detailed description of the issue, including affected products, quantities, dates, locations, and any observed nonconformances.

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

**Read-Only Fields** (🔒)

* **SCAR ID:** A system-generated, unique identifier used for tracking and reference.

{% hint style="warning" %}
This ID is assigned upon submission.

<p align="center"><kbd><strong>IMAGE</strong></kbd></p>
{% endhint %}

***

{% endstep %}

{% step %}

### Perform Initial Assessment

Perform an assessment of the identified issue.

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

* **Unconfirmed / Test OK (Fault Not Found):** Select to indicate that testing or evaluation did not confirm the reported issue.
  * If selected, use the designated field to provide an explanation for your assessment, including any relevant pictures or test reports.
* **Customer-Caused:** Select to indicate that the issue was determined to be caused by customer handling, use, or process conditions.
  * If selected, use the designated field to provide an explanation for your assessment, including any relevant pictures or test reports.
* **Validated Supplier Responsibility:** Select to confirm that the supplier has been determined to be responsible for the identified issue.
* **Attach Any Relevant Documents:** Upload supporting documents such as inspection reports, photos, test results, or customer complaints.

***

{% endstep %}

{% step %}

### Identify Root Cause

Conduct and document a root cause analysis for the identified issue.

* **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.

***

{% endstep %}

{% step %}

### Submit SCAR

Click **Submit** to enter the SCAR into the **SCAR Management** workflow, routing it to the designated supplier representative for [investigation](/interfacing-help-files/quality-managers/action-item-application/creating-and-managing-scars/execute-scar-investigation.md).

***

{% endstep %}
{% endstepper %}

***

## See Also

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Tracking &#x26; Monitoring SCARs</strong></td><td>Browse and filter all submitted SCARs across the organization.</td><td><a href="https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FNZOvD3ldHJ3i1zsvDksS%2FCR-V16-Icons-1.png?alt=media&amp;token=7c420cc4-9abf-4601-8fc3-8e9769771b27">App-V16-Icons-1.png</a></td><td><a href="/interfacing-help-files/quality-managers/action-item-application/tracking-and-monitoring-scars.md">Tracking &amp; Monitoring SCARs</a></td></tr></tbody></table>


---

# 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/create-new-scar.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.