Data Template: Hire to Retire - Employee Lifecycle
Your Hire to Retire - Employee Lifecycle Data Template
- Recommended attributes to collect
- Key activities to track
- Extraction guidance
Hire to Retire - Employee Lifecycle Attributes
| Name | Description | ||
|---|---|---|---|
Activity Name ActivityName | The name of the specific event or task that occurred in the employee's lifecycle. | ||
Description This attribute describes a single step or milestone in the Hire to Retire process. Each record in the event log represents one activity, such as 'Offer Extended' or 'Performance Review Conducted'. The sequence of these activities forms the process map. Analyzing the different activities, their order, and their frequency is the core of process mining. It helps to understand what work is being done, identify deviations from the standard process, and locate bottlenecks. Why it matters It defines the steps of the process, allowing for the visualization of the process flow and the analysis of process variations and performance. Where to get Derived from various modules in ADP Workforce Now, representing business events. This often requires mapping system events or status changes to standardized activity names. Examples Job Requisition CreatedOffer AcceptedPerformance Review ConductedEmployee Terminated | |||
Employee ID EmployeeId | A unique system-generated identifier assigned to each employee upon being hired. | ||
Description The Employee ID serves as the unique identifier for each individual's lifecycle within the organization. All events, from job application to termination, are linked to this ID, enabling a holistic view of an employee's journey. In process mining, this ID is essential as the Case ID. It connects all disparate activities like 'Onboarding Initiated', 'Performance Review Conducted', and 'Employee Terminated' into a single, chronological process flow for each employee. This allows for end-to-end analysis of every employee's path through the company. Why it matters It is the fundamental key that links all employee-related events together, making it possible to reconstruct and analyze the entire employee lifecycle process. Where to get This is a primary key in most employee master data tables within ADP Workforce Now. Examples 900134875900256981900487332 | |||
Event Timestamp EventTimestamp | The precise date and time when the activity occurred. | ||
Description This timestamp marks the start of an activity and is fundamental for process analysis. It establishes the chronological order of events, which is necessary to build the process map and understand the flow of the employee lifecycle. Event Timestamp is used to calculate all time-based metrics, such as cycle times between activities (e.g., time to hire) and the duration of specific stages. Analyzing timestamps reveals delays, bottlenecks, and the overall speed of the process. Why it matters It provides the temporal dimension of the process, enabling all duration calculations, bottleneck analysis, and the correct ordering of events. Where to get Typically found as a 'creation date', 'effective date', or 'last modified date' on records within various ADP Workforce Now modules. Examples 2023-01-15T09:00:00Z2023-03-20T14:30:00Z2024-05-10T11:25:13Z | |||
Last Data Update LastDataUpdate | The timestamp indicating when the data was last refreshed or extracted from the source system. | ||
Description This attribute shows how current the data in the process mining tool is. It is a single timestamp applied to the entire dataset during each data load. This information is critical for users to understand the timeliness of the analysis. It helps them know if they are looking at data from yesterday, last week, or last month, which frames their interpretation of the process performance and any recent changes. Why it matters It informs users about the freshness of the data, ensuring they understand the time frame of the analysis and can trust the results. Where to get Generated and stamped on the dataset by the data pipeline or ETL tool at the time of data extraction. Examples 2024-07-28T04:00:00Z | |||
Source System SourceSystem | The system from which the event data was extracted. | ||
Description This attribute identifies the origin of the data. For this process view, it will primarily be 'ADP Workforce Now', but in a broader context, events might come from other integrated systems like an Applicant Tracking System (ATS) or a learning management system (LMS). Tracking the source system helps in data validation, troubleshooting, and understanding the scope of the process data. It ensures clarity on data provenance, especially in environments with multiple integrated HR systems. Why it matters It provides crucial context about data origin, which is essential for data governance, validation, and managing process analyses that span multiple systems. Where to get This is typically a static value added during the data extraction and transformation (ETL) process to label the records. Examples ADP Workforce NowADP_WFN_ETL | |||
Department Name DepartmentName | The department to which the employee or job requisition belongs. | ||
Description This attribute allows for the segmentation of the Hire to Retire process by organizational unit. By filtering or comparing departments, analysts can identify variations in hiring cycle times, onboarding efficiency, or turnover rates. For example, the 'Hiring Cycle Time Analysis' dashboard relies on this attribute to show which departments have the longest or shortest times to hire. Why it matters Department-level analysis is critical for identifying localized process issues and tailoring improvement initiatives to specific business areas. Where to get Available in the employee's position or organizational assignment data in ADP Workforce Now. Examples SalesEngineeringMarketingHuman Resources | |||
Employment Status EmploymentStatus | The current employment status of the employee, such as Active, Terminated, or On Leave. | ||
Description This attribute tracks the overall state of the employee's lifecycle case. It's fundamental for understanding the current workforce composition and for filtering analyses to specific employee populations, like only active employees for performance review analysis or only terminated employees for offboarding analysis. The status changes in response to key lifecycle events like 'Offer Accepted' or 'Employee Terminated'. Why it matters It provides critical context for the case, allowing analysts to filter for relevant employee populations and understand the process flow leading to different outcomes. Where to get A primary field on the employee's core profile in ADP Workforce Now, often labeled 'Employment Status' or similar. Examples ActiveTerminatedLeave of AbsencePending Start | |||
Event Completion Timestamp EventCompletionTimestamp | The timestamp indicating when the activity was completed. | ||
Description This field marks the end of an activity. It is crucial for calculating the processing time or duration of individual tasks within the employee lifecycle. For example, the difference between the Event Timestamp and the Event Completion Timestamp for 'Background Check Initiated' would represent how long the check was in progress. This helps pinpoint specific activities that are taking longer than expected. Why it matters Calculating precise activity durations is essential for identifying bottlenecks and measuring the efficiency of specific steps like onboarding tasks or performance reviews. Where to get Consult ADP Workforce Now documentation. This may be a separate field or inferred from a subsequent status change. Examples 2023-03-15T11:00:00Z2023-05-21T17:35:10Z2024-01-20T10:05:00Z | |||
Hire Date HireDate | The official start date of the employee's employment. | ||
Description The Hire Date is a cornerstone attribute for lifecycle analysis. It serves as the baseline for calculating employee tenure and is a critical input for the 'Early Employee Attrition Rate' KPI, which measures turnover within a specific period after this date. It anchors the employee journey and allows for time-based cohort analysis to see how processes and outcomes have changed over time. Why it matters It is essential for calculating employee tenure and identifying trends in early attrition, which can point to issues in the hiring or onboarding process. Where to get A standard, critical field in the employee's core HR profile in ADP Workforce Now. Examples 2022-08-012023-01-152024-05-20 | |||
Job Title JobTitle | The specific job title or role of the employee or position being filled. | ||
Description Job Title provides a more granular level of detail than Department for analyzing HR processes. It is essential for understanding how processes differ for various roles, such as executive versus entry-level positions. This attribute is used in dashboards like 'Hiring Cycle Time Analysis' and 'Internal Talent Mobility' to break down cycle times and movement patterns by role. Why it matters It enables role-specific analysis to understand if hiring, promotion, or turnover patterns are concentrated in particular job functions. Where to get Available in the employee's position data in ADP Workforce Now. Examples Software EngineerSales DirectorHR Business PartnerMarketing Analyst | |||
Termination Reason TerminationReason | The reason recorded for an employee's termination, such as voluntary or involuntary. | ||
Description When an employee's lifecycle ends, the Termination Reason provides crucial context about the exit. This data is vital for the 'Early Employee Attrition Trends' dashboard, where it helps differentiate between regrettable and non-regrettable turnover. Analyzing termination reasons can reveal underlying issues in management, company culture, or compensation that need to be addressed. Why it matters Understanding why employees leave is fundamental to developing effective retention strategies and improving the overall employee experience. Where to get This data is captured during the termination workflow in ADP Workforce Now. Examples Voluntary - ResignationInvoluntary - PerformanceInvoluntary - LayoffRetirement | |||
User Name UserName | The name of the user, such as an HR representative or manager, who executed the activity. | ||
Description This attribute identifies the human resource involved in a process step. Analyzing activities by user helps understand workload distribution, identify training needs, or flag cases where specific individuals are associated with process delays or deviations. For instance, you could analyze if onboarding tasks are completed faster by certain HR team members. Why it matters It provides accountability and allows for performance analysis at the individual or team level, helping to optimize resource allocation and training. Where to get Consult ADP Workforce Now documentation. Often found in fields like 'Modified By', 'Created By', or 'Processor'. Examples John SmithJane DoeHR_Admin_User | |||
Business Unit Name BusinessUnitName | The larger business unit or division the employee belongs to. | ||
Description The Business Unit provides a higher-level organizational grouping than Department. It is useful for executive-level dashboards that compare performance across major divisions of the company. For example, an analysis could reveal that one business unit has a significantly higher internal mobility rate, prompting further investigation into their talent development practices. Why it matters It enables high-level strategic analysis of HR processes, helping leadership understand performance and trends across different divisions. Where to get Part of the organizational structure data in ADP Workforce Now, associated with an employee's position. Examples Consumer ProductsEnterprise SoftwareGlobal Services | |||
Is Early Attrition IsEarlyAttrition | A flag indicating if an employee's termination occurred within a predefined early period. | ||
Description This is a calculated boolean attribute that simplifies attrition analysis. It is derived by comparing the 'TerminationDate' to the 'HireDate'. If the difference is less than a defined threshold (e.g., 365 days), the flag is set to true. This attribute directly powers the 'Early Employee Attrition Trends' dashboard and the corresponding KPI, making it easy to filter for and aggregate cases of early turnover. Why it matters It simplifies the identification and analysis of early turnover, a key indicator of potential issues in the recruitment and onboarding processes. Where to get Calculated within the process mining tool by comparing 'HireDate' and 'TerminationDate'. Examples truefalse | |||
Job Requisition ID JobRequisitionId | A unique identifier for the job requisition that initiated the hiring process. | ||
Description The Job Requisition ID links all early-stage hiring activities, from creation to offer acceptance, to a specific open position. It acts as a sub-identifier within the broader employee lifecycle. This is particularly useful for the 'Hiring Cycle Time Analysis' dashboard to accurately measure time-to-hire for each distinct position, even if multiple candidates are considered. Why it matters It allows for accurate analysis of the recruitment funnel and cycle times for each specific job opening, rather than just by candidate. Where to get Originates from the recruitment or talent acquisition module within ADP Workforce Now. Examples REQ-2023-00123REQ-2024-00456REQ-2024-00789 | |||
Performance Rating PerformanceRating | The rating given to an employee during a performance review cycle. | ||
Description This attribute captures the outcome of the 'Performance Review Conducted' activity. It can be used to correlate performance with other lifecycle events, such as promotions, compensation changes, or terminations. Analyzing this data can help assess the effectiveness of the performance management process and identify trends, such as whether high performers are more likely to be promoted or to leave the company. Why it matters It connects performance outcomes to process events, allowing for deeper analysis of talent management, retention, and the impact of performance reviews. Where to get Data originates from the Performance Management module within ADP Workforce Now. Examples Exceeds ExpectationsMeets ExpectationsNeeds ImprovementOutstanding | |||
SLA Adherence Status SlaAdherenceStatus | A calculated status indicating if an activity was completed on time or late. | ||
Description This attribute is derived by comparing an activity's completion timestamp with its 'SlaTargetDate'. The result is a simple, clear status like 'On Time' or 'Late'. This is used in the 'Compliance & Critical Task Monitoring' dashboard to provide an at-a-glance view of SLA performance, allowing users to quickly identify and drill down into overdue tasks without needing to perform date comparisons manually. Why it matters It translates complex date comparisons into a simple, actionable status, making it easier to monitor and manage SLA compliance across the organization. Where to get Calculated within the process mining tool by comparing the activity's 'EventCompletionTimestamp' to the 'SlaTargetDate'. Examples On TimeLateIn Jeopardy | |||
SLA Target Date SlaTargetDate | The target date by which a specific activity should be completed. | ||
Description The SLA Target Date is a critical piece of data for compliance and performance monitoring. It sets the expectation for how long certain critical tasks should take. This attribute is the basis for the 'SLA Adherence, Background Check' KPI and is used in the 'Compliance & Critical Task Monitoring' dashboard to flag overdue items. By comparing the actual completion timestamp to this target date, the process mining tool can automatically identify breaches. Why it matters It enables automated monitoring of compliance and service level agreements, highlighting delays in critical tasks that could pose business or legal risks. Where to get Consult ADP Workforce Now documentation. This may be a custom field or derived based on business rules (e.g., Hire Date + 5 days). Examples 2023-04-102024-02-282024-07-05 | |||
Termination Date TerminationDate | The official last day of an employee's employment. | ||
Description The Termination Date marks the end of the employee lifecycle. It is used in conjunction with the Hire Date to calculate the final tenure of an employee. This attribute is fundamental for analyzing turnover rates, understanding the offboarding process duration, and segmenting the employee population for historical analysis. Why it matters This date defines the end of the employee journey, enabling precise calculation of tenure and turnover metrics. Where to get A standard field that is populated when the termination process is completed in ADP Workforce Now. Examples 2023-11-302024-06-142024-07-31 | |||
Training Name TrainingName | The name or title of the training course assigned to an employee. | ||
Description This attribute provides context for the 'Training Assigned' and 'Training Completed' activities. It allows for analysis of specific training programs, such as mandatory compliance training or role-specific development courses. The 'Training Assignment & Completion' dashboard uses this attribute to track completion rates for different courses and identify which training programs may have low engagement or are frequently overdue. Why it matters It allows for granular analysis of training program effectiveness, compliance, and employee development progress. Where to get Originates from the Learning Management System (LMS) module within ADP Workforce Now or an integrated third-party LMS. Examples Cybersecurity Awareness 2024New Manager EssentialsCode of Conduct Annual Refresher | |||
Work Location WorkLocation | The physical or designated location where the employee works. | ||
Description This attribute helps in analyzing the Hire to Retire process from a geographical view. It can be used to compare process performance, such as hiring times or turnover rates, across different offices, cities, or countries. This can highlight regional differences in management practices, labor market conditions, or compliance requirements that impact the employee lifecycle. Why it matters It enables geographical segmentation to identify regional process variations and ensure that HR practices are effective and compliant across all locations. Where to get A standard field in the employee's profile and position data within ADP Workforce Now. Examples New York, NYLondon, UKSan Francisco, CARemote | |||
Hire to Retire - Employee Lifecycle Activities
| Activity | Description | ||
|---|---|---|---|
Employee Profile Created | Indicates the official creation of the employee's record in the core HR system. This is an explicit event captured from the creation date of the employee's master data record. | ||
Why it matters This activity marks the official start of the employee's journey within the HR system. It is a fundamental prerequisite for all subsequent lifecycle events like payroll and benefits setup. Where to get This is a core event in the ADP HR module. The creation timestamp or effective 'Hire Date' of the employee's primary record is used. Capture Creation date of the employee's master record or the 'Hire Date' field. Event type explicit | |||
Employee Terminated | Represents the final official separation of the employee from the company, when their status becomes inactive. This event is inferred from a change in the employee's status field to 'Terminated'. | ||
Why it matters This activity marks the definitive end of the employee lifecycle case. The effective date of this status change is the employee's official termination date. Where to get Inferred from the 'Employee Status' field in the core HR profile data in ADP. The effective date of this status change serves as the event timestamp. Capture Effective date of 'Employee Status' field changing to 'Terminated'. Event type inferred | |||
Job Requisition Created | Marks the formal creation of a request to hire for a new or existing position. This event is captured from the creation timestamp of a new job requisition record within the recruitment module. | ||
Why it matters This activity is the primary trigger for the hiring process. It serves as the starting point for measuring the 'Time to Hire' KPI and analyzing the efficiency of the recruitment funnel. Where to get Sourced from the ADP Recruiting & Hiring module. This is typically an explicit event logged with the creation date of the job requisition record. Capture Creation timestamp of the job requisition record in the recruiting module. Event type explicit | |||
Offer Accepted | Marks the candidate's official acceptance of the job offer, initiating the pre-boarding process. This event is inferred from the candidate's application status changing to 'Offer Accepted' or 'Hired'. | ||
Why it matters This activity concludes the main recruitment cycle and is the endpoint for the 'Time to Hire' KPI. It signifies the transition from candidate to new hire. Where to get Inferred from status changes on the candidate application record in the ADP Recruiting & Hiring module. The date of this status change is used as the event timestamp. Capture Status change of candidate application to 'Offer Accepted' or 'Hired'. Event type inferred | |||
Payroll Setup Completed | Indicates that the new hire's payroll information, such as bank details and tax forms, has been entered and verified. This event is typically inferred when the employee's payroll status becomes 'Active'. | ||
Why it matters This is a critical step to ensure employees are paid correctly and on time. It is a key component of the 'Onboarding Cycle Time' KPI. Where to get This is inferred from status fields within the ADP Payroll module. The effective date of the employee's status changing to 'Active for Payroll' serves as the timestamp. Capture Effective date of payroll status becoming 'Active'. Event type inferred | |||
Termination Initiated | Indicates the start of the offboarding process, triggered by an employee's resignation or an involuntary termination. This event is captured when a termination transaction is first entered into the system. | ||
Why it matters This activity is the trigger for all offboarding procedures. It is the starting point for analyzing offboarding efficiency and is critical for the 'Early Employee Attrition Rate' KPI. Where to get Captured from the ADP HR module when a manager or HR user initiates a termination workflow. The creation date of this transaction is used as the timestamp. Capture Creation date of the termination request or transaction. Event type explicit | |||
Background Check Initiated | Represents the start of the pre-employment background screening process. This is typically captured when an order is placed with a third-party screening vendor or an internal process is kicked off. | ||
Why it matters This is a critical compliance checkpoint. Monitoring this activity helps ensure adherence to hiring policies and SLAs for pre-employment screening. Where to get This information may come from the ADP Recruiting module or an integrated background check provider. It is often inferred from a status change or a specific date field like 'Background Check Start Date'. Capture Timestamp associated with a status change to 'Background Check in Progress'. Event type inferred | |||
Benefits Enrollment Completed | Represents the employee's successful completion of their initial benefits selection process. This is captured when the employee's benefits enrollment record is marked as complete or approved. | ||
Why it matters Timely benefits enrollment is crucial for employee satisfaction and compliance. Delays in this activity can indicate issues with the onboarding communication or system usability. Where to get Sourced from the ADP Benefits Administration module. This is typically inferred from the 'Enrollment Completion Date' or a status change to 'Enrolled'. Capture Timestamp of benefits enrollment record status change to 'Completed'. Event type inferred | |||
Candidate Applied | Represents the moment a candidate submits their application for an open job requisition. This is captured when a new candidate profile is linked to a specific job requisition in the system. | ||
Why it matters Tracking application submissions helps analyze the effectiveness of sourcing channels and measures the volume of candidates entering the hiring pipeline for each position. Where to get Located in the ADP Recruiting & Hiring module. This event corresponds to the timestamp when the candidate's application record is created. Capture Creation timestamp of the candidate application record. Event type explicit | |||
Compensation Change Approved | Indicates that a change to an employee's salary or compensation package has been approved. This is captured when a compensation change transaction is finalized in the system. | ||
Why it matters Analyzing compensation changes provides insights into salary trends, budget adherence, and the outcomes of performance reviews or promotions. Where to get Sourced from the HR or Compensation module in ADP. This is an explicit event with an effective date associated with the approved pay rate change. Capture Effective date of an approved compensation change transaction. Event type explicit | |||
Exit Interview Conducted | Represents the completion of the exit interview with the departing employee. This is typically captured manually via a date field or a completed task in an offboarding checklist. | ||
Why it matters While not always mandatory, tracking this activity helps ensure that valuable feedback is collected from departing employees as part of a standardized offboarding process. Where to get This data may be stored in the ADP HR module as part of an offboarding workflow or in a dedicated talent management module. It's often a date field that is manually populated. Capture Population of an 'Exit Interview Completion Date' field. Event type explicit | |||
Offboarding Tasks Completed | Marks the completion of all required offboarding tasks, such as asset return and system access revocation. This event is inferred when the offboarding checklist or workflow reaches its final, completed status. | ||
Why it matters This activity is essential for ensuring a secure and compliant employee exit. It is the endpoint for the 'Offboarding Process Completion' analysis. Where to get Inferred from the offboarding checklist or workflow within the ADP HR or Onboarding modules. The timestamp of the final task completion or overall workflow completion is used. Capture Completion timestamp of the master offboarding checklist or workflow. Event type inferred | |||
Offer Extended | Indicates that a formal job offer has been presented to a candidate. This is typically inferred from a status change on the candidate's application record, moving to a status like 'Offer Extended' or 'Offer Pending'. | ||
Why it matters This is a key milestone in the hiring process. Measuring the time from application to offer helps identify delays in the screening and interview stages. Where to get Inferred from status changes on the candidate's application within the ADP Recruiting & Hiring module. The timestamp of the status change serves as the event time. Capture Status change of candidate application to 'Offer Extended' or a similar state. Event type inferred | |||
Onboarding Initiated | Represents the formal start of the new hire onboarding process or workflow. This event is often captured when an onboarding task checklist or workflow is assigned to the new employee. | ||
Why it matters This activity marks the beginning of the new hire integration process. Analyzing the time from this point to completion helps measure onboarding efficiency. Where to get Sourced from the ADP Onboarding module. This is typically inferred from the assignment date of the onboarding workflow or the first onboarding task. Capture Assignment date of the onboarding checklist or workflow. Event type inferred | |||
Performance Review Conducted | Represents the completion of a formal performance review cycle for an employee. This is typically captured from the completion date of the performance review form or workflow. | ||
Why it matters This activity is a key milestone in the performance management process. Tracking it helps monitor the timeliness and consistency of reviews across the organization. Where to get Sourced from the ADP Performance Management module. It is inferred from the completion date or final approval timestamp of the review form. Capture Completion or final approval date of the performance review form. Event type inferred | |||
Promotion Approved | Represents the official approval of an employee's promotion to a new role or title. This event is captured from the effective date of the 'Job Role' or 'Title' field changing for the employee. | ||
Why it matters This activity is a key indicator of internal mobility and talent development. It is essential for calculating the 'Internal Mobility Cycle Time' KPI. Where to get Inferred from a change in the 'Job Title' or 'Job Code' field on the employee's record in the core ADP HR module. The effective date of this change is the event time. Capture Effective date of a change in the employee's Job Title field. Event type inferred | |||
Role Change Initiated | Marks the beginning of a process to change an employee's role, including lateral moves or transfers. This is captured when a 'Job Change' request or transaction is created. | ||
Why it matters This activity is the starting point for analyzing internal mobility processes. Understanding the duration from initiation to approval reveals efficiency in talent management. Where to get Sourced from the ADP HR module, often via a manager self-service action. It is captured from the creation date of a job change request transaction. Capture Creation date of a job or position change request. Event type explicit | |||
Training Assigned | Indicates that a specific training course or learning plan has been assigned to an employee. This is captured from the creation of an assignment record in the learning management system. | ||
Why it matters This activity is crucial for monitoring compliance with mandatory training and tracking employee development. It's the first half of the 'Training Assignment-Completion Rate' KPI. Where to get This information comes from the ADP Talent or Learning module. The timestamp of the training assignment record is used. Capture Creation date of the training assignment record for the employee. Event type explicit | |||
Extraction Guides
Extraction methods for this process are currently being validated. Please check back later or contact us for assistance.
