> 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/e3d-user-manual/interface/toc175916526/steel-design2/design-results.md).

# Steel Design Results

How to view steel design results, update member sections, and review detailed member calculations.

Steel Design > Steel Design Results allows you to view the steel design results.

![](https://560001759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWNe8U6EBBBdUJHdb2X9G%2Fuploads%2Fgit-blob-e4f74649340146ae97b0f4ef7b4b636852b47dc3%2FSteel%20design%20result%20table.jpg?alt=media)

It also allows you to update member sections.

The section column in the screen capture above includes a list box that contains the member original section (first entry in the list box) and designed section candidates (second or more entries in the list box). You can change the member sections by picking the proper section candidates. Please be advised you need to re-analyze and design after one or more member sections are updated.

In addition, you can add all the section candidates to Section Pool, which can be used in the next round of design.

Finally, you can view the detailed calculation procedure for each member for the most critical load condition.


---

# 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/e3d-user-manual/interface/toc175916526/steel-design2/design-results.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.
