> 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/pile-capacity-check-t-ex1-cug.md).

# Pile Capacity Check T

This section configures the code check template for pile capacity verification.

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

## Steps

### Step 1: Navigate to Pile Capacity Check T

Navigate to **Templates for Code Check > Pile Capacity Check T** in the tree view.

### Step 2: Configure Axial Capacity

Set parameters for pile axial capacity verification:

* Compression capacity
* Uplift (tension) capacity
* Resistance factors

### Step 3: Configure Lateral Capacity

Set parameters for lateral load capacity if applicable:

* Lateral soil resistance
* Pile head fixity conditions

### Step 4: Define Group Effects

Configure pile group efficiency factors if multiple piles are used.

<details>

<summary><strong>Quick Tip:</strong> Geotechnical Parameters</summary>

Pile capacity depends on soil conditions. Ensure geotechnical recommendations are properly incorporated into the capacity calculations.

</details>

## Verification

{% hint style="success" %}
After completing these steps, the pile capacity 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/pile-capacity-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.