Who this is for, and the moment
The change request says “update the opex driver mapping”. The reviewer asks what it touches. Referenced By gives you the next hop. Eight hops later you have a list on a notepad and no confidence it is complete, and the board pack is on it somewhere.
The selection
CAL03 Opex.Forecast Opex in Caldergate FP&A, downstream.
The result
Caldergate FP&A › CAL03 Opex.Forecast Opex 5,017,824 cells · 16.04% of the model's effortModules in reach
| Module | Line items | Nearest | Cells |
|---|---|---|---|
CAL03 Opex | 4 | 1 | 20,071,296 |
CAL07 P&L by Cost Centre | 6 | 3 | 114,912 |
CAL06 Department Summary | 3 | 3 | 7,776 |
CAL11 Reporting Prep | 3 | 4 | 57,456 |
CAL08 Cash Flow | 6 | 5 | 3,456 |
OUT01 Management Pack | 4 | 5 | 76,608 |
OUT02 Board Pack | 1 | 7 | 19,152 |
The path to the board pack
Actions touching modules in reach
| Action | Kind | Module | Process | Last run |
|---|---|---|---|---|
| Export P&L to Board Reporting | export, reads | CAL07 P&L by Cost Centre | Publish Board Pack | 2026-09-08 |
| Export Board Pack | export, reads | OUT02 Board Pack | Publish Board Pack | 2026-09-08 |
Other models, inferred from import names
Board Reporting inferred 2 import actions into DAT01 P&L, DAT02 Board Lines · Workforce Planning inferred 1 import action into Inputs - Settings
Reach stays inside the model: the exports carry no line-item mapping across models, so other models are listed from the import names, as inferred, and never counted as line items. Actions are linked at module level. Saved views, pages, dashboards and line item subsets are not in the exports. Reach describes formula references; it does not prove a value will change.
Evidence drawer · what each chip opens
- Line itemCAL03 Opex.Forecast OpexLine Items export
- ActionExport P&L to Board ReportingActions export
- ActionExport Board PackActions export
Twenty-seven line items, each counted once at its shortest distance. Seven modules, with how many line items each carries and how near it sits. The path from the formula to the board pack, link by link. Two export actions that read modules in reach, both in the Publish Board Pack process, both run on 8 September. Two other models listed from the import names, as inferred.
The evidence
The reach is counted over the dependency closure the grammar builds from the Line Items export, checked against Anaplan’s own Referenced By column (test 6.2, clear on this estate). Actions come from the Actions export and are linked at module level, because the export does not say which line items an action reads.
What to notice
- The count goes in the change request as it is: 27 line items, 7 modules, 2 exports, 2 downstream models to warn. A reviewer can open any row.
- The limits are printed with the result. Reach describes formula references; it does not prove a value will change, and it cannot see saved views or pages. The app says so under every count, so nobody reads the number as more than it is.
- The app draws the same reach as a graph that grows one click at a time. The table is what you paste; the graph is what you explore.

Related
Use cases: Is it safe to delete · Why it was built this way · The fix list.