> For the complete documentation index, see [llms.txt](https://docs.enercalc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enercalc.com/sel-faq/using-the-software/calculation-modules/foundations2/pole-embedment/moment-entries-removed-for-non.md).

# Moment entries removed for nonconstrained poles

Why moment entries were removed from nonconstrained pole footing designs.

## Why can I no longer apply moments to my nonconstrained pole footing designs?

The Pole Footing module was updated on 22 Aug 2012 to remove the moment input for the nonconstrained condition. Here is the explanatory text from the Enhancement/Change History section of the program:

"Moment entries have been removed for nonconstrained cases. After review we felt the program was not properly applying the moments in all cases. The code formulas used do not stipulate how to apply concentrated moments. For cases of moments with no lateral load, the moment was applied as a 0.01 lb load at a height = M / 0.01. For cases with nonzero lateral loads the moment was simply added to the calculated moment at the ground surface. While all of the results looked reasonable the lack of code direction has led us to remove that ability."


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enercalc.com/sel-faq/using-the-software/calculation-modules/foundations2/pole-embedment/moment-entries-removed-for-non.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.