5.3 Job Families, Family Groups & Job Requisitions

5.3 Job Families, Family Groups & Job Requisitions

Quick Summary: Job Families cluster related Job Profiles by functional discipline; Job Family Groups roll families into higher-level buckets for reporting and eligibility. Job Requisitions express hiring demand against that catalog—usually a Job Profile and related staffing constraints—so recruiting fills seats without inventing one-off titles outside the job architecture.

After you can create profiles and explain profile–position–worker links, HCM Fundamentals tasks T18 Job family / family groups and T19 Job requisitions test whether you can organize the catalog and request staffing against it.

Job Families: Purpose

A Job Family is a grouping of Job Profiles that share a common functional discipline. Examples:

• Software Engineering → Engineer I, Engineer II, Senior Engineer, Staff Engineer
• Nursing – Acute Care → RN I, RN II, Charge Nurse
• Finance Operations → Payroll Specialist I/II, Accounts Payable Analyst

Families are not Supervisory Organizations. They do not define who reports to whom. They organize the job catalog for:

1. Reporting — headcount or average pay by family
2. Compensation eligibility — plans or grades limited to certain families
3. Talent and skills frameworks — career paths within a discipline
4. Job-based security groups — access based on family or family group match
5. Recruiting analytics — openings and time-to-fill by discipline

Exam trap: Job Family and Job Family Group are job catalog objects, not organization types. They are not assigned as a substitute for Supervisory Organization, Company, or Cost Center on a position’s org assignments list.

Job Family Groups

A Job Family Group is a higher-level container of Job Families. Example:

Job Family Group: Technology
├── Job Family: Software Engineering
│   ├── Job Profile: Software Engineer I
│   ├── Job Profile: Software Engineer II
│   └── Job Profile: Staff Software Engineer
├── Job Family: IT Support
│   ├── Job Profile: Desktop Support Analyst
│   └── Job Profile: IT Support Lead
└── Job Family: Data & Analytics
    └── Job Profile: Data Analyst II

Why groups matter:

• Executive and HR reports often need “all Technology” without listing every family.
• Eligibility rules may target an entire group (for example, a stock plan for Technology family group).
• Job-based security can key off family group for broader access patterns.
• Clean groups prevent analytics chaos when individual families proliferate.

Creating families and family groups (conceptual)

Typical administrative flow (security-gated to catalog owners):

1. Create Job Family Group (name, effective dating as required).
2. Create Job Family and associate it to the correct family group.
3. When creating or editing Job Profiles, assign the profile to the Job Family.
4. Validate roll-up with a simple report: profiles by family by family group.
5. Wire compensation eligibility, security, or talent config to families/groups only after names stabilize.

Configuration scenario: Global Retail Co. creates Job Family Group “Store Operations,” then families “Store Leadership,” “Store Associates,” and “Inventory & Logistics.” All store manager profiles sit in Store Leadership; associates sit in Store Associates. Compensation builds an eligibility rule for a store bonus plan using Job Family Group = Store Operations. Headcount dashboards filter family group without hard-coding profile names.

How Families Organize Profiles for Reporting and Compensation

Reporting

Without families, reports must list dozens or hundreds of Job Profiles. With families:

• Matrix reports can show headcount by Cost Center × Job Family or openings by Region × Job Family Group.
• Succession and skills reports can constrain to one discipline.
• Audit reports can find profiles missing a family (data quality).

Compensation

Compensation eligibility rules commonly include attributes such as Country, Job Family, Job Family Group, Management Level, Company, or custom calculated fields. That is why correct family assignment on the profile is not cosmetic: a worker whose profile sits in the wrong family may be ineligible for the correct bonus, allowance, or grade profile package.

Job Requisitions

A Job Requisition (often shortened to “req”) is the recruiting/staffing demand object: a formal request to fill a need. On the Pro HCM Core exam, you should understand requisitions as consumers of the job structure, not as a replacement for Job Profiles.

What a requisition typically specifies

Create job requisition (conceptual flow)

1. Initiator (HR, manager, or recruiter—per security and BP) starts Create Job Requisition (or related action from a position/org).
2. Select Job Profile (and position if the seat already exists).
3. Confirm organization, location, and other hiring constraints.
4. Set openings, target hire dates, and justification as required.
5. Submit through the business process (approvals, budget checks, To Dos).
6. Once approved, recruiting works the req; when a candidate is ready, Hire (or similar) fills the worker into the position/job using the same profile alignment.

Configuration scenario: A manager needs two more Store Associates for the West region. They create a job requisition for Job Profile “Store Associate,” Supervisory Org “Store 214,” two openings, location Store 214, referencing unfilled positions if Position Management tracks them. Approvals route per BP. Recruiters post using the profile description and qualifications. Hire events complete the chain from req → worker job → position fill.

Job Family Group
      └── Job Family
            └── Job Profile
                  ├── Position(s)
                  ├── Worker Job(s)
                  └── Job Requisition(s)

Requisitions vs Profiles vs Positions

Exam trap: Creating a requisition does not replace creating the Job Profile. If the role is brand new to the enterprise, create (or approve) the Job Profile first, assign family, then create positions/requisitions that reference it. Requisitions also do not reorganize supervisory reporting—that remains org/reorg work.

Families, Comp, and Security—Connected Examples

1. Eligibility: A geographic differential grade profile applies only when Job Family Group = “Client Services” and Country = US.
2. Reporting: Quarterly workforce review shows attrition by Job Family within the Technology family group.
3. Security: A Job-Based Security Group grants limited HR read access to workers whose profile is in Job Family “Employee Relations.”
4. Requisition quality: Recruiters filter open reqs by family group to balance workload across clinical vs corporate hiring.

Practical Build Checklist (Exam-Relevant)

When a lab or scenario involves families and requisitions:

1. Confirm family groups exist for major architectures.
2. Create families under the correct group with clear names.
3. Assign every new Job Profile to a family on create/edit.
4. Point compensation eligibility and key reports at family/group, not one-off profile lists, when possible.
5. For hiring demand, Create Job Requisition with the correct profile (and position/org constraints).
6. Complete approvals in My Tasks; fill via hire/staffing, not by editing the family name.

Common Exam Confusions

Master this section and you can place every catalog object—profile, family, family group, requisition—in the staffing and recruiting story the Workday Pro HCM Core exam expects under tasks T18 and T19.