Study guide

8.3 Ending Contingent Worker Contracts

Workday Pro HCM Core Certification Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts & Format 1.2 Eligibility, Learning Path & Access 1.3 Study Strategy & Blueprint Map

2 Navigation & Business Objects

2.1 Navigation Techniques in Workday 2.2 Business Objects & Finding Data

3 Organizations & Hierarchy

3.1 Organization Types & Subtypes 3.2 Supervisory Organizations & Reporting Structure 3.3 Cost Centers, Company Hierarchies & Locations 3.4 Leadership Roles & Worker Organization Assignments

4 Staffing Models

4.1 Position Management Staffing Model 4.2 Job Management Staffing Model 4.3 Hiring Restrictions on Organizations

5 Job Profiles & Job Structure

5.1 Creating & Editing Job Profiles 5.2 Job Profiles, Jobs, Positions & Workers 5.3 Job Families, Family Groups & Job Requisitions

6 Compensation Fundamentals

6.1 Compensation Framework Components 6.2 Eligibility Rules & Compensation Defaulting 6.3 Packages, Grades & Grade Profiles 6.4 Salary Plans, Allowance Plans & Worker Comp Events

7 Jobs, Positions & Staffing Events

7.1 Creating Positions & Position Hiring Restrictions 7.2 Managing Filled, Unfilled, Close & Freeze 7.3 Hire Process End-to-End 7.4 Job Changes & Additional Staffing

8 Termination & Contingent Workers

8.1 Terminate Employees 8.2 Contracting Contingent Workers 8.3 Ending Contingent Worker Contracts

9 Configurable Security

9.1 Functional Areas, Domains & Business Processes 9.2 User-Based, Role-Based & Workday-Assigned Groups 9.3 Domain Security Policies 9.4 BP Security Policies, Org Access & Activation

10 Business Process Framework

10.1 Organizations, Security & BP Relationships 10.2 Default, Org-Specific & Rule-Based Definitions 10.3 Definition, Type, Event & Step

11 Business Process Steps & Approvals

11.1 Actions & Subprocesses 11.2 Approvals & Approval Chains 11.3 Completing Tasks During Business Processes

12 Business Process Configuration

12.1 Condition Rules 12.2 Advanced Routing, Labels & Help Text 12.3 Custom Notifications 12.4 Step Ordering Letters & Validation Conditions

13 BP Management & Security

13.1 Mass and Individual BP Management 13.2 BPs and Configurable Security Interaction

14 Report Writer Fundamentals

14.1 Standard Reports & Copy/Modify 14.2 Building Custom Reports: Index vs Standard 14.3 Sorting, Filtering & Prompts 14.4 Report Security, Sharing & Ownership

15 Advanced Reporting & Calculated Fields

15.1 Scheduling Reports 15.2 Matrix Reports 15.3 Discovery Boards 15.4 Calculated Fields & Report Performance

8.3 Ending Contingent Worker Contracts

Key Takeaways Explain This Topic AI

End Contingent Worker Contract is the exit event for contingent engagements; do not use employee Terminate for a pure contractor end.

Contrast with employee termination: different BP, different subtype path, overlapping themes (dates, reason/context, offboarding-style tasks, seat vacancy in Position Management).

Contract end date on the engagement and the End Contract event work together to close the contingent relationship as of the intended effective dating.

Convert-to-employee is a separate conceptual path: ending contingent status and establishing Employee via the appropriate hire/conversion process—not a silent side effect of End Contract alone.

After end contract in Position Management, the Position typically becomes vacant for reuse; Job Management ends occupancy without a persistent empty seat.

Last updated: September 2026

8.3 Ending Contingent Worker Contracts

Study index: T-numbers here refer to this guide’s index of an older Workday topic list. They are not current Workday task IDs or published exam weights.

Quick Summary: When a contractor engagement finishes, you run End Contingent Worker Contract —not employee Terminate . The event ends the contingent relationship as of the contract end dating, can trigger offboarding-style tasks, vacates positions under Position Management, and is distinct from converting a contingent into an employee.

Older-guide topic T36 End contingent worker contracts completes the contingent pair with T35. Practice scenarios can mix vocabulary: "terminate the contractor," "end the assignment," "convert them to FTE." Your job is to map plain language to the correct Workday event family and predict seat and subtype outcomes.

What End Contingent Worker Contract Does

End Contingent Worker Contract is the staffing business process that ends a Contingent Worker 's active contract/engagement in HCM.

When the event completes:

The contingent work relationship is no longer active as of the event's effective dating.

The worker leaves the active contingent roster for that engagement's supervisory/job context.

In Position Management , the occupied Position typically becomes vacant (available to fill) unless closed or frozen.

In Job Management , occupancy ends without leaving a durable empty seat object.

Configured BP steps can create To Dos (badge return, system access, supplier notification) similar in shape to employee offboarding—but still on the contingent exit BP design.

  • Element Contingent end contract
  • Who Contingent Worker on an active contract
  • Event End Contingent Worker Contract
  • Key dating Contract end / effective end of engagement
  • Seat (PM) Position vacated, not auto-deleted
  • History Preserved for audit and rehire/recontract reporting

Exam trap: Ending a contract does not delete the person from Workday history, does not auto-Hire them as an employee, and does not auto-close every position in the supervisory org.

Direct Contrast: Terminate Employee vs End Contingent Contract

Memorize this comparison table—it is the useful T34 vs T36 comparison.

  • Dimension Terminate (Employee) End Contingent Worker Contract
  • Worker subtype Employee Contingent Worker
  • What ends Primary employment relationship Contingent contract/engagement
  • Entry sibling event Hire Contract Contingent Worker

Typical reason drivers Resignation, involuntary, retirement, etc. Contract completed, early end, non-renewal, etc.

Benefits/payroll posture Employee exit processing Contingent exit (generally not employee benefits termination story)

  • Position Management seat Vacates position Vacates position
  • Job Management seat No persistent vacant seat No persistent vacant seat

Wrong-tool failure Using End Contract on an employee Using Terminate on a pure contingent Employee lifecycle: Hire → work → Terminate

Contingent lifecycle: Contract CW → engagement → End Contingent Worker Contract

  • Conversion concept: Contingent engagement ends / converts → Employee via Hire/convert path (not automatic)
  • Shared themes (so distractors feel plausible)

Both exits:

Are business processes with initiate, approve, To Do, and complete states.

Care about effective dating .

Affect active org membership and reporting headcount.

Interact with staffing model for seat outcomes.

May need Cancel / Correct / Rescind awareness if mistakes occur (same BP operation rules: Cancel in progress only; Correct vs Rescind after complete).

Differences that decide the answer

If the stem says employee , employment , resignation , eligible for rehire in an employment sense → Terminate .

If the stem says contractor , statement of work ended , supplier engagement complete , contract end date reached → End Contingent Worker Contract .

Contract End Date vs Running the End Event

Contingent engagements usually carry a planned contract end date from contracting time (T35). That planned date is not always the same as "someone already ran End Contract."

  • Concept Role
  • Planned contract end Expected end captured on the contract; used for planning, alerts, and reporting
  • End Contingent Worker Contract event Transaction that actually ends the active contingent relationship
  • Early end End event before original planned end (project canceled, performance, budget)

Extension Contract dates updated / extended before end—if you already ended, you may need recontract or correction paths per design

Configuration scenario: Maya's contract was planned through 30 November. On 15 October the project is canceled. HR initiates End Contingent Worker Contract effective 18 October with an early-end reason. The planned November date is superseded by the completed end event. Position "Cutover Consultant – Wave 2" becomes vacant on the Position Management org. Supplier Apex is notified via a BP notification. Maya is not run through employee Terminate.

Exam trap: Having a contract end date in the past does not mean you should Hire the person to "refresh" them, and it does not mean you Terminate them as an employee. If they remain contingent and need a new engagement, that is a new or renewed contract path—not employee termination.

Convert to Employee (Exam-Depth Concept)

Organizations often convert successful contractors to employees. At Pro HCM Core depth, know the concept , not a 40-step tenant cookbook:

What conversion means

The person should become an Employee subtype with a proper Hire (or tenant convert) path.

The contingent relationship should not remain the active primary story for that employment.

Data quality matters: wrong subtype left behind creates reporting and payroll defects.

What conversion is not

False statement Why false

"End Contingent Worker Contract automatically Hires them as Employee" End Contract ends contingent; it does not by itself create employment

"Change Job converts contingent to employee" Change Job moves job context; subtype conversion is not a casual job change label

"Edit Position Restrictions changes Worker subtype" Restrictions describe the seat, not the person's employment subtype

"Terminate the contingent, then they become employee" Terminate is the employee exit path—wrong tool for contingent end

Clean conceptual sequence (illustrative):

Contingent is active on a contract (possibly in a position).

Business decides to employ them.

Contingent engagement is ended or converted per the tenant's supported convert/hire process.

Employee relationship is established with Hire/convert effective dating, compensation, and org/position assignment appropriate for employees.

Downstream employee onboarding BPs run—not contingent end tasks alone.

Scenario: Jordan contracted 9 months as Contingent Worker on Position P-220. Leadership offers full-time employment. Operations ends or converts the contingent engagement and completes an employee Hire into an appropriate employee seat/profile with compensation defaults. Jordan is not "terminated as employee" to start employment, and not left as contingent while receiving employee payroll.

  • Seat Outcomes After End Contract Contingent fills Position (PM)
  • │
  • └── End Contingent Worker Contract (complete)
  • │
  • ├── Contingent engagement inactive
  • └── Position → Vacant
  • │
  • ├── Contract another contingent into same seat
  • ├── Hire an employee into same seat (if restrictions allow)
  • ├── Freeze / Close seat
  • └── Leave vacant for planning

Under Job Management , headcount/occupancy drops; there is no numbered empty seat waiting. Restrictions on the org still govern the next Contract Contingent Worker or Hire.

Related Events to Keep Separate

  • Event Use when
  • End Contingent Worker Contract Contingent engagement ends
  • Terminate Employee primary employment ends
  • End Additional Job Secondary job ends; primary continues (either subtype context as designed)
  • Change Job Move/change job without ending the whole relationship
  • Contract Contingent Worker Start/renew contingent engagement
  • Hire Start employee employment
  • Rescind/Correct Awareness (Brief)

Same BP surgery rules as Termination:

Cancel only while End Contract is in progress.

Correct after complete for limited data fixes without full unwind.

Rescind after complete to reverse and unwind downstream effects when the end should not have completed.

Do not answer "delete the contingent worker" as the remediation for a wrong end date.

Practical Mental Checklist (T36)

Subtype = Contingent ? → End Contingent Worker Contract, not Terminate.

Confirm effective end dating (planned end vs early end).

Predict position outcome from staffing model.

If the business wants an employee , plan convert/Hire—End Contract alone is not employment.

If the completed event is wrong → Correct or Rescind, not Cancel.

Chapter Close: T34–T36 as One Story

  • Task Entry Exit Subtype
  • T34 (Hire from earlier tasks) Terminate Employee
  • T35 Contract Contingent Worker — Contingent
  • T36 — End Contingent Worker Contract Contingent

Staffing models (T10–T14), positions (T28–T31), and BP operations (Cancel/Correct/Rescind) are the cross-links. If you can staff and unstaff both subtypes without mixing events—and you know convert-to-employee is a deliberate second path—you have finished Termination & Contingent Workers as HCM Core practice.