> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-onboarding/getting-started/building-codes-supported.md).

# Building codes supported

How to find the building codes and design standards supported by ENERCALC SEL.

ENERCALC SEL supports the following building codes and design standards. It also includes databases of commonly available steel and wood sections and material properties.

### Supported codes and standards

| Material or scope | Standards                                  |
| ----------------- | ------------------------------------------ |
| Building Code     | **IBC 2024**, IBC 2021, IBC 2018, IBC 2015 |
| Design Loads      | **ASCE 7-22**, ASCE 7-16, ASCE 7-10        |
| Concrete          | **ACI 318-25**, ACI 318-19, ACI 318-14     |
| Masonry           | **TMS 402-22**, TMS 402-16, ACI 530-13     |
| Steel             | **AISC 360-22**, AISC 360-16, AISC 360-10  |
| Wood              | **NDS 2024**, NDS 2018, NDS 2015           |
| Wood Lateral      | **SDPWS 2021,** SDPWS 2015                 |

### State-specific modifications

ENERCALC SEL doesn't support state-specific modifications to governing codes and design standards. State-specific, agency-specific modifications are complex to add and maintain.

[Read more on ENERCALC's perspective here](https://enercalc.com/CBC2022).


---

# 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://enercalc.com/docs/sel-onboarding/getting-started/building-codes-supported.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.