> 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-user-manual/calculation-modules/earth-retention/soldier-pile-2.md). # Soldier Pile Retaining Wall How to design cantilevered or tied-back soldier pile retaining walls in ENERCALC SEL. Soldier pile retaining walls, also called soldier beam walls, are generally used at construction sites for temporary shoring. Steel piles are driven into the ground, or placed in drilled holes filled with lean concrete, at a spacing such that lagging can be placed between the piles, and the excavation can proceed down to the level of the finished grade on the low side. The stability of a soldier pile retaining wall depends upon the active earth pressure being resisted by passive pressure on the embedded section of the pile. Pile spacing is typically 6 – 10 feet on center. ![](https://3283832020-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiBJmBoewuy4ZcBC7RF3m%2Fuploads%2Fgit-blob-8a3af24e60b65ff52b8c6ab1183d4430619b8bf0%2FClip43a.jpg?alt=media) This module is suitable for cantilevered soldier piles (no tie-backs) or soldier piles with tie-backs. --- # 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-user-manual/calculation-modules/earth-retention/soldier-pile-2.md?ask=&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.