2.7 Errors, auditing and trusting a spreadsheet
Checked against Microsoft's Excel for Windows keyboard references, August 2026
What you'll be able to do
Find out why a number is wrong instead of typing over it. Read what each error value is telling you. Follow a formula's inputs across the sheet. Build the checking row that catches tomorrow's mistake before a reader does.
Before you start
Any workbook of yours with real formulas in it. The audit teaches more on your own work.
The work
- Same either way: read errors as admissions, not failures.
#DIV/0!means the formula divided by an empty or zero cell.#N/Ameans a lookup found nothing, for one of the three causes in the lookup topic.#VALUE!means text was fed into arithmetic.#REF!means the formula's target was deleted, so the reference itself is gone.#NAME?means a misspelled function, or text left without quotation marks. Each one names its cause, and the fix starts from that name. - Same either way: handle the misses you expect without silencing real faults.
=IFNA(XLOOKUP(...), "not on file")catches only #N/A, the miss you planned for, and lets every other error stay loud.=IFERROR(...)swallows all of them, including the #REF! that means the sheet is damaged. Reach for IFNA first, and use IFERROR only when any failure honestly means the same fallback. Wrapping a wrong formula in IFERROR to make the red go away hides a fault instead of handling it. - No documented keyboard shortcut for this — use the menu: to see where a suspicious cell's inputs come from, select it and go to Formulas → Trace Precedents. Arrows draw the flow of data into the cell. Trace Dependents draws who reads from it, and running that before you edit anything tells you what you are about to disturb. Remove Arrows, on the same tab, clears the drawing.
- No documented keyboard shortcut for this — use the menu: to watch a formula work, select it and go to Formulas → Evaluate Formula. Each press of Evaluate works out the next piece, underlined, and you see the wrong turn happen. For a quick look at one piece instead, select it in the formula bar and press F9 to work it out in place. Press Esc so the result is not saved into the formula.
- Same either way: build the checking row. Wherever two routes must agree, make a cell that says so. Column totals against a grand total:
=IF(SUM(H2:H13)=H15, "OK", "CHECK"). It costs one row, and it catches the kind of error that reaches readers: the wrong number that looks believable. - Same either way: audit the sheet visually in ten seconds. Press CtrlGrave accent to show every formula at once, and the hard-typed number hiding in a formula column stands out immediately. Press it again to go back.
Try it
In your own workbook: cause each error once on a scratch sheet and fix it from its name. Follow one important cell's precedents and dependents. Walk one formula through Evaluate Formula. Then add a checking cell where two totals must agree, and leave it in.
Check yourself
What does #REF! tell you that #N/A does not?
#REF! means the formula's target was deleted, so the sheet's structure is damaged. #N/A means a lookup ran correctly and found nothing, which is often legitimate.
Why is IFNA usually the right wrapper and IFERROR the risky one?
IFNA catches only the miss you planned for, and lets structural faults stay visible. IFERROR silences everything, including errors that mean the sheet is broken.
Before editing a much-used cell, which trace do you run, and why?
Trace Dependents. It shows every formula that reads from that cell, which is how far your edit will reach.
What is a checking column, and what kind of error does it catch?
A cell that asserts that two routes to the same number agree, such as column totals against a grand total. It catches the believable wrong number that no error value ever flags.
What does CtrlGrave accent reveal that the normal view hides?
Every formula at once, including the cell in a formula column where somebody typed a number over the formula.
Go deeper
We haven't checked most of these for screen reader use yet.
Back to Errors, auditing and trusting a spreadsheet: work through the checklist