Data Template: Hire to Retire - Employee Lifecycle
Your Hire to Retire - Employee Lifecycle Data Template
- Recommended attributes to collect
- Key activities to track
- Practical extraction guidance
Hire to Retire - Employee Lifecycle Attributes
| Name | Description | ||
|---|---|---|---|
|
Activity Name
ActivityName
|
The name of the specific employee lifecycle event that occurred. | ||
|
Description
This attribute describes a single step or milestone in the hire-to-retire process, such as 'Offer Accepted', 'Performance Review Conducted', or 'Employee Terminated'. These activities form the nodes in the process map. Analyzing the sequence, frequency, and duration between these activities is the core of process mining. It helps identify common process paths, deviations, and bottlenecks, which is critical for understanding and optimizing the employee lifecycle.
Why it matters
This attribute defines the steps in the process, allowing for the visualization and analysis of the employee journey.
Where to get
This is typically derived from event logs, audit trails, or by mapping status changes in various UKG Pro modules (e.g., Recruiting, Onboarding, Performance).
Examples
Offer AcceptedPerformance Review ConductedTermination Initiated
|
|||
|
Employee ID
EmployeeId
|
The unique identifier for an employee's lifecycle within the organization. | ||
|
Description
The Employee ID serves as the primary key that connects all lifecycle events for a single employee. It traces the journey from the initial job application and hiring, through various roles and performance reviews, to the final termination and offboarding. In process mining analysis, this attribute is fundamental as the Case ID. It allows for the reconstruction of each employee's end-to-end journey, enabling analyses such as tenure calculation, career path visualization, and turnover pattern identification across different employee segments.
Why it matters
This is the essential Case ID that links all employee-related events together, making it possible to analyze the entire employee journey.
Where to get
This is a core field in most UKG Pro employee profile or master data modules.
Examples
100234598345125501298
|
|||
|
Event Time
EventTime
|
The timestamp indicating when the employee lifecycle event occurred. | ||
|
Description
This attribute provides the exact date and time for each activity, which is essential for ordering events chronologically and calculating durations between them. It forms the timeline of the employee's journey. In process analysis, this timestamp is used to calculate all time-based metrics, such as hiring cycle time, onboarding duration, and time-to-promotion. It is fundamental for performance monitoring, SLA adherence checks, and identifying delays in the process.
Why it matters
This timestamp is crucial for sequencing events correctly and calculating all performance metrics like cycle times and durations.
Where to get
Every transaction or event record in UKG Pro should have a creation or effective date timestamp.
Examples
2023-01-15T09:00:00Z2023-06-20T14:35:10Z2024-02-01T11:21:00Z
|
|||
|
Last Data Update
LastDataUpdate
|
The timestamp when the data was last refreshed from the source system. | ||
|
Description
This attribute indicates the freshness of the data being analyzed. It records the date and time of the last successful data extraction from UKG Pro. In any analysis, knowing the data's timeliness is critical for interpreting the results correctly. It helps users understand if they are viewing the most current process performance and avoids drawing conclusions based on outdated information.
Why it matters
Informs users about the timeliness of the data, ensuring that analyses are based on up-to-date information.
Where to get
This is a metadata field generated by the data extraction tool or script, recording the timestamp of the run.
Examples
2024-05-20T04:00:00Z2024-05-19T04:00:00Z2024-05-18T04:00:00Z
|
|||
|
Source System
SourceSystem
|
Identifies the source system from which the data was extracted. | ||
|
Description
This attribute specifies the origin of the event data, for example, 'UKG Pro'. It is particularly useful in environments where data from multiple systems is combined. For analysis, it helps in data governance, troubleshooting data quality issues, and understanding the technological landscape of the process. It ensures that insights are attributed to the correct system of record.
Why it matters
Provides essential context for data origin, which is crucial for data governance, validation, and multi-system process views.
Where to get
This is typically a static value added during the data extraction and transformation process to label the dataset's origin.
Examples
UkgProUkgPro-RecruitingUkgPro-Payroll
|
|||
|
Department
Department
|
The department or organizational unit the employee belongs to. | ||
|
Description
This attribute represents the department, such as 'Engineering', 'Finance', or 'Human Resources', to which an employee is assigned. Like the job role, this can change during an employee's tenure. Analyzing by department is a primary way to break down process performance across the organization. It is used in nearly all dashboards, from Hiring Cycle Time to Performance Review Adherence, to identify which parts of the business are performing efficiently and which require attention.
Why it matters
Enables performance comparison across different business units, helping to pinpoint department-specific process issues or best practices.
Where to get
Available in the employee's organizational assignment information in UKG Pro.
Examples
TechnologySales and MarketingFinance
|
|||
|
Event Performer
EventPerformer
|
The user or system agent who executed the activity. | ||
|
Description
This attribute identifies the individual or automated system responsible for completing a process step. This could be a recruiter, a hiring manager, an HR administrator, or a system batch job. Analyzing the event performer helps understand resource allocation, workload distribution, and performance differences between individuals or teams. It can highlight opportunities for automation where manual activities are causing bottlenecks and can be used to see if specific users deviate from the standard process.
Why it matters
Identifies who performed an action, which is essential for resource analysis, workload balancing, and identifying training opportunities.
Where to get
This is often found in audit trail logs or 'Last Modified By' fields associated with transactions in UKG Pro.
Examples
recruiter.janemgr.john.doeSYSTEM_BATCH
|
|||
|
Job Requisition ID
JobRequisitionId
|
The unique identifier for the job opening or requisition. | ||
|
Description
This attribute links all early-stage recruitment activities, from creation to offer acceptance, to a specific job opening. It acts as a mini-case ID within the broader employee lifecycle, grouping all candidates who applied for the same position. For hiring analysis, this ID is crucial. It allows the calculation of 'Average Hiring Cycle Time' per requisition and helps analyze the efficiency of the recruitment process for different roles or departments. It connects the 'Job Requisition Created' activity to all subsequent candidate-related events.
Why it matters
Groups all recruitment activities for a specific job opening, enabling accurate hiring funnel and cycle time analysis.
Where to get
This is a primary key in the UKG Pro Recruiting or Talent Acquisition module.
Examples
REQ-2023-05-101REQ-2024-01-205REQ-FIN-003
|
|||
|
Job Role
JobRole
|
The specific title or role of the employee at the time of the event. | ||
|
Description
The Job Role attribute captures the employee's position, such as 'Software Engineer', 'Sales Manager', or 'HR Business Partner'. This can change over time through promotions or role changes. This is a critical dimension for analysis, used to segment and compare process performance. It helps answer questions like, 'Which job roles have the highest turnover?' or 'What is the average hiring time for technical vs. non-technical roles?'. It is essential for the Employee Turnover and Hiring Cycle Time dashboards.
Why it matters
Allows for filtering and comparing processes by employee function, which is key to identifying role-specific trends and bottlenecks.
Where to get
This information is stored in the employee's job or position record within UKG Pro.
Examples
Software Engineer IISenior Financial AnalystMarketing Coordinator
|
|||
|
Manager Name
ManagerName
|
The name of the employee's direct manager at the time of the event. | ||
|
Description
This attribute identifies the direct supervisor of the employee. The manager is often a key actor in many hire-to-retire subprocesses, such as approving promotions, conducting performance reviews, and initiating role changes. In analysis, the manager dimension helps identify variations in process execution that may be tied to specific managers or management styles. It supports KPIs like 'Manager Transition Cycle Time' and can reveal inconsistencies in how processes like onboarding or performance management are handled by different leaders.
Why it matters
Helps analyze process variations by manager, identifying potential training needs or recognizing high-performing leaders.
Where to get
This is part of the employee's reporting structure data within UKG Pro's core HR module.
Examples
Jane SmithJohn DoeEmily Jones
|
|||
|
SLA Target Date
SlaTargetDate
|
The target date by which an activity, like a performance review, should be completed. | ||
|
Description
The Service Level Agreement (SLA) Target Date defines the deadline for certain time-sensitive activities. It is most commonly used for performance reviews, which are typically scheduled annually or semi-annually. This attribute is essential for measuring compliance and adherence to internal policies. By comparing the actual completion time ('EventTime') to the 'SlaTargetDate', we can calculate KPIs like 'Performance Review Adherence' and identify departments or managers who are consistently late with critical tasks.
Why it matters
Enables the measurement of compliance with internal deadlines, especially for performance reviews and other scheduled tasks.
Where to get
This date is often stored in the UKG Pro Performance Management module or can be derived based on the employee's hire date.
Examples
2023-12-31T23:59:59Z2024-06-30T23:59:59Z2024-03-15T23:59:59Z
|
|||
|
Termination Reason
TerminationReason
|
The reason for an employee's departure, such as voluntary or involuntary. | ||
|
Description
This attribute provides context for why an employee's tenure ended. Reasons are often categorized into groups like 'Voluntary - Resignation', 'Involuntary - Performance', or 'Retirement'. This is a vital attribute for any meaningful turnover analysis. It allows the business to distinguish between regrettable and non-regrettable attrition and to focus retention efforts effectively. For example, a high number of voluntary terminations in a specific department may signal management or cultural issues.
Why it matters
Provides critical context for turnover analysis, helping to differentiate between voluntary and involuntary departures.
Where to get
This data is captured during the termination process and stored in the employee's record in UKG Pro.
Examples
Voluntary ResignationInvoluntary - PerformanceRetirement
|
|||
|
Business Unit
BusinessUnit
|
The larger business division or unit the employee belongs to. | ||
|
Description
The Business Unit represents a higher level of organizational structure than a department, such as 'Consumer Products' or 'Enterprise Solutions'. This attribute allows for high-level, strategic analysis of the workforce. It can be used to compare process performance across major divisions of the company, providing an executive-level view of HR process efficiency and employee turnover.
Why it matters
Enables high-level analysis of process performance across major organizational divisions.
Where to get
This is part of the employee's organizational assignment data in UKG Pro.
Examples
Global Technology ServicesCloud and Cognitive SoftwareCorporate HQ
|
|||
|
Candidate ID
CandidateId
|
A unique identifier for a job applicant before they become an employee. | ||
|
Description
The Candidate ID tracks an individual throughout the recruitment process, from application to offer. Once hired, this ID is linked to the new Employee ID. This identifier is crucial for analyzing the pre-hire process in detail. It allows for tracking candidate conversion rates at each stage (application, interview, offer) and is essential for dashboards like 'Background Check Compliance' to ensure all steps are followed for each candidate who accepts an offer.
Why it matters
Tracks individuals through the recruitment funnel, enabling analysis of conversion rates and pre-hire process compliance.
Where to get
This is a primary key in the UKG Pro Recruiting or Applicant Tracking System (ATS) module.
Examples
CAND-843921CAND-910234CAND-100345
|
|||
|
Employee Tenure
EmployeeTenure
|
The total length of time an employee has been with the organization. | ||
|
Description
Employee Tenure is a calculated duration representing the period from the 'Employee Hired' date to either the 'Employee Terminated' date or the current date for active employees. It provides a measure of employee longevity. This metric is fundamental for workforce analysis. It can be used as a dimension to understand how process issues affect employees at different stages of their career. For example, analyzing turnover by tenure can reveal if new hires are leaving disproportionately, indicating potential issues with onboarding or role alignment.
Why it matters
Measures employee longevity, which is a key outcome metric and a valuable dimension for analyzing turnover and engagement.
Where to get
This metric is calculated using the 'Employee Hired' event timestamp and either the 'Employee Terminated' timestamp or the current date.
Examples
3153600000015768000000063072000000
|
|||
|
Employment Type
EmploymentType
|
Categorizes the employee's work arrangement, such as full-time or part-time. | ||
|
Description
This attribute defines the nature of the employment contract, for example, 'Full-Time', 'Part-Time', 'Contractor', or 'Intern'. This status can influence which processes and policies apply to an individual. In analysis, segmenting by employment type can reveal different process behaviors. For instance, the onboarding process for contractors may be significantly different and faster than for full-time employees. This dimension adds valuable context to process variations.
Why it matters
Provides important context that explains variations in process paths and durations for different types of workers.
Where to get
This is a standard field on the employee's core HR profile in UKG Pro.
Examples
Full-TimePart-TimeContractorIntern
|
|||
|
Event End Time
EventEndTime
|
The timestamp indicating when an activity with a measurable duration was completed. | ||
|
Description
While many lifecycle events are instantaneous, some, like 'Background Check' or 'Interview', have a distinct start and end time. This attribute captures the completion timestamp for such activities. Having an end time is necessary for accurately calculating the processing time of individual activities. This allows for a more granular analysis of where time is spent within the process, moving beyond simple cycle time calculations between different activities.
Why it matters
Enables the calculation of the actual duration (processing time) of specific activities, offering a deeper view of process bottlenecks.
Where to get
This may need to be sourced from a separate 'completion date' field in UKG Pro transaction records.
Examples
2023-01-15T11:30:00Z2023-06-21T10:00:10Z2024-02-01T11:25:00Z
|
|||
|
Hiring Cycle Time
HiringCycleTime
|
The total time from creating a job requisition to an offer being accepted. | ||
|
Description
This calculated metric measures the total duration of the recruitment process for a specific job opening. It is typically calculated as the time difference between the 'Job Requisition Created' event and the 'Offer Accepted' event for a given Job Requisition ID. This is a primary KPI for the talent acquisition function, directly measuring the speed of hiring. Analyzing this metric helps identify bottlenecks in the recruitment funnel and is the key component of the 'Hiring Cycle Time Analysis' dashboard.
Why it matters
This is a key performance indicator for recruitment efficiency, quantifying the time it takes to secure a new hire.
Where to get
This is calculated at the case level (per Job Requisition or Employee) using timestamps from the event log.
Examples
388800000025920000005184000000
|
|||
|
Is Performance Review Late
IsPerformanceReviewLate
|
A boolean flag indicating if a performance review was completed after its target date. | ||
|
Description
This is a derived boolean attribute that flags instances where a 'Performance Review Conducted' activity occurred after its corresponding 'SlaTargetDate'. It is calculated by comparing 'EventTime' with 'SlaTargetDate'. This attribute simplifies compliance analysis. Instead of comparing dates directly in every chart, this flag allows for easy filtering and aggregation to calculate the 'Performance Review Adherence' KPI. It quickly highlights non-compliant cases for further investigation.
Why it matters
Provides a simple, binary flag for identifying and analyzing late performance reviews, directly supporting compliance monitoring.
Where to get
This is calculated during data transformation by comparing the 'EventTime' of the review activity with the 'SlaTargetDate'.
Examples
truefalse
|
|||
|
Location
Location
|
The geographical location or office where the employee is based. | ||
|
Description
This attribute specifies the employee's physical or assigned work location, which could be a city, country, or specific office building. It helps in understanding geographical variations in the process. Analyzing by location can uncover regional differences in hiring times, turnover rates, or adherence to global processes. This is particularly useful for large, multinational organizations looking to standardize their HR operations while accounting for local regulations and customs.
Why it matters
Allows for geographical segmentation of the process, highlighting regional differences in performance and compliance.
Where to get
This is part of the employee's work location information stored in their UKG Pro profile.
Examples
New York, USALondon, UKSingapore
|
|||
|
Processing Time
ProcessingTime
|
The duration of time spent actively working on an activity. | ||
|
Description
Processing Time measures the actual time an activity took to complete, from its start to its end. It is calculated as the difference between the 'EventEndTime' and the 'EventTime'. This metric provides a more precise measure of efficiency than cycle time, as it focuses on the duration of a single task rather than the waiting time between tasks. It is useful for identifying which specific activities are the most time-consuming in the entire process.
Why it matters
Measures the actual work duration of an activity, helping to pinpoint which specific tasks are taking the most time.
Where to get
This is calculated from the 'EventTime' and 'EventEndTime' attributes during data transformation.
Examples
864000003600000600000
|
|||
|
Salary Grade
SalaryGrade
|
The compensation grade or band associated with the employee's role. | ||
|
Description
The Salary Grade is an administrative category used by HR to group jobs for compensation purposes. Changes in this grade are often associated with promotions or significant role changes. This attribute is useful for analyzing career progression and the timeliness of data updates. For the 'Employee Data Update Delay' KPI, one could measure the time between a 'Promotion Approved' event and the corresponding change in the 'Salary Grade' field, ensuring HR systems are updated promptly.
Why it matters
Helps track career progression and verifies that compensation-related data is updated in a timely manner following promotions.
Where to get
This is stored in the employee's compensation or job data record within UKG Pro.
Examples
IC3M2EXEC1
|
|||
Hire to Retire - Employee Lifecycle Activities
| Activity | Description | ||
|---|---|---|---|
|
Employee Hired
|
This activity marks the official creation of the employee record in the core HR system, transitioning them from a candidate to an employee. It is captured from the creation date of the core employee profile, often including their start date. | ||
|
Why it matters
This is the definitive point where a candidate becomes an employee in the system of record. It is a fundamental milestone for tracking onboarding efficiency and data timeliness.
Where to get
This is a core event in UKG Pro HR. It can be identified by the creation date of the employee's primary record or their official 'Hire Date' field.
Capture
Use the 'Hire Date' or creation timestamp from the primary employee table or profile.
Event type
explicit
|
|||
|
Employee Terminated
|
This is the final, official event where the employee's status changes to 'Terminated' in the system on their last day of employment. This is captured from the effective date of the termination action. | ||
|
Why it matters
This activity is the primary end point for the employee lifecycle. It is essential for calculating turnover rates and accurately defining the employee's tenure.
Where to get
This is a core HR data point in UKG Pro. It is the effective date of the approved termination transaction in the employee's job history record.
Capture
Use the 'Termination Date' or 'Effective Date' from the employee's final job data record.
Event type
explicit
|
|||
|
Job Requisition Created
|
This activity marks the official start of the hiring process when a new job requisition is created and submitted for approval. It is typically captured as an explicit event when a user finalizes the requisition form in the UKG Pro recruiting module. | ||
|
Why it matters
This is the primary start point for the entire Hire to Retire process. Analyzing the time from this event to 'Offer Accepted' is crucial for measuring the hiring cycle time KPI and identifying recruitment bottlenecks.
Where to get
Recorded in the UKG Pro Recruiting module. This is likely an explicit event log or can be inferred from the creation timestamp of the job requisition record.
Capture
Use the creation timestamp of the job requisition record in the recruiting data tables.
Event type
explicit
|
|||
|
Offer Accepted
|
This event signifies that a candidate has formally accepted the job offer. This is usually captured by a recruiter updating the candidate's status in the UKG Pro system, triggering the next steps in the hiring process. | ||
|
Why it matters
This is a key success milestone in the recruitment process and concludes the hiring cycle time analysis. It serves as the trigger for pre-onboarding activities like background checks.
Where to get
Captured in the recruiting module when the candidate's status is updated to 'Offer Accepted' or a similar state. The timestamp of this status change should be used.
Capture
Use the timestamp when the application status changes to 'Offer Accepted', 'Hired', or an equivalent value.
Event type
inferred
|
|||
|
Payroll Setup Completed
|
This event occurs when the new employee's payroll information, such as bank details and tax forms, is fully entered and verified. This is often inferred from the completion of specific payroll-related tasks in an onboarding checklist. | ||
|
Why it matters
Ensuring timely and accurate payroll setup is critical for a positive new hire experience and operational efficiency. This KPI helps track the final step of core onboarding.
Where to get
This can be inferred from the completion date of payroll-related tasks in the UKG Pro Onboarding module or from the first payroll run data for the employee.
Capture
Inferred from the completion timestamp of all required payroll data entry tasks in the onboarding workflow.
Event type
inferred
|
|||
|
Termination Initiated
|
This activity marks the beginning of the offboarding process when a request to terminate an employee is submitted. It is captured from the creation of a termination transaction, prior to the employee's final day. | ||
|
Why it matters
This is the starting point for the offboarding process. Analyzing the time from this event to 'Offboarding Tasks Completed' helps measure the efficiency and thoroughness of the exit process.
Where to get
Captured in the core HR module when a termination action is entered for an employee. The timestamp corresponds to when this action was first saved or submitted.
Capture
Use the creation or submission timestamp of the termination request/transaction in the employee's job data.
Event type
explicit
|
|||
|
Background Check Initiated
|
Represents the start of the background screening process for a candidate who has accepted an offer. This event is often logged when an HR user initiates the check through an integrated third-party service via UKG Pro. | ||
|
Why it matters
Tracking this activity is essential for ensuring compliance and monitoring the efficiency of pre-employment screening. Delays here can significantly impact the new hire's start date.
Where to get
May be recorded in UKG Pro's onboarding module or through an API log if integrated with a third-party screening provider. Look for a status change or a specific event log.
Capture
Requires identifying the specific transaction or status update related to initiating a background check.
Event type
explicit
|
|||
|
Candidate Applied
|
Represents the moment a candidate submits their application for an open job requisition. This is captured when a candidate profile is successfully created and linked to a specific job opening within the system. | ||
|
Why it matters
Tracking application volume and timing helps analyze the effectiveness of recruitment sources and sourcing strategies. It's a key early-stage event in the talent acquisition funnel.
Where to get
Logged in the applicant tracking system (ATS) component of UKG Pro. Each application should have a submission timestamp.
Capture
Extract the application submission timestamp associated with a candidate and job requisition ID.
Event type
explicit
|
|||
|
Exit Interview Conducted
|
Represents the completion of an exit interview with a departing employee. This is often captured manually by HR or inferred from the completion of an exit interview task in an offboarding checklist. | ||
|
Why it matters
Tracking the completion rate of exit interviews is important for gathering feedback to improve employee retention. Low completion rates may indicate process gaps.
Where to get
May be logged in the UKG Pro Onboarding/Offboarding module as a completed task or in the core HR system as a note or custom field. Capture is often inconsistent.
Capture
Inferred from the completion timestamp of an 'Exit Interview' task in a workflow or a custom field update.
Event type
inferred
|
|||
|
Interview Scheduled
|
This event occurs when an interview is formally scheduled with a candidate in the system. It is usually captured through the recruiting module's interview scheduling feature, which logs the date and time. | ||
|
Why it matters
Analyzing the time between application and interview, and between interview stages, helps identify delays in the screening and selection process. It is a key milestone in the hiring funnel.
Where to get
Found within the UKG Pro Recruiting or ATS module. It can be identified by looking at interview records associated with a candidate's application, specifically the creation date of the schedule.
Capture
Use the creation timestamp of an interview record linked to the candidate's application.
Event type
explicit
|
|||
|
Offboarding Tasks Completed
|
This final activity marks the completion of all administrative offboarding tasks, such as asset recovery and system access removal. It is typically inferred from the completion of an offboarding checklist. | ||
|
Why it matters
Ensuring all offboarding steps are completed is critical for security and compliance. This activity helps verify that the offboarding process was followed correctly and consistently.
Where to get
Found in the UKG Pro Onboarding/Offboarding module. This is inferred from the completion timestamp of the final task in the offboarding checklist or workflow.
Capture
Use the completion timestamp of the offboarding checklist or the final task within that checklist.
Event type
inferred
|
|||
|
Offer Extended
|
Marks the point when a formal job offer is generated and sent to a candidate. This is typically an explicit action logged in the recruiting module when an offer letter is created or an offer status is updated. | ||
|
Why it matters
This activity is a critical milestone before hiring. Tracking the time from this event to 'Offer Accepted' helps measure candidate decision time and the competitiveness of offers.
Where to get
UKG Pro's recruiting module should have a specific status or log entry for job offers. Look for an offer status change to 'Extended' or a creation date on an offer record.
Capture
Inferred from a change in the candidate's application status to 'Offer Extended' or a similar state.
Event type
inferred
|
|||
|
Onboarding Initiated
|
This signifies the start of the formal onboarding process or workflow for the new employee. This is typically captured when an onboarding workflow is assigned or started in the UKG Pro Onboarding module. | ||
|
Why it matters
This activity kicks off the new hire integration process. Analyzing the time from this point to subsequent steps like 'Payroll Setup Completed' measures onboarding efficiency.
Where to get
Found in the UKG Pro Onboarding module. This is likely the start timestamp of a checklist or workflow assigned to the new employee.
Capture
Use the creation timestamp of the onboarding workflow or task list for the employee.
Event type
explicit
|
|||
|
Performance Review Conducted
|
This activity marks the completion of a formal performance review cycle for an employee. It is usually captured when a manager submits the final review form in the performance management module. | ||
|
Why it matters
Monitoring this activity is essential for tracking adherence to performance management policies. It helps ensure employees receive regular feedback for their development and engagement.
Where to get
Logged in the UKG Pro Performance Management module. The event can be identified by the submission or completion timestamp of a performance review form.
Capture
Use the final submission or approval timestamp of the performance review document.
Event type
explicit
|
|||
|
Promotion Approved
|
This event signifies the final approval of an employee's promotion. This is typically captured when a transaction changing the employee's job title, grade, or compensation for a promotion is approved and becomes effective. | ||
|
Why it matters
Tracking promotion approvals is key to analyzing internal mobility and career progression. The cycle time from initiation to approval reveals efficiency in the talent management process.
Where to get
This event is captured through employee job data change records. It can be identified by looking for approved transactions with a 'Promotion' reason code and its effective date.
Capture
Filter for approved job data changes where the action reason is 'Promotion' and use the approval or effective timestamp.
Event type
explicit
|
|||
|
Role Change Initiated
|
Represents any change in an employee's job, including promotions, transfers, or lateral moves. This is captured when a manager or HR initiates a job data change request in the system. | ||
|
Why it matters
This activity provides visibility into all types of internal employee movement, not just promotions. It helps understand organizational dynamics and restructuring.
Where to get
Logged in UKG Pro's core HR module as an 'employee job change' or similar transaction. The initiation date of the transaction should be used.
Capture
Use the creation timestamp of a job information change record, identified by various action reason codes like 'Transfer' or 'Reassignment'.
Event type
explicit
|
|||
|
Training Assigned
|
Represents the assignment of required training courses or learning paths to an employee. This is typically logged when a manager or admin assigns training in the UKG Pro Learning module. | ||
|
Why it matters
This activity is crucial for tracking compliance and employee development. The cycle time from hire to training assignment measures how quickly new employees are enabled.
Where to get
Recorded in the UKG Pro Learning or talent management module. Look for the assignment date of a course or learning plan to the employee's profile.
Capture
Use the enrollment or assignment timestamp from the learning management system (LMS) data tables.
Event type
explicit
|
|||