Skip to content
CodelessOps

/architect · Use cases · Change something

The reach of a change

"What does a change to Forecast Opex touch?"

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

SelectionCAL03 Opex.Forecast Opex, downstream
Selection Caldergate FP&A › CAL03 Opex.Forecast Opex 5,017,824 cells · 16.04% of the model's effort
IF ITEM(Accounts) = Accounts.'6100 Rent' THEN 'INP02 Opex Drivers'.Rent ELSE IF ITEM(Accounts) = Accounts.'6110 Rates' THEN 'INP02 Opex Drivers'.Business Rates ELSE IF … ELSE 0 (12 branches)
Line items reached271 direct · 26 indirect
Modules7in this model
Links deep81 · 1 · 4 · 5 · 7 · 4 · 3 · 2 by distance
Footprint20.35Mcells in reach

Modules in reach

ModuleLine itemsNearestCells
CAL03 Opex4120,071,296
CAL07 P&L by Cost Centre63114,912
CAL06 Department Summary337,776
CAL11 Reporting Prep3457,456
CAL08 Cash Flow653,456
OUT01 Management Pack4576,608
OUT02 Board Pack1719,152

The path to the board pack

Forecast OpexOpexOpex GBPCAL07 · OpexCAL07 · EBITDACAL11 · EBITDAOUT01 · EBITDAOUT02 · EBITDA

Actions touching modules in reach

ActionKindModuleProcessLast run
Export P&L to Board Reportingexport, readsCAL07 P&L by Cost CentrePublish Board Pack2026-09-08
Export Board Packexport, readsOUT02 Board PackPublish Board Pack2026-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
✓ Counted over the estate's closure: every line item once at its shortest distance, modules rolled up, actions at module level, other models from import names.
A real result, re-set for this page. Real app, fictional estate, 12 October 2026.

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.

The Dependencies page: the reach of a change to Forecast Opex drawn as a graph, with the counts beside it

Real app, fictional estate, captured 8 October 2026.

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

Run Anaplan in-house?

Start with the Model Health Check on your own exports.

The 42 tests and the action plan run free, hosted or on your own machine, and nothing is stored. Then give me 30 minutes and bring the three questions you would ask about your estate.