Google Sheets IFS: Else Results, Syntax, and Fixes

Google Sheets’ IFS function has no separate else argument: if none of its conditions is true, it returns #N/A. To supply an else result, add TRUE as the final condition and put your default value after it, such as IFS(condition1, result1, TRUE, "Other").

How IFS works in Google Sheets

IFS checks conditions in the order you list them and returns the result paired with the first condition that evaluates to TRUE. It stops at that match, so a later condition is not used to replace an earlier result. The function is useful when a cell needs to be assigned one of several labels, rates, or actions without writing a long chain of nested IF functions.

The general syntax is IFS(condition1, value1, [condition2, value2, ...]). Each condition must have a corresponding value, and the arguments alternate between condition and result. The square brackets in the syntax description indicate optional additional pairs; do not type those brackets into the formula. IFS is not the same as an if-then-else statement in a programming language: it has no special ELSE keyword or dedicated final argument.

If all listed conditions are false, Sheets returns #N/A. That result is intentional: it signals that none of the cases you defined applied. A final TRUE condition provides a catch-all because TRUE is always true, provided the formula reaches it.

How to add an else result

Put the fallback condition and its result at the end of the IFS argument list. For example, if a status is not one of the recognized values, the final pair can return a message telling the user to review it.

With status values in B2, use this formula to label the values Paid, Pending, and Overdue and return a default for anything else:

=IFS(B2="Paid","Complete",B2="Pending","In progress",B2="Overdue","Contact customer",TRUE,"Review")

If B2 contains Pending, the result is In progress. If B2 contains Refunded, or another value not matched by the first three conditions, the result is Review. The final TRUE does not mean the formula checks whether B2 is TRUE; it is a constant catch-all condition.

You can choose any suitable fallback value: a word such as Other, a number such as 0, a message such as Check input, or an empty string written as "". The best choice depends on what will use the result next. A clear label may be easier to audit than a blank, while a blank may be preferable in a report where unmatched records should not display text.

Worked example: grade bands

Suppose a score is in A2 and you want to assign letter grades. The conditions should be arranged from the highest threshold down so a high score is not caught by a broader, lower threshold first.

With the score in A2, this formula returns A for 90 or more, B for 80–89, C for 70–79, and Below C for anything lower:

=IFS(A2>=90,"A",A2>=80,"B",A2>=70,"C",TRUE,"Below C")

For a score of 84, the first condition is false and the second is true, so the answer is B. For 68, the first three conditions are false and the final TRUE condition supplies Below C. A score of exactly 80 is B, while exactly 90 is A; the greater-than-or-equal operators include the boundary values.

It is possible to write overlapping conditions, but their order determines the outcome. If the condition for 70 or more came before the condition for 90 or more, a score of 95 would match the 70-or-more case first. That is why a reliable IFS formula is not just a list of rules: it is an ordered list of rules.

Choose conditions and order carefully

Before building the formula, decide what should happen at every boundary and what should happen to an unexpected value. Then translate each rule into a condition-result pair. For numeric bands, write down whether endpoints belong to the lower or upper band; for text categories, decide whether capitalization, spaces, or spelling differences should count as a match.

Put specific cases before broad ones. A test for a particular status should usually come before a general fallback.
Use consistent boundaries. For example, if one range ends below 80 and the next begins at 80, the rules do not overlap and do not leave a gap.
Keep the fallback last. Since TRUE always matches, anything after it is unreachable.
Make the default informative. A value such as Review can expose missing categories; a blank can hide them.

For text checks, ordinary equality comparisons match the text specified in the condition. A cell with a trailing space may therefore fail to match an expected label, even when the difference is hard to see. If your data comes from forms, imports, or manual entry, consider cleaning the source values or using a separate validation step rather than adding many increasingly complicated conditions.

Blank cells and missing data

A common surprise is that a blank input can still satisfy a numeric comparison. In Sheets, blank cells used in comparisons may behave like zero, so a grade formula can classify an empty score as Below C rather than leaving the result empty. Decide explicitly whether an empty input is a legitimate value, an error, or a state that should produce no output.

With a score in A2, this version returns a blank when A2 is empty and otherwise applies the grade rules:

=IF(A2="","",IFS(A2>=90,"A",A2>=80,"B",A2>=70,"C",TRUE,"Below C"))

The outer IF handles the missing-input case before IFS evaluates the score bands. For a blank A2, the displayed result is blank; for A2 equal to 84, it is B. This approach is different from using a blank as the IFS fallback: a fallback only applies when all prior conditions are false, and a blank may already have matched one of them.

Also consider whether a formula-generated empty string should count as empty in your workflow. The test shown above checks whether the cell appears empty as a value, but data-cleaning needs can be more involved if cells contain spaces or imported text. When a formula returns an unexpected category, inspect the source cell and its exact contents before changing the thresholds.

IFS compared with IF, SWITCH, and IFNA

IFS is often easier to read than nested IF when each condition is a different test. Nested IF can be a good alternative for a small number of cases or when you specifically want the familiar if-this-then-that structure. With a score in A2, the following formula gives the same grade bands as the earlier example:

=IF(A2>=90,"A",IF(A2>=80,"B",IF(A2>=70,"C","Below C")))

The final argument of the innermost IF acts as the else result. As more cases are added, however, nested parentheses can make the logic harder to scan and edit. IFS keeps each condition paired with its result, but it still needs the final TRUE pair when you want an explicit default.

SWITCH is another Google Sheets function, but it is designed for comparing one expression against a series of exact values. It can suit a list of fixed text labels, while IFS is better suited to different logical tests such as thresholds or compound conditions. IFNA can display a chosen value when a formula returns the specific #N/A error, but wrapping IFS in IFNA is usually less precise than adding a TRUE fallback. IFNA may also conceal an unrelated #N/A generated within an expression, making it harder to spot a data or lookup problem.

Common IFS problems and how to fix them

When an IFS formula behaves unexpectedly, check the argument pairs and the order before rewriting it. A missing result for a condition, an early catch-all, or a mismatch between the input and expected text can cause errors or surprising outputs.

#N/A appears: No condition evaluated as TRUE. Add a final TRUE condition if a default is appropriate, or keep the error if it should reveal an uncovered case.
The default appears too soon: Move the TRUE pair to the end. Any conditions after it can never be reached.
A boundary score gets the wrong label: Review the operators and order. Check whether the rule calls for > or >= at that exact value.
A known text value goes to the fallback: Check spelling, leading or trailing spaces, and whether the formula points at the intended cell.
The formula is rejected: Check that every condition has a result, parentheses are balanced, and commas separate the arguments. Spreadsheet locale settings can affect formula separators; examples here use commas.

For long formulas, split the logic into smaller pieces or place intermediate checks in helper columns. Helper columns make it easier to see which condition is being met and can be simpler for another person to maintain. In a shared sheet, meaningful labels and a visible Review or Other fallback can help identify new categories before they silently enter a report.

Frequently Asked Questions

Does Google Sheets IFS have an ELSE argument?
No. IFS has condition-result pairs but no special ELSE argument. Add TRUE as the last condition and the desired default as its paired result.

What happens if no IFS condition is true?
Sheets returns #N/A. Add a final TRUE pair to return a chosen fallback, or leave the error in place if an unmatched case should be investigated.

Can the IFS fallback be blank?
Yes. Pair the final TRUE condition with "" to return an empty string when none of the earlier conditions match. Keep in mind that this can make unmatched records less visible.

Can I use TRUE as the first IFS condition?
You can, but it will match immediately, so every condition after it is ignored. Use TRUE only as the final catch-all condition.

Why does a blank cell get a result instead of the fallback?
A blank can satisfy a comparison, particularly a numeric comparison that treats it like zero. Add a separate blank check before IFS if empty inputs should return a blank or a specific message.

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.