Here's a formula problem that feels familiar to anyone who has tried to make a spreadsheet behave like a thinking tool rather than a rigid grid. The user wants a "Days Since" column that adapts to three different scenarios: use the Last Action date when it exists, fall back to the Submitted date when it doesn't, and show nothing once a task is completed. They've built something close, but it breaks on empty rows and refuses to stop counting after completion. This is exactly the kind of friction that makes people wonder if spreadsheets are fighting them instead of working for them.
The real insight here is not about nested IF statements or the quirks of NETWORKDAYS. It's about the gap between what a spreadsheet can do and what it should do for you. The user's first attempt failed because they treated the formula as a single logical gate: check this, then that, then the other. That approach works until it doesn't, and it especially fails when dates are missing or when the logic has to stop itself. The second attempt is more honest, it explicitly checks for empty cells before deciding which date to use, but it still returns a large number on rows with no dates at all. That number isn't a bug; it's a symptom of a formula that doesn't know when to stay silent.
What this user really needs is not a better formula in the traditional sense, but a clearer mental model. The rule is simple: if Completed has a value, output nothing. If Completed is empty, check Last Action. If Last Action has a date, calculate workdays from that. If Last Action is empty, calculate from Submitted. And if all three date cells are empty, output nothing. That's four conditions, not two. The user's last attempt tried to fold the "all empty" case into an AND condition that only checked two columns, missing the third. A cleaner approach would nest the logic so that the first test is "is Completed filled?" and the last fallback is "are all dates empty?" rather than trying to guess which date to use in the absence of any.
This matters because the spreadsheet is not the end goal. The goal is to stop manually tracking days, to stop worrying about whether a completed task still shows 45 days since the last action, and to stop seeing 44,000 appear in a cell that should be blank. A formula that handles these edge cases correctly is not a clever trick, it's a small piece of automation that frees someone to focus on the work itself. That is the promise of moving from legacy tools to smarter ones: not faster formulas, but fewer decisions. The user is already halfway there. The next step is to stop patching logic and start thinking in layers: check for completion first, then check for presence of dates, then calculate. Do that, and the large numbers disappear, the conditional formatting works, and the column finally adapts to the data instead of demanding the data adapt to the column.