> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/openbrimfea/loads-fea/staged-construction-fea.md). # Staged Construction \[FEA] Staged Construction models the erection sequence. Each **Stage** inherits the deformed, stressed state of its prior stage, activates or deactivates parts of the structure, applies its loads, and passes the resulting state forward. This matters because **the structure that carries each load is the structure that existed when the load was applied**. A girder erected simply supported and later made continuous carries its self-weight on the simple span forever, regardless of the finished geometry - and only a staged analysis reproduces that. **States** declare what is present at each stage and whether it contributes stiffness, weight, or both. **Loading** schedules existing load cases into stages. **Changes** modify object properties from a stage onward - releasing falsework, locking a bearing. **Prestressing** schedules tendon stressing operations. **Tendon Path Points** define the tendon geometry those operations act on. A staged result **should** differ from a single all-at-once analysis. If the two agree exactly, the staging is not taking effect. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.openbrim.org/templates/openbrimfea/loads-fea/staged-construction-fea.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.