> For the complete documentation index, see [llms.txt](https://www.ftcwiki.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.ftcwiki.org/how-to-build-competitive-robots/how-to-compete/design-workflow.md).

# Design Workflow

### Design Workflow

One of the most important habits to develop is a CAD-first workflow. Rather than cutting parts and experimenting physically, strong teams model their entire robot in CAD before building anything. This includes not just major systems like drivetrains and lifts, but also fine details like screw clearances, cable routing, and range-of-motion constraints. Designing in CAD allows you to check for part collisions, run mechanical simulations, and iterate quickly without wasting time or materials. Platforms like Onshape are especially popular due to their collaboration features, and built-in hardware libraries.

<div><figure><img src="/files/isb4idKNo07SDL4yiMnw" alt=""><figcaption><p>FTC 23511 Seattle Solvers</p></figcaption></figure> <figure><img src="/files/vXgtMefz3U9XmiYsp70m" alt=""><figcaption><p>Mastersketch to full Robot</p></figcaption></figure></div>

Prototyping is still essential, but it should be fast and intentional. The goal of prototyping isn’t just to build something that works—it’s to answer specific design questions. Effective teams use cardboard, foam board, or scrap polycarbonate to test geometry and mechanism concepts before committing to a final version. Each prototype should focus on validating a single factor, such as roller spacing, gear ratios, or sensor placement. Teams that document their results thoroughly, using photos, videos, and notes, are better equipped to justify decisions in their engineering portfolio and iterate with purpose.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.ftcwiki.org/how-to-build-competitive-robots/how-to-compete/design-workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.