> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidparts/manufacturing-guide/work-a-step.md).

# Work a step

![Shop-floor step lifecycle](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-a3a3f9a9679dfdc0b7034384f26447cde5f87c73%2F05-step-lifecycle.png?alt=media)

## Start, done, Undo

1. **Start (station)**, for example **Start Debur**, when you pick the part up.

   ![A work card waiting at Debur, with Start Debur](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-9057db88f02981f034a6fd8eff4cd2ecde6f09be%2Fwork-card-start.jpg?alt=media)
2. Your name and a timer show on the route. When the work is finished, tap **(Station) done**, for example **Debur done**.

   ![The same card in progress, with Debur done](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-910686711dd18c609b0f3116c777cc1ac3477b31%2Fwork-card-in-progress.jpg?alt=media)
3. The MO leaves your queue and appears in the next station's. Pressed done by mistake? Tap **Undo** on the message that pops up.

   ![After Debur done: the MO is Waiting QC, and the message offers Undo](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-8841bce6fbb85a86e12d5a976e1319954da86bd6%2Fwork-card-undo.jpg?alt=media)

At QA the done button reads **QA pass**. See [QA](/raidparts/manufacturing-guide/qa.md).

## Rules of the floor

RAIDParts enforces these, so you'll see a message if one blocks you.

* **Order of steps.** A step can't start until the earlier steps are complete. CAM and Bandsaw can run at the same time.
* **Take over.** Starting a step someone else has in progress asks you to confirm, then puts your name on it. Finishing someone else's step also asks first.
* **Undo limits.** You can only reopen a step while nothing after it has started.
* **On hold means stop.** A held MO can't be started, marked done or failed at QA. See [Holds and cancels](/raidparts/manufacturing-guide/holds-and-cancels.md).

Admins can override the order of steps and reopen any step, so ask one if you're stuck.

## Status

| Step status | Meaning                      |
| ----------- | ---------------------------- |
| Pending     | Waiting in the station queue |
| In progress | Someone has started it       |
| Complete    | Done                         |

| MO status  | Meaning                               |
| ---------- | ------------------------------------- |
| Queued     | No step started yet                   |
| Working    | At least one step has started         |
| Waiting QC | QA is the next step                   |
| Completed  | Every step is complete                |
| Canceled   | Stopped by an admin, kept for records |

Status is worked out from the steps; nobody sets it by hand.


---

# 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.raidrobotics.org/raidparts/manufacturing-guide/work-a-step.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.