Reference: Fields in People Analytics
People Analytics renders data from mapped fields to calculate metrics and generate content for KPIs, stories, and visualizations. For each topic area you select, some fields are required and some fields are optional. Fields are assigned to the corresponding pipeline: Worker, Hiring, or Skills.
Worker Fields
People Analytics organizes Worker fields into these categories:
Worker Basic Information
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Report Effective Date
| Date | Effective date of the monthly data snapshot. | 2018-01-01 | Required | |
Employee ID
| Text | Unique identification of the worker. | H7O90lme0012U | Required | |
Employee Name
| Single Instance | Full legal name of the worker. | Jane Smith | ||
Active Status
| Boolean | Boolean field that indicates the active status of the employee. | True/False | Required | |
Worker Type
| Single Instance | Worker type (employee or contingent worker) for a worker. | Regular | Required | |
Hire Date
| Date | Most recent hire date for the worker. This field can't be effective dated. | 2018-01-01 | Required | |
Termination Date
| Date | Effective date of the last termination of the worker.
To include terminations with a next-day rehire, use the Termination Date - All field. | 2018-01-01 | Required | |
Ethnicity
| Single Instance/ Text | Ethnicity of the worker. | Asian, Black or African American, White, Hispanic, Two or More Races, Other, Native Hawaiian or Other Pacific Islander, American Indian or Alaska Native | ||
Generation
| Single Instance | Generation cohort of the worker. | Baby Boomers (year range) | ||
Intersection 1
| Single Instance/ Text | Field that defines the intersection values found in the VIBE Index. Refer to setup details for VIBE Index for instructions on how to choose and create intersections. | Male-Asian | Required to configure the VIBE Index topic area. |
Job Hierarchy
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Job Family Group
| Single Instance/ Text | Category of the job family group. | Sales | ||
Single Job Family
| Single Instance/ Text | Job family for the primary position of the worker. | Pre-Sales | ||
Job Details
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Job Level
| Single Instance | Job level position of the employee. | P3 | ||
Manager ID
| Text | Unique identification of the manager of the worker. | H7090192Sfdfj102 | ||
Is Leader
| Boolean | Boolean value that indicates whether an employee is in a leadership (usually director and above) position. | True/False | ||
Manager
| Boolean | Boolean value for whether a worker is in a manager role. | True/False | ||
Last Promotion Date
| Date | Effective date of the last promotion of the employee. | 2018-01-01 |
Compensation
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Total Compensation Calc Field
| Currency | Total compensation for a worker in USD.
We don't recommend using a different currency, as it skews People Analytics results. | 402800.00 USD | ||
Compa Ratio
| Numeric | Employee compensation rate. Formula field must follow for calculating compa-ratio: Base Pay or Primary Compensation / Compensation Range 50th percentile or Range Midpoint Value. (Compensation Range 50th percentile or Range Midpoint Value is determined by system setup.) | 1.038 | ||
Compa Ratio Range
| Single Instance | Category for compensation rate. | Above Compa-Ratio |
Primary Hierarchy
For more details, see Concept: Hierarchies and Organizations in People Analytics.
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Assigned Organization
| Single Instance | The organization that is assigned to the primary position of the worker. Typically, this is Supervisory Organization, but in rare cases might be a different organization type, such as a custom organization or Cost Center. | Planning Workforce QA | Required | |
Level 1
| Single Instance | The 1st level of the hierarchy that you want to analyze. Typically, this is the 2nd level from the top of the organization, 1 level below the CEO.
The field you select must be in the same organization hierarchy as the Assigned Organization. | 2000 Executive Management | ||
Level 2
| Single Instance | The 2nd level of the hierarchy that you want to analyze. Typically, this is the 3rd level from the top of the organization, 2 levels below the CEO.
The field you select must be in the same organization hierarchy as the Assigned Organization. | 3000 Finance Administration | ||
Level 3
| Single Instance | The 3rd level of the hierarchy that you want to analyze. Typically, this is the 4th level from the top of the organization, 3 levels below the CEO.
The field you select must be in the same organization hierarchy as the Assigned Organization. | 4000 Executive Management |
Secondary Hierarchy
For more details, see Concept: Hierarchies and Organizations in People Analytics.
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Level 1
| Single Instance/ Text | The 1st level of the hierarchy that you want to analyze. Typically, this is part of a geographical hierarchy, such as market region. | North America | ||
Level 2
| Single Instance/ Text | The 2nd level of the hierarchy that you want to analyze. Typically, this is part of a geographical hierarchy, such as country. | United Kingdom | ||
Level 3
| Single Instance/ Text | The 3rd level of the hierarchy that you want to analyze. Typically, this is part of a geographical hierarchy, such as city.
When you constrain access to the application data using the secondary hierarchy, then this level must be associated with the worker, and you must opt into this field. | Pleasanton |
Organization Details
For more details, see Concept: Hierarchies and Organizations in People Analytics.
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Organization Level
| Numeric | Number of levels down from the top level of the organization to the assigned organization. | 4 | ||
Management Level
| Single Instance/ Text | Management level of the worker. | 6 Director | ||
Cost Center
| Single Instance | Cost center (or equivalent) used for reporting. | 2069 - Augmented Analytics | ||
Company
| Single Instance/ Self-Referencing Instance | Company name or ID of the company. | Workday, Inc. |
Talent and Performance
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
High Potential
| Boolean | Boolean value for whether an employee is of high potential, based on the company definition of high potential (values only for employees, not contingent workers). | True/False | ||
High Performer
| Boolean | Boolean value for whether an employee is a high performer, based on the company definition of high performer. | True | ||
Current Rating
| Numeric/ Single Instance/ Text | Numeric value representing the employee rating, which is based on the company definition of current rating. | 4 |
Tenure Information
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Length of Service in Partial Years
| Numeric | Employee tenure in years, including partial years. | 4.23 | ||
Tenure Category
| Single Instance/ Text | Tenure category for the worker in their current position. | 10-15 Years |
Termination Information
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Term Category
| Text | Field representing termination category. Values "Voluntary" / "Involuntary" must be present as text. If they're not, import the appropriate field as a Text field. | Voluntary/ Involuntary | ||
Termination Reason
| Single Instance/ Text | Primary termination reason for the worker. | Personal |
Other
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|
Hiring Fields
Hiring fields are only available for Workday Recruiting customers. People Analytics organizes Hiring fields into these categories:
Recruiting Process
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Created Moment
| Date | Moment at which the recruiting status instance was originally created in Workday. | 10/15/2015 10:23:10 AM | Required | |
Candidate ID
| Text | ID of the candidate on the job application. | CANDIDATE-16-11 | Required | |
Stage
| Single Instance/ Text | Recruiting stage of the recruiting status. This field is of the type instance. | Review | Required | |
Stage Name
| Text | Recruiting stage of the recruiting status. This field is of the type text. | Review | ||
Status Start Date
| Date | Date and time the candidate entered the recruiting status. | 2019-21-09 | Required | |
Time In Stage
| Numeric | Duration of time the candidate spent in the recruiting stage. | 10 | ||
Disposition Reason
| Text | Disposition reason for a candidate being rejected/declined for the recruiting process. | Does not meet job qualifications | ||
Candidate Disposition Reason
| Text | External-facing disposition reason for an internal and external candidate job application business process. | Qualifications not met |
Candidate Information
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Gender
| Single Instance | Gender of the candidate. | Female | ||
Ethnicity
| Single Instance/ Text | Ethnicity of the candidate. | Asian, Black or African American, White, Hispanic, Two or More Races, Other, Native Hawaiian or Other Pacific Islander, American Indian or Alaska Native | ||
Candidate Veteran Status
| Single Instance/ Text | Veteran status of the candidate. | I am not a veteran | ||
Candidate Disability
| Single Instance/ Text | Disability status of the candidate. | No, I don't have a disability | ||
Candidate Worker
| Single Instance | Name of the candidate, if a worker record is available in Workday. | Quinn Richardson | ||
Worker Job Requisition
| Single Instance | Job requisition from the worker record of the hired candidate, if a worker record is available in Workday. | R-00015 Web Content Manager (Open) | Required | |
Candidate Worker Hire Date
| Date | Date and time of the initial hire of the candidate, if a worker record is available in Workday. | 2010-24-10 |
Candidate Processing
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Hire Stage
| Boolean | Boolean value for whether the recruiting process is in the hire stage. | True/False | ||
Candidate Stage
| Single Instance/ Text | Recruiting stage the candidate is in for the job requisition, not taking notification delays into consideration. | Ready For Hire | ||
Last Recruiting Stage
| Single Instance/ Text | Last recruiting stage the candidate was in before being rejected/declined for the recruiting process. | Review | ||
Job Application Offer Status
| Single Instance | Most recent offer status of the job application that is in the offer stage or employment agreement stage. | Offer |
Job Requisition Information
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Reference ID
| Text | ID of the job requisition to which the candidate applied. | R00367 | ||
Job Requisition
| Single Instance | Job requisition to which the candidate applied. | R-00015 Web Content Manager (Open) | Required | |
Recruiting Start Date
| Date | First date the recruiting process can start for the position on the job requisition. | 2015-15-10 | ||
Job Requisition Filled Date
| Date | Date and time on which the job requisition was filled. | 2010-24-10 | ||
Candidate Job Requisition Status
| Single Instance/ Text | Status of the job requisition to which the candidate applied. | Review | ||
Employee Type
| Single Instance | Employee type on the job requisition. | Regular | ||
Time Type
| Single Instance/ Text | Time type hiring requirement on the job requisition. | Full time | ||
New Position
| Boolean | Boolean value for whether the job requisition created a new position. | True/False | ||
Job Profile
| Single Instance/ Text | Job profile for the job requisition. | Regional Sales Manager | ||
Job Posting Title
| Text | Name of the position on the job requisition. | Senior Risk Specialist | ||
Job Requisition Management Level
| Single Instance | Management level for the job profile on the job requisition. | 11 Individual Contributor |
Source of Candidates
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Candidate Source Category
| Single Instance | Category of the recruiting source of the candidate for the job application. | External | ||
Candidate Source
| Single Instance/ Text | Recruiting source (internal, referral, or other) for the candidate for the job application. | LinkedIn | ||
Job Application Source
| Single Instance | Recruiting source (LinkedIn, Glassdoor, etc.) for the candidate for the job application. | Referral | ||
Internal Candidate
| Boolean | Boolean value for whether the source category for this job application is of internal type. | True/False |
Primary Hierarchy
For more details, see Concept: Hierarchies and Organizations in People Analytics.
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Assigned Organization
| Single Instance | The organization that is assigned to the primary position of the job requisition. Typically, this is Supervisory Organization, but in rare cases might be a different organization type, such as a custom organization or Cost Center. | Planning Workforce QA | Required | |
Level 1
| Single Instance | The 1st level of the hierarchy that you want to analyze. Typically, this is the 2nd level from the top of the organization, 1 level below the CEO.
The field you select must be in the same organization hierarchy as the Assigned Organization. | 2000 Executive Management | ||
Level 2
| Single Instance | The 2nd level of the hierarchy that you want to analyze. Typically, this is the 3rd level from the top of the organization, 2 levels below the CEO.
The field you select must be in the same organization hierarchy as the Assigned Organization. | 3000 Finance Administration | ||
Level 3
| Single Instance | The 3rd level of the hierarchy that you want to analyze. Typically, this is the 4th level from the top of the organization, 3 levels below the CEO.
The field you select must be in the same organization hierarchy as the Assigned Organization. | 4000 Executive Management |
Secondary Hierarchy
For more details, see Concept: Hierarchies and Organizations in People Analytics.
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Level 1
| Single Instance/ Text | The 1st level of the hierarchy that you want to analyze. Typically, this is part of a geographical hierarchy, such as market region. | North America | ||
Level 2
| Single Instance/ Text | The 2nd level of the hierarchy that you want to analyze. Typically, this is part of a geographical hierarchy, such as country. | Germany | ||
Level 3
| Single Instance/ Text | The 3rd level of the hierarchy that you want to analyze. Typically, this is part of a geographical hierarchy, such as city.
When you constrain access to the application data using the secondary hierarchy, then this level must be associated with the worker, and you must opt into this field. | London |
Organization Details
For more details, see Concept: Hierarchies and Organizations in People Analytics.
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Cost Center
| Single Instance/ Text | Cost center (or equivalent) used for reporting. If you use Cost Center as the primary or secondary hierarchy, then you can select a field from a different organization that Workday can use for providing more details on the job requisition. | 2069 - Augmented Analytics |
Skills Fields
People Analytics organizes Skills fields into these categories:
Required Opt-ins
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Match Score
| Numeric | Match score is a calculation that compares a worker's current portfolio of explicit and inferred skills to the skills (explicit and inferred) listed on their job profile. Workday calculates the skill gaps and subtracts the total from 1 to assign each worker a score on a scale of 0 - 1.
This is an opt-in field and isn't a part of the field mapping for the Skills pipeline. | 0.45 | Required | HCM ML automatically generates values for this field. |
Worker Skills and Gaps
Field | Field Type | Description | Example Value | Required? | How To Populate This Field In Workday |
|---|---|---|---|---|---|
Skill Categories
| Multi-Instance | Skill categories assigned to a maintained or Skills Cloud skill. | Pre-Sales, Retail Sales | Required | |
Skill Reference ID
| Text | Skill Reference ID to use for lookups within our Workday Web Services. | S0929 | Required | |
Skills Report Effective Date
| Date | Field that determines which skills records are included in the monthly data snapshot. | 2022-01-01 | Required |