7.4 Job Changes & Additional Staffing
Key Takeaways
- Change Job moves an existing Worker’s job assignment—common reasons include Transfer, Promotion, Demotion, Lateral Move, and Data Change—without creating a brand-new Worker.
- Reason codes matter: they drive routing, compensation subprocesses, and reporting; promotion often pairs with Propose Compensation Change while pure data changes may not.
- Add Job creates an additional job for an existing Worker (dual employment) so one person can occupy more than one staffing relationship at once.
- Switch Primary Job toggles which of multiple active jobs is primary for defaults such as primary supervisory context, costing defaults, and reporting—without ending the other job.
- Exam traps: Change Job ≠ Hire; Add Job ≠ Hire; Switch Primary Job ≠ End Additional Job; Edit Position Restrictions ≠ Change Job for the person.
7.4 Job Changes & Additional Staffing
Quick Summary: After Hire, workers move. Change Job handles transfers, promotions, demotions, laterals, and data changes on an existing employment. Add Job creates dual employment. Switch Primary Job re-points which concurrent job is primary. These are staffing movements—not new Worker creation and not seat freeze/close alone.
Blueprint task T33 Staffing movements — job changes & additional staffing tests whether you pick the correct event when the person already exists. Termination and contingent contracting remain Chapter 8; this section stays on movements and multi-job patterns.
Change Job — The Workhorse Movement BP
Change Job updates an existing Worker’s job assignment. It does not create a new Worker and does not end employment the way Terminate does.
Typical Change Job reason codes
| Reason (conceptual) | Business meaning | Common side effects |
|---|---|---|
| Transfer | Move to another org/team/seat, often similar level | New manager path, org assignments; comp may or may not change |
| Promotion | Higher level / higher responsibility | Often triggers compensation proposal; management level / profile change |
| Demotion | Lower level / responsibility | Comp and profile changes; sensitive approvals |
| Lateral Move | Sideways move at comparable level | Org/seat/profile may change without “promotion” semantics |
| Data Change | Correct or update job data without a true “move story” | Location, title correction, FTE/time-type adjustment per design |
Tenants configure exact reason lists and which reasons launch which subprocesses. For the exam, memorize the cluster: Transfer / Promotion / Demotion / Lateral / Data Change as the standard Change Job family—not Hire, Rehire, or Onboarding as Change Job reasons.
What Change Job can alter
Depending on the event and security:
- Job Profile (and thus defaults for title, management level, classification)
- Supervisory Organization / manager path
- Position (move from one seat to another in Position Management)
- Location, time type, company, cost center, and other org assignments
- Compensation via linked propose/request steps when reason and BP require it
Existing Worker + current Job
│
▼
Change Job (reason code)
│
├── New profile / level (promo/demo/lateral)
├── New Sup Org / Position / location
├── Optional Propose Compensation
└── Approvals → effective-dated new job truth
Configuration scenario: Priya is a Financial Analyst II in Sup Org FP&A East, position P-200. She is promoted to Senior Financial Analyst in FP&A West, position P-350, effective 1 July. HR initiates Change Job with reason Promotion, selects the new position/profile, proposes a new salary inside the Senior grade, and routes manager + compensation approval. Hire would be wrong—Priya is not a new Worker.
Change Job vs Edit Position Restrictions
This pair is a classic exam trap:
| If the stem focuses on… | Use |
|---|---|
| The person’s assignment, manager, pay, or move story | Change Job |
| The vacant seat’s design (profile/location/org on the Position) | Edit Position Restrictions |
| Both a filled seat redesign and the incumbent | Often both, sequenced per process design—not one magic button |
Exam trap: Edit Position Restrictions does not transfer a worker to a new manager. Change Job does not close a vacant seat.
Position Management Implications for Job Changes
When workers move between seats:
- Old position typically becomes unfilled (unless another concurrent design applies).
- New position becomes filled (must be vacant/staffable—watch freeze/close).
- Headcount stories stay seat-accurate if you move people through positions rather than only editing free text.
In Job Management, Change Job still updates the worker’s job and org context, but you are not always selecting a pre-existing vacant Position ID for every move.
Additional Staffing: Add Job
Add Job creates an additional employment relationship for a Worker who already exists. This is the dual-employment / multi-job pattern.
When Add Job is correct
- Employee works two roles concurrently (e.g., part-time instructor + administrative job).
- Worker needs a second position without ending the first.
- Cross-entity or multi-assignment designs where one person legally holds two jobs in the tenant model.
Add Job vs Hire vs Change Job
| Process | Worker exists? | Ends current job? | Result |
|---|---|---|---|
| Hire | Usually no (new employee) | N/A | New Worker + first job |
| Change Job | Yes | Replaces/updates the job being changed | One job path changes |
| Add Job | Yes | No | Second (additional) job added |
Configuration scenario: Sam is a full-time Payroll Specialist (primary job). The university also needs Sam to teach one evening course. HR runs Add Job for the adjunct instructor assignment instead of Hire (Sam already exists) and instead of Change Job (payroll role must continue).
After Add Job, the Worker occupies two jobs; under Position Management that can mean two positions filled by the same person.
Switch Primary Job
When multiple jobs are active, one is Primary. Switch Primary Job changes which job is primary.
Why primary matters (exam-level)
Primary job commonly influences:
- Default supervisory / reporting context users see first
- Costing / company defaults in some processes
- Compensation and benefits anchoring depending on tenant design
- Which assignment is treated as the main employment story in analytics
What Switch Primary Job does not do
| Not accomplished by Switch Primary Job | Correct alternative |
|---|---|
| Create the second job | Add Job |
| End an extra job | End Additional Job (or related end-job process) |
| Move someone to a new Sup Org as a transfer story | Change Job |
| Terminate employment entirely | Terminate |
| Close a vacant seat | Close Position |
Exam trap: Switch Primary Job toggles primary among existing active jobs; it is not a hidden Terminate and not a Hire.
Staffing Movement Decision Tree
Use this under timed exam pressure:
Is the person brand new as an employee?
YES → Hire (or contingent contract path if not employee)
NO → Do they need a SECOND concurrent job?
YES → Add Job
NO → Are you only changing which concurrent job is primary?
YES → Switch Primary Job
NO → Change Job (transfer/promo/demo/lateral/data change)
Is the issue a vacant seat’s attributes?
→ Edit Position Restrictions
Is employment ending?
→ Terminate (Chapter 8)
Is a contractor starting/ending?
→ Contingent processes (Chapter 8)
Effective Dating and Approvals on Movements
Like Hire, job changes and Add Job are effective-dated business processes:
- Future-dated promotions stage leadership changes before the effective day.
- Historical as-of reporting shows the old job before the change date.
- Approvals and compensation subprocesses depend on reason and BP definition.
Configuration scenario: Effective 1 October, a lateral transfer moves a nurse between units with no pay change. Reason Lateral Move routes manager approvals but skips aggressive compensation review. A Promotion for another nurse the same day forces Propose Compensation and multi-level approval. Same BP family, different reason-driven behavior.
Common Exam Confusions (T33 Grid)
| Wrong assumption | Correct concept |
|---|---|
| “Promotion requires Hire” | Promotion is Change Job for existing workers |
| “Dual employment is two Hires” | Second concurrent role is Add Job |
| “Switch Primary Job ends the old job” | It only changes which job is primary |
| “Change Job closes the old position always as delete” | Old seat typically becomes unfilled, not deleted |
| “Data Change means Terminate and rehire” | Data Change is a Change Job reason pattern for corrections/updates |
| “Add Job creates a new person number always as first hire” | Add Job requires an existing Worker |
End-to-End Stories to Narrate Cold
- Promotion: Change Job + Promotion reason + new profile/position + Propose Compensation.
- Transfer: Change Job + Transfer + new Sup Org/position; position P-old unfilled, P-new filled.
- Dual employment: Add Job for second seat; optionally Switch Primary Job later if the secondary becomes main.
- Seat-only redesign: Edit Position Restrictions on vacant P-x; no Change Job until someone occupies it.
Master these movements and T33 becomes a matching exercise: new person → Hire; move person → Change Job; second job → Add Job; which job is main → Switch Primary Job; seat design → position tools; exit → Terminate (next chapter).
Which Change Job reason cluster is typically configured for staffing movements of existing workers?
A Worker already employed full-time must also hold a concurrent part-time teaching job without ending the first role. Which process should you use?
What does Switch Primary Job do for a Worker with multiple active jobs?
An administrator needs to move an existing employee to a new Supervisory Organization and Job Profile with a pay increase for a promotion. Which pairing is most appropriate?