8.1 Terminate Employees

8.1 Terminate Employees

Quick Summary: Termination ends an Employee's primary employment in Workday. You capture reason, last day of work, termination date, and rehire eligibility; the business process then drives offboarding tasks and downstream effects. In Position Management the seat becomes vacant; completed events require Correct or Rescind—not Cancel—to change after the fact.

Jobs and Positions staffing events (T28–T36) close the hire-to-exit lifecycle. Blueprint task T34 Terminate employees sits after Hire (T32) and staffing movements (T33). On Workday Pro HCM Core (50 questions, 80% pass, 100 minutes), Termination is a high-frequency scenario topic because it touches staffing models, business processes, security initiation rights, and position vacancy—not because you must memorize every offboarding checklist item in a customer's tenant.

What Terminate Does

Terminate is the business process that ends an Employee worker's primary employment relationship. When the event completes successfully:

• The worker's employment status transitions out of active employment (subject to effective dates on the event).
• Organization and position occupancy for that primary job end as of the event's effective dating.
• Downstream processes configured on the Termination BP can fire: offboarding To Dos/checklists, benefits end, payroll final pay, system-access related tasks, and notifications.
• History is preserved. Workday does not "delete the person" as the default model; termination is a lifecycle state change with audit trail.

Exam trap: Terminate is not the same as deleting a Worker record, not the same as End Additional Job, and not the same as End Contingent Worker Contract (T36). Using the wrong exit event is a classic distractor.

Last Day of Work vs Termination Date

Many exam and real-world scenarios hinge on date nuance:

Practical nuances for T34

1. They can be the same day. Many resignations set last day of work = termination date.
2. They can differ. Example: last day of work is Friday after a notice period, but policy or regional practice sets termination effective dating in a specific way for benefits or leave. The exam expects you to recognize both concepts, not invent one universal legal rule for every country.
3. Effective dating drives visibility. After the event's effective date, the worker should no longer appear as an active employee in the supervisory org for ongoing staffing decisions; history remains queryable under security.
4. Do not confuse with position availability date. Freezing/closing a position or changing earliest hire date is a position lifecycle task (T30–T31), not a field you invent on Terminate to "delete" capacity.

Configuration scenario: Alex resigns. Last day of work is 15 March. HR initiates Termination with last day of work 15 March, termination date aligned to that exit, reason Voluntary – Resignation, eligible for rehire = Yes. In a Position Management org, Position P-882 becomes vacant after the event completes. Facilities still has a To Do to collect the laptop—because offboarding steps are configured on the Termination BP, not because Terminate auto-invents a separate "Asset Management app" on the exam.

Downstream Effects You Must Expect

Termination is a staffing event with a long tail. High-level effects:

Staffing / organization

• Primary job ends; worker leaves the active roster of the Supervisory Organization.
• Position Management: Position remains and is typically vacant (available to fill) unless HR closes or freezes it.
• Job Management: No persistent vacant seat object; headcount/occupancy simply decreases.

Business process framework

• Approvals may be required (manager, HR Partner) per BP definition.
• To Dos, checklists, and subprocesses implement offboarding: return equipment, exit interview, revoke access, knowledge transfer.
• Notifications can alert security, IT, or payroll partners.

Cross-functional systems (conceptual)

Exam trap: Termination does not reverse the worker's entire historical hire, compensation history, or financial journals as a blanket rule. Unwinding a completed bad termination is a Rescind problem (or Correct for limited data fixes), not "run Terminate again."

Terminate vs Related Exit / Job Events

If a worker has multiple jobs, ending only a secondary assignment is not Terminate. If the stem says "contractor engagement ends," do not answer with employee Terminate.

Cancel, Correct, and Rescind on Termination Events

Because Termination has heavy downstream effects, exam items often test event surgery after mistakes:

Awareness for T34 (not a full BP chapter): If HR entered the wrong termination date and the event already completed with benefits and access tasks fired, Cancel is no longer available. Choose Correct when a limited data fix is appropriate, or Rescind when the termination should never have completed and downstream work must reverse. Permission to Cancel/Rescind/Correct is governed by Business Process Security Policy, not by "whoever initiated."

Scenario: An HR Partner completes Termination for the wrong employee. The event is complete. The fix is not Cancel. Security-permitted Rescind (with careful coordination) is the path to reverse a completed false termination; then process the correct worker if needed.

Offboarding at Exam Depth

Offboarding is not a separate blueprint chapter title in T34, but it is how Termination BPs deliver consistent exit operations:

• Configured as To Dos, checklists, and subprocesses on the Termination definition.
• Ensures every exit triggers the same operational handoffs (IT, facilities, manager knowledge transfer).
• Does not replace the need for a proper Termination reason, dates, and staffing model awareness.

Keep offboarding high level: know it hangs off the Termination BP; do not invent proprietary step names as universal exam truth.

Position Lifecycle After Employee Termination

Employee active in Position (PM)
        │
        └── Terminate (complete)
                  │
                  ├── Worker no longer active employee
                  └── Position → Vacant (unless Close / Freeze)
                            │
                            ├── Backfill Hire into same Position
                            ├── Freeze (block hire temporarily)
                            └── Close (retire seat capacity)

Exam link to T11/T30–T31: Termination does not auto-close the position, does not auto-switch the supervisory org to Job Management, and does not delete Job Profiles.

Practical Mental Checklist (T34)

1. Is the person an Employee with primary employment ending? → Terminate.
2. Capture reason, last day of work, termination date, rehire eligibility.
3. Predict seat outcome from staffing model (vacant seat vs no seat).
4. Expect offboarding steps from BP design.
5. If the event is wrong after completion → Correct or Rescind, never Cancel.

Master Terminate as the controlled employee exit event: dates and reason first, model-aware seat effects second, BP lifecycle operations third—then you are ready for contingent contract entry and exit (T35–T36).