> 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/qa.md).

# QA

Every route ends at QA. An MO at QA shows **Waiting QC**.

## Pass

1. Open the MO from the QA queue, or scan its label.
2. **Start QA** and inspect the part against its drawing and the 3D model on the card.
3. **QA pass** when it's good.

QA pass completes the MO and marks the design part **manufactured**, so it counts toward [assembly readiness](/raidparts/designer-guide/cots-and-readiness.md).

## Fail and send back

![The QA fail dialog, with Debur picked and a reason filled in](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-1859834174bf28c9cbf2dbefb627dcabc5f5500d%2Fqa-fail-dialog.jpg?alt=media)

1. Tap **QA fail…**.
2. Pick the earlier step that can fix the part. Only steps on this MO's route are listed.
3. Say what's wrong, for example "Burrs left on the inside edge". The reason is saved in the MO notes.
4. Tap **Send back to (station)**.

That step and every step after it go back to **Pending**. The MO reappears in that station's queue, and the card shows **Sent back by QA** with a count of how many times.

![The work card after QA fail: Sent back by QA once, the reason in Notes, and Debur waiting again](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-de2a3befbf429d975ba6c22b3bbfb94c2e6edab4%2Fqa-sent-back.jpg?alt=media)

![QA fail and rework](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-c3ab56d05c7d844e43b94062c6fb17b3b78ce778%2F07-qa-rework.png?alt=media)

## Good to know

* **QA fail…** only shows when the MO is at QA.
* A held MO can't be passed or failed until an admin decides.
* An issue that isn't about this part, like a broken gauge? Use [Problem](/raidparts/manufacturing-guide/problems.md) instead.


---

# 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/qa.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.