> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/core-concepts/workflow/start.md).
# Start
*Start* is the point from which all tasks start.
When new assets are uploaded, depending on your settings for the *Start* stage, tasks are either held in *Start* (e.g., if you wish to pre-label them before sending them to a labeling task), or are immediately sent to the stage plugged into the output of *Start*.
The *Start* stage will show you a number of statistics related to your project, such as how many tasks are in your project and how many have and have not reached the *Complete* stage.
#### Settings
**Auto Forward on Upload** (default: on): When Auto Forward is toggled on, whenever new tasks are created, e.g. by uploading new assets, they are immediately sent to the stage connected to the output of *Start.* They are not held in start. By toggling it off, tasks will stay in the *Start* stage until you re-queue them to another stage.
{% hint style="warning" %}
If you have tasks (e.g. Task 1, Task 2, and Task 3) in the Start stage, then turn on Auto Forward, then upload more assets (Task 4, Task 5), **all** tasks in the Start stage will be forwarded to the next stage, including Task 1, 2, and 3, even though they were uploaded when Auto Forward was off.
{% endhint %}
**Manual Forward**: Clicking on *Next Stage* will send all tasks currently in the *Start* stage to the stage connected to the output of *Start*. If you wish to only forward tasks from a certain stage, you may do so by clicking on the search bar next to the button and by picking the stage(s) to forward from the dropdown. You may type to quickly search for batches.
---
# 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.imerit.net/core-concepts/workflow/start.md?ask=&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.
