> 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/downloading-work-papers.md).

# Downloading work papers

## The deliverable is the exported leadsheet set

Once a review's findings are cleared and signed off, the leadsheets themselves - not a separate report - are the work paper for the engagement. Exporting them produces a record of what was checked, what was found, and who signed off on each item, in a format that can be filed, archived, or handed to whoever needs it outside of Filed.

## Sign off before exporting

Export what you actually want to stand as the completed record: sign off each row or the whole leadsheet first, using the L1-L3 model described in [Sign-off levels](https://docs.filed.com/reference/products/ai-review/sign-off-levels.md). See [Signing off on leadsheets](https://docs.filed.com/reference/products/binder/leadsheets.md#signing-off-on-leadsheets) for the walkthrough.

## Exporting

**Walkthrough: export the signed-off leadsheets**

1. Open the Download dialog from the Docs panel's **⋯** menu and choose **Download workpaper**.
2. Make sure **Leadsheets** is checked, and use the format selector to choose **Excel** or **CSV**.
3. Click **Download** to generate the export.

See [Exporting leadsheets](https://docs.filed.com/reference/products/binder/leadsheets.md#exporting-leadsheets) for the full walkthrough and screenshot.

## Choosing Excel vs. CSV

Both formats contain the same underlying leadsheet data. Excel is generally easier to review or annotate further outside Filed; CSV is a better fit for feeding the data into another system or spreadsheet-based process. Pick whichever the downstream use calls for.

## This fits into the broader re-review loop

Exporting is usually the last step after a round of fixes and a fresh review - see [Re-review workflow](https://docs.filed.com/reference/products/ai-review/re-review-workflow.md) for the full fix-in-tax-software, re-export, re-review cycle this export typically sits at the end of.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.filed.com/reference/products/ai-review/downloading-work-papers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
