> 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/faq/openings/how-to-extend-sill-header-to-the-nearest-vertical-studs.md).

# How to extend sill/header to the nearest vertical studs?

1. Go to **Framing Configurations**:

<figure><img src="https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2Fd1DeKRMjpmX6MAlzJ3km%2FOpen%20framing%20configs.gif?alt=media&amp;token=2bb39c8c-7118-4d00-aea7-de09e3f9012d" alt=""><figcaption></figcaption></figure>

2. Switch to the **Opening Framing** tab
3. Choose which configurations to modify - for **Non-Structural Walls** or **Structural Walls**:&#x20;

<figure><img src="https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FrggZoMWA1WOiYgxOUu18%2FOpening%20framing.gif?alt=media&amp;token=cd2a940b-5c18-4ced-ba38-042263d5f46b" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note**: check the wall instance parameter **Structural**.&#x20;

If the **box is checked**, modify configurations for **Structural Walls**.&#x20;

If the **box is unchecked** - for **Non-Structural Walls**.
{% endhint %}

4. Click **Edit Configurations**
5. In the new dialogue, switch to the **Trimmer** tab
6. Check the box in the **Extend Sill\&Header** parameter
7. **Save** the opening configurations and click **Save** in the main dialogue:

<figure><img src="https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FTDhJsld4YsfUHXXwCEqa%2FEdit%20opening%20configs.gif?alt=media&amp;token=b895d9ca-2249-4676-b323-088ccc264229" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
**Warning**: the automation of the extended sill/header doesn't work around the **beam pockets** at the very top/bottom of the wall.&#x20;

To extend the sill/header around the beam pockets you'll need to **switch off** the **Extend Sill\&Header** parameter and follow [**this workflow**](/3d-modeling-and-design/metal-framing/faq/openings/how-to-extend-sill-header-to-the-nearest-vertical-studs-of-a-beam-pocket.md) instead.
{% endhint %}

8. Click on **Frame Wall**
9. **Select a wall** and choose **Delete and Reframe** in the pop-up:

<figure><img src="https://239424168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqtUsszuAWXIZhQhrvjnb%2Fuploads%2FU4ny2YjthoE1eD5I2UtA%2FReframe%20wall.gif?alt=media&amp;token=0fd68cfd-428b-457c-9307-1560003144c2" alt=""><figcaption></figcaption></figure>

***

{% hint style="info" %}
If you can't find the answers you're looking for, please [contact our support team](https://helpdesk.besmart.software/support/tickets/new).
{% endhint %}


---

# 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/faq/openings/how-to-extend-sill-header-to-the-nearest-vertical-studs.md?ask=<question>&goal=<user_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.
