> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-faq/using-the-software/calculation-modules/retaining-walls/cantilevered-retaining-wall/calculation-of-factored-soil-p.md).

# Calculation of Factored Soil Pressures

How the Cantilevered Retaining Wall module calculates factored soil pressures for footing design.

## How does the module calculate factored soil pressures for footing design?

1. Using the service loads, the program solves for the eccentricity by dividing total the moment by the total vertical load.
2. Using the eccentricity and the footing dimensions, the program then determines which category the pressure distribution falls into, based on the extent of the pressure diagram and the location of the resultant.
3. Finally, based on the category determined above, the program calculates the toe and heel pressures. In this step, the program uses an effective factored vertical load of 1.4 times the service-level vertical loads. The factor of 1.4 is meant to be an approximation of a weighted average load factor for each of the contributing loads.


---

# 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://enercalc.com/docs/sel-faq/using-the-software/calculation-modules/retaining-walls/cantilevered-retaining-wall/calculation-of-factored-soil-p.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.
