ATS May 27, 2026
ATS-RECRUITMENT-PIPELINE
Requisitions → postings → applications with pipeline-stage lifecycle. Realizes REQ-MGMT and CANDIDATE-EXP (application flow slice). Embedded-masters `candidates`, optionally `hcm_positions` and `org_units` for canonical position/org context.
Use the ATS-RECRUITMENT-PIPELINE semantic blueprint
/semantic-model-deployer deploy https://www.semantius.com/blueprints/ats-recruitment-pipeline-semantic-blueprint.md Customize this ATS-RECRUITMENT-PIPELINE blueprint
/semantic-model-analyst customize https://www.semantius.com/blueprints/ats-recruitment-pipeline-semantic-blueprint.md Entity summary
| Name | Description |
|---|---|
| Applications | A candidate's submission against a specific requisition. Carries pipeline stage, status (active / rejected / withdrawn / hired), source, and the full evaluation history. |
| Job Postings | Published, candidate-facing version of a requisition on a career site or job board. One requisition can have many postings (per board, language, or region). |
| Job Requisitions | Approved request to hire for a specific role. The master ATS work item, carries headcount, level, location, hiring manager, recruiter, and status (draft / open / on_hold / filled / cancelled). |
| Candidates | Person known to the recruiting org, with or without an active application. Carries contact details, resume, tags, GDPR consent, and source. Distinct from Employee until hired. |
| Job Profiles | Canonical role definition in the job catalog: title, family, level, responsibilities, required skills and competencies, pay range, FLSA classification. Distinct from positions (which are slots referencing a profile). Many positions share a single job profile. |
| Locations | - |
| Org Units | Node in the organizational hierarchy: division, business unit, department, team. Carries manager, cost center alignment, geographic scope, and parent/child relationships. HCM masters the operational hierarchy; EPM contributes the cost-center mapping (which would be Finance-mastered once a Finance/GL domain is loaded). |
| Positions | Approved slot in the org - a 'chair' with role definition, cost center, reporting line, location, and FTE allocation. Distinct from job_profiles (the catalog definition) and from employees (the person filling the slot). A position can be open, filled, or eliminated. SWP designs future positions via org_designs; HCM operationalizes them once approved. |
| Position Demand Forecasts | Projected need for specific roles derived from the capacity model: which positions, when, where, at what level. Feeds the requisition pipeline - approved demand becomes an authorised requisition in ATS via the headcount.approved handoff. |
| Predictive Models | ML / statistical model outputs deployed in PA: flight-risk scores, performance trajectory, internal-mobility likelihood. Carries the model identifier, training window, target metric, and the materialized scores per employee. Consumes employees and employment_events as features. |
| Project Resource Allocations | Forward-looking resource commitment plan (skill, planned utilisation %, effective period) - distinct from executed assignments. |
flowchart TD classDef master fill:#d4f4dd,stroke:#27ae60,color:#0b3d20; classDef embedded_master fill:#fff4cc,stroke:#c79100,color:#5b4500; classDef consumer fill:#e8def8,stroke:#7b1fa2,color:#3a155d; classDef platform_builtin fill:#e0e0e0,stroke:#424242,color:#1a1a1a; job_requisitions["Job Requisitions"] job_postings["Job Postings"] job_applications["Applications"] candidates["Candidates"] hcm_positions["Positions"] org_units["Org Units"] locations["Locations"] predictive_models["Predictive Models"] position_demand_forecasts["Position Demand Forecasts"] project_resource_allocations["Project Resource Allocations"] job_profiles["Job Profiles"] users["Users"] org_units -->|"contains"| hcm_positions job_profiles -->|"defines"| hcm_positions hcm_positions -->|"spawns (opt)"| job_requisitions job_profiles -->|"feeds (opt)"| job_postings job_requisitions -->|"is advertised through"| job_postings job_requisitions -->|"receives"| job_applications job_postings -->|"is applied to via"| job_applications candidates -->|"submits"| job_applications job_requisitions -->|"updates (opt)"| position_demand_forecasts org_units -->|"rolls_up_to (opt)"| org_units locations -->|"rolls_up_to (opt)"| locations position_demand_forecasts -->|"triggers (opt)"| job_requisitions users -->|"manages (opt)"| hcm_positions users -->|"leads (opt)"| org_units users -->|"owns (opt)"| job_profiles job_requisitions -->|"has recruiter and hiring manager"| users job_applications -->|"has owning recruiter"| users org_units -->|"has members (opt)"| users locations -->|"houses (opt)"| users users -->|"prepares (opt)"| position_demand_forecasts users -->|"allocates"| project_resource_allocations class job_requisitions master; class job_postings master; class job_applications master; class candidates embedded_master; class hcm_positions embedded_master; class org_units embedded_master; class locations embedded_master; class predictive_models consumer; class position_demand_forecasts consumer; class project_resource_allocations consumer; class job_profiles embedded_master; class users platform_builtin; style hcm_positions stroke-dasharray:5 5; style org_units stroke-dasharray:5 5; style locations stroke-dasharray:5 5; style predictive_models stroke-dasharray:5 5; style project_resource_allocations stroke-dasharray:5 5;