3.3 Job Changes: Transfers, Promotions & Lateral Moves

The Unified Change Job Framework

In legacy enterprise HR systems, modifying an employee's role required distinct, disconnected transactions: one screen for a transfer, a separate screen for a promotion, another for a location change, and yet another for a compensation adjustment. Workday eliminates this fragmentation through the Change Job business process (Change Job).

Change Job is an architectural framework that consolidates all internal talent mobility, organizational transfers, career progressions, and administrative job data updates into a single, unified, dynamically branching business process. Depending on the data entered at initiation, Workday dynamically determines which screens to display, which sub-processes to trigger, and how approvals must route across management hierarchies.

Primary Event Classifications Under Change Job

While executed under the singular Change Job process definition, transactions fall into distinct operational types:

• Transfer: Moving a worker from one supervisory organization or manager to another.
• Promotion: Vertical career progression characterized by an increase in Job Profile level, increased compensation grade, and elevated responsibilities.
• Demotion: Moving to a lower Job Profile level or grade, either voluntarily or due to performance restructuring.
• Lateral Move: Transitioning to a different position, job profile, or department at the same organizational level.
• Data Change: Non-structural updates to existing job records, including changes to Business Title, Work Shift, Location, Scheduled Hours, or Worker Type (e.g., converting a Temporary employee to Regular).

+-----------------------------------------------------------------------------------------+
|                              CHANGE JOB UNIFIED FRAMEWORK                               |
+-----------------------------------------------------------------------------------------+
| INITIATION: Worker Selection + Date + Reason Category / Reason                           |
+-----------------------------------------------------------------------------------------+
|                                 DYNAMIC STEP EXECUTION                                  |
| - Job Details: Select Receiving Org, Position/Job Profile, Location                     |
| - Position Disposition: (Sending Org) Vacate Position vs Close Position vs Overlap     |
| - Propose Compensation Change: Base Salary, Grade Profiles, Allowances, Stock           |
| - Costing Allocations: Update Financial Charging                                        |
| - Propose Administrative Details: Company Insider, Management Level, Work Shift         |
+-----------------------------------------------------------------------------------------+
|                                 DUAL-HIERARCHY ROUTING                                  |
| [Sending Org Manager / HR]  --->  [Receiving Org Manager / HR]  --->  [Comp Partner]    |
+-----------------------------------------------------------------------------------------+

---

Event Reasons, Reason Categories, and Dynamic Routing

The behavior of the Change Job workflow is fundamentally driven by two foundational configuration elements: Reason Categories and Event Reasons.

Reason Categories vs Event Reasons

• Reason Category: A high-level classification defined by Workday (e.g., Transfer, Promotion, Demotion, Lateral Move, Data Change, Reorganization). Reason Categories cannot be created arbitrarily; they represent macro groupings understood by system logic.
• Event Reason: A granular, customer-defined business justification nested under a Reason Category. For example, under the Reason Category Promotion, an enterprise might configure Event Reasons such as:
  • Promotion > Annual Review Cycle
  • Promotion > In-Line Career Milestone
  • Promotion > Competitive Internal Application

How Reasons Drive Business Process Logic

Workday's Business Process Framework utilizes Reason Categories and Event Reasons as operands in rule conditions to dynamically branch the Change Job workflow:

• Conditional Step Inclusion: If Reason Category = Promotion, the business process includes the Propose Compensation Change step as mandatory. If Reason Category = Data Change > Change Business Title, the compensation step is suppressed.
• Dynamic Approval Routing: If Event Reason = Transfer > Cross-Border Relocation, the process dynamically routes approval to the Global Mobility Partner and Tax Specialist. If Event Reason = Transfer > Same Department, international steps are skipped.
• Notification Triggers: Reason categories inform IT service desks, facilities management, and security access teams regarding equipment provisioning or physical badge changes.

---

Cross-Organizational Transfers: Dual Management Hierarchy Routing

When a worker transfers between two distinct supervisory organizations (e.g., moving from Marketing to Product Management), the transaction spans two separate chains of command. Workday manages this through Dual Management Hierarchy Routing.

Step Sequencing in Cross-Organizational Transfers

1. Initiation: The transfer can be initiated by the Sending Manager (releasing), the Receiving Manager (hiring), or an HR Partner.
2. Sending Hierarchy Actions: The releasing manager or HR partner confirms the release date and specifies the disposition of the vacated position.
3. Receiving Hierarchy Actions: The receiving manager or HR partner configures the worker's new position, job profile, work location, scheduled weekly hours, and proposed compensation package.
4. Dual Approvals: Workday requires approval from both hierarchies:
   • Releasing Approval: The sending manager confirms agreement to release the worker on the effective date.
   • Receiving Approval: The receiving manager approves the incoming placement and financial commitments.
5. Consolidated Executive / Partner Approvals: If the transfer involves grade jumps or cross-company movements, elevated roles (such as the Compensation Partner or Cost Center Manager) execute secondary reviews.

Effective Dating Mechanics in Job Changes

Every job change transaction requires an Effective Date:

• Future-Dated Transfers: If a transfer is approved on May 10th with an effective date of June 1st, the worker remains fully active in the sending organization until 11:59 PM on May 31st. At 12:00 AM on June 1st, Workday automatically moves the worker to the receiving organization, updates their security groups, re-points their manager rollups, and shifts payroll charging without manual intervention.
• Retroactive Transfers: If a job change is entered on June 15th with an effective date of June 1st, Workday applies the organizational change retrospectively. If compensation changed, Workday Payroll identifies retroactive earnings differences during the next pay calculation, generating automated retroactive pay adjustments.

---

Position Management Mechanics: Vacate, Close, and Overlap

In a supervisory organization operating under Position Management, transferring an incumbent out of a position requires an explicit decision regarding the vacated position's disposition. During the Change Job workflow, the system prompts the administrator with three choices:

+-----------------------------------------------------------------------------------------+
|                     POSITION DISPOSITION OPTIONS IN CHANGE JOB                         |
+-----------------------------------------------------------------------------------------+
| 1. VACATE POSITION (Keep Open for Backfill)                                            |
|    - Position status changes to Open / Unfilled                                         |
|    - Headcount remains allocated to sending supervisory org                             |
|    - Retains original position restrictions; ready for immediate recruiting             |
+-----------------------------------------------------------------------------------------+
| 2. CLOSE POSITION (Retire Headcount)                                                    |
|    - Position is permanently closed and deactivated                                     |
|    - Headcount in sending supervisory org decrements by 1                               |
|    - Used when role is eliminated or budget is reallocated                              |
+-----------------------------------------------------------------------------------------+
| 3. OVERLAP POSITION (Temporary Co-occupancy)                                            |
|    - Outgoing incumbent and incoming replacement share position temporarily             |
|    - Requires 'Allow Overlap' setting on position restrictions                          |
|    - Used for handovers, training, or transition coverage                               |
+-----------------------------------------------------------------------------------------+

Managing the Destination Position

In Position Management, a worker cannot be transferred into a vacuum. The receiving supervisory organization must have an approved, open position available on or before the transfer effective date.

• If a position already exists, the initiator selects it from the prompt.
• If no position exists, the Change Job business process can be configured to include a Create Position sub-process directly within the workflow, allowing the receiving manager to request a new position concurrently with the transfer.

---

Dual Employment: The Add Additional Job Business Process

Enterprises frequently employ individuals who hold multiple concurrent roles within the same organization (e.g., a university adjunct lecturer who also works as a lab researcher, or a hospital registered nurse who takes on supplemental weekend shifts in an urgent care clinic). Workday accommodates this via the Add Additional Job business process (Add Additional Job).

Primary Job vs Secondary Job Architecture

Workday's multi-job model is built on an asymmetric hierarchy where one assignment is designated as the Primary Job and all concurrent assignments are classified as Secondary (Additional) Jobs:

Switching the Primary Job

If an employee's secondary job becomes their primary career commitment, an administrator initiates the Switch Primary Job business process (Switch Primary Job).

• The user specifies an effective date for the switch.
• The designated secondary job is elevated to Primary status, assuming control over benefits eligibility, primary manager rollups, and core worker governance.
• The former primary job is simultaneously demoted to Secondary status.
• Exam Rule: A primary job cannot be terminated while active secondary jobs exist unless an administrator first executes Switch Primary Job or executes a multi-job concurrent termination.

---

Comprehensive Configuration Table: Staffing Transitions & Routing

---

Exam Traps & Common Misconceptions

• Exam Trap 1: Terminating a Primary Job with Active Secondary Jobs. Questions frequently ask what happens if an HR partner attempts to terminate an employee's primary job while they hold an active secondary role. Fact: The system throws a validation error. You must first run Switch Primary Job to designate a new primary job, or terminate all jobs simultaneously.
• Exam Trap 2: Vacate vs Close Position. A question will present a scenario where an organization eliminates a position upon an employee's promotion. Fact: The administrator must select Close Position. Selecting Vacate Position leaves the position active and open for backfilling.
• Exam Trap 3: Position Overlap as a Headcount Expansion. Scenarios often ask whether "Allow Overlap" permanently raises authorized headcount. Fact: Overlap is a temporary operational exception designed for knowledge transfer; it does not alter permanent authorized headcount.
• Exam Trap 4: Event Reason vs Reason Category. Questions test whether administrators can invent new Reason Categories in Workday. Fact: Reason Categories are fixed/system-defined; administrators configure customized Event Reasons that map to those categories.
• Exam Trap 5: Multiple Position Management Requirements. An administrator tries to transfer an employee into a Position Management department without an approved open position. Fact: The transfer cannot complete without an open, available position in the destination organization.