> For the complete documentation index, see [llms.txt](https://docs.betterbuilding.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.betterbuilding.io/user-guide/2d-building/drawing/split-zones.md). # Split Zones A zone is drawn to the required dimension and has the same height as all other Zones drawn over the same Drawing. Sometimes, a Zone needs to be split, or divided into smaller sub-zones for more accurate modeling. ## Split a Zone To split a zone into two, first navigate to the 'Split Zones' symbol and select the zone you want to divide. Hold down 'Shift' to add a new point to the zone, or if points have been previously added during zone editing, you can use those. Next, left-click to select the first point where you want to initiate the split, then choose the second point.

Note that the original zone name will be retained in the split zone, so it's advisable to update the name of the newly created zone for clarity. --- # 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.betterbuilding.io/user-guide/2d-building/drawing/split-zones.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.