Most models repeat the same logic for several things: departments, products, channels, debt tranches, customer cohorts. In a spreadsheet that is a block of rows copied per element. In Layerz it is one line bound to a list.
A list and its elements
A list is a named registry of elements (Departments: Sales, Product, G&A), at most 500 of them. A line bound to it (its liste_ref) holds one series per element. Assumptions, formulas and balances can be bound to a list.
Salaries[i] = Headcount[i] * Average salary[i]
Inside a list-mode formula, Item[i] is the current element's value. A bare reference to a list line, Headcount, is always its total across the elements.
Totals and subscripts
- The total of a list line is computed and readable by any formula, whether its total row is displayed or not.
- A subscript reads one element:
Salaries[`Sales`]. Lags apply to subscripts:Salaries[`Sales`]_Y-1. - A rate list (prices, percentages) folds by average instead of sum when the line carries
aggregation: "average".
Mapping between lists
An element of one list can map to elements of another: a Groups list whose Banks element maps to Bank 1 and Bank 2 of a Creditors list. A subscript then rolls up the mapped elements, like a SUMIF:
Bank repayments = Repayment[`Banks`]
Declare a mapping once, on either side; it serves both directions.
Patterns
- Seasonality:
Revenue[i] = Annual revenue[i] * Seasonalitywith a monthly curve. - Cohorts and ramp-ups: a per-element offset, auto-filled by
LIST_INDEX, reads a curve at each cohort's age. - Per-element roll-forward:
Stock[i] = Flow[i] + Stock[i]_M-1, or a list-mode balance. - Allocation:
G&A[i] = Shared G&A * Revenue[i] / Revenue.
Lists are not scenarios
A list is a dimension of the plan (who, what). A scenario is another version of the plan (what if). Scenarios are branches, never list elements.