Skip to main content
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

1

draft

Created in a draft engagement — invisible to the client.
2

requested

The engagement is sent; the item becomes visible and the client is asked for it.
3

submitted

The client uploads the required file(s) and marks it submitted, notifying the firm owner.
4

accepted / needs revision

The firm accepts (terminal — the document becomes evidence) or requests a revision with a structured reason.
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.
A review decision applies to the item’s current submission. Superseded or rejected files are kept as “previous attempts” and never deleted.