When to split department variance views instead of one company pack
One company-wide pack can bury local signals. Splitting by department works when ownership, calendars, and thresholds differ.
A single company variance pack feels efficient until operations, sales, and shared services talk past each other. Different calendars and different materiality rules belong in different views — with a thin company summary on top.
Split when budget owners never sit in the same review, when thresholds differ by an order of magnitude, or when one department closes later because of volume-based accruals. Keeping them in one scroll creates false comparisons.
Keep a company roll-up for the CFO: total plan, total actual, top five exceptions, and open items. Detail lives in department packs that the relevant controller can defend.
Watch shared cost allocations. If IT or facilities land differently across departments, document the method in both the company and department views so the same baht is not argued twice.
When Flow Workhub commissions a dashboard, we often start with one pilot department, then decide whether a company pack alone is enough. The split is a governance choice, not a styling preference.