Who this is for, and the moment
The FD asks whether the model is any good. The honest answer is a list of things to look at, with the evidence for each, and an equally honest list of what could not be checked. Not a score. The 42 tests are that list, run the same way on every model, with Anaplan’s own checklist wording behind each one.
The question
Every test, every model, on the active snapshot.
The result
| Area | Tests | Found | Clear |
|---|---|---|---|
| 1 Performance and size. Where calculation time and cells go, and the formula patterns Anaplan documents as expensive. | 8 | 8 | 0 |
| 2 Usage and leftovers. What nothing appears to read: candidates to ask about, never verdicts. | 5 | 4 | 1 |
| 3 Dependencies and change impact. What depends on what, inside a model and between models. | 5 | 5 | 0 |
| 4 Correctness and maintainability. Totals that may be wrong, repeated logic, and formulas the next builder has to decode. | 17 | 13 | 4 |
| 5 Imports, exports and processes. What loads the model, what has stopped running, what sits outside every process. | 4 | 3 | 1 |
| 6 How far to trust the analysis. Checks the report runs on itself, so every finding says how strong its evidence is. | 3 | 0 | 3 |
Every test
| # | Test | Result |
|---|---|---|
| 1.1 | Where calculation effort concentrates | found · 3 Workforce Planning not run: needs the Calculation Effort column |
| 1.2 | SUM combined with LOOKUP or SELECT | found · 1 |
| 1.3 | Large text line items | found · 5 |
| 1.4 | FINDITEM on a large line item | found · 1 |
| 1.5 | Text joins on a large line item | found · 2 |
| 1.6 | Per-item functions repeated on every cell | found · 10 |
| 1.7 | Line items with a dimension their formula does not use | found · 12 |
| 1.8 | Where the cells are | found · 4 |
| 2.1 | Modules nothing reads | found · 7 |
| 2.2 | Unread modules that repeat a module in use | clear |
| 2.3 | Calculated line items nothing reads | found · 5 |
| 2.4 | Data loaded but never read | found · 1 |
| 2.5 | Names that say leftover | found · 4 |
| 3.1 | Line items with the widest change impact | found · 1 |
| 3.2 | Pass-through chains | found · 4 |
| 3.3 | Circular references | found · 1 |
| 3.4 | Which model feeds which | found · 6 feeds |
| 3.5 | Dimensions shared across models | found · 7 |
| 4.1 | The same calculation under two names | found · 2 |
| 4.2 | Line items that only copy another | found · 14 |
| 4.3 | Formulas that differ in exactly one place | clear |
| 4.4 | Identical formula text that cannot be compared | clear |
| 4.5 | The same line item and formula in more than one model | found · 8 |
| 4.6 | Formulas with more than 10 IFs | found · 1 |
| 4.7 | Hard-coded numbers in formulas | found · 9 |
| 4.8 | Very long formulas | found · 1 |
| 4.9 | SELECT on a fixed period or version | found · 4 |
| 4.10 | DIVIDE() where a zero divisor shows Infinity | found · 15 |
| 4.11 | Subsidiary views used in calculation | found · 2 |
| 4.12 | Summaries on line items nothing reads | found · 37 |
| 4.13 | Modules with more than 50 line items | found · 1 |
| 4.14 | Empty modules | found · 1 |
| 4.15 | Modules without notes | found · 4 |
| 4.16 | Percentages whose totals are added up | clear |
| 4.17 | The odd one out in a run of matching formulas | clear |
| 5.1 | Imports and exports outside every process | found · 12 |
| 5.2 | Imports and exports with no recent run | found · 7 |
| 5.3 | Imports and exports never run | clear |
| 5.4 | Several imports loading one target | found · 1 |
| 6.1 | Formulas the parser did not follow | clear · 0 |
| 6.2 | Agreement with Anaplan's own Referenced By | clear · 0 |
| 6.3 | Input checks on the files | clear · 0 |
A test that found something is an observation or a review candidate, never a verdict; clear means the pattern was not found in these exports; not run means an export or column the test needs is missing, never that the model is clear.
Evidence drawer · what each chip opens
- Test6.2 Agreement with Anaplan's own Referenced Byclear
- Test6.1 Formulas the parser did not followclear
- Rule42-test catalogue, anaplan-estate v0.2.0checks.py
Six areas, from performance and size through to the three checks the report runs on itself. Thirty-three tests found something to review. Nine came back clear. One partial gap: calculation effort could not be assessed for one model because its export predates the Calculation Effort column, and the app names the owner note that explains why.
The evidence
The catalogue is one numbered registry, published in the Model Health Check and run unchanged inside the Architect. The three coverage checks are the ones to read first: 0 formulas the parser did not follow, 0 disagreements with Anaplan’s own Referenced By, 0 input problems. Below 95% agreement on 6.2 every dependent finding would be downgraded. On this estate it came back clear.
What to notice
- Found is not failed. The app’s own note under the table: a test that found something is an observation or a review candidate, never a verdict; clear means the pattern was not found in these exports; not run means a column the test needs is missing, never that the model is clear.
- The biggest counts are housekeeping: 37 summaries on line items nothing reads, 15 DIVIDE() calls that would show Infinity on a zero divisor. Those never compete for the plan. The plan is the next page.
- Clear is reported with the same prominence as found. Nine tests passed, and the FD gets to see which.
Related
Use cases: The fix list · What nothing reads · What did you test. Technical: Model Health Check.

