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.

What a model contains

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.

Model properties

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.
Effective date	The date this structure takes effect. Used to order snapshots — see Planning over time.
Protected	Blocks direct edits. See below.
Private	Restricts who can see it. See below.

Protected models

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

Private models

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 a model

Copying is how a plan starts. You get a full duplicate of the units, slots and reporting lines, and you choose whether the people come with it:

• With assignments — the copy is a faithful snapshot, right down to who sits where. This is what you want for “next quarter, starting from today”.
• Without assignments — same structure, every slot vacant. This is what you want for a design exercise, or a hiring plan where the shape matters and the names don’t yet.

A copy remembers what it came from, so when you later compare or merge it, the original is offered as the default counterpart.

Archiving and deleting

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.

Pinning

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.

Restricting which people a model can use

A model can carry a person filter — a rule limiting which people are offered for assignment and which appear in its people list. A model covering only the Berlin office, for instance, need not offer the whole company in every dropdown.

Related

• Units and slots — what’s inside a model.
• Planning over time — turning models into a dated series.
• Compare and merge — moving changes between models.
• Analyse a model — the views that read a model back to you.