Semantius Logo
← Blueprints
View BlueprintDownload
HCMJune 27, 2026

Organization and Position Management

The org and positions module is where you model the shape of the organization rather than the people in it. Author and publish job profiles, approve and open positions against budgeted headcount, and maintain the org-unit hierarchy through creation, reorganization, merges, and closures. This is the planning surface that recruiting, compensation, and workforce planning all consume. Publishing a job profile opens the door to a requisition; approving a position signals where to hire; reorganizing a unit cascades to access and reporting lines. Get the structure right here and every downstream people process inherits a clean foundation.

Use the Organization and Position Management semantic blueprint

/semantius-admin use the architect, analyst and modeler skills to update the semantius platform with the model specified in https://www.semantius.com/blueprints/hcm-org-positions-semantic-blueprint.md

Entity summary

Name data_object Description
Job Profiles job_profiles Canonical role definitions in the job catalog: title, family, level, responsibilities, required skills, pay range, and FLSA class. Many positions share one profile.
Org Units org_units Nodes in the organizational hierarchy such as divisions, departments, and teams, with manager, cost center alignment, geographic scope, and parent-child links.
Positions hcm_positions Approved org slots with role definition, cost center, reporting line, location, and FTE allocation. Each can be open, filled, or eliminated.
Cost Centers cost_centers Organizational units for cost allocation, with code, manager, hierarchy, and currency, driving variance and departmental reporting.
Financial Plans financial_plans Umbrella records for financial planning artifacts: annual budget, rolling forecast, and long-range plan, with period, version, and approval state.
Job Requisitions job_requisitions Approved requests to hire for a specific role, carrying headcount, level, location, hiring manager, recruiter, and status. 
flowchart TD
  classDef master fill:#d4f4dd,stroke:#27ae60,color:#0b3d20;
  classDef contributor fill:#cfe8ff,stroke:#1976d2,color:#0d3a66;
  classDef consumer fill:#e8def8,stroke:#7b1fa2,color:#3a155d;
  classDef platform_builtin fill:#e0e0e0,stroke:#424242,color:#1a1a1a;
  cost_centers["Cost Centers"]
  job_requisitions["Job Requisitions"]
  hcm_positions["Positions"]
  job_profiles["Job Profiles"]
  org_units["Org Units"]
  financial_plans["Financial Plans"]
  users["Users"]
  org_units -->|"contains"| hcm_positions
  job_profiles -->|"defines"| hcm_positions
  cost_centers -->|"funds"| org_units
  hcm_positions -->|"spawns"| job_requisitions
  org_units -->|"maps_to"| cost_centers
  org_units -->|"rolls_up_to"| org_units
  users -->|"manages"| hcm_positions
  users -->|"leads"| org_units
  users -->|"owns"| job_profiles
  users -->|"owns"| cost_centers
  job_requisitions -->|"has recruiter and hiring manager"| users
  org_units -->|"has members"| users
  class cost_centers contributor;
  class job_requisitions consumer;
  class hcm_positions master;
  class job_profiles master;
  class org_units master;
  class financial_plans consumer;
  class users platform_builtin;
  style cost_centers stroke-dasharray:5 5;
  style job_requisitions stroke-dasharray:5 5;
  style financial_plans stroke-dasharray:5 5;