1.3 Worker Types, My Tasks & Delegation

Key Takeaways

  • Workday classifies workers into Employees (direct payroll/employment) and Contingent Workers (non-payroll contractor/consultant talent).
  • Pre-hire records store personal identification data prior to hire and serve as the foundation for duplicate-matching algorithms.
  • The Worker Profile organizes operational data across dedicated functional tabs including Job, Compensation, Personal, and History.
  • My Tasks Inbox contains actionable workflow items requiring user intervention, while Notifications delivers informational system broadcasts.
  • Delegation reassigns workflow tasks to a delegate; all approved actions are permanently logged as 'Approved by [Delegate] on behalf of [Delegator]'.
Last updated: September 2026

1.3 Worker Types, My Tasks & Delegation

Quick Answer: In Workday, a Worker is an overarching entity encompassing two distinct worker types: Employees (direct legal employment, company payroll, full benefit plans) and Contingent Workers (independent contractors, consultants, and agency temps invoiced through accounts payable). Before an individual can be hired, they exist as a Pre-Hire record, which provides duplicate identity matching. The Worker Profile organizes personal, job, compensation, and business process history data across structured tabs. Daily workflow management centers on My Tasks (with an Inbox for pending actions and an Archive for completed history) versus read-only Notifications. When users are out of the office, Delegation reassigns workflow tasks, with Workday immutably stamping every approved transaction as "Approved by [Delegate] on behalf of [Delegator]".


The Worker Concept: Employees vs. Contingent Workers

At the core of Workday Human Capital Management is the concept of the Worker. A worker represents a person who maintains a working relationship with the enterprise.

                                  +---------------------------------------+
                                  |                WORKER                 |
                                  | (Abstract Person in Work Relationship)|
                                  +---------------------------------------+
                                                      |
                       +------------------------------+------------------------------+
                       |                                                             |
                       v                                                             v
    +-------------------------------------+                       +-------------------------------------+
    |              EMPLOYEE               |                       |          CONTINGENT WORKER          |
    | - Paid through Workday/Ext. Payroll |                       | - Invoiced through Procurement / AP |
    | - Eligible for Employee Benefits    |                       | - Vendor / Agency Association       |
    | - Holds Position/Job Management     |                       | - Fixed-term Contract Placement     |
    +-------------------------------------+                       +-------------------------------------+

1. Employee

An Employee is an individual engaged in a direct legal contract of employment with a company legal entity within the enterprise tenant:

  • Compensation: Paid directly via regular salary or hourly wages through Workday Payroll or an external payroll integration interface.
  • Benefits: Eligible for statutory and company-sponsored benefits programs (health, retirement, life insurance).
  • Headcount: Occupies an approved headcount seat within the organization's staffing model.
  • Lifecycle: Pre-Hire $\rightarrow$ Hire $\rightarrow$ Onboarding $\rightarrow$ Active Employment $\rightarrow$ Termination/Retirement.

2. Contingent Worker (CW)

A Contingent Worker represents external, non-employee talent providing services to the enterprise. This includes independent contractors, third-party consultants, outsourced service providers, and agency temporary workers:

  • Compensation: Contingent workers are never paid through Workday Payroll. Their compensation is processed as purchase orders, vendor invoices, or time-and-materials billings through Accounts Payable / Financials.
  • Contract Placement: Contracted through the Contract Contingent Worker business process rather than the Hire business process.
  • Vendor Linkage: Must be associated with a Supplier / Staffing Agency record and a designated Contingent Worker Type (e.g., Consultant, Agency Temp, Independent Contractor).
  • Benefits: Ineligible for employee benefit plans in Workday.
  • Lifecycle: Pre-Hire $\rightarrow$ Contract Contingent Worker $\rightarrow$ Active Placement $\rightarrow$ End Contingent Worker Contract.

Employee vs. Contingent Worker Comparison Matrix

AttributeEmployeeContingent Worker (CW)
Initiating Business ProcessHire EmployeeContract Contingent Worker
Payment MechanismWorkday Payroll / External Payroll InterfaceAccounts Payable (Supplier Invoices)
Benefits EligibilityEligible based on plan rulesNot eligible
Staffing Model AssociationPosition Management or Job ManagementPosition Management or Job Management
Supplier / Agency LinkNoneMandatory association with Supplier/Vendor
Separation Business ProcessTerminate EmployeeEnd Contingent Worker Contract
Rehire / ConversionEligible for RehireCan be converted to Employee via Hire process

Pre-Hire Records & Identity Management

In Workday, an individual's personal biographical record exists independently of their employment relationship.

What is a Pre-Hire Record?

A Pre-Hire is an identity container that holds personal, demographic, and contact information for an individual before an active employment or contingent placement begins. A pre-hire record contains:

  • Legal Name and Preferred Name.
  • Contact Information (Home address, personal email, phone numbers).
  • National Identification Numbers (SSN, National ID, Tax ID).
  • Date of Birth and Citizenship data.

Pre-Hire Creation Channels

Pre-hire records enter the Workday tenant through several mechanisms:

  1. Workday Recruiting: When a job candidate advances through the interview pipeline and reaches the Offer or Background Check stage, the candidate record automatically transitions to a Pre-Hire record.
  2. Manual Creation: An HR administrator executes the Create Pre-Hire task directly in the tenant.
  3. Integration Inbound: An external applicant tracking system (ATS) loads candidates into Workday via an inbound Web Service or EIB.

Duplicate Record Detection & Management

One of the most critical responsibilities of an HCM administrator is preventing duplicate pre-hires:

  • When a new pre-hire is created or an application is submitted, Workday executes an automated duplicate matching algorithm comparing the National ID, Legal Name, and Date of Birth against all existing Pre-Hires, Employees, and Terminated Workers in the tenant.
  • If a match is detected, the system prompts the recruiter or HR administrator to Use Existing Pre-Hire rather than creating a duplicate record.
  • Consequences of Duplicates (Exam Watchpoint): Creating a duplicate pre-hire fragments the worker's historical record, splits tax withholdings, breaks continuous service calculations, and compromises historical compensation and talent performance reporting.

Worker Profile Layout & Core Functional Tabs

The Worker Profile is the centralized 360-degree operational dashboard for an individual worker. It is divided into an executive summary header and dedicated functional tabs.

+---------------------------------------------------------------------------------------------------+
|  Logan McNeil   (21001)                                          [ Related Actions (...) ]        |
|  VP, Human Resources | Global Modern Services | San Francisco | Full-Time Regular Employee       |
+---------------------------------------------------------------------------------------------------+
|  [Job]  |  [Compensation]  |  [Personal]  |  [History]  |  [Pay]  |  [Benefits]  |  [Time Off]     |
+---------------------------------------------------------------------------------------------------+

Header Summary (Worker Card)

Displays high-level demographic and organizational context:

  • Worker Photo, Preferred Name, Legal Name, Worker ID.
  • Primary Business Title, Position Title, and Job Profile.
  • Supervisory Organization and Manager name.
  • Primary Work Location, Worker Type (Employee/CW), and Time Type (Full-Time/Part-Time).

The Job Tab

Contains operational attributes governing the worker's position and duties:

  • Position details, business title, job profile, job family, and management level.
  • Full-Time Equivalent (FTE) percentage, scheduled weekly hours, and standard working hours.
  • Work space, work address, and location details.

The Compensation Tab

Displays the worker's total financial reward structure:

  • Total Base Pay and annual salary / hourly wage breakdown in local currency.
  • Assigned Compensation Package, Compensation Grade, and Grade Profile.
  • Active Compensation Plans (Salary Plan, Hourly Plan, Allowance Plans, Unit Allowance Plans).
  • Variable compensation components (Bonus Plans, Merit Plans, Commission Plans, Stock Plans).

The Personal Tab

Maintains sensitive biographical and compliance records:

  • Legal name, former names, and preferred name.
  • Home addresses, personal phone numbers, and emergency contacts.
  • Identification data: Social Security Number, National IDs, passports, work permits, and visas.
  • Demographic details: Date of birth, gender, marital status, citizenship, and military status.

The History Tab & Business Process Audit Logs

The History Tab provides a complete chronological audit trail of every business process event initiated, completed, rescinded, or cancelled for this worker throughout their enterprise tenure:

  • Displays the event name (e.g., Hire, Change Job, Request Compensation Change), status, effective date, initiator, and completion timestamp.
  • Clicking on an event opens the Process History sub-tab, showing the exact progression through each step, approval, review, and notification in the workflow.

Workflow Orchestration: My Tasks vs. Notifications

Workday separates operational tasks requiring human intervention from informational system broadcasts.

My Tasks Architecture (Formerly Workday Inbox)

My Tasks is the primary operational hub where workers, managers, and HR administrators interact with automated business processes. It consists of two primary tabs:

  1. Inbox Tab:

    • Contains pending, actionable workflow items assigned directly to the user or to a security role held by the user.
    • Actionable Step Types: Action steps, Approval steps, Approval Chains, Review steps, and To-Do task confirmations.
    • Items remain in the Inbox until the user explicitly executes an action (e.g., Approve, Submit, Deny, Send Back, or Done).
  2. Archive Tab:

    • A searchable, permanent repository of all business process events that the user has previously acted upon.
    • If a manager approves a promotion on Monday, the task immediately leaves their Inbox and appears in their Archive tab on Tuesday.
    • Users can filter Archive items by time range (e.g., Last 30 Days, This Year) to review what decisions they made and inspect current downstream process status.

Notifications: Asynchronous System Alerts

Notifications are strictly informational, read-only system broadcasts that require no transactional action or approval:

  • Examples: System maintenance announcements, notifications that an asynchronous background report has completed and is available in W-Drive, or alerts that an expense report has been paid.
  • Notifications can be marked as read or cleared, but they have no bearing on business process routing or workflow completion.

My Tasks vs. Notifications Functional Breakdown

FeatureMy Tasks: InboxMy Tasks: ArchiveNotifications
Primary ContentPending workflow tasks awaiting actionPast business process events acted uponInformational alerts and broadcast messages
User Action Required?Yes (Approve, Deny, Submit, Send Back)No (Read-only historical view)No (Mark as read, dismiss)
Impact on WorkflowHolds the business process until completedNone (Process is already moved forward)None (Purely informational)
RetentionRemoved immediately upon action completionPermanently retained for user auditingRetained according to tenant notification policies

Delegation Configuration, Boundaries & Execution

When a worker or manager is absent (due to annual leave, medical leave, or travel), organizational business processes must not stall. Workday solves this through Delegation.

Business Rationale and Mechanics of Delegation

Delegation allows a worker (the Delegator) to authorize another worker (the Delegate) to act on their behalf for specific workflow tasks and approvals during a defined time window.

  • Configured using the Manage Delegation or Delegate Tasks task in Workday.
  • Requires specifying a mandatory Begin Date and End Date.
  • Can be stopped early or modified at any time by the delegator or an authorized HR administrator.

Scoping Delegated Authority

Administrators and users can configure delegation granularity:

  1. All Business Processes: The delegate receives all pending approvals and task steps assigned to the delegator.
  2. Specific Business Processes: The delegator restricts delegated authority to selected process types (e.g., delegating only Request Time Off and Expense Report Approvals, while retaining exclusive control over Compensation Changes and Disciplinary Actions).
  3. Initiation Delegation: Allows the delegate to initiate specific business processes on behalf of the delegator.

Retaining Access During Delegation

Workday provides a checkbox setting: "Retain Access to Delegated Tasks in My Tasks".

  • If enabled, actionable items route to both the delegator's Inbox and the delegate's Inbox simultaneously.
  • Either party can take action on the pending item. As soon as one party approves or submits the step, the task clears from both inboxes.

Delegation Approval Process

Delegation is not inherently unmonitored. When an employee or manager submits a delegation request, it triggers the Delegate Task business process definition, routing to the delegator's manager or HR Partner for approval. This governance gate ensures that a manager cannot unilaterally delegate managerial approval authority to an unqualified subordinate without executive oversight.


Audit Logging of Delegated Actions

A critical legal and regulatory compliance question on the Workday HCM certification exam centers on non-repudiation and audit logging during delegation.

The "On Behalf Of" Immutable Stamp

When a delegate executes an approval step or submits a business process task on behalf of the delegator, Workday does NOT pretend the delegator took the action. Instead, the in-memory event kernel explicitly and immutably records:

Approved by [Delegate Name] on behalf of [Delegator Name]

Business Process Event History (Example: Job Change Approval Step)
---------------------------------------------------------------------------------
Step:               Manager Approval
Assigned To:        Marcus Vance (Department Manager - Delegator)
Action Taken By:    Teresa Sloane (Senior Analyst - Delegate)
System Audit Log:   Approved by Teresa Sloane on behalf of Marcus Vance
Timestamp:          2026-09-20 14:32:18 PST

Accountability & Security Principles

  • Non-Repudiation: The audit trail clearly documents who physically performed the action while linking it to the authority of the delegator.
  • Temporary Nature: Delegation reassigns workflow task routing; it does not permanently grant the delegate the underlying security groups of the delegator outside of the delegated task context.

Certification Pitfalls & Common Exam Traps

  1. The Contingent Worker Payroll Trap: Any exam option suggesting that a contingent worker should be enrolled in a Workday Payroll earnings plan or processed through a payroll pay group is always incorrect. Contingent workers are strictly paid through Accounts Payable via vendor invoices.
  2. Pre-Hire vs. Active Worker Security: Pre-hires cannot log into the standard employee self-service portal, hold supervisory organization memberships, or possess worker-based security group assignments until the Hire Employee business process has completed.
  3. My Tasks Archive vs. Notifications: When asked where a manager can verify that they successfully approved a time-off request three days ago, the correct answer is My Tasks > Archive, NOT Notifications. Notifications only contain informational broadcasts.
  4. Delegation Audit Tracking: The exam frequently tests whether an action approved by a delegate is recorded as approved by the delegator, the delegate, or both. The exact system log records: "Approved by [Delegate] on behalf of [Delegator]".
Loading diagram...
Worker Lifecycle and Delegation Workflow Progression
Test Your Knowledge

A Department Director delegates all business process approvals to a Team Lead during a two-week vacation. While the Director is away, the Team Lead reviews and approves a job promotion for a team member. How does Workday record this transaction in the business process event history?

A
B
C
D
Test Your Knowledge

Which of the following correctly describes a foundational difference between a Pre-Hire record and an Active Worker in Workday?

A
B
C
D
Test Your Knowledge

A manager needs to locate a compensation increase request that they approved last week to verify the effective date that was submitted. Where in the Workday user interface can the manager find this completed transaction?

A
B
C
D