> For the complete documentation index, see [llms.txt](https://docs.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.filed.com/reference/products/ai-review/re-review-workflow.md).

# Re-review workflow

## The loop: fix, re-export, re-review

AI Review is designed to be run more than once on the same client. The typical cycle is:

1. Run AI Review on a draft return and work through the findings in the Leads tab.
2. Correct the issues that need correcting directly in tax software.
3. Produce an updated draft return PDF from tax software.
4. Bring the updated PDF back into AI Review to start a fresh run.
5. Repeat until the findings on the latest run are clear, signed off, or explained.

Each run is independent and produces a complete, fresh set of leadsheets rather than patching the previous run. See [Re-running AI Review](/reference/products/ai-review.md#re-running-ai-review) for what happens to prior runs when a new one starts.

## Getting the updated return back into Filed

There are two ways to bring a revised draft back into AI Review:

* **Upload it directly.** Start a new run from the client's AI Review page and drop the updated PDF into Step 1, the same flow used for the first run. See [Running AI Review](/reference/products/ai-review.md#running-ai-review).
* **Print it in with Filed Printer.** If [Filed Printer](/reference/plugins/filed-printer.md) is set up, printing the revised return from tax software sends it straight into the client's workspace - Filed matches it to the client automatically from the SSN on a 1040. The printed file lands under the client's AI Review, where **Create Review** starts the run.

Either path produces the same result: a new AI Review run compared against the current state of the binder.

## The final leadsheet set is the work paper

Once the findings on the latest run are cleared, sign off the leadsheets - by row or by whole sheet, using the same [sign-off levels](/reference/products/ai-review/sign-off-levels.md) as the rest of the Binder - and export them. See [Downloading signed-off lead sheets as work papers](/reference/products/ai-review/downloading-work-papers.md) for the full walkthrough; the exported leadsheets are the signed-off work paper for the engagement.

## Sign-off carries across runs

A leadsheet sign-off is scoped to the run it was placed on. Because a new run produces a fresh set of leadsheets, previously signed-off findings are not automatically carried forward onto the new run - each new run's leadsheets reflect the current state of the return and need their own sign-off pass.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.filed.com/reference/products/ai-review/re-review-workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.