> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/plans-and-autoplan/clear-to-build-reporting.md).
# Clear to build reporting
The clear to build report is a standard report found under "Parts/Inventory/Plans".
The report combines the plans data generated by Autoplan with the aBOM to give you a full picture of the status of your build(s).
### Notable assemblies
This view in the Clear to Build report helps break down the BOM into reportable sections. To use this feature, you need to set up an attribute at the part library level to indicate the Notable Assembly. **Set this attribute as either a text or single-select input and make sure the name is exactly "Notable Assembly" (not case sensitive).**
{% embed url="" %}
When generating outputs, the "Notable Assembly" serves as an initial reference point. As the system traverses the Bill of Materials (BOM), the value associated with a high level (parent) notable assembly will propagate down the hierarchy. This propagation continues through all subsequent components in the structure until another assembly with a different notable assembly name or attribute is encountered.
For the example in the video above:
1. Starting from a "Notable Assembly" each component below it inherits the associated attributes until a different assembly name (e.g., "Base") is reached.
2. From the "Base" assembly onward, every subsequent component in the structure will inherit the attributes of "Base."
This hierarchy-based propagation ensures that attributes are consistently inherited by child components, depending on the last encountered assembly name with the "Notable Assembly" attribute populated.
---
# 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://manual.firstresonance.io/plans-and-autoplan/clear-to-build-reporting.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.
