> 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/incident-application/creating-and-managing-incidents/execute-root-cause-investigation-and-create-actions/execute-incident-investigation.md).

# Execute Incident Investigation

Conduct and document a delegated investigation.

## Workflow Overview

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

<i class="fa-user">:user:</i> **Performed By:** Assigned Investigator (e.g., Subject Matter Expert, QA Specialist, Process Owner)

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

***

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

The **Incident Investigation** task can be accessed through any of the following:

* The **To Do** module.
* The **Notification Panel** (via the **Notification Bell**).
* The **direct link** provided in the email notification.

***

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

After receiving an investigation request, review the details and perform 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 %}

{% hint style="info" %}

#### Saving Your Work

To save progress without submitting, click **Save** in the top-right corner of the panel.

* The task remains in the **To Do** module for you to revisit and complete later.
  {% endhint %}

***

{% stepper %}
{% step %}

### Perform Investigation

Use the available fields to document your investigation activities:

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

* **Provide Investigation Related File(s):** Upload any supporting documentation or evidence related to the investigation.
* **What Is Your Investigation Result?:** Document the outcome of your investigation, including observations, findings, identified issues, contributing factors, and any relevant recommendations.

***

{% endstep %}

{% step %}

### Submit Investigation

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

{% hint style="info" %}

#### What Happens Next

Once submitted, any related files will be automatically integrated into the [**Execute RCA Investigation and Create Action(s)**](/interfacing-help-files/quality-managers/incident-application/creating-and-managing-incidents/execute-root-cause-investigation-and-create-actions.md) form, populating the **RCA File(s)** attachment field.

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

Additionally, an overview of the investigation exchange is presented in the **Requested Investigation** grid.

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

***

{% 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/incident-application/creating-and-managing-incidents/execute-root-cause-investigation-and-create-actions/execute-incident-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.