> 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/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/templates-for-code-check-ex1-cug/load-rating-code-check-t-ex1-cug.md).

# Load Rating Code Check T

This section configures the code check template for load rating analysis.

{% hint style="info" %}
**Navigation:** Templates for Code Check > Load Rating Code Check T
{% endhint %}

## Steps

### Step 1: Navigate to Load Rating Code Check T

Navigate to **Templates for Code Check > Load Rating Code Check T** in the tree view.

### Step 2: Configure Rating Method

Select the load rating method:

* **LRFR (Load and Resistance Factor Rating):** Modern approach per AASHTO MBE
* **LFR (Load Factor Rating):** Legacy approach

### Step 3: Configure Rating Vehicles

Define rating vehicles:

* HL-93 design load
* Legal loads (Type 3, Type 3S2, Type 3-3)
* Permit loads (as required)

### Step 4: Set Rating Factors

Configure condition factors and system factors:

* Condition factor (φc)
* System factor (φs)

<details>

<summary><strong>Quick Tip:</strong> Rating Levels</summary>

LRFR uses three rating levels: Design Load Rating, Legal Load Rating, and Permit Load Rating. Each level has different load factors and requirements.

</details>

## Verification

{% hint style="success" %}
After completing these steps, the load rating code check template is ready for rating analysis.
{% endhint %}


---

# 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/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/templates-for-code-check-ex1-cug/load-rating-code-check-t-ex1-cug.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.