> 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/box-culvert-workflow/reports-bc/culvert-loads-summary-bc.md).

# Culvert Loads Summary \[BC]

The Culvert Loads Summary documents the culvert's geometry and every load applied to it, with the governing code reference and the intermediate quantities behind each number — the equivalent soil heights for the surcharge, the spread footprint and impact factor for the live load, the interaction factor for the vertical earth load, and the applied resultant per analysis case.

It is a checking document: it lets a reviewer confirm that what the model applied is what the code asks for, without opening the load objects one by one. It finds the load objects itself through the culvert selected below, so no load needs to be listed here.

## General

**Box Culvert:** The culvert barrel to report on. A selection is required. Every load object that selects this barrel is picked up automatically.

**Decimals Shown:** Number of decimal places used for the reported values, between 0 and 6.


---

# 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/templates/box-culvert-workflow/reports-bc/culvert-loads-summary-bc.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.