ORGONAUT
Login Signup
Docs
Org model
Positions

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
  • assigned actor (optional)
  • 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.

Holding a position

Assigning an actor (person, robot, or agent) to a position is the mechanism for defining their role metadata, such as their official title and role type.

Unique occupancy

An actor can hold only one active position at a time within a specific scenario or the Live Baseline. Orgonaut enforces unique occupancy:

  • Assigning an actor to a new position automatically releases them from their previous position in that same context.
  • This ensures that role-based metrics and matrix views reflect a clear "one role per contributor" model.

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 (structural membership) is managed through Placements and is independent of position occupancy.

Creating positions efficiently

Adding or editing a position opens a wide modal from the Positions list, Charts/Org Units add menus, scenario add menus, and Position profile actions. The modal keeps you on the current screen after saving.

From the position modal, you can:

  • search existing teams
  • create a new team inline when needed
  • classify by role type for matrix row behavior
  • set budgeted team, planned FTE, budget fields, effective dates, and structured metadata from Advanced

This supports fast role design while preserving scenario context.

Dedicated Position create and edit pages are no longer part of the web workflow; use the in-page Add Position and Edit Position actions instead.

Scenario and read-only behavior

Position CRUD is scenario-aware:

  • Live Baseline position edits affect live data.
  • Scenario edits stay inside the scenario context.
  • Archived and snapshot contexts are read-only.

Best-practice flow

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

Common mistakes

  • Treating positions as occupancy records: Positions are for role metadata. Structural membership is managed via Placements.
  • Relying on budgeted team to infer home department or team: Budgeted team is planning intent. Always use Placements for canonical structural reporting.
  • Skipping currency setup: Ensure currency is configured before entering salary or rate data to avoid budget inconsistencies.