> For the complete documentation index, see [llms.txt](https://kb.bravegen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bravegen.com/carbon/core-concepts/data-collection/tasks/quarantine.md).

# Quarantine

Review and approve task data before it is included in emissions reporting.

BraveGen tasks can be placed in a *Quarantine* state, allowing the **Data Approver** to manually review and approve the collected data before it is included in emission reporting.

When a task reaches quarantine a user can choose to dispute the task by clicking the 'dispute' button on the top right, which will prompt the user for a reason. This will be emailed to the **Data Supplier** and the task will be moved back into the awaiting data state.

Whether a task enters quarantine is determined by the quarantine setting on it's parent [process](/carbon/core-concepts/data-collection/processes.md).

### Task Quarantine Options

#### Quarantine: Always

All tasks will move to a quarantine state once data has been entered

#### Quarantine: Never

All tasks will skip the quarantine state and automatically be included in emissions reporting

#### Quarantine: Collisions Only

Tasks will be quarantined if they contain data which would collide with an existing data set. Tasks not deemed in collision will be automatically approved and included in emissions reporting. See [Resolving Collisions](/carbon/core-concepts/data-collection/tasks/resolving-collisions.md) for more information on what determines a collision.

#### Quarantine: Outside Threshold (coming soon)

~~<mark style="background-color:$info;">Set a threshold % increase or decrease on the seasonal average which will trigger the task to enter quarantine. Note: Quarantine will not be triggered for the first year of data, while the seasonal average is established.</mark>~~

### FAQ

<details>

<summary>Can I update the quarantine option on a single task?</summary>

No. This can only be set on the parent process

</details>
