> 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-tax-prep/video-walk-through.md).

# Video walk-through

Follow a full data entry run from start to finish, using a sample 2025 individual return. You'll see how Filed syncs with your tax software, reads and flags documents, builds a data entry plan, and sends everything to your software with backups and a PDF on file.

{% embed url="<https://studio.saltfish.ai/demo-share/demo_1790827838659_3dkjjbvob>" %}

## What this video covers

* Starting a data entry run and syncing with your tax software (with an automatic backup)
* How Filed reads documents and what green vs. orange flags mean
* Mapping documents to the right tax software screens
* Reviewing the plan and fixing flagged fields
* Sending forms to your tax software, plus the post-send backup and PDF
* Re-sending later for late documents or corrections
* Checking the finished entries in your tax software


---

# 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-tax-prep/video-walk-through.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.
