> 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/assign-collector-s.md).

# Assign Collector(s)

Assign or update evidence collectors and collection dates for each round.

## Workflow Overview

<i class="fa-location-dot">:location-dot:</i> **Current Task:** Assign Collector(s)

<i class="fa-user">:user:</i> **Performed By:** Assigned Lead Evidence Collector

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

***

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

The **Assign Collector(s)** 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.

{% hint style="danger" %}

#### Task Availability

The **Assign Collector(s)** task is generated only if at least one audit requirement is included in testing.

* A requirement is included only if **all** of the following conditions are met:
  * 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
* If any condition is not met, the task is skipped.
  {% endhint %}

***

## Completing the Task

After receiving notification, review the current assignments and collection schedule (if defined). Then assign or update collectors and set or revise collection dates as needed.

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

### Review Audit Context

Before proceeding, review the audit details to familiarize yourself with the overall setup, including:

* Audit schedule
* Assigned participants
* Evidence collectors
* Collection dates for each round

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

***

{% endstep %}

{% step %}

### Manage Evidence Collectors & Collection Schedule

Assign or update evidence collectors, and define or modify collection dates for each round.

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

#### <i class="fa-user-magnifying-glass">:user-magnifying-glass:</i> Assign Collectors

Use the **Collector** column to assign or update the collector for each record.

{% hint style="info" %}
Click **Save Changes** or click outside the grid to apply updates. To cancel, click **Discard Changes**.
{% endhint %}

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

#### <i class="fa-calendar-range">:calendar-range:</i> Set Collection Dates

You can enter or update collection dates individually or in bulk.

**For individual records:**

* Enter or update dates directly in the grid using the following columns:
  * **Round 1 Start /** **End**
  * **Round 2 Start /** **End**
* Click **Save Changes** or click outside the grid to apply.
  * To cancel, click **Discard Changes**.

**For multiple records:**

* Select one or more records using the **Selected** checkbox.

{% hint style="success" icon="lightbulb" %}
**Tip:** Use **Select All** and **Deselect All** as needed.
{% endhint %}

* Confirm your selection by clicking **Save Changes** or clicking outside the grid.
  * To cancel, click **Discard Changes**.
* Enter dates in the **Round 1** and **Round 2** fields.
* Click **Set Entered Dates** to apply the dates to all selected records.

{% hint style="danger" %}
If both rounds share the same start and end dates, they are assigned as a single task. If the dates differ, however, each round is assigned as a separate task.
{% endhint %}

***

{% endstep %}

{% step %}

### Submit Collectors

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

→ Next Step: [Confirm Schedule](/interfacing-help-files/auditors/managing-internal-audits-apps/planning-and-executing-audits/confirm-schedule.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/assign-collector-s.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.