> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/3d-modeling-and-design/metal-framing/feature-descriptions/wall-metal-framing/frame-wall/validate-walls.md).
# Validate Walls
**Validate Walls –** checks if the walls in the current project fit the predefined settings. Only validated walls should be framed.
Predefine the settings for wall validation → click **Check Walls in Project**.
*Result:*
**Wall+M** scans all wall instances in the your project and provides a report as to whether they fit the predefined sizes:
**Wall+M** also analyzes the layers in the wall and gives a report about the wall types.
*For example, **Wall+M** will frame the layer if it has a material assigned, so there is an option to select **Wall layer must have material assigned** and check all wall types. In this same dialog, you can click **Edit Type** and go to wall type modification where you have the option to assign the needed material.*
Here you can assign the needed material and this wall type will be ready for the framing process:
After adding a material, close the dialog and run **Validate Walls** again to make sure the problem has been solved.
---
# 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.besmart.software/3d-modeling-and-design/metal-framing/feature-descriptions/wall-metal-framing/frame-wall/validate-walls.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.
