> 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/beams2/concrete-beams/concrete-beam-discrepancy-betw.md).

# Concrete Beam Discrepancy Between Moment Check and Steel Area Check

Why the Concrete Beam module can flag minimum steel limits even when φMn exceeds Mu, and why required steel differs from hand calcs.

## Why does the Concrete Beam module say to "Check As Min Limits" when it also says φMn > Mu?

These are two separate, independent checks that answer different questions, so passing one says nothing about the other.

The $$\phi M\_n \geq M\_u$$ check is a **strength** check: it confirms the section has enough moment capacity for the applied demand.

The As Min check is a **prescriptive, code-based** check: ACI 318 Section 9.6.1.2 requires a minimum area of flexural reinforcement, largely for ductility, independent of how much capacity the section happens to have. As Min Req'd is the larger of the two Section 9.6.1.2 expressions:

$$
A\_{s,\min} = \max\left(\frac{3\sqrt{f'\_c}b\_w d}{f\_y}, \frac{200 b\_w d}{f\_y}\right)
$$

Section 9.6.1.3 then waives that minimum wherever the reinforcement provided is at least 4/3 of the strength-required area (As Req'd Strength). Where that exemption applies, As Min Req'd is reported as "N/A."

Because one check is about strength and the other is a prescriptive minimum, a section can satisfy φMn > Mu and still be flagged for minimum steel. When that happens, apply engineering judgment to confirm the design provides adequate reinforcement for ductility.

## Why does As Req'd Strength appear to disagree with the φMn moment check (and with a first-principles hand calc)?

As Req'd Strength and φMn are computed with two different levels of rigor, so they don't always tell a consistent story.

As Req'd Strength is a simplified estimate. It takes $$M\_n = \left| M\_u \right| \mathbin{/} \phi$$ and solves $$\text{As Req'd Strength} = M\_n / \left\[ f\_y (d - a/2) \right]$$, locating the neutral axis at the code net-tensile-strain limit and treating the tension steel as a single lumped area at one effective depth $$d$$ that is assumed fully yielded. That's essentially the same shortcut a first-principles hand calc uses, so the two normally land close to each other.

φMn, by contrast, comes from a full strain-compatibility solver that evaluates the strain in each layer of bars at its own depth (so partially yielded bars contribute only their real stress) and includes the beneficial effect of any compression reinforcing. Because the simplified As Req'd Strength is conservative, it can suggest a section needs more steel than the rigorous φMn check actually requires. That gap is why As Req'd Strength can appear to disagree with the φMn result, and why either value can differ from a hand calc built on different simplifying assumptions.


---

# 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/beams2/concrete-beams/concrete-beam-discrepancy-betw.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.