Read time: 8 minutes

Last week we combed through the aesthetics — now it’s time to get into the meat and potatoes 🍴 of the mandatory new Change Job experience coming with the 2026R2 release, starting off with initiating actions and templates!

There are five Change Job initiating actions that can be launched directly from the UI for a selected worker. Let’s start by taking a closer look at them 🕵

Introduced 10+ years ago, these are the good ol’ trusty Change Job initiating actions you’re used to having by your side.

Change Job is the absolute OG, the famous one-stop shop workhorse of Workday HCM.

Aside from being the main initiating action for job changes across the board, it’s also the one that triggers for every internal move initiated from Recruiting when it doesn’t result in a Sup Org change.

Far less popular than Change Job, Request Transfer is used for a much more specific purpose — to, well, request a transfer for any worker you don’t otherwise have access to.

The initiation step is quite limited, providing only the options to propose a new Team and Location. The rest of the fields becoming available once the current manager approves the transfer.

Every internal move resulting in a team change (i.e. a change in Sup Org) that’s initiated from Recruiting uses this action.

This initiating action already serves as a purpose-driven template; job changes initiated this way are limited to sections and fields relevant to location changes.

Similar to Change Location, this contingent-only Change Job initiating action has always been a true purpose-driven template, built specifically for CW contract changes, excluding all other sections (aside from the must-have starting fields, of course).

Even though these four legacy Workday staples aren’t retiring yet, they’re being heavily outpaced by the new contender: Start Job Change.