Nested IF Statements in Excel

A nested IF places one IF inside another to test several conditions in sequence. In financial models it assigns ratings, applies tiered rates, or classifies accounts when the logic depends on more than two outcomes. Nested IFs are flexible and need no extra tables, but they grow hard to read fast, which is exactly where modeling errors hide.

Syntax and how it works

A single IF is =IF(logical_test, value_if_true, value_if_false). To handle a third outcome you put another IF in the value_if_false slot: =IF(test1, result1, IF(test2, result2, result3)). Excel evaluates the tests in order and stops at the first one that is true, so the order of branches is the logic.

Because each false branch can hold another IF, you can chain many tests. Modern Excel allows up to 64 nested levels, but readability collapses long before that. The key mental model is a ladder: each rung checks a condition, and falling off the bottom rung yields the final else result.

Worked example: credit rating from a score

A score sits in F1. You want to return a rating: 90 and above is A, 75 to 89 is B, 60 to 74 is C, and anything below 60 is D. Order the tests from the highest threshold down so each one only has to check a single boundary.

1. Enter =IF(F1>=90, "A", IF(F1>=75, "B", IF(F1>=60, "C", "D"))).
2. If F1 is 82, the first test F1>=90 is false, so Excel moves to the next IF.
3. The second test F1>=75 is true, so the formula returns B and stops.
4. Because the ladder runs high to low, you never have to write a compound AND for each band.

A score of 82 stops at the second rung and returns B.

Why analysts use them and where they fit

Nested IFs are the right tool when the outcomes are few, the logic is unlikely to change, and you do not want to maintain a separate lookup table. They keep the rule inside the formula, which is convenient for a quick classification column.

They start to cost more than they save once the branches multiply or the thresholds become assumptions someone will want to tune.

• Use a nested IF for two to four clean outcomes with stable boundaries.
• Switch to IFS when you have many conditions and want a flat, readable list.
• Switch to a lookup table with VLOOKUP approximate match or XLOOKUP when the bands are real assumptions that belong in cells.
• Move threshold numbers like 90 and 75 into labeled cells so reviewers can see and change them.

Common pitfalls in models

Branch order is the top trap. If you test F1>=60 before F1>=90, every score above 60 returns the first matching band and the higher bands never fire. Always order overlapping comparisons from the strictest boundary down.

Mismatched parentheses are the second trap. Each nested IF adds a closing parenthesis, and deep ladders are easy to miscount. Hardcoded thresholds buried in the formula are the third: they are invisible to a reviewer and tedious to update across a column, so promote them to assumption cells.