> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neudocs.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Statuses

> Reference for request, item, scan, correctness, and evidence states.

## Request statuses

| Status          | Meaning                                                                |
| --------------- | ---------------------------------------------------------------------- |
| **Draft**       | Created but not yet active for client collection.                      |
| **Sent**        | Delivered or made available to the client; no submission recorded yet. |
| **In progress** | The client or staff workflow has started and required work remains.    |
| **Completed**   | Every required item is approved or otherwise validly resolved.         |
| **Cancelled**   | Staff stopped the request before normal completion.                    |

## Item statuses

| Status             | Meaning                                                        |
| ------------------ | -------------------------------------------------------------- |
| **Needed**         | The client still needs to submit a file or answer.             |
| **Uploaded**       | A submission exists and is awaiting or undergoing review.      |
| **Approved**       | Staff accepted the item.                                       |
| **Rejected**       | Staff requires a replacement or corrected answer.              |
| **Not applicable** | The item was marked as not applicable under the request rules. |

## Upload scan statuses

Uploads can be pending, clean, infected, or in an error state. Only safe, available content should enter normal review.

## Correctness statuses

Correctness evaluation can pass, warn, fail, report an error, or mark a format unsupported. The effect depends on the item's [correctness mode](/verification/correctness).

## Evidence anchor states

An exported proof can have no anchor, be pending, confirmed, invalid, or temporarily unreachable. The public verifier derives the result from the bundle and proof instead of trusting a stored label.


## Related topics

- [Document correctness](/verification/correctness.md)
- [Core concepts](/concepts.md)
- [Exports](/workflow/exports.md)