> 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/auditors/managing-internal-audits-apps/tracking-and-monitoring-audits/manage-audit-findings.md).
# Manage Audit Findings
Use the **Manage Audit Findings** module to create, review, and maintain audit findings.
IMAGE
***
## Working with Audit Findings
Follow the steps below to locate, review, and manage audit findings efficiently.
{% stepper %}
{% step %}
### Filtering Audit Findings
Use the **Search Panel** to filter the audit findings shown in the grid. You can filter by:
* **Type of Finding:** Select the finding type.
* **Creation Date:** Select the date when the finding was created.
{% hint style="info" %}
#### Actions:
* **Filter:** Click to apply your criteria and update the grid with matching results.
* **Clear Filter:** Click to remove all filters and restore the full list of findings.
{% endhint %}
***
{% endstep %}
{% step %}
### Managing Audit Findings
Use the action buttons in the grid to manage audit findings:
* **Add**: Click to create a new audit finding.
Enter New Finding
The **Enter New Finding** form allows you to define and document new findings.
IMAGE
1. **Define Details**
Complete the relevant fields to configure the finding:
* **Type:\*** Select the finding type (e.g., Minor Observation, Major Observation, Non-Conformity).
* **Notes:\*** Provide a clear and detailed description, including context and supporting evidence.
━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Read-Only Fields** (🔒)
* **Finding ID:** A system-generated, unique identifier used for tracking and reference.
***
2. **Save Changes**
When ready to save, choose one of the following options:
* **Save and New**: Click to save the finding and open a new form to create another.
* **Save and Close**: Click to save the finding and close the form.
* **Delete** ( :trash-can: ): Click to remove an audit finding.
{% hint style="info" %}
Confirm deletion by clicking **Save Changes** or clicking outside the grid. To cancel, click **Discard Changes** or **Undo** ( :rotate-left: ).
{% endhint %}
* **Edit** ( :pen: ): Click to modify an audit finding.
* **View** (  ): Click to open an audit finding in read-only mode.
{% hint style="success" icon="lightbulb" %}
**Tip:** To quickly review the full description and details of a finding, click the **Expand** ( :up-right-and-down-left-from-center: ) icon inside the cells of the **Notes** column.
{% 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/auditors/managing-internal-audits-apps/tracking-and-monitoring-audits/manage-audit-findings.md?ask=&goal=
```
`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.