4.2 Position Creation, Restrictions & Availability Dates

4.2 Position Creation, Restrictions & Availability Dates

Quick Answer: Under Workday's Position Management staffing model, an individual Position must be created and approved through the Create Position business process before any recruiting or hiring activity can occur. Every position enforces Position Restrictions (Job Profile, Location, Worker Type, Worker Subtype, and Time Type) that act as strict governance guardrails. Two critical dates regulate the position lifecycle: the Availability Date (the earliest date the position can be posted, recruited, or filled) and the Earliest Hire Date (the absolute earliest calendar date a worker can start). Chronologically, Workday enforces that Earliest Hire Date must be on or after Availability Date.

---

The Position Creation Business Process Workflow

In organizations utilizing Position Management, headcount is strictly regulated. Unlike Job Management—where workers can be hired directly into a supervisory organization up to a general limit—Position Management requires a distinct, persistent Position object to exist for every seat.

Initiating Position Creation

An authorized user (such as an HR Partner, Recruiter, or Manager) initiates the creation of a new position through:

• Related Actions on the target Supervisory Organization -> Organization -> Create Position, or
• Launching the global task Create Position.

Because positions are anchored directly inside supervisory organizations, the initiator must specify exactly one supervisory organization as the structural home for the new position.

Workflow Governance and Approval Routing

The Create Position business process (BP) definition governs the review, approval, and downstream actions required to authorize new headcount. A typical enterprise approval workflow includes:

+-------------------------------------------------------------------------+
|                 CREATE POSITION BUSINESS PROCESS WORKFLOW               |
+-------------------------------------------------------------------------+
| [Initiation: Manager / HR Partner]                                      |
|  - Enters Position Request Reason, Number of Positions, Dates,          |
|    and Position Restrictions (Job Profile, Location, Time Type).        |
|        |                                                                |
|        v                                                                |
| [Action Step: Propose Default Compensation]                             |
|  - System defaults compensation from Job Profile; Compensation Partner  |
|    refines base pay, grade, and bonus plan targets.                     |
|        |                                                                |
|        v                                                                |
| [Review Step: Financial Costing / Accounting Allocations]               |
|  - Cost Center Manager reviews financial worktags and budget impact.     |
|        |                                                                |
|        v                                                                |
| [Approval Step: HR Executive / Finance Leadership]                      |
|  - Final governance sign-off to activate enterprise headcount.          |
|        |                                                                |
|        v                                                                |
| [Event Completion: Position Status Transitions to 'Open / Available']  |
+-------------------------------------------------------------------------+

Position Request Reasons

Workday requires selecting a Position Request Reason when creating a position. These reasons are tenant-configurable and categorize the business justification for headcount expansion:

• New Position > Business Growth
• New Position > Reorganization
• New Position > Strategic Project Initiative
• Backfill / Replacement (used when creating replacement positions in advance of expansions)

---

Deep Dive: Position Restrictions Architecture

Every position created under Position Management houses a set of rules known as Position Restrictions. Position Restrictions define the immutable boundaries of the seat. When downstream staffing transactions (Hire Employee, Contract Contingent Worker, Change Job, Transfer Employee) are executed against that position, Workday auto-populates the restrictions and enforces compliance.

+-------------------------------------------------------------------------+
|                     POSITION RESTRICTIONS CONTAINER                     |
+-------------------------------------------------------------------------+
| 1. Job Profile: Senior Financial Analyst (Determines FLSA & Pay Type)   |
| 2. Location: New York Corporate Headquarters (Drives Tax & Comp Grade)  |
| 3. Worker Type: Employee (Restricts against Contingent Workers)         |
| 4. Worker Subtype: Regular (Excludes Temporary, Interns, Contractors)   |
| 5. Time Type: Full-Time (Requires standard 40 scheduled hours/week)     |
| 6. Qualifications: BS in Finance, 5+ Years Experience (Optional)        |
+-------------------------------------------------------------------------+

The Five Core Position Restriction Attributes

1. Job Profile

The Job Profile defines the functional role, FLSA status, pay rate type, and default compensation grade. A position cannot exist without an assigned Job Profile. The position restriction inherits the characteristics of the job profile, locking the seat into that job catalog definition.

2. Location

Represents the primary physical work location or designated remote business site assigned to the position. This location dictates:

• Regional tax reporting configurations.
• Applicable holiday calendars in Workday Absence Management.
• Geographical pay differentials in Compensation Grade Profiles.

3. Worker Type

A strict, binary classification enforced at the system architecture level:

• Employee: Direct payroll employee of the corporate entity.
• Contingent Worker: External contractor, staff augmentation resource, or consultant managed through a vendor.

Exam Trap Alert: If a position is restricted to Worker Type: Employee, Workday will actively prevent an HR specialist from executing the Contract Contingent Worker task against that position. Attempting to seat a contingent worker in an employee position triggers a hard stop validation error unless the user first executes Edit Position Restrictions.

4. Worker Subtype

Granular classifications configured within the tenant under either Employee or Contingent Worker categories:

• Employee Subtypes: Regular, Temporary, Intern, Fixed-Term, Apprentice.
• Contingent Worker Subtypes: Agency Contractor, Independent Consultant, Outsourced Resource.

5. Time Type

Specifies the operational schedule commitment:

• Full-Time: Typically 30 to 40 standard scheduled hours per week (dependent on statutory definitions and enterprise company configurations).
• Part-Time: Scheduled hours less than the enterprise full-time threshold.

How Restrictions Govern Downstream Staffing Events

When a candidate is hired or a worker transfers into an approved position:

1. Auto-Defaulting: The Hire business process automatically extracts the Job Profile, Location, Time Type, Worker Type, and Worker Subtype from the position restrictions. The user does not need to re-enter this data.
2. Validation Enforcement: If an initiator attempts to alter the Time Type from Full-Time to Part-Time inside the Hire event, Workday evaluates the position restrictions. If the position restrictions allow only Full-Time, the system issues an error: "The selected Time Type does not match the position restrictions."

---

Temporal Governance: Availability Date vs. Earliest Hire Date

Perhaps the single most heavily tested technical nuance regarding Workday position management is the chronological relationship between the Availability Date and the Earliest Hire Date.

1. Availability Date

The Availability Date defines the moment the position becomes an active, viable object in the Workday tenant:

• It governs when a Job Requisition can be created and linked to the position.
• It dictates when the position can be posted to internal or external career sites.
• It represents the date from which recruiting pipelines can begin associating candidate records with the position.

2. Earliest Hire Date

The Earliest Hire Date defines the earliest calendar date on which a worker can functionally begin employment in that position:

• It is the earliest allowable Effective Date for a Hire Employee, Contract Contingent Worker, or inbound Transfer Employee business process.
• A worker cannot have an official start date earlier than the Earliest Hire Date.

The Mathematical and Chronological Golden Rule

Workday enforces a strict programmatic validation rule across these dates:

$\text{Availability Date} \le \text{Earliest Hire Date} \le \text{Effective Hire Date}$

$\text{Earliest Hire Date} \text{ can NEVER precede } \text{Availability Date}$

If an administrator inputs an Earliest Hire Date of May 1, 2026 and attempts to set an Availability Date of June 1, 2026, the Workday UI displays an immediate red validation banner blocking form submission.

Chronological Timeline Example: Advance Pipeline Sourcing

      March 1, 2026                   June 1, 2026                    June 15, 2026
------------+-------------------------------+-------------------------------+------->
            |                               |                               |
            v                               v                               v
    AVAILABILITY DATE               EARLIEST HIRE DATE             ACTUAL HIRE DATE
  - Position active in tenant     - Absolute earliest date       - Incumbent onboarded
  - Requisition opened & posted     worker can start               and seated in position
  - Candidate interviewing        - Cannot start in May!

Enterprise Scenarios: Why Separate Dates Matter

---

Position Title vs. Business Title: Structural vs. Incumbent Designations

Workday maintains a clear distinction between the title of the structural seat and the title of the human being occupying that seat.

Position Title

• Anchor: Bound to the Position Restrictions on the position object.
• Default Source: Auto-populates from the underlying Job Profile title when the position is created.
• Customization: Can be customized on the position restrictions (e.g., Job Profile = Senior Financial Analyst; Position Title = Senior Financial Analyst - Mergers & Acquisitions).
• Persistence: Remains attached to the position even when the seat becomes vacant.

Business Title

• Anchor: Bound to the Worker's Job Record (the incumbent worker).
• Default Source: Inherits from the Position Title (or Job Profile title if no custom position title exists).
• Customization: Can be freely modified using the Edit Business Title task without altering the underlying position restrictions, changing the job profile, or launching a compensation review.
• Visibility: Appears on the worker's profile card, org charts, public directories, and external email signatures.

Summary Comparison

---

Headcount vs. Full-Time Equivalent (FTE) Metrics

Workday tracks workforce capacity through two distinct dimensions: Headcount and Full-Time Equivalent (FTE).

Headcount

• A discrete integer count of distinct human beings or authorized seats.
• In Position Management, each position object represents exactly 1 Headcount ($1.0$).
• A supervisory organization with 10 approved positions has an authorized headcount limit of 10, regardless of whether those positions are full-time or part-time.

Full-Time Equivalent (FTE)

• A continuous mathematical ratio representing scheduled labor hours relative to the organization's standard full-time workweek:

$\text{FTE} = \frac{\text{Position Scheduled Weekly Hours}}{\text{Enterprise Standard Weekly Hours}}$

• Calculation Example: If standard working hours equal 40 per week:
  • A full-time position scheduled for 40 hours has an $\text{FTE} = \frac{40}{40} = 1.0$.
  • A part-time position scheduled for 20 hours has an $\text{FTE} = \frac{20}{40} = 0.50$.
  • A part-time position scheduled for 10 hours has an $\text{FTE} = \frac{10}{40} = 0.25$.

Architectural Rule for Part-Time Positions

Under Position Management, every part-time worker still requires their own individual position object. Two part-time workers scheduled for 20 hours each cannot share a single 1.0 FTE position. Instead, the organization must create:

• Position A: Scheduled Hours = 20 (Headcount = 1, FTE = 0.5)
• Position B: Scheduled Hours = 20 (Headcount = 1, FTE = 0.5)
• Total Impact: Headcount = 2, Total FTE = 1.0.

---

Configuration Walkthrough: Step-by-Step Position Creation

To configure an approved position in Workday, follow this precise administrative sequence:

1. Locate Supervisory Organization: Navigate to the supervisory organization that will house the seat.
2. Initiate Task: Click Related Actions on the supervisory organization -> select Staffing -> Create Position.
3. Specify Request Reason & Quantity: Select a valid Position Request Reason and enter the number of positions (typically 1).
4. Define Availability and Earliest Hire Dates: Ensure Availability Date $\le$ Earliest Hire Date.
5. Establish Position Restrictions:
   • Select the approved Job Profile.
   • Choose the primary Location.
   • Set Worker Type (Employee or Contingent Worker).
   • Choose Worker Subtype (Regular, Temporary, etc.).
   • Set Time Type (Full-Time or Part-Time).
6. Define Costing & Accounting Defaults: (Optional) Designate default Cost Center, Fund, or Program worktags.
7. Submit for Business Process Routing: Route through the configured Create Position business process workflow for compensation review and executive approval.

---

Common Certification Pitfalls & Exam Traps

1. Inverted Availability and Hire Dates: An exam question presents a scenario where an administrator attempts to hire an employee on March 15 into a position with an Earliest Hire Date of April 1. Workday will hard-block this transaction. A worker cannot be hired with an effective date earlier than the Earliest Hire Date.
2. The Worker Type Mismatch Trap: A manager attempts to contract an external consultant into a vacant position that was configured with Worker Type: Employee. The transaction fails. The position restrictions must be modified to Worker Type: Contingent Worker via Edit Position Restrictions before contracting.
3. Business Title Editing Misconception: Test takers often believe that updating a worker's Business Title requires launching Edit Position Restrictions or Change Job. In reality, Edit Business Title is a standalone task that updates the worker's working title without touching the underlying position object.
4. Headcount vs. FTE Part-Time Sharing: An exam item asks: "Can two 0.5 FTE workers be hired into a single 1.0 FTE position in Position Management?" The answer is strictly No. Position Management requires one distinct position per worker (unless temporary overlap is explicitly enabled).