Study guide
4.1 Position Management Staffing Model
Workday Pro HCM Core Certification Exam
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts & Format 1.2 Eligibility, Learning Path & Access 1.3 Study Strategy & Blueprint Map
2 Navigation & Business Objects
2.1 Navigation Techniques in Workday 2.2 Business Objects & Finding Data
3 Organizations & Hierarchy
3.1 Organization Types & Subtypes 3.2 Supervisory Organizations & Reporting Structure 3.3 Cost Centers, Company Hierarchies & Locations 3.4 Leadership Roles & Worker Organization Assignments
4 Staffing Models
4.1 Position Management Staffing Model 4.2 Job Management Staffing Model 4.3 Hiring Restrictions on Organizations
5 Job Profiles & Job Structure
5.1 Creating & Editing Job Profiles 5.2 Job Profiles, Jobs, Positions & Workers 5.3 Job Families, Family Groups & Job Requisitions
6 Compensation Fundamentals
6.1 Compensation Framework Components 6.2 Eligibility Rules & Compensation Defaulting 6.3 Packages, Grades & Grade Profiles 6.4 Salary Plans, Allowance Plans & Worker Comp Events
7 Jobs, Positions & Staffing Events
7.1 Creating Positions & Position Hiring Restrictions 7.2 Managing Filled, Unfilled, Close & Freeze 7.3 Hire Process End-to-End 7.4 Job Changes & Additional Staffing
8 Termination & Contingent Workers
8.1 Terminate Employees 8.2 Contracting Contingent Workers 8.3 Ending Contingent Worker Contracts
9 Configurable Security
9.1 Functional Areas, Domains & Business Processes 9.2 User-Based, Role-Based & Workday-Assigned Groups 9.3 Domain Security Policies 9.4 BP Security Policies, Org Access & Activation
10 Business Process Framework
10.1 Organizations, Security & BP Relationships 10.2 Default, Org-Specific & Rule-Based Definitions 10.3 Definition, Type, Event & Step
11 Business Process Steps & Approvals
11.1 Actions & Subprocesses 11.2 Approvals & Approval Chains 11.3 Completing Tasks During Business Processes
12 Business Process Configuration
12.1 Condition Rules 12.2 Advanced Routing, Labels & Help Text 12.3 Custom Notifications 12.4 Step Ordering Letters & Validation Conditions
13 BP Management & Security
13.1 Mass and Individual BP Management 13.2 BPs and Configurable Security Interaction
14 Report Writer Fundamentals
14.1 Standard Reports & Copy/Modify 14.2 Building Custom Reports: Index vs Standard 14.3 Sorting, Filtering & Prompts 14.4 Report Security, Sharing & Ownership
15 Advanced Reporting & Calculated Fields
15.1 Scheduling Reports 15.2 Matrix Reports 15.3 Discovery Boards 15.4 Calculated Fields & Report Performance
4.1 Position Management Staffing Model
Key Takeaways Explain This Topic AI
Position Management creates persistent Position seats in a Supervisory Organization that exist independent of any Worker and support seat-level headcount control.
In Position Management you typically Create Position (with position restrictions) before Hire can fill that seat; one filled position maps to one primary worker occupancy at a time.
When a Worker terminates or leaves a position, the Position remains vacant unless you close or freeze it—persistence is the hallmark of this model.
Use Position Management when finance and workforce planning need budgeted seats, vacancy tracking, and multi-step approval before hiring capacity exists.
Staffing model is set on the Supervisory Organization; changing it later on a live org is difficult, so design the model deliberately at create time.
Last updated: September 2026
4.1 Position Management Staffing Model
Study index: T-numbers here refer to this guide’s index of an older Workday topic list. They are not current Workday task IDs or published exam weights.
Quick Summary: Position Management is the staffing model that treats every seat as a durable Workday Position object. You create and approve positions with restrictions, hire workers into those seats, and keep the seat when someone leaves—so headcount, vacancy, and budget control live at the position layer rather than only on the worker.
Staffing Models sit inside HCM Fundamentals (a current published HCM Core concept). Older-guide study topics T10–T14 all depend on one design fact: every Supervisory Organization uses a staffing model that governs how workers enter the org. The two models to differentiate are Position Management and Job Management . This section deep-dives Position Management (T11); the next section contrasts Job Management and formal differentiation (T10, T13).
What a Staffing Model Controls
A staffing model is not a security group and not a job catalog object. It is the rule set on a Supervisory Organization that answers:
Must a Position exist before Hire?
Does a seat survive when the worker leaves?
Where do hiring limits and default attributes live—on each position, or on the organization?
Concept What it is Where it is set
Staffing model Position Management or Job Management (tenant design) Supervisory Organization (at create / staffing attributes)
Position Discrete seat in a Sup Org (Position Management) Create Position / Edit Position Restrictions
Job Profile Reusable catalog template (title, grade, qualifications) Job Profile setup—not the staffing model itself
Hiring restrictions Rules that constrain who/what can be hired Position (Position Mgmt) and/or organization (esp. Job Mgmt)
Exam trap: Job Profile ≠ Position. A Job Profile is the template; a Position is the specific seat that uses a profile (and other restrictions) inside a Supervisory Organization.
- Characteristics of Position Management
- Persistent seats ("seat on the bus")
In Position Management , each Position is a first-class business object that can exist before anyone is hired and after someone leaves. Think of numbered seats: seat 12A still exists if the passenger gets off the bus. That persistence enables:
Vacancy tracking — open/unfilled positions are reportable objects, not just "headcount is short."
Seat history — successive incumbents can be associated with the same position ID over time for workforce planning narratives.
Pre-hire capacity — recruiters and managers work against an approved vacant seat, not only a vague departmental wish.
One worker per primary seat (typical rule)
Under Position Management, a filled position is occupied by one primary worker at a time (standard design). Overlaps, dual occupancy, and special cases can appear in advanced staffing, but for exam fundamentals assume: one open or filled primary seat = one designed occupancy unless the scenario explicitly teaches an exception.
Seat-level attributes via position restrictions
When you create or edit a position, you set position restrictions (and related organization assignments) that describe the seat—not the person temporarily sitting in it. Typical restriction dimensions include:
- Job Profile (and sometimes related job catalog linkage)
- Location
- Worker type / time type expectations (employee vs contingent context as designed)
- Organization assignments such as Cost Center, Company, Region (alongside the Supervisory Organization)
- Compensation-related defaults where the design uses position-level defaults
Those restrictions drive Hire and Change Job validation: you cannot casually hire a profile or location that the position does not allow without first changing restrictions (subject to security and business process).
Headcount control by design
Position Management's strategic value is enforced capacity . In a pure Position Management supervisory org, you generally cannot hire into capacity that does not exist as an open position . Creating a new seat often requires a Create Position business process with approvals (HR, finance, manager—per tenant BP design). Finance partners like this model because payroll dollars map to budgeted seats rather than unbounded hire volume.
When to Use Position Management
Prefer Position Management when… Avoid / reconsider when…
Roles are budgeted seat-by-seat (corporate HQ, regulated clinical ratios, leadership) High-velocity seasonal or storefront hiring would drown HR in Create Position traffic
Vacancy rate and time-to-fill by seat matter You only care that total org headcount stays under a soft cap
Seat-specific location, grade, or security-sensitive attributes differ across peers Every hire in the org is interchangeable under the same job profile
Finance must approve capacity before recruiting Speed of hire is more important than seat-level audit
Hybrid reality: Many tenants use Position Management for corporate and management orgs and Job Management for high-turnover frontline orgs. Workday allows different models on different Supervisory Organizations; the configuration decision should match the control vs speed trade-off, not to force one model enterprise-wide.
Position Lifecycle Overview
Memorize the lifecycle narrative for T11 and later Jobs & Positions tasks (T28–T31). Create Position → (Open / Unfilled)
- │
- ├── Hire / Staff into Position → Filled
- │ │
- │ └── Worker leaves (Terminate, Transfer out, etc.)
- │ │
- │ └── Position becomes Vacant again (unless closed)
- │
- ├── Freeze Position → hiring blocked while frozen
- └── Close Position → seat retired; not available to fill
- Lifecycle stages in plain language
Create Position — Establish the seat in a Position Management Sup Org with restrictions and org assignments. Capacity now exists as an unfilled position.
Open / available to fill — Recruiting may open a requisition against the position (tenant-dependent); Hire targets that position ID.
Filled — Worker occupies the position; position still exists as the seat of record.
Vacant after exit — On termination (or other leave of the seat), the Position remains and can be backfilled or deliberately closed/frozen. This is the exam contrast with Job Management, where no persistent empty seat remains.
Freeze — Temporarily prevent staffing into the position without permanently retiring it (planning freezes, reorganizations).
Close — End the seat's life as an available capacity object; use when the budgeted role is eliminated.
Configuration scenario: Apex Manufacturing places Plant Leadership under Position Management. Finance approves Create Position for "Plant Controller — Plant 3" with Cost Center Plant3-Ctrl and Location Plant 3 HQ. Recruiting opens a requisition against that vacant position. After hire, the controller resigns; the position stays open. HR reuses the same seat for the backfill instead of inventing a new headcount story. If the plant is sold, they close the position rather than leave an eternal vacancy.
Administrative Trade-offs
Position Management is powerful but not free:
More transactions: Create Position, Edit Position Restrictions, Close/Freeze, plus Hire.
Less improvisation: Two great candidates and one seat still means one hire until a second position is created and approved.
Reporting discipline: Vacancy and headcount reports assume positions are maintained—orphaned open positions pollute dashboards.
Exam trap: Termination does not auto-delete the position, auto-convert the org to Job Management, or reverse all downstream events. The seat stays unless you close or freeze it per process.
Practical Mental Checklist (Exam)
When a stem says "need headcount control," "budgeted seat," "vacant position after termination," or "create position before hire," the model is Position Management . When a stem says "no persistent seat," "high-velocity hire," or "restrictions only at org level," you are in Job Management territory (next section).
Master Position Management as the control-heavy default for corporate design, then contrast it cleanly with Job Management so T10 differentiation questions become automatic.