> 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/default-value-of-0-0018-for-as.md).

# Default Value of 0.0018 for Asmin in Footing

Why the footing offers a default minimum steel ratio of 0.0018 and how the user can control that value.

## Why does the program offer a default value of 0.0018 for Asmin in the footing? Isn't 0.0018 only for slabs?

First it is worth mentioning that the user has control over that calculation by way of the value shown in the screen capture below:

![](https://1076748670-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtBL2fEQRwrlKSM2irFL0%2Fuploads%2Fgit-blob-ac70db7aa70d9881c4b4e37cb00d8421f56e1849%2FMin_Steel_Control.jpg?alt=media)

Having said that, here is the logic behind the default value of 0.0018:

ACI 318-14 Section 13.3.2.1 requires that design and detailing...shall be in accordance with the applicable provisions of Chapter 7 and Chapter 9.

This implies that ***at least some*** of the requirements of Chapter 7 (all about one-way slabs) are applicable to footings. It is largely open to interpretation. So we configure the software to allow the user to make that decision, and we provide a "compliant" default value for that particular control, just to be conservative.


---

# 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/default-value-of-0-0018-for-as.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.
