Capabilities/Workforce Management
People change. The organizational model has to preserve responsibility through that change.
Workforce management is how an organization holds its structure steady while the people in it move. It separates the position from the person, the assignment from the name, and responsibility from both — so that when someone arrives, moves or leaves, the record of who was accountable stays intact.
The memory problem
When people move, meaning tends to move with them.
In many organizations the structure lives inside the people who happen to occupy it. A position is understood as whoever currently holds it; responsibility is remembered as a name rather than a seat. When that person changes role or leaves, the position’s history, its reporting line and the record of who was accountable go blurry.
Directories, personnel files and recruitment tools each hold a piece of this, but none of them holds the organization as a structure that persists. The question is not how to store people. It is how to model positions, assignments and responsibility so the organization keeps its shape while the people in it change.
The living organization model
A structure that persists, an assignment that changes, a responsibility that belongs to neither alone.
The model separates what stays from what moves. Organizational units, positions and locations form a structural layer that persists. People and assignments form a layer that changes as the organization is staffed. Responsibility connects the two — and it belongs to an authorized assignment, not to a person’s name and not to an empty position. Identity and access read this model to decide what a person may do; they consume it, they do not own it.
Persists — the structural layer
Changes — the assignment layer
Structural layer
Remains defined as people and assignments change.
Organizational unit
Units and the reporting relationships between them — the line of the organization.
Position
A defined seat of work inside a unit. It remains when the person in it leaves.
Location
Where a position operates. It can change without dissolving the position.
Responsibility
Belongs to an authorized assignment. Not to a name on its own, and not to a position left empty.
Assignment layer
Changes as the organization is staffed and re-staffed.
Person
A known individual the model refers to — not the responsibility itself.
Assignment
Places a person into a position for a period, with the roles that period carries.
Continuity register
A position is established within a unit.
An assignment places a person into the position, and responsibility begins.
The assignment ends. The person moves on; the position and its record remain.
The unit is restructured. Earlier assignments keep their meaning and are not erased.
The elements shown are structural, not a personnel file. The model describes how positions, assignments and responsibility relate; it does not publish who holds them.
Responsibility through change
The organization keeps its shape while the people in it move.
A person may change position
A move updates the assignment, not the identity of the position. The seat stays defined; who occupies it is what changed.
A position outlives its holder
When a person leaves, the position remains open and described. It is not deleted with the departure, and it does not carry the previous holder forward as though nothing happened.
Responsibility follows the assignment
What a person is accountable for comes from an authorized assignment for a period, not from their name. When the assignment ends, so does the responsibility it granted.
Structural change preserves history
Units can be merged, split or renamed. Past positions and assignments keep the meaning they held at the time, so the organization can be re-drawn without erasing what it used to be.
Where this sits
This defines the structure. It does not decide the action.
Three disciplines meet around the same people, and it helps to be exact about which does what.
Workforce management defines the organizational and personnel structure — units, positions, assignments and responsibility. Identity and access decides what a person is permitted to do, reading that structure. Enterprise resource planning connects this workforce context to the wider operations of the organization.
This page is about the structure of the organization as it changes. What a person may do with that structure, and how it connects to finance and operations, are neighbouring disciplines — linked here, not folded in. This is not a module inside a larger product.
Records and lifecycle
The record of the organization outlives any one version of it.
Workforce records
Units, positions, people and assignments are held as governed records — described, versioned and retrievable — not as a directory that only shows the present.
Position and assignment history
Every position and every assignment keeps its own history, so an earlier structure can be read as it stood, not only as it is now.
Presence and availability
Where the work calls for it, attendance and leave are recorded against assignments as facts about a period — kept in proportion, never as a public account of a person.
Controlled organizational change
Restructures, new units and redrawn reporting lines are made as deliberate, recorded changes, so the model can evolve without losing the thread of what came before.
Workforce lifecycle
A person’s relationship to the organization opens, changes and closes. The model follows that arc through assignments, keeping the record of each stage rather than discarding it at the end.
Connections
The structure other systems read.
Identity and access
Access decisions read positions and assignments to establish what a person may do. The structure is defined here; the permission is decided in identity and access.
Finance and operations
Budgets, procurement and day-to-day work attach to units, positions and assignments, so cost and activity carry the organization’s real structure. That wider connection is enterprise resource planning.
Reporting
Workforce visibility is read from these governed records — how the organization is shaped, where positions sit, how assignments have moved — through reporting and business intelligence, without re-keying people into a separate system.
Describe the organization as it actually changes.
Bring the units, the positions and the way responsibility moves through them. The model is engineered around how your organization is structured and re-structured, not around a fixed picture of an org chart.