Analyse a model

Once a model has structure in it, the views down the left of an open model are how you interrogate it. They’re all read-only: nothing here changes the model, so click freely.

Summary

The overview. Headcount, how much of it is filled, and what the whole thing costs.

Cost is split into filled and vacant, which is usually the number that matters — not what the organization costs today, but what it costs fully staffed. The unit tree below rolls cost up the hierarchy, so a parent shows the total of everything beneath it and you can expand toward whichever branch looks expensive.

The Summary also reports unmatched positions — ones no cost profile covers, and which are therefore contributing nothing to your total. Treat a non-zero count as a to-do list; the total is understated until it’s zero.

Counts and Costs

Pivot tables — the same shape twice, once for headcount and once for money.

Break the model down by role, role category, level, location, company, or vacancy, against the unit hierarchy, and read off where headcount and spend actually sit. Empty rows and columns can be hidden to get a dense table out of a sparse organization.

Both views also plot a trend when the model has time in it — either across the snapshots on a timeline or across the start and end dates on individual positions. You can plot at each change or at a regular monthly interval. Where a timeline is in play, each column heads a snapshot and clicks through to the model behind it.

Positions shared across several units contribute once to headcount and have their cost divided between those units, so the rollups still add up. There’s a toggle for showing those partial counts explicitly.

Units, Org Chart, Diagram, and Matrix

Four ways of seeing the same structure:

View	Shows
Units	The hierarchy as an editable tree, with a panel for the selected unit’s positions and people.
Org Chart	The reporting structure, drawn from each position’s reports to.
Diagram	Units as cards with their positions inside — the shape of the organization rather than its reporting lines. Toggle which attributes are shown on each position.
Matrix	A crosstab of roles against units, either orientation, for spotting which teams hold which capabilities and where the gaps are.

Slots and People

Slots lists every position in the model as a table: filter by unit, by any attribute, or by whether it’s filled, sort by any column, and export the result to CSV. It’s the view to reach for when the question is a list rather than a shape.

People shows the model from the other side — who’s placed in it, and who in the organization isn’t.

Problems

An automatic review of the model, run each time you open the view. It reports:

Problem	Meaning
Duplicate person	Someone is assigned to more than one position in this model.
Attribute mismatch	A person’s own role, level, location, or company differs from that of the position they occupy.
Reporting cycle	A chain of reports to that loops back on itself.
Orphaned slot	A position that has ended up belonging to no unit.
Excluded person assigned	Someone is placed in the model whom the model’s own person filter excludes.

Several offer a fix in place — combining duplicate assignments or clearing one of them, aligning mismatched attributes in either direction, breaking a reporting cycle, removing orphaned positions.

Not everything reported is a mistake. Somebody deliberately holding two positions, or acting up into a more senior post, will show here and is fine. The view’s job is to make sure it’s a decision rather than an accident.

Audit log

Every model carries its own audit log — what changed, when, and who did it. There’s an organization-wide log as well, covering everything else. For a single position, open its details and switch to the Audit Log tab to see that position’s own history, change by change.

Cost profiles — fixing unmatched positions.
Planning over time — what makes the trend views work.
Compare and merge — analysing two models against each other.