> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/reviewing_a_case/case_status/how-to-update-a-case-status.md).

# How to update a case status

You can update the case status either from the individual case page or from the **Cases table**.

**Finalized** case status can be applied only from the individual case page to prevent unintended [case completion](/emedgene/emedgene-analyze-manual/case-completion-and-reporting.md).

## On the [individual case page](/emedgene/emedgene-analyze-manual/reviewing_a_case/individual_case_page.md)

{% stepper %}
{% step %}
Open the case page.
{% endstep %}

{% step %}
In the page header, select the dropdown (<i class="fa-chevron-down">:chevron-down:</i>) icon next to the current case status.
{% endstep %}

{% step %}
Select the new status you want to apply.
{% endstep %}
{% endstepper %}

<figure><img src="https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-5b3650ef877641776a3a2aeb1fef51c508266fc0%2F1.%20How%20to%20update%20a%20case%20status_On%20the%20Individual%20case%20page%20VL.gif?alt=media" alt=""><figcaption></figcaption></figure>

***

## In the [Cases table](/emedgene/emedgene-analyze-manual/getting_around_the_platform/cases_tab/cases_table.md)

{% stepper %}
{% step %}
Open the **Cases** **tab**.
{% endstep %}

{% step %}
In the **Cases table**, locate the relevant case row and select the case status.
{% endstep %}

{% step %}
From the dropdown menu, select the new status.
{% endstep %}
{% endstepper %}

![](https://1131024994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGCW0DnLlE7QjoZPNmKIi%2Fuploads%2Fgit-blob-61c2f915855404ac8624d24c9b7c48be6430872d%2Fcase_status_5_case_status_change_2_23.gif?alt=media)

## Learn more

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Case status</strong></td><td>Overview of case status behavior, history, and related workflows.</td><td><i class="fa-up-right-from-square">:up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/reviewing_a_case/case_status.md">Learn more</a></td></tr><tr><td><strong>Case statuses in a case lifecycle</strong></td><td>Review status transitions, control types, and the reference status list.</td><td><i class="fa-up-right-from-square">:up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/reviewing_a_case/case_status/out-of-the-box-case-statuses.md">Learn more</a></td></tr><tr><td><strong>Case progress indicator (v100.40.0+)</strong></td><td>Understand progress indicator states for cases in processing or failure states.</td><td><i class="fa-up-right-from-square">:up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/reviewing_a_case/case_status/case-progress-indicator-v100.40.0+.md">Learn more</a></td></tr><tr><td><strong>Case status management</strong></td><td>Create custom statuses and reorder them for your organization.</td><td><i class="fa-up-right-from-square">:up-right-from-square:</i> <a href="/emedgene/emedgene-analyze-manual/settings/management/test-statuses.md">Learn more</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.bioinsight.illumina.com/emedgene/emedgene-analyze-manual/reviewing_a_case/case_status/how-to-update-a-case-status.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.