> 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/pier-footing-code-check-t-ex1-cug.md).

# Pier Footing Code Check T

This section configures the code check template for pier footing design verification.

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

## Steps

### Step 1: Navigate to Pier Footing Code Check T

Navigate to **Templates for Code Check > Pier Footing Code Check T** in the tree view.

### Step 2: Configure Flexure Checks

Set parameters for footing flexural verification:

* Bottom reinforcement for positive moment
* Top reinforcement for pile uplift (if applicable)

### Step 3: Configure Shear Checks

Set parameters for footing shear capacity:

* One-way shear (beam shear)
* Two-way shear (punching shear)
* Critical section locations

### Step 4: Configure Bearing Pressure Checks

Set allowable bearing pressure limits based on geotechnical recommendations.

<details>

<summary><strong>Quick Tip:</strong> Critical Section for Shear</summary>

For one-way shear, the critical section is at distance 'd' from the column face. For two-way shear, the critical perimeter is at 'd/2' from the column.

</details>

## Verification

{% hint style="success" %}
After completing these steps, the pier footing code check template is ready for design verification.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openbrim.org/examples/concrete-bridge-examples/example-concrete-u-girder-bridge/templates-for-code-check-ex1-cug/pier-footing-code-check-t-ex1-cug.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.