> 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-user-manual/project-manager/loads-forces-division.md).

# Loads & Forces Divisions

Understand the historical Loads and Forces divisions that appear under ASCE 7-10 and 7-16 project files.

**Historical Note:** When Loads & Forces calculations were first introduced, they were automatically included in the Project Manager when starting a new project file, appearing as a set of preloaded Loads & Forces divisions. These divisions and modules will continue to appear in ENERCALC SEL project files when the governing code is set to ASCE 7-10 or ASCE 7-16.

The screen capture below shows the Project Manager view for a SEL project with the governing code set to ASCE 7-16.

![](https://3283832020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiBJmBoewuy4ZcBC7RF3m%2Fuploads%2Fgit-blob-67f632848ee0814bf69cca20aa22aa3783ab48f1%2FProject%20Manager%20-%20Historical%20Loads%20%26%20Forces%20Divisions%20-%20Expanded.png?alt=media)

See specific descriptions under [Calculation Modules > Loads & Forces Division](/docs/sel-user-manual/project-manager/loads-forces-division.md).


---

# 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-user-manual/project-manager/loads-forces-division.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.