> 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/planning-and-executing-audits/evaluate-requirements.md).

# Evaluate Requirements

Review assigned requirements, document evidence and findings, and submit completed audit results.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Evaluate Requirements

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

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

{% hint style="info" %}
In this context, 'assigned auditors' includes both the Lead Auditor and any auditors designated to specific requirements.
{% endhint %}

***

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

The **Evaluate Requirements** 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

Once the audit schedule is confirmed and the scheduled start date or time have been reached, proceed with evaluating your assigned requirements.

<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.&#x20;

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

***

{% stepper %}
{% step %}

### Verify Assigned Requirements

To validate a requirement:

* Double-click the requirement, or
* Click **Edit** ( <i class="fa-pen">:pen:</i> )

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

<details>

<summary><mark style="color:blue;"><strong>Validate Requirement</strong></mark></summary>

The **Validate Requirement** form allows you to assess and confirm compliance with a specific requirement.

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

***

<i class="fa-thumbtack-angle">:thumbtack-angle:</i> **Checklist**

Use this section to complete any checklist associated with the requirement.

{% hint style="danger" %}
The **Checklist** section appears only if a checklist has been assigned.
{% endhint %}

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

To update a checklist item:

* Click the **Edit** ( <i class="fa-pen">:pen:</i> ) icon next to the item or double-click the item.
* Enter the required information in the window that opens
* Use the navigation buttons as needed:

  * **Previous:** Click to save and navigate to the previous item.
  * **Save and Close:** Click to save and close the window.
  * **Next:** Click to save and navigate to the next item.

  <div data-gb-custom-block data-tag="hint" data-style="danger" class="hint hint-danger"><p>The <strong>Previous</strong> and <strong>Next</strong> buttons are unavailable on the first and last items, respectively.</p></div>

{% hint style="warning" %}
To mark the requirement as complete, all checklist items must be fully addressed.
{% endhint %}

***

<i class="fa-thumbtack-angle">:thumbtack-angle:</i> **Evidence**

Use this section to review, add, and manage evidence for requirement validation.

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

1. **Review Evidence from Collectors**

If available, expand this sub-section to review and evaluate evidence collected for tests linked to the requirement.

{% hint style="danger" %}

#### Section Availability

The **Evidence from Collectors** section appears only when:

* The requirement is included in testing, meeting the following conditions:
  * It was configured to undergo testing (**Requires Testing?** selected).
  * It is linked to one or more tests
  * At least one linked test has associated evidence
* All [collected](/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/collect-evidence.md) evidence has been [reviewed and approved](/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/review-evidence.md).
  {% endhint %}

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

To individually review collected evidence:

* Click **View** ( ![](https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FIAlpvjgSBR3lKZjwsXm7%2FIMS-KI-L-9.svg?alt=media\&token=262f3701-b544-43fe-b1bc-d17a29a18e55) ) next to the relevant evidence record.
  * In the form that appears, you can access samples from each collection round for the selected evidence, including details from the evidence result description, as well as any attached files or links.

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

To schedule an additional (third) round of evidence collection:

* Configure the schedule:
  * **Select Evidence:** Select the relevant evidence record(s).
  * **Round Start:** Select the start date for the third round.
  * **Round End:** Select the end date for the third round.
  * **Set 3rd Round Dates:** Click to apply the schedule.
    * The selected dates will populate the **Test Evidence** grid.
* Click **Save and Close** at the bottom of the **Validate Requirement** form.
  * The third round will be triggered on the specified start date.

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

2. **Add and Document Evidence**

To add and document evidence for a requirement, you can use any of the following methods:

* **Description**
  * **Evidence Summary:** Provide a clear description of the evidence and its outcome.
* **Files**
  * **Upload Supporting Files:** Upload supporting files as needed.

{% hint style="info" %}
Uploaded files are automatically recorded in the **Evidence Repository** grid.
{% endhint %}

* **Links**
  * **Evidence Link:** Enter the web address of the resource.
    * Expected Format: `http://example.com`
  * **Link Name:** Enter a user-friendly name.
    * If left blank, the URL is used as the display name.
  * **Add Evidence Link:** Click to add the link.
    * As links are added, they populate the below grid.

      * To remove a link, select the corresponding **Delete** ( <i class="fa-trash-can">:trash-can:</i> ) icon.

      <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Confirm deletion by clicking <strong>Save Changes</strong> or clicking outside the grid. To cancel, click <strong>Discard Changes</strong> or <strong>Undo</strong> ( <i class="fa-rotate-left">:rotate-left:</i> ).</p></div>

{% hint style="info" %}
Added links are also recorded in the **Evidence Repository** grid.
{% endhint %}

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

3. **Request Additional Evidence (Optional)**

To request specific evidence for requirement validation:

* Click **Request Specific Evidence**.
* In the section that appears, select a recipient and specify the required evidence.
* Click **Send Request** to submit.

{% hint style="info" %}
If you change your mind before submitting, click **Cancel** to withdraw the request.
{% endhint %}

{% hint style="info" %}
All requests are recorded in the **Evidence Repository** grid. When the assigned party submits evidence, the corresponding entry is updated with the provided files or links, along with any accompanying message.
{% endhint %}

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

The **Evidence Repository** grid provides a comprehensive overview of the evidence handling process. It logs all auditor actions related to evidence, such as uploading, requesting, and receiving evidence, including URLs.

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

***

<i class="fa-thumbtack-angle">:thumbtack-angle:</i> **Observations**

Use this section to record observations or findings related to the requirement.

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

To add an observation:

* Click **Add**.
* Complete the form:
  * **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.
* Choose one of the following:
  * **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.

{% hint style="info" %}
Any observations added here will also populate the **Observations** grid in the **Evaluate Requirement** form.

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

* To view an observation, click the corresponding **View** ( ![](https://1488562728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTx7AmE0d2Q4ja20EYjF5%2Fuploads%2FIAlpvjgSBR3lKZjwsXm7%2FIMS-KI-L-9.svg?alt=media\&token=262f3701-b544-43fe-b1bc-d17a29a18e55) ) icon.
* To access the full contents of the notes associated with an observation, click the corresponding **Expand** ( <i class="fa-up-right-and-down-left-from-center">:up-right-and-down-left-from-center:</i> ) icon
  {% endhint %}

Added entries appear in the grid with the following options:

* **Edit** ( <i class="fa-pen">:pen:</i> )**:** Click to modify an observation.
* **Delete** ( <i class="fa-trash-can">:trash-can:</i> ): Click to remove an observation.

{% hint style="info" %}
Confirm deletion by clicking **Save Changes** or clicking outside the grid. To cancel, click **Discard Changes** or **Undo** ( <i class="fa-rotate-left">:rotate-left:</i> ).
{% endhint %}

***

<i class="fa-thumbtack-angle">:thumbtack-angle:</i> **Audit Findings**

If preferred, you can record findings directly in the provided text field.

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

***

<i class="fa-square-check">:square-check:</i> **Complete Requirement**

Select **This Requirement is Completed** to mark the requirement as complete.

***

<i class="fa-circle-chevron-right">:circle-chevron-right:</i> **Save Changes**

Click **Save and Close** to save your updates and exit the form.

</details>

{% hint style="info" %}

#### Bulk Requirement Verification

To verify and complete all requirements, select the **Mark All Requirements as Verified** checkbo&#x78;**.**

* This automatically selects the **Requirement Completed** checkbox for each requirement

If a requirement has an associated checklist that remains incomplete, it will be excluded from this action.
{% endhint %}

***

{% endstep %}

{% step %}

### Add Comments (Optional)

Use the **General Comments** field to document observations, findings, or any relevant notes related to the audit.

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

{% hint style="info" %}
Your comments will be visible to the audit manager in the [**Review & Approve Audit Results**](/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/review-and-approve-audit-results.md) form.
{% endhint %}

***

{% endstep %}

{% step %}

### Finalize Evaluation

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

{% hint style="danger" %}

#### Submission Requirements

You will not be able to submit results until all assigned requirements, including any associated checklists, are completed.

If evidence collection is still in progress when you attempt to submit, you will be prompted to confirm submission.

* Confirming will automatically close any tasks assigned to evidence collectors and remove them from the **To Do** module.
  {% endhint %}

→ Next Step: [Review & Approve Audit Results](/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/review-and-approve-audit-results.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 Audits</strong></td><td>Monitor the status and progress of audits using lists and dashboards.</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/auditors/managing-internal-audits-apps/tracking-and-monitoring-audits.md">Tracking &amp; Monitoring Audits</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/auditors/managing-internal-audits-apps/planning-and-executing-audits/evaluate-requirements.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.