Positions

Positions and placements solve different planning problems.

Position: role metadata and budget intent
Placement: who is actually placed in which org unit

Use both, but do not substitute one for the other.

What a position captures

Position records include:

title
role type
budgeted team (optional — links to a team org unit for planning purposes)
planned FTE
employment type (perm/contractor)
target annual salary or daily rate
currency
effective dates

This is planning metadata used for role structure, matrix grouping, and budget analysis.

Important constraints

Budgeted team is optional. Positions can exist without a team assignment — useful for early role planning before team structure is finalised.
Choosing a budgeted team on a position does not place a person or agent on that team. Operational placement still lives in org_unit_actor and must be managed through placement flows.

Creating positions efficiently

From position create/edit, you can:

search existing teams
create a new team inline when needed
classify by role type for matrix row behavior

This supports fast role design while preserving scenario context.

Scenario and read-only behavior

Position CRUD is scenario-aware:

baseline position edits affect live
scenario edits stay inside scenario
archived/snapshot contexts are read-only

Best-practice flow

Define positions for important seats.
Set role type and budget fields.
Optionally assign a budgeted team.
Place actors via placements.
Validate matrix/charts and scenario delta outputs.

Common mistakes

treating positions as occupancy records
relying on budgeted team to infer home department or team
skipping currency setup before entering salary or rate data