> 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/truss-bridge-workflow/construction-tb/substructure-construction-tb/backfill-soil-construction-tb.md).

# Backfill Soil Construction \[TB]

## Backfill Soil Construction

Places one Backfill Soil object into the staged construction model at a stage. The passive soil springs of the picked soil are generated by this object and join the analysis at the selected stage, the same way the abutment itself joins at its Abutment Construction stage. Every value of the springs (profile, directions, behavior, wing walls and the elevation band) comes from the picked Backfill Soil, so a staged model and an unstaged one describe the same soil and differ only in when it arrives.

A fill raised in lifts is modeled cumulatively, one Backfill Soil object per lift, each constructed at its own stage. Each construction automatically switches off the springs of the other lifts on the same abutment from its stage on, so the deeper lift replaces the shallower one instead of adding to it. There is nothing to connect by hand: add one soil object and one construction object per lift.

In a construction stage analysis the springs are active from the selected stage on. In an analysis case that is not part of the construction sequence, all springs are active, so that case sees the same soil stiffness as an unstaged model.

### General

**Stage:** The construction stage at which the backfill is placed and its springs join the analysis. The user must provide a value.

**Backfill Soil:** Pick the Backfill Soil object to construct. Its Staged Construction input must be set to Yes; otherwise that soil already generates its own springs and the passive stiffness would be doubled, which is reported as a validation issue. The user must provide a value.


---

# 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/truss-bridge-workflow/construction-tb/substructure-construction-tb/backfill-soil-construction-tb.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.
