> 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/efr-user-manual/calculation-types/working-with-beam-calculations/beam-supports13.md).

# Beam Supports

How ENERCALC for Revit identifies and suggests the elements that support a beam to define span geometry and load path.

Upon launching a beam calculation, ENERCALC for Revit will start the process by identifying the elements that support the beam. This will allow span geometry to be defined in the ENERCALC calculation module, and will establish the connective relationships that determine load path, re-calculation order, and change warnings. ENERCALC for Revit leverages a variety of information available in the Revit model, including physical solid location of the beam element, line location of the beam element, and proximity to other elements in order to suggest the most probable support elements and present them to the user.

Beams may be supported by any of the following element types:

* Structural Columns (from below or above)
* Structural Framing as beams
* Structural Walls

Beams may be not supported by any of the following element types:

* Structural Framing as vertical bracing
* Structural Framing as horizontal bracing
* Structural Floors
* Structural Foundations
* Structural Walls with a non-bearing usage type
* Non-Structural Walls
* Any other non-structural element

The suggested supports will be automatically selected in the Revit interface for the user’s attention. The prompt on the approval form will indicate the number of suggested supports found.

![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-0a465cfce699481e238b46f65b2f914508500abc%2Fclip0083.png?alt=media)

![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-1982ff253193947028021cdfceedccad2cf8e31f%2Fclip0084.png?alt=media)

![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-edf1111c4dc70394886ec2894b13e3896d6dd5c1%2Fclip0085.png?alt=media)

![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-fb1aafa0e6554aeb0c5dadfa800893bf5d7548a0%2Fclip0086.png?alt=media)

.


---

# 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/efr-user-manual/calculation-types/working-with-beam-calculations/beam-supports13.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.
