Skip to content
KiweelyKiweelyKiweely

Why Candidates Get Stuck Between ‘Offer Accepted’ and ‘Ready for Hire’ in Workday Recruiting

Candidates stall between Offer Accepted and Hire in Workday Recruiting when the Make Offer Decision step remains incomplete, Automatic Stage Routing rules fail, parallel Background Check or Candidate Home tasks block Ready for Hire, or the target position fails availability checks.

  • By Kiweely
  • 7 min read
On this page

When a candidate signs an offer on Friday and HR still cannot see a Hire event on Monday morning, the breakdown almost always sits in one of four places: an unfinished Make Offer Decision or Candidate Home task inside a recruiting subprocess, a failing condition rule on Automatic Stage Routing or Possible Next Steps in the dynamic Job Application business process, a security mismatch between Ready for Hire and the downstream staffing workflow, or a target Position Restriction whose Available for Hire flag flipped to No.

Because Job Application is a dynamic container of linear subprocesses (Review, Screen, Assessment, Interview, Reference Check, Offer, Employment Agreement, Background Check, and Ready for Hire), looking only at the recruiter’s pipeline view hides which layer stalled. Open Business Process Event History on the candidate’s job application first and match what you see against this diagnostic table.

Fast Triage: Where Did the Handoff Break?

What You See on the Job Application Actual State in Workday Exact Fix or Diagnostic Check
What You See on the Job ApplicationCandidate e-signed the offer letter, but stage still says Offer Actual State in WorkdayReview Document finished, but Make Offer Decision (completion step) or a candidate task is still awaiting action Exact Fix or Diagnostic CheckComplete Make Offer Decision, check Candidate Home tasks, or check for >72 skipped steps stalling Offer
What You See on the Job ApplicationOffer is Successfully Completed, but candidate sits in Offer with no auto-advance Actual State in WorkdayAutomatic Stage Routing (ASR) failed because stage ASR rules or Possible Next Steps rules returned false Exact Fix or Diagnostic CheckCheck ASR conditions and Possible Next Steps conditions on the Offer tab of Job Application
What You See on the Job ApplicationRecruiter clicks Move Forward, and Ready for Hire is missing from the dropdown Actual State in WorkdayCondition rule on Possible Next Steps failed, or recruiter’s role is missing from that row’s Group Exact Fix or Diagnostic CheckSelect Business Process > View Definition on the event, inspect Offer / Background Check tab
What You See on the Job ApplicationCandidate entered Ready for Hire, but Hire (or Change Job) never launched Actual State in WorkdayQuestionnaire/task inside Ready for Hire is incomplete, or initiator lacks Initiating Actions on Hire Exact Fix or Diagnostic CheckCheck Ready for Hire subprocess history and Hire business process security policy
What You See on the Job ApplicationHire fails to complete with "proposed organization, position, headcount restriction, or job requisition selected is no longer available" Actual State in WorkdayTarget position has Available for Hire = No (frozen, Earliest Hire Date after hire date, or competing event) Exact Fix or Diagnostic CheckAudit all 9 position availability rules (detailed below)

1. “Offer Accepted” Is Not the Same as “Offer Subprocess Completed”

Recruiters routinely assume that once DocuSign, Adobe Acrobat Sign, or Workday e-signature marks the Review Document step complete, the Offer workflow is finished. In Workday, Offer only completes when its designated Completion step (typically Make Offer Decision) finishes. If Make Offer Decision is routed manually to Primary Recruiter instead of automated upon candidate acceptance, the subprocess stays In Progress until the recruiter clicks through their My Tasks item.

Check three less obvious traps inside Offer and parallel stages:

  1. Unfinished Candidate Home tasks: Teams often attach Change Personal Information, Change Government Identifiers, Complete Questionnaire, or Update Candidate U.S. Veteran Status steps to Offer, Background Check, or Ready for Hire. External candidates only see those tasks if they have a Candidate Home account (controlled via Require Candidate Home Account on Edit Tenant Setup - Recruiting and the External Site Task Link notification field). Note also that Candidate Home has no general inbox; if your email notification omitted External Site Task Link or Create Candidate Home Account URL, the candidate never sees the gating task.
  2. Stalled Offer event after 72 consecutive skipped steps: Complex global Offer definitions packed with conditional document generation blocks and regional approvals can hit Workday’s loop-prevention ceiling: if an Offer process hits more than 72 consecutive steps that require no manual interaction (Not Required or Automatically Skipped), Workday stalls the event. A business process administrator must run Manually Process Business Process to advance it, then split the definition into rule-based Offer definitions.
  3. Effective-dating lag on in-progress applicants: Suppose you fixed a broken step on Job Application yesterday, yet candidates who applied three weeks ago still hit the old routing. By default, Workday locks a candidate’s Job Application and subprocess definitions to the date they applied. Run the Maintain Business Process Definition Selection report to enable business process and subprocess effective dating so updates apply immediately to in-progress candidates.

Need to Fix Hire Date or Pay After Reaching Ready for Hire?

Once a candidate reaches Ready for Hire, Workday locks the completed Offer subprocess against direct Correct actions. Similarly, if a tenant uses both Offer and Employment Agreement sequentially, advancing into Employment Agreement permanently disables reverting to Offer or renegotiating. To amend offer terms at Ready for Hire, cancel the Hire event first, run Undo Move on the job application, re-initiate Offer, and advance again.

2. Why Automatic Stage Routing (ASR) or “Move Forward” Hides Ready for Hire

When Offer or Background Check completes and Automatic Stage Routing fails to push the candidate into Ready for Hire, administrators usually check the ASR rule and stop there. Workday actually requires three conditions to hold simultaneously for ASR to fire:

  1. The subprocess step where ASR is enabled must reach completion.
  2. Every condition rule configured inside Automatic Stage Routing for that stage must evaluate to true.
  3. Every condition rule also listed under Possible Next Steps for that exact stage transition (for example, Offer -> Ready for Hire) on the Job Application dynamic definition must evaluate to true.

That third requirement catches experienced admins off guard. If Possible Next Steps has a rule checking Background Check Status = Pass while the candidate is an internal transfer whose Background Check stage was skipped, ASR silently stops—and when the recruiter clicks Move Forward manually, Ready for Hire disappears from the dropdown too. Verify both rule sets and confirm the recruiter’s security group is assigned in the Group column on Possible Next Steps.

3. The Recruiting-to-HCM Security Boundary

Ready for Hire is the completion step of Job Application. When Ready for Hire finishes (either immediately if only Step a Initiation exists, or after final questionnaires and Decline Remaining Jobs / Decline Remaining Candidates batch steps), Workday crosses out of Recruiting and launches one of five HCM staffing business processes depending on the candidate and requisition:

  • Hire (external new hire or rehire)
  • Contract Contingent Worker
  • Change Job (internal employee transfer or promotion)
  • Convert Contingent Worker
  • Add Additional Job

Here is where domain vs. business process security policies collide. Having permission on the Ready for Hire subprocess security policy does not grant permission to launch Hire or Change Job. Open the Business Process Security Policy for Hire (and Change Job for internal mobility) and verify two sections for the security group completing Ready for Hire (such as Primary Recruiter or Recruiting Coordinator):

  • Initiating Actions: Must include the Recruiting / Ready for Hire initiating action for that group.
  • View All: Workday’s Hire Business Process Guidelines specifically recommend granting View All on Hire to roles that initiate the process so all initiation validations execute properly.

Also watch Autocomplete behavior on Hire: if you enabled Enable Autocomplete on Hire (or automatic compensation on Propose Compensation Hire), remember that Propose Compensation Hire autocomplete applies to external candidates only, never autocompletes Request One-Time Payment or Request Stock Grant, and falls back to manual workflow whenever any required staffing field was left blank in Recruiting and lacks a rule in Maintain Staffing Field Defaults.

4. The Nine Position Restrictions That Block Hire Completion

Sometimes Ready for Hire triggers Hire, and the transaction immediately hits a hard wall:

text
Error: This business process could not be completed because the proposed
organization, position, headcount restriction, or job requisition selected
is no longer available to be filled.

In Position Management supervisory organizations, Workday only marks a seat Available for Hire = Yes when all nine of these conditions hold at the moment Hire runs:

  1. The Create Position business process is fully Completed.
  2. Position Availability Date is on or before today’s date.
  3. Position Earliest Hire Date is on or before the Hire effective date (pulling a candidate’s start date forward by one week frequently violates Earliest Hire Date!).
  4. The position restriction is not already filled and has no in-progress or completed Freeze Position event.
  5. The parent Supervisory Organization is not frozen.
  6. No in-progress merit promotion is tied to the position restriction.
  7. No other in-progress staffing event already proposes this position restriction.
  8. No future-dated Move Worker (By Organization) or Move Worker (Supervisory) event is pending on the restriction.
  9. No in-progress or completed Close Position event (or in-progress Job Requisition edit event) locks the restriction.

Check Unassigned Tasks as well once Hire launches: if an onboarding step inside Hire was accidentally routed to Employee as Self instead of Pre-Employee as Self for a future-dated hire whose Workday account is not yet active, the Hire workflow stalls with no assignee.

Tracing Stuck Candidates Without Clicking Twelve Screens

Diagnosing a single stuck candidate across Job Application dynamic tabs, Offer subprocess history, Maintain Business Process Definition Selection, Hire initiating security, and position restriction dates takes 20 minutes of tab-hopping per ticket. Consultants and HRIS admins using Kiweely Vine connect directly to the tenant, inspect every condition rule, subprocess status, and position availability date on the stalled application in one conversation, and run multi-persona browser tests in a visible, stoppable browser before changing business process definitions with explicit consent.

Frequently asked questions

Why did a candidate sign the offer letter in Candidate Home, yet the application never moved to Ready for Hire?

Signing a Review Document step via Workday e-signature, DocuSign, or Adobe Sign does not complete the Offer subprocess by itself unless the final Make Offer Decision completion step is also completed or automated, and Automatic Stage Routing plus Possible Next Steps condition rules evaluate to true.

Why is Ready for Hire missing when a recruiter clicks Move Forward on an accepted candidate?

On the dynamic Job Application business process, Workday hides a next step whenever a condition rule on Possible Next Steps evaluates to false, or when the user's security group is not listed in the Group column for that stage transition.

Why didn't our recent edit to the Job Application business process fix candidates who applied last month?

By default, Workday initiates the Job Application business process and its subprocesses using the definition effective on the candidate's application date. Enable business process effective dating on the Maintain Business Process Definition Selection report so changes apply to in-progress candidates.

How do I change a Hire Date or salary on an offer after the candidate already reached Ready for Hire?

Once a job application reaches Ready for Hire, the Offer subprocess is complete and cannot be corrected directly. Cancel the downstream Hire event first, then use Undo Move on the job application to step back, re-initiate Offer with the updated details, and advance back to Ready for Hire.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.