> 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/tributary-beams14.md).

# Tributary Beams

How to confirm tributary beams during beam calculation launch to establish load path, recalc order, and change warnings.

After the final approval of all supporting elements, the next step in the beam calculation launch process is to confirm the identity of tributary beams. Tributary beams are defined as beams supported by the main designed beam, which may contribute load that influences the design.

Identifying these beams will establish the connective relationships that determine load path, re-calculation order, and change warnings, as well as allowing ENERCALC for Revit to retrieve load-linked reaction forces from upstream calculations. 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 tributary elements and present them to the user.

The calculation launch form will proceed automatically to the “Tributary Beams” tab as soon as the support confirmation is complete.

![](https://4249100372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgHVzpA9PT0VcuNGp6j39%2Fuploads%2Fgit-blob-95d1498f0f0f57f1bea5f5a6e77d0f0a0ae82f4f%2Fclip0123.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/tributary-beams14.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.
