Financial model review
Check named ranges in financial models
Review named ranges in an Excel financial model. Check their worksheet scope, source cells and period coverage with worked examples and a review checklist.

A formula such as =Units*UnitPrice is easier to read than an unexplained combination of cell addresses. It is useful only if the names point to the intended inputs. A descriptive name can still refer to an old assumption, an incomplete range or a different value on one worksheet.
Review the definition behind the label before relying on it. The following examples are invented and deliberately small, so you can check the expected result independently of the workbook.
Start with one important named assumption
Suppose Forecast!B4 holds 100 units, and the workbook-level name UnitPrice refers to =Inputs!$B$2. That input contains EUR 25. The formula in Forecast!B5 is:
=B4*UnitPrice
Revenue should be EUR 2,500. A useful first review is to locate Inputs!B2, confirm its EUR-per-unit label and compare the value with the approved assumption. The name itself establishes none of those facts.
In a working copy, changing the price to EUR 26 should make this simplified revenue EUR 2,600. If revenue does not move, inspect whether the formula uses another name or a different input. Restore the original price when the test is finished.
This test is more informative than renaming a cryptic input: it checks whether the assumed relationship actually operates. A calculation can look readable while remaining disconnected from the assumption you intended to change.
Inspect Name, Scope and Refers To
In supported desktop versions, open Formulas > Name Manager. Select the relevant name and inspect its definition and scope. Names can refer to cells, constants or formulas, so do not assume every entry represents a visible input cell. Microsoft's Name Manager guide explains these controls.
For each important assumption, record the name, its intended meaning, units, scope and referenced location. Prioritize names used in revenue, costs, financing and key output metrics. You do not need to rename every entry before understanding which ones matter.
An unfamiliar name is not automatically redundant. It may support a table, a formula or another workbook feature. Do not bulk-delete names merely because you cannot see an obvious use in the first worksheet.
The same name can mean different things on different sheets
Excel names can have workbook-wide or worksheet-local scope. A local name can take precedence over an identically spelled workbook name on that worksheet. Microsoft explains name scope and precedence in its names-in-formulas documentation.
Consider a workbook-level UnitPrice pointing to EUR 25, alongside a worksheet-local UnitPrice on Forecast pointing to EUR 30. On Forecast, the unqualified formula =B4*UnitPrice can then use EUR 30, giving EUR 3,000 for 100 units. On a different sheet without that local definition, the workbook-level name can give EUR 2,500 for the same quantity.
Neither result must produce an Excel error. The EUR 500 difference comes from scope. A local definition might be intentional for a separate product, but then its purpose should be clear to the next reviewer.
Inspect both definitions before changing either. Agree whether the assumptions should be shared or distinct, then give them names and references that communicate that decision. Test affected sheets after the change; correcting one displayed total does not prove every dependent calculation is now appropriate.
A valid named range can omit a forecast month
Suppose January, February and March revenue is EUR 1,000, EUR 1,200 and EUR 1,400 in Forecast!B5:D5. A quarterly total using =SUM(QuarterRevenue) should return EUR 3,600 if that name covers all three months.
If QuarterRevenue still refers only to =Forecast!$B$5:$C$5, the formula returns EUR 2,200. The missing EUR 1,400 is not a broken-reference error: the range is valid, but incomplete for the intended period.
Compare each named range's endpoints with the row labels and period headings. This is especially useful after inserting months, appending a year or copying a schedule from another model. A fixed reference does not become complete merely because its name says Quarter or Annual.
For more range and copy checks, use the monthly forecast formula guide. The purpose is to compare the definition with the intended financial scope, rather than infer correctness from tidy labels.
Review broken and external definitions carefully
A definition containing #REF! deserves investigation. Find which deleted or moved input it was meant to reference before selecting a replacement. A definition pointing to another workbook also needs a documented source and an agreed way to maintain access.
Name Manager can filter names with errors, but it does not display every hidden name or every name created through VBA. Its visible list is therefore useful evidence, not proof that every dependency has been reviewed. See the Microsoft guide for these limits, and our external workbook link guide for the dependency questions to ask.
Finish with a focused review record
- List the important named inputs and outputs you inspected.
- Confirm each name's meaning, units, scope and referenced range.
- Investigate duplicate spellings across local and workbook scope.
- Compare range endpoints with the intended months or business units.
- Test one controlled input change and restore the approved value.
- Record unresolved definitions rather than guessing replacements.
FinModelCheck does not currently provide a complete audit of defined names, scope conflicts or named-range completeness. It checks supported saved Excel errors, broken references, external workbook links and embedded numeric coefficients without recalculating Excel. No Findings does not establish that named assumptions are correct.
Try the checker for its supported inspection and view the example report. The complete PDF is free in your current valid owning browser session without registration. Keep the manual name review alongside that report when handing over a financial model.


