> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adopt.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Reviewing and approving work
> The heart of your day in Adopt — the review queue, how to check prepared work, and how to approve it or send it back.
Every agent output waits for a person before it's final, and that person is you. If you do one thing in Adopt each day, it's clearing your review queue — this page is how.
## The review queue
Your review queue lists everything waiting on you, each item marked **action needed**. It's the first place to look when you sit down. Each row tells you, at a glance:
* **which client and task** it's for (e.g. *Revenue Flux Reports · XYZ Corp*),
* **what was prepared** and how much needs you (e.g. *"2 exceptions awaiting Controller decision"*),
* **how long it's been waiting** — so nothing quietly ages past its deadline.
An item sits in the queue for one engagement (one process for one client), and only reviewers assigned to that engagement see it. If you review R\&D for a client but not their transfer pricing, you'll only ever see the R\&D items.
## Opening an item
Open an item and you land in the workspace for that run: the client's **files** on the left, the **conversation** in the middle where the agent narrates what it did, and a live **Workflow** panel on the right showing every step of the run and exactly where it paused for you.
The agent doesn't just hand you an answer — it shows its work and **cites its sources**. Because every figure traces back to the document it came from, you can check a number the way you'd check a junior preparer's: open the source, confirm it supports the output.
## A worked example: a flux review
Say the **Revenue Flux Reports** agent has run for a client. The Workflow panel shows the steps it completed — *Confirm period → Pull GL + budget → Run variance engine → Drill material lines* — all marked **Done**, with *Resolve exceptions* marked **Review** and *Draft commentary*, *Build workbook*, and *CFO sign-off* still **Pending**. The run has stopped at a gate and is waiting on you.
The agent explains what it found in plain language, then opens a **Controller exceptions gate** with an **"Action needed"** card. For example, *Exception 1 of 2 — Data Costs (5100): Unknown Vendor*:
| Field | Value |
| ------------------------ | -------------------------------------------- |
| **Account** | 5100 — Data Costs |
| **Vendor** | Acme Data Partners LLC |
| **Amount** | \$45,000 |
| **Date** | 2026-05-14 |
| **Agent classification** | Unknown driver — owner confirmation required |
| **Confidence** | Low |
You pick an action (confirm the classification, recode it, or send it back), and only once you've cleared the exceptions does the agent move on to draft the commentary and build the workbook. Nothing downstream happens until you decide.
## Your two decisions
* **Approve** — the work is correct. It becomes final and can be shared or promoted. Your approval is recorded with your name and the time.
* **Send back** — something's off. Add notes describing what needs to change, and the work returns for correction. Nothing is shared until it comes back and you approve it.
"Approve" is a professional sign-off, not a formality. It's what makes the output final and is recorded in the audit trail — treat it with the same weight you'd give signing the workpaper yourself.
## Why your approval matters
Every approval is recorded — who approved, and when — as part of an auditable trail. That record is exactly what lets Adopt be used for regulated finance work: there's always a named person standing behind each final output. See [Human-in-the-loop review](/core-concepts/human-in-the-loop) for how the gate works underneath.
## Tips
Work the queue oldest-first so nothing breaches a deadline, and set up [notifications](/end-user-guide/notifications) so items come to you instead of you checking all day. If an item cites a file that looks wrong or out of date, that's usually a files issue — see [Working with clients and files](/end-user-guide/clients-and-files).
## Next steps
1. [Human-in-the-loop review](/core-concepts/human-in-the-loop) — the concept behind the gate
2. [Notifications](/end-user-guide/notifications) — get pinged the moment something needs you
3. [Your dashboard](/end-user-guide/your-dashboard) — the wider view of your work