> 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-faq/using-the-software/calculation-modules/linked-loads/linked-loads-for-concrete-and-masonry.md).

# Linked loads for concrete and masonry

Why Linked Loads supports steel and wood beams, while concrete and masonry loads require manual entry.

## Why are Linked Loads primarily limited to steel and wood framing systems?

Load Linking is currently limited primarily to steel and wood framing systems because those framing systems are typically well represented by transferring the vertical support reactions from one member to another.

Concrete and masonry framing can behave quite differently. Depending on the framing and detailing, the forces transferred between members may involve more than a vertical reaction. Effects such as frame continuity, fixity, torsion, bearing, and reinforcement detailing can all influence the design of the supporting member. As a result, simply transferring the calculated end reaction may not accurately represent the actual load path or produce an appropriate design.

Rather than risk giving the impression that these effects have been accounted for when they have not, the concrete and masonry beam modules currently require these loads to be entered manually. This allows the engineer to determine the appropriate loading based on the framing conditions and detailing of the structure.

We understand that automatic load transfer for concrete and masonry would be a useful workflow improvement, and it is something we may revisit in the future if we can implement it in a way that accurately reflects the underlying engineering assumptions.


---

# 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-faq/using-the-software/calculation-modules/linked-loads/linked-loads-for-concrete-and-masonry.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.
