> 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/steel-tub-girder-bridge-workflow/templates-for-code-check-stg.md).

# Templates for Code Check \[STG]

The purpose of code check and load rating templates is to collect generic inputs that remain constant for each code check or load rating station. For example, including haunch section properties for steel tub girder design is a template-level option. However, the transverse stiffener spacing may vary at each station, so it needs to be defined separately for each station. While the results may differ at each code check station, the extracted result case will remain the same. Therefore, with the load combination table inputs, we can gather the mapped results at the template level.


---

# 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/steel-tub-girder-bridge-workflow/templates-for-code-check-stg.md?ask=<question>&goal=<endgoal>
```

`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.