R025 — Orphaned or Invalid Named Range
Executive Summary
Key Takeaways
- ✓ R025 checks every defined name in the workbook for two distinct, independent conditions — an invalid (broken) target, and an orphaned (valid but unreferenced) one.
- ✓ An invalid name is flagged at high confidence, since a broken or unresolvable target is a directly observable fact.
- ✓ An orphaned name is flagged at medium confidence, asking a reviewer to confirm whether the assumption it represents is still active.
- ✓ Name comparison is case-insensitive throughout, consistent with how Excel itself treats defined names.
Purpose¶
R025 checks every named range (defined name) in the workbook for two distinct, independent defects: an invalid name, whose target is broken or unresolvable, and an orphaned name, whose target is valid but is not referenced by any formula in the model.
Detection Logic¶
For each defined name in the workbook, its recorded target value is first checked for validity — if the target is empty or itself contains an Excel error marker, the name is flagged as invalid, at high confidence, since a broken target is a directly observable fact. If the target is valid, the name is checked against the set of every name genuinely referenced as a real name reference somewhere in the model's formulas (comparison is case-insensitive, matching Excel's own treatment of names). A valid name found in no formula's real references is flagged as orphaned, at medium confidence.
Why It Matters¶
An invalid named range means any formula still attempting to reference it will itself return an error — the same underlying risk R002 (Broken Links) addresses at the cell-reference level, applied to named ranges specifically. An orphaned named range is a quieter risk: the name still resolves correctly, so it does not produce a visible error, but nothing in the model actually uses it, meaning whatever assumption or value it represents has no path to influence any output — the model's real logic has moved on without it, even though the name itself remains defined and technically valid.
Evidence Produced¶
For an invalid name, the finding's evidence names the defined name, its scope, and its broken target value. For an orphaned name, the evidence names the defined name, its scope, its (valid) target, and a description noting that the name is not referenced by any formula in the model.
Severity¶
Medium. Weight 7.5. R025 is not one of the five critical-override rules. Confidence is high for the invalid condition and medium for the orphaned condition.
Example¶
Trigger — invalid. A defined name TaxRate_2024 points to a range on a worksheet that was later
deleted, and its recorded target now contains a broken-reference error marker. R025 flags this name as
invalid, at high confidence.
Trigger — orphaned. A defined name LegacyDiscountRate resolves correctly to a valid cell, but no
formula anywhere in the current model references it by name. R025 flags this name as orphaned, at medium
confidence, asking whether the assumption is still active.
Non-trigger. A defined name that resolves correctly and is referenced by at least one formula in the model. R025 does not fire for this name under either condition.
Recommended Remediation¶
For an invalid name, either repair the reference to point at the correct current range, or delete the name if its target genuinely no longer exists and is not needed. For an orphaned name, confirm whether the assumption it represents is still active; if it is retained deliberately for future use, document that intent, and if it is genuinely stale, remove it to keep the model's defined names an accurate reflection of what the model actually uses.
Related Rules¶
R025 shares the Model Governance taxonomy category with the other Model Governance rules published in the Rule Reference, and is closely related in concept to R024 — Unused Input Driver — see the Rule Taxonomy page for the full category membership.
Related Articles¶
- Named Ranges — the Knowledge Centre's buyer-facing guide to named range management and its relationship to link integrity.
Version History¶
No version-specific changes to R025's severity, weight, or category are recorded as of engine version 2.1.0. This section will be updated in the same edit as any future change to the rule's declared attributes.
How OXXON tests thisRun a free structural check with FMAE
Frequently Asked Questions
What does FMAE rule R025 check for?
Two distinct defects in the workbook's defined names — an invalid name, whose target range or sheet is broken or cannot be resolved (often because it was deleted), and an orphaned name, which resolves correctly but is not referenced by any formula anywhere in the model.
Why are invalid and orphaned names flagged at different confidence levels?
An invalid name's broken target is a directly observable, unambiguous fact, so it is flagged at high confidence. Whether an orphaned name still represents an active assumption is more of a judgment call — the name might be retained deliberately for future use — so it is flagged at medium confidence, asking a reviewer to confirm rather than asserting a defect.
Can a name be both invalid and orphaned?
R025 checks invalidity first; if a name's target is broken, it is reported as invalid and is not separately evaluated for the orphaned condition, since a broken target cannot be meaningfully referenced anyway.
Related Articles
FMAE Rule Taxonomy
Every rule in the FMAE structural rule pack declares a category attribute at the point it is defined in source — this is not a classification imposed on the rules afterward for documentation purposes, it is the classification the engine itself uses. Six categories cover all 26 rules — Structural (18 rules), Assumptions Governance (1), Integrity Controls (2), Structural Hygiene (1), Aggregation Logic (1), and Model Governance (3). This page publishes that taxonomy as the FMAE equivalent of a control catalog's classification scheme, cross-linked to the Rule Reference page for each member rule.
Finding Data Model & Confidence
Every FMAE finding carries the same fixed structure — which rule triggered it and that rule's identity at the time it ran, its evidence, a narrative explanation, and a confidence label of high, medium, or low. Confidence is a deterministic categorical label derived from how strongly a row's cells agree on a pattern, not a machine-learning probability estimate. Stating this plainly matters, since describing FMAE's confidence as AI-derived or probabilistic would overstate what the engine actually does.
R024 — Unused Input Driver
R024 (Unused Input Driver) flags a numeric, non-formula cell on a worksheet already identified as a model's input layer that no formula anywhere in the model actually references. An input that cannot be traced to any output is either a stale assumption that was never connected, or a driver that was intended to feed a calculation but was silently missed. Confidence is deliberately kept low, since the engine only resolves single-cell references and cannot see a driver consumed only through a range formula or an Excel data table.
Named Ranges in Financial Models
A named range in Excel is a cell or range of cells that has been assigned a descriptive name through the Name Manager, allowing formulas to reference the name rather than the cell address. Named ranges improve formula readability and reduce errors from incorrect cell referencing in large models. However, they introduce structural risks when they are deleted, renamed, or allowed to accumulate as an unmanaged inventory: formulas that reference a deleted named range display #NAME? errors, and formulas that reference a renamed named range silently reference the wrong range if the old name is reused with a different definition.