> 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/e3d-training-manual/building-the-model/working-with-loads/load-cases.md).

# Load Cases

How to define the individual load types like dead, live, wind, and seismic that combine within load combinations.

Think of Load Cases as the individual load types that get combined in the load combinations.

So a typical model will probably have Dead, Live, Wind, Seismic, etc. Other available load types include Roof Live and Snow.

To define the Load Cases that will be used in a model click **Create > Load Cases**. The *Load Cases* dialog opens and is pre-populated with a load case named Default. You can use this case if you want, but you can't change the name "Default". If you prefer, just create all the load cases you want and completely ignore the presence of the Default load case.

![](https://3750289988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlRZtG5Ynp58kYzLHYbR7%2Fuploads%2Fgit-blob-5c88c8e3e1b21830854a0d2c97003622f3f77f6f%2FLoad%20cases%20dialog.jpg?alt=media)

For each Load Case that you create, give it a recognizable name, and select the Type of load at the far right.

The Load Cases that you create here will be used when you start assigning load items in subsequent steps, because any load item that is added to a model *must* be assigned to one Load Case.


---

# 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/e3d-training-manual/building-the-model/working-with-loads/load-cases.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.
