> 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/managing-testing/test-evidence-management.md).
# Test Evidence Management
Create and manage evidence used to support audit testing.
Use the **Test Evidence Management** module to create, view, and manage evidence records that support the execution and validation of audit tests.
IMAGE
***
## Working with Evidence
Follow the steps below to locate, review, and manage evidence efficiently.
{% stepper %}
{% step %}
### Filtering Evidence
Use the **Search Panel** to filter the evidence shown in the grid. You can filter by:
* **Evidence ID:** Enter the unique identifier for the evidence.
* **Evidence Name:** Enter the full or partial name of the evidence.
{% 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 evidence.
{% endhint %}
***
{% endstep %}
{% step %}
### Managing Evidence
Use the action buttons in the grid to manage evidence:
* **Add**: Click to create a new evidence record.
Create Evidence
The **Create Evidence** form allows you to define and configure the required evidence for tests.
IMAGE
1. **Define Details**
Complete the relevant fields to configure the evidence:
* **Evidence Name:** Enter a brief, descriptive title for the evidence.
* **Sample Size:** Enter the number of items or instances to be tested.
* **Population:** Enter the total number of items within the population from which the sample is drawn.
* **Test Method(s):** Select one or more methods used to evaluate the evidence
* **Frequency:** Select how often the evidence should be collected or reviewed.
* **Prerequisites:** Specify any conditions or requirements that must be met before the evidence can be collected.
* **Procedure:** Provide step-by-step instructions for collecting and evaluating the evidence.
━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Read-Only Fields** (🔒)
* **Evidence 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 record and open a new form to add another.
* **Save and Close:** Click to save the record and close the form.
* **Delete** ( :trash-can: ): Click to remove an evidence record.
{% 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 evidence record.
* **View** (  ): Click to open an evidence record in read-only mode.
***
{% endstep %}
{% endstepper %}
***
## See Also
---
# 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/managing-testing/test-evidence-management.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.
