> For the complete documentation index, see [llms.txt](https://docs.compliancebot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.compliancebot.io/evidence-tasks/evidence-task-workflow/edit-evidence-task.md).

# Edit Evidence Task

### <mark style="color:orange;">**Editing a Task**</mark>

To modify an existing task in ComplianceBot, update its details such as the title, purpose, description, committee name, Slack channel, schedule, or meeting information.&#x20;

This ensures the task remains aligned with current requirements and priorities.&#x20;

* Navigate to <mark style="color:blue;">**Settings**</mark> and click on <mark style="color:blue;">**Tasks**</mark><mark style="color:blue;">.</mark>
* Click the dropdown arrow next to the task you want to edit.
* Click the <mark style="color:blue;">**Edit Icon**</mark> to modify the <mark style="color:blue;">**Title**</mark><mark style="color:blue;">,</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**Purpose**</mark><mark style="color:blue;">,</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**Description**</mark><mark style="color:blue;">,</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**Committee Name**</mark><mark style="color:blue;">,</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**Slack Channel Name**</mark><mark style="color:blue;">,</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**Schedule**</mark><mark style="color:blue;">, or</mark> <mark style="color:blue;"></mark><mark style="color:blue;">**Upcoming Meeting Details**</mark><mark style="color:blue;">.</mark>
* Make the necessary changes.
* Save the changes.

<figure><img src="/files/7ERfq5vw33SU67Mtf6fL" alt=""><figcaption></figcaption></figure>


---

# 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://docs.compliancebot.io/evidence-tasks/evidence-task-workflow/edit-evidence-task.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.