Skip to content

Models

A model is one version of your organizational structure: a tree of units, the positions inside them, and who fills those positions. A workspace holds as many models as your plan allows, and they are independent — editing one never changes another.

That independence is the whole idea. One model can describe how the organization looks today while another describes how you’d like it to look next quarter, and Resorcerer can tell you precisely how they differ and what the difference costs.

Units The hierarchy — departments, teams, squads. See Units and slots.
Slots Positions. Each belongs to at least one unit, carries attributes, and may have a person in it.
Assignments Which person sits in which slot, in this model.
Reporting lines Which slot reports to which, drawn as the org chart.

What a model does not contain is the raw material it’s built from. People, roles, levels, locations, companies, and cost profiles all live at the organization level and are shared by every model. Deleting a model never deletes a person.

Field Notes
Name How the model is identified everywhere.
Summary A short line shown in the models list.
Description Longer notes, written in Markdown.
Labels Tags you define, for filtering the list — draft, approved, FY26. The same labels classify units.
Effective date The date this structure takes effect. Used to order the points on a timeline — see Planning over time.
Protected Blocks direct edits. See below.
Private Restricts who can see it. See below.

A protected model can’t be edited directly. Units, slots, and assignments are all frozen; the name, description, and labels stay editable.

What it does still accept is a merge. That combination is the point: mark the model that represents your real organization as protected, and the only way anything changes is by being reviewed and merged in. Nobody drags a team into the wrong place while clicking around.

Action Unprotected Protected
Edit units and slots Yes No
Assign people Yes No
Merge changes in Yes Yes
Edit name, description, labels Yes Yes

A protected model can also be made live: Resorcerer then watches your people directory and turns every joiner, leaver, move, and attribute or manager change that affects it into a reviewable sync proposal, merged in the same way as any other change — instead of anyone editing the model directly. Any number of models can be live at once, each with its own people in scope, unit source, and review rules, so a company-wide chart and a model per region can all stay current side by side. A live model carries a Live badge, and it can’t be un-protected, archived, or moved to the trash until live sync is turned off in its Live sync dialog — press Live in the model’s header to open it. See Keep a model live.

By default every model in the workspace is visible to everyone in it. Marking a model private limits it to organization admins and the people you grant access to explicitly, from Manage access on the model.

Use it for a restructure that isn’t ready to be seen, or for planning that involves individuals by name.

Copying is how a plan starts. You get a full duplicate of the units, slots and reporting lines. There’s no option to leave the people out, so check the copy before you share it: if its slots are filled, the copy carries those names. For a design exercise, or a hiring plan where the shape matters and the names don’t yet, vacate the slots in the copy.

A copy remembers what it came from, so when you later compare or merge it, the original is offered as the default counterpart. A model that wasn’t copied is offered your live model instead, when the workspace has exactly one.

Archiving hides a model from the default list while leaving it fully readable — the right home for last year’s plans. Deleting removes it from the list and sends it to the trash, where it can be restored until it’s purged.

A snapshot is a read-only copy of a model taken at a moment — before a sync proposal is applied, on a schedule, or whenever you press Snapshot now. A model’s snapshots are listed on its Snapshots tab rather than in the models list, even with Show archived on, and they don’t count toward your plan’s model limit. Copy a snapshot to get an ordinary model you can edit.

Pinning a model puts it at the top of the models page for quick access. It’s a per-workspace convenience and changes nothing about the model itself.

Every model offers every person in your people directory for assignment, and its People view lists them all. There is no per-model person filter: if you want a model to follow only part of the organization — the Berlin office, say — make it live and set its people in scope. That scope decides who produces sync proposals for the model and nothing else; it never hides anyone from assignment.