11.3 Employment Offers, eSignatures & Ready for Hire Transition

11.3 Employment Offers, eSignatures & Ready for Hire Transition

Quick Answer: The culmination of the recruiting lifecycle occurs through the Make Offer business process, which structures proposed compensation, grade profiles, allowances, and proposed start dates. Compensation proposals undergo strict rule validation against grade spreads before routing through multi-tier approval chains. Formal offer packages are generated using Workday Docs or integrated eSignature platforms (DocuSign, Adobe Acrobat Sign), injecting dynamic tokens and conditional legal text. Once signed, advancing the candidate to Ready for Hire marks the definitive boundary between Recruiting and Core HCM. Workday's Pre-Hire reuse architecture prevents duplicate person records by matching historical identifiers (National ID, Date of Birth). The staffing handoff seamlessly maps requisition, pre-hire, and offer metadata directly into the Core HCM Hire (or Change Job) event, launching downstream Onboarding.

---

The Make Offer Business Process & Compensation Structuring

When a candidate successfully clears interview and screening evaluations, the recruiter advances the Job Application to the Offer stage, triggering the Make Offer business process.

+-------------------------------------------------------------------------+
|                       MAKE OFFER BUSINESS PROCESS                       |
+-------------------------------------------------------------------------+
                                     |
                                     v
+-------------------------------------------------------------------------+
|                     1. PROPOSE COMPENSATION & TERMS                     |
| - Base Salary / Hourly Plan        - Compensation Grade & Profile       |
| - Bonus & Commission Plans         - Sign-on Bonus (One-Time Payment)   |
| - Relocation / Travel Allowance    - Proposed Start Date                |
+-------------------------------------------------------------------------+
                                     |
                                     v
+-------------------------------------------------------------------------+
|                    2. SYSTEM COMPENSATION VALIDATIONS                   |
| - Is proposed pay within Grade / Profile Min-Max boundaries?            |
| - Soft Warning: Pay below midpoint or near maximum                      |
| - Hard Stop / Critical: Pay exceeds maximum without VP approval        |
+-------------------------------------------------------------------------+
                                     |
                                     v
+-------------------------------------------------------------------------+
|                    3. MULTI-LEVEL APPROVAL WORKFLOW                     |
| [Hiring Manager] ---> [Compensation Partner] ---> [Finance Director]   |
+-------------------------------------------------------------------------+
                                     |
                                     v
+-------------------------------------------------------------------------+
|                    4. DOCUMENT GENERATION & eSIGNATURE                  |
| - Workday Docs or DocuSign/Adobe Sign integration                       |
| - Conditional clauses based on jurisdiction (e.g., Non-compete rules)   |
| - Candidate signs electronically -> Pre-Hire attachment created        |
+-------------------------------------------------------------------------+

Compensation Proposal Mechanics

The Make Offer task captures the complete proposed financial and contractual relationship:

• Base Pay: Proposing an hourly wage or annual salary linked to the position's assigned Compensation Grade and Compensation Grade Profile (e.g., applying geographic pay differentials).
• Variable Pay Plans: Attaching eligible Bonus Plans (e.g., Annual Corporate Management Incentive Plan) or Commission Plans based on job profile rules.
• Allowances: Proposing recurring allowances such as Car Allowances, Housing Subsidies, or Mobile Phone Stipends.
• One-Time Payments: Structuring upfront sign-on bonuses, relocation bonuses, or initial equity grant targets.
• Contractual Attributes: Designating Proposed Start Date, Worker Subtype (Regular vs. Temporary), Time Type (Full-time vs. Part-time), and Scheduled Weekly Hours.

Compensation Validations: Soft Warnings vs. Hard Stops

To protect corporate labor margins and pay equity, Workday executes real-time validation rules during offer creation:

• Soft Warnings: If the proposed base salary falls below the grade minimum or between the midpoint and maximum, Workday can present an informational warning requiring the recruiter to confirm acknowledgment.
• Critical Validations (Hard Stops): If a proposed salary exceeds the Compensation Grade Maximum, the system can enforce a critical validation error. The transaction cannot be submitted into workflow without attaching documented compensation committee justification or triggering a specialized executive approval branch.

Counter-Offers and Offer Revisions

In dynamic hiring environments, candidates frequently negotiate compensation or start dates. Workday accommodates this without aborting the recruitment lifecycle:

• Revise Offer Action: Allows recruiters to adjust proposed compensation numbers, change bonus percentages, or update the proposed start date.
• Workflow Re-triggering: The business process framework evaluates which steps must re-execute. If a salary change remains within authorized compensation bounds, subsequent executive approvals may be bypassed based on configured step condition rules.

---

Offer Letter Generation & eSignatures

Once offer terms are approved internally, Workday facilitates the automated assembly and legal execution of employment documentation.

+-------------------------------------------------------------------------+
|                       DOCUMENT GENERATION ENGINE                        |
+-------------------------------------------------------------------------+
|  Template Base: Master Offer Letter (Workday Docs / Word Layout)        |
+-------------------------------------------------------------------------+
                                     |
                  +------------------+------------------+
                  |                                     |
                  v                                     v
+-----------------------------------+ +-----------------------------------+
|       DYNAMIC MERGE TOKENS        | |    CONDITIONAL TEXT BLOCKS        |
| - {Candidate.Legal_Name}          | | - IF Country = 'US' AND           |
| - {Position.Job_Title}            | |   State = 'California'            |
| - {Offer.Proposed_Base_Salary}    | |   THEN Insert Labor Code Notice   |
| - {Offer.Proposed_Start_Date}     | | - IF Management_Level = Executive |
| - {Org.Manager_Name}              | |   THEN Insert Equity Schedule     |
+-----------------------------------+ +-----------------------------------+
                                     |
                                     v
+-------------------------------------------------------------------------+
|                        eSIGNATURE EXECUTION                             |
|                                                                         |
| [Workday Native eSign]    OR    [DocuSign / Adobe Acrobat Sign API]     |
|          |                                       |                      |
|          v                                       v                      |
| Candidate signs in Portal               External envelope signed        |
|          |                                       |                      |
|          +-------------------+-------------------+                      |
|                              v                                          |
|     Completed Signed PDF Archived to Pre-Hire Worker Documents          |
+-------------------------------------------------------------------------+

Workday Docs vs. External Document Templates

Workday provides two primary methodologies for generating offer documentation:

1. Workday Docs: An embedded, cloud-native document authoring tool. Administrators design rich, responsive document templates directly within the Workday interface, incorporating corporate branding, typography, tables, and dynamic headers/footers.
2. External Template Uploads: Generating documentation from uploaded Microsoft Word (.docx) files configured with specialized Workday XML merge tags.

Dynamic Merge Tokens and Conditional Clauses

Templates dynamically pull live transactional metadata through merge tokens:

• Standard tokens inject the candidate's legal name, job profile title, reporting manager, supervisory organization, base salary, and pay frequency.
• Conditional Text Blocks: Templates evaluate business rules to inject or suppress specific legal text. For instance, an employment agreement template can automatically append state-specific intellectual property disclosures for California employees, or insert non-compete clauses only for workers above a specific management grade.

eSignature Delivery Channels

Workday supports both native and third-party electronic signatures:

• Workday Native eSignature: The candidate logs into the External Candidate Portal (or Workday Mobile) and reviews the rendered PDF. They sign by clicking an electronic signature acknowledgment, capturing IP address, user credentials, and precise timestamp audit trails.
• DocuSign / Adobe Acrobat Sign Integrations: Workday transmits an encrypted payload containing the generated PDF to the eSignature vendor via pre-built web service APIs. The vendor routes signature envelopes, manages signee authentication, and returns the executed PDF alongside a cryptographic completion certificate.
• Document Archival: Regardless of signing method, the finalized, counter-signed PDF is permanently attached to the candidate's Pre-Hire repository under Worker Documents.

---

The 'Ready for Hire' Stage & Transition Milestone

The Ready for Hire stage represents the definitive functional milestone that concludes the recruiting process and prepares the candidate for operational staffing.

+-------------------------------------------------------------------------+
|                     RECRUITING DOMAIN BOUNDARY                          |
|                                                                         |
|  [Candidate Application] ---> [Offer Accepted] ---> [READY FOR HIRE]    |
+-------------------------------------------------------------------------+
                                                         |
                                                         | Functional Boundary
                                                         | (Staffing Handoff)
                                                         v
+-------------------------------------------------------------------------+
|                      CORE HCM DOMAIN BOUNDARY                           |
|                                                                         |
|  [Pre-Hire Record] ---> [Hire / Change Job BP] ---> [Active Worker]     |
+-------------------------------------------------------------------------+

Operational Purpose of Ready for Hire

Moving an application to Ready for Hire communicates that all pre-employment contingencies have been successfully satisfied:

• The formal offer letter has been electronically signed and counter-signed.
• Background screening adjudication has returned a passing / clear result.
• Required pre-employment compliance forms (such as licenses or certifications) have been validated.

Headcount Reservation & Open Requisition Impact

• When a candidate enters Ready for Hire, Workday reserves the target position, preventing other recruiters from advancing competing candidates to the offer stage for that specific position.
• However, moving to Ready for Hire does not decrement the requisition's official headcount. Headcount is formally consumed only when the downstream Core HCM Hire business process completes its final approval step.

---

Pre-Hire Identity Architecture & Duplicate Prevention

One of the most critical and heavily tested areas of the Workday HCM certification is the Pre-Hire data model and duplicate prevention architecture.

+-------------------------------------------------------------------------+
|                        PRE-HIRE IDENTITY MODEL                          |
+-------------------------------------------------------------------------+
| Business Object: Pre-Hire                                               |
| Contains: Legal Name, Contact Info, National ID, Biographical Data      |
| Cardinality: Exactly ONE Person = Exactly ONE Pre-Hire Record           |
+-------------------------------------------------------------------------+
                                     |
                   +-----------------+-----------------+
                   |                                   |
                   v                                   v
+------------------------------------+ +-----------------------------------+
|          SCENARIO A: NEW TALENT    | |        SCENARIO B: REHIRE         |
| - First-time applicant             | | - Former employee or past recruit |
| - No matching National ID or name  | | - Existing Pre-Hire in database   |
| - Create New Pre-Hire committed    | | - MANDATORY: Reuse Existing       |
|                                    | |   Pre-Hire Record                 |
+------------------------------------+ +-----------------------------------+
                                                       |
                                                       v
                                       +-----------------------------------+
                                       | CRITICAL DANGERS OF DUPLICATES:   |
                                       | - Corrupted tax history (W-2s)    |
                                       | - Broken seniority / vesting dates|
                                       | - Fragmented security profiles    |
                                       +-----------------------------------+

Pre-Hire vs. Candidate vs. Worker Business Objects

Understanding the Workday object hierarchy is essential for avoiding architectural errors:

1. Candidate: A recruiting-specific entity representing a person who expressed interest in employment. A person can have multiple candidate profiles across different career sites.
2. Pre-Hire: The foundational, legal person record in Workday. A Pre-Hire contains legal identifiers (Social Security Number, National ID), home address, personal email, and birth date. A Pre-Hire is not yet an employee and does not hold an active organizational position.
3. Worker: An active or terminated Employee or Contingent Worker record. A Worker is instantiated by attaching a Pre-Hire to an organizational position via the Hire business process.

Automated Duplicate Detection Matching Criteria

When a candidate reaches Ready for Hire, Workday triggers the Duplicate Pre-Hire Match engine. The system evaluates a combination of deterministic and probabilistic matching attributes:

• Government National ID: Social Security Number (SSN), National Insurance Number (NINO), or National Tax ID.
• Legal Name & Date of Birth: Exact matching on Legal First Name, Legal Last Name, and Date of Birth.
• Contact Coordinates: Personal email address and primary telephone number.

The Golden Rule: Reusing Existing Pre-Hires

If Workday identifies that a candidate was previously employed by the enterprise (a Rehire) or previously applied for another position, the recruiter must select and reuse the existing Pre-Hire record.

Consequences of Creating Duplicate Pre-Hires (Exam Watchpoint)

Failing to reuse an existing Pre-Hire and erroneously creating a new duplicate pre-hire record causes catastrophic data corruption across the enterprise:

• Tax Record Fragmentation: The worker will have two distinct tax identifiers, corrupting year-end tax reporting (e.g., generating two conflicting W-2 forms with miscalculated FICA wage caps).
• Loss of Historical Continuity: The rehire's original hire date, continuous service date, vesting schedules for stock grants, and accrued retirement seniority are completely severed.
• Security & User Account Collisions: Single Sign-On (SSO) and Active Directory/Okta integrations will encounter duplicate account collisions when attempting to map the worker's corporate email and username.

---

The Staffing Handoff: Recruiting to Core HCM

Once a candidate is in Ready for Hire and their Pre-Hire record is verified, the talent acquisition lifecycle transitions into Core HCM operational staffing.

+-------------------------------------------------------------------------+
|                    RECRUITING TO CORE HCM HANDOFF                       |
+-------------------------------------------------------------------------+
                                     |
                  +------------------+------------------+
                  |                                     |
                  v                                     v
+-----------------------------------+ +-----------------------------------+
|       EXTERNAL CANDIDATE          | |        INTERNAL CANDIDATE         |
+-----------------------------------+ +-----------------------------------+
| Launches: HIRE EMPLOYEE BP        | | Launches: CHANGE JOB BP           |
| - PBO: Pre-Hire                   | | - PBO: Worker                     |
| - Moves Pre-Hire to Worker Status | | - Action: Transfer, Promote, Move |
+-----------------------------------+ +-----------------------------------+
                  |                                     |
                  +------------------+------------------+
                                     |
                                     v
+-------------------------------------------------------------------------+
|                    AUTOMATED DATA INHERITANCE                           |
| - Position Restrictions -> Target Supervisory Org, Job Profile, Location|
| - Pre-Hire Record -------> Legal Name, Contact Information, National ID |
| - Make Offer Proposal ---> Propose Compensation Hire Step Defaults      |
+-------------------------------------------------------------------------+
                                     |
                                     v
+-------------------------------------------------------------------------+
|                    DOWNSTREAM ONBOARDING LAUNCH                         |
| - Form I-9 / Right to Work Verification                                 |
| - Payment Elections (Direct Deposit Bank Routing)                       |
| - Benefit Elections (Health, Dental, Retirement)                        |
+-------------------------------------------------------------------------+

External Candidates: Launching the Hire Process

For external candidates, moving to Ready for Hire generates a pending action or inbox task to initiate Hire Employee (or Contract Contingent Worker if the requisition was for contingent talent):

• The business process inherits all foundational attributes without manual re-entry.
• The Pre-Hire record is converted into an active Worker record upon the arrival of the effective hire date.

Internal Candidates: Launching the Change Job Process

For existing employees who applied through the internal career site, the Hire business process is never used:

• Launching Hire Employee on an active worker would create a corrupt duplicate employment record.
• Instead, Workday automatically routes the internal candidate into the Change Job business process (categorized as a Transfer, Promotion, or Lateral Move).
• Change Job updates the worker's supervisory organization, position assignment, and compensation package while preserving their original hire date, continuous service record, and employee ID.

Automated Data Mapping and Inheritance Matrix

Downstream Onboarding Integration

The successful completion of the Hire event immediately triggers the Onboarding business process definition for the new worker. Subprocesses and checklists deploy to the new hire's Workday inbox:

• Government Compliance: Electronic Form I-9 verification (US), Right to Work checks (UK), or country-specific tax withholding declarations (W-4).
• Payment Elections: Establishing direct deposit banking details and payroll payment elections.
• Benefit Enrollments: Initiating the New Hire Benefit Event, allowing the employee to select medical, dental, life insurance, and retirement plans within their open enrollment window.

---

Step-by-Step Configuration Walkthrough

1. Configuring the Make Offer Business Process

To define how compensation offers are structured and approved:

Task: Edit Business Process Definition (Make Offer)
  -> Add Step A: Action -> Propose Compensation (Assigned: Recruiter)
  -> Add Step B: Approval -> Hiring Manager Approval (Assigned: Manager)
  -> Add Step C: Approval -> Compensation Review (Assigned: Compensation Partner)
       - Add Rule Condition: "Proposed Base Salary > Grade Midpoint OR Any Sign-on Bonus > 10,000 USD"
  -> Add Step D: Approval -> Finance Review (Assigned: Finance Partner)
  -> Add Step E: Action -> Generate Document (Assigned: Recruiter / System)
       - Select Template: "Standard Corporate Offer Letter Template"
  -> Add Step F: Integration -> Send to DocuSign / Workday Native eSign
  -> Add Step G: Action -> Review Signed Offer (Assigned: Recruiter)
  -> Save and activate definition

2. Executing the Pre-Hire Duplicate Check and Hire Transition

When an external candidate's offer is signed and verified:

Task: Move Candidate to Ready for Hire (From Job Application)
  -> System executes automated Duplicate Detection algorithm
  -> Match Alert Dialogue appears:
       - "Possible duplicate Pre-Hires found based on National ID and Last Name"
       - Option 1: "Select Existing Pre-Hire: Jane Doe (Pre-Hire 10042 - Former Employee)"
       - Option 2: "Create New Pre-Hire"
  -> Action: Select "Jane Doe (Pre-Hire 10042)" to enforce rehire reuse
  -> Confirm candidate status = "Ready for Hire"
  -> Navigate to Supervisory Organization -> Related Actions -> Staffing > Hire Employee
       - Select Existing Pre-Hire: "Jane Doe"
       - System auto-populates Job Requisition, Position, and Offer Compensation
       - Submit Hire business process into approval routing

---

Certification Pitfalls & Common Exam Traps

1. The Ready for Hire Employment Trap: An exam question will ask whether a candidate who enters the 'Ready for Hire' stage can log into internal company systems or be paid on the next payroll run. No! Ready for Hire is merely a recruiting milestone. The individual is not an employee until the Core HCM Hire business process is initiated, fully approved, and reaches its effective date.
2. The Duplicate Pre-Hire Rehire Error: Questions often present a scenario where a former employee is rehired, but an administrator creates a new Pre-Hire record to "save time" instead of matching the existing record. The exam tests your understanding of the downstream fallout: corrupted tax reporting, duplicate W-2s, and the loss of original continuous service dates.
3. Internal Candidate Staffing Action: If an exam question asks what task a recruiter must launch when an active internal worker accepts an offer in another department, the answer is Change Job (or Transfer/Promote). Launching Hire Employee on an active worker creates a duplicate worker instance and triggers severe system errors.
4. Offer Compensation vs. Requisition Default: An exam question might suggest that the compensation proposed during Make Offer is locked to whatever was originally entered on the Job Requisition. This is false. While the requisition establishes initial budgeting guidelines, the Make Offer process allows recruiters to propose customized compensation plans, subject to compensation policy validations and approval workflows.