7.3 Hire Process End-to-End
Key Takeaways
- Hire is the staffing business process that creates a new Employee Worker (when the person is new) and places them into a job—into a vacant Position under Position Management or into a Supervisory Organization under Job Management rules.
- Common initiators include HR Partners and other secured staffing roles; approvers follow the Hire business process definition (manager, HR, finance, compensation as designed).
- Propose Compensation (or equivalent compensation steps) often runs in the Hire flow so pay is set with grade/package defaults and eligibility validation before the worker is fully staffed.
- Effective dating on Hire determines when the employment and job become true; entry moment is not the same as hire effective date.
- Exam traps: Hire ≠ Create Position; Hire ≠ Add Job (Add Job is additional employment for an existing Worker); Contract Contingent Worker is the contingent counterpart, not classic employee Hire.
7.3 Hire Process End-to-End
Quick Summary: Hire is the core staffing event that brings a new Employee Worker into Workday (or staffs a rehire path when configured) and assigns a job. In Position Management you fill a vacant Position; in Job Management you hire into the Supervisory Organization under org hiring restrictions. Compensation proposal steps, approvals, and effective dating complete a compliant hire.
Blueprint task T32 Hire process sits at the center of HCM Fundamentals. Almost every earlier topic—organizations, staffing models, Job Profiles, position restrictions, compensation defaulting—shows up inside one Hire event.
What Hire Creates and Changes
| Outcome | Typical Hire result |
|---|---|
| Worker | Creates a new Employee Worker when the person does not already exist as that worker type |
| Job | Creates the worker’s primary job assignment (profile, org context, time type, etc.) |
| Position occupancy | In Position Management, fills the targeted vacant Position |
| Organization assignments | Applies Sup Org and related orgs from position/job context |
| Compensation | Through propose/request compensation steps tied to the Hire BP |
| Downstream work | Onboarding To Dos, benefits eligibility windows, security role implications as designed |
Hire vs related staffing verbs (high-yield)
| Process | Creates new Worker? | Typical use |
|---|---|---|
| Hire | Yes (new employee path) | Brand-new employee employment |
| Contract Contingent Worker | Contingent worker path | Non-employee contractor staffing (Chapter 8) |
| Add Job | No | Additional job for an existing Worker (dual employment) |
| Change Job | No | Transfer, promotion, demotion, lateral, data change for existing job |
| Create Position | No | Seat capacity only |
Exam trap: If the person already works for you and needs a second concurrent job, the answer is often Add Job, not Hire. If they are brand new as an employee, Hire is correct.
Position Management vs Job Management Hire Paths
Position Management:
Vacant Position (restrictions) ──► Hire into Position ──► Filled Position + Worker Job
Job Management:
Sup Org hiring restrictions ──► Hire into Sup Org ──► Worker Job (no persistent vacant seat inventory)
Position Management hire essentials
- Identify the open Position (or Create Position as part of / before Hire per tenant design).
- Validate proposed attributes against position restrictions (Job Profile, location, worker type, etc.).
- Complete Hire BP steps including personal data, job details, compensation, and approvals.
- On success, position is filled and the worker’s primary job points at that seat.
Job Management hire essentials
- Choose the Supervisory Organization.
- Select an allowed Job Profile and attributes inside org hiring restrictions.
- Complete Hire BP; no pre-created vacant Position ID is required for each headcount.
- Headcount increases without leaving a durable empty seat when they later leave.
Configuration scenario: Northwind Corporate HQ (Position Management) hires Sam into vacant P-8840 “Payroll Specialist I.” Store Ops West (Job Management) hires Jordan as “Sales Associate” under store org restrictions without selecting a vacant position seat. Same Hire BP type family, different capacity mechanics.
Initiators, Approvers, and BP Shape
Hire is a business process. Exam language expects you to think in BP terms even before the dedicated BP chapters:
Common initiators
- HR Partner (role-based on the Sup Org) — classic generalist initiator
- Central HR Admin / staffing specialist roles in some designs
- Occasionally manager self-service initiation when security and BP definition allow
Common approvers and contributors
| Role / step type (conceptual) | Why it appears on Hire |
|---|---|
| Manager | Confirms the hire into their team |
| HR Partner / HR Admin | Policy and data quality |
| Compensation Partner | Pay proposal review when routed |
| Finance | Headcount or budget gates when configured |
| To Dos | Background check, equipment, I-9-style tasks (tenant/country specific) |
Exact chains are tenant-configured. The exam cares that Hire is not a single silent save: it is an event with steps, security, and possible subprocesses (Propose Compensation, Edit Service Dates, etc.).
Propose Compensation in the Hire Context
Compensation is not a separate chapter’s problem only—Hire is where many workers receive their first pay setup.
What you should expect conceptually
- Job Profile and compensation eligibility rules determine which package/plans/grades can apply.
- Compensation defaulting may propose grade, salary plan amounts, or allowance defaults from profile/package design.
- A Propose Compensation (or Request Compensation Change–style) step collects the actual offer pay.
- Validation may warn or block amounts outside grade min/mid/max or grade profile ranges.
- Approvals may differ for above-range offers.
| Hire compensation idea | Link to Compensation chapter |
|---|---|
| Grade on profile | Default pay band guidance |
| Eligibility rules | Which plans the hire can receive |
| Package | Bundle of plans available |
| Salary / allowance plans | Components of total pay |
| Maintain worker compensation later | Post-hire changes via compensation events |
Exam trap: Completing Hire without thinking about compensation is incomplete; assuming compensation replaces Hire is also wrong. Compensation steps are part of or subprocess of the staffing event, not a substitute for creating the Worker job.
Effective Dating on Hire
Effective date on Hire is when employment and the job assignment become true in HCM:
- Future-dated hires stage workers who start next month.
- As-of reporting shows no active primary job before the effective date.
- Payroll and benefits eligibility windows key off effective-dated employment, not “when HR clicked Submit.”
| Concept | Meaning |
|---|---|
| Hire effective date | When the worker is employed / job is active as of |
| Entry moment | When the initiator submitted the event in the UI |
| Position effective / availability | Seat capacity timing—must align so the seat is fillable as of the hire date |
Configuration scenario: Offer accepted 10 March for start date 1 April. HR initiates Hire with effective date 1 April into a position available 1 April. Manager approval completes 12 March. The worker is not treated as active on 15 March reports even though the BP already finished—effective dating controls the business truth.
End-to-End Hire Narrative (Memorize)
- Capacity ready — Position open (Position Management) or org restrictions allow hire (Job Management).
- Initiate Hire with security on the target org/position.
- Enter legal/name, contact, and biographic data as required.
- Confirm job details — Job Profile, location, time type, company, cost center, Sup Org/position.
- Complete Propose Compensation with eligible plans and valid amounts.
- Route approvals and complete To Dos.
- Event completes → Worker + Job active as of effective date; position filled if applicable.
- Optional onboarding processes continue after Hire completion.
Failure Diagnosis Table
| Symptom | Likely cause class |
|---|---|
| Cannot find Hire task / cannot submit | Security (domain/BP permissions, org assignment) |
| No vacant position to select | Capacity — Create Position first or wrong staffing model expectation |
| Position listed but hire blocked | Freeze/close/availability or restriction mismatch |
| Profile not allowed | Position restrictions or org hiring restrictions |
| Pay amount rejected | Compensation grade / eligibility / validation |
| Event sits in Inbox | Approval step pending |
What Hire Does Not Do
- Does not replace Create Job Profile for a brand-new enterprise role type (create catalog first).
- Does not permanently close a position when someone later leaves.
- Does not perform Terminate or End Additional Job.
- Does not by itself redesign Supervisory Organization hierarchies (that is reorganization / org admin).
If you can walk Hire from capacity → initiate → job details → compensation → approve → effective-dated Worker, you have T32 at Pro level and a bridge into job-change staffing in the next section.
What does a successful employee Hire typically create when the person is new to the tenant as an employee?
In Position Management, what must generally be true before Hire can fill a seat?
Why does Propose Compensation commonly appear during the Hire business process?
An existing Worker needs a second concurrent job without ending the first. Which process is appropriate instead of Hire?