8.3 Ending Contingent Worker Contracts

8.3 Ending Contingent Worker Contracts

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.

Blueprint task T36 End contingent worker contracts completes the contingent pair with T35. Exam stems love to 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.

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 highest-yield T34 vs T36 grid.

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."

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

Clean conceptual sequence (illustrative):

1. Contingent is active on a contract (possibly in a position).
2. Business decides to employ them.
3. Contingent engagement is ended or converted per the tenant's supported convert/hire process.
4. Employee relationship is established with Hire/convert effective dating, compensation, and org/position assignment appropriate for employees.
5. 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

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)

1. Subtype = Contingent? → End Contingent Worker Contract, not Terminate.
2. Confirm effective end dating (planned end vs early end).
3. Predict position outcome from staffing model.
4. If the business wants an employee, plan convert/Hire—End Contract alone is not employment.
5. If the completed event is wrong → Correct or Rescind, not Cancel.

Chapter Close: T34–T36 as One Story

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 at Workday Pro HCM Core exam depth for the 50-question, 80%, 100-minute blueprint.