# Engineering Notebook

The engineering notebook is the pièce de rèsistance of a VEX team. From the engineering notebook, one should be able to follow the **entire** design process of a team. At a basic level, the notebook should have:

* Analysis of the **game**
* Possible **designs**
* **Selection** of the best design
* Step-by-step documentation of the **building** process
* The full **code** for the robot
* **Testing** and test results
* Project **management** notes

{% hint style="info" %}
In this section, we will be using team 96504C's Spin Up notebook as an example. While this notebook did earn 4 Excellence Awards, it is not a perfect notebook. Still, it's a good starting point.
{% endhint %}

{% content-ref url="/pages/AhiD16ZO9InaKRG9Dykv" %}
[Formatting](/ascend/vex-robotics/engineering-notebook/formatting.md)
{% endcontent-ref %}

{% content-ref url="/pages/guGYBK8saxfR2I3MKxQ0" %}
[Notebook Walkthrough](/ascend/vex-robotics/engineering-notebook/notebook-walkthrough.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://ascendrobotics.gitbook.io/ascend/vex-robotics/engineering-notebook.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.