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

# Request items

> The atomic unit of evidence collection, and its status lifecycle.

A **Request Item** is a single ask within a period — the smallest unit of evidence collection, e.g. "Upload signed financial statements for FY2025". It's the atomic unit of Clivanta.

Each item carries:

* An explicit, stored **status** (the single source of truth).
* Its **files**, with full version history.
* **Two comment threads** — one client-facing, one firm-internal (with @-mentions).
* An **immutable activity log**.

## Status lifecycle

<Steps>
  <Step title="draft">Created in a draft engagement — invisible to the client.</Step>
  <Step title="requested">The engagement is sent; the item becomes visible and the client is asked for it.</Step>
  <Step title="submitted">The client uploads the required file(s) and marks it submitted, notifying the firm owner.</Step>
  <Step title="accepted / needs revision">The firm accepts (terminal — the document becomes evidence) or requests a revision with a structured reason.</Step>
</Steps>

An item can also be **cancelled** — history is preserved, and it's excluded from client-facing counts.

## What "outstanding" means

"What's still missing" is derived from the stored status, not from whether a file exists:

* **Outstanding** = `requested` or `needs revision`.
* **Satisfied** = `accepted`.
* `cancelled` and `draft` are excluded from client-facing counts.

This is why the client portal, your worklist, reminder selection, and exports always agree — they all read the same audited status.

<Note>
  A review decision applies to the item's *current submission*. Superseded or rejected files are kept as "previous attempts" and never deleted.
</Note>