Data Template: Hire to Retire - Employee Lifecycle

Universal process mining template
Data Template: Hire to Retire - Employee Lifecycle

Your Hire to Retire - Employee Lifecycle Data Template

Universal process mining template

This is our generic process mining data template for Hire to Retire - Employee Lifecycle. Use our system-specific templates for more specific guidance.

Select a specific system
  • Standardized data fields for consistency across systems
  • Recommended activities for full process visibility
  • Guidance for seamless data extraction and preparation

Hire to Retire - Employee Lifecycle Attributes

This section outlines the recommended data fields and attributes for constructing a robust event log, enabling comprehensive analysis of your employee lifecycle process.
5 Required 8 Recommended 4 Optional
NameDescription
Activity Name
ActivityName
The name of a specific event, task, or milestone that occurred in the employee's lifecycle, such as 'Offer Accepted' or 'Performance Review Completed'.
Description

The Activity Name describes a distinct step within the hire-to-retire process. These activities are the building blocks of the process map, representing everything from the initial job requisition to the final termination confirmation.

In analysis, this attribute is used to visualize the process flow, identify the sequence of events, and measure the frequency and duration of each step. It is crucial for understanding what actions are taking place, discovering deviations from the standard process, and pinpointing stages that cause delays or require improvement, such as a lengthy background check or a delayed onboarding task.

Why it matters

This attribute defines the steps in the process map, which is the foundation for all process mining analysis and visualization.

Where to get

Generated from event logs, status change records, or specific transaction data within the HR system.

Examples
Employee HiredOnboarding CompletedCompensation Change ApprovedTermination Initiated
Employee ID
EmployeeId
The unique identifier assigned to each employee, which serves as the primary case ID for their entire lifecycle within the organization.
Description

The Employee ID is a unique key that follows an individual from their initial hiring process through to their eventual termination. It links all related lifecycle events, such as onboarding, performance reviews, promotions, and offboarding, into a single, cohesive journey.

In process mining, this attribute is fundamental for case correlation. It allows the analysis engine to reconstruct the end-to-end process flow for each employee. By using the Employee ID as the Case ID, analysts can track cycle times, identify bottlenecks in specific employee journeys, and analyze variations in how the lifecycle process is executed across different individuals or groups.

Why it matters

This is the essential Case ID that connects all employee lifecycle events, making it possible to analyze the complete journey from hire to retire.

Where to get

Typically available in the core employee master data tables or records within an HR Information System (HRIS).

Examples
EMP-10345982110USR-A54209
Event Timestamp
EventTimestamp
The precise date and time when a specific lifecycle activity or event was recorded.
Description

The Event Timestamp marks the point in time that an activity occurred. This timestamp is essential for ordering events chronologically to reconstruct the employee's journey accurately. It serves as the primary temporal data point for performance analysis.

This attribute is used to calculate cycle times between activities, measure the overall duration of processes like hiring or offboarding, and identify time-based bottlenecks. It enables trend analysis over time and is fundamental for creating time-sensitive KPIs, such as 'Average Time to Hire' or 'Onboarding Cycle Time'.

Why it matters

This timestamp is critical for sequencing events correctly and calculating all time-based performance metrics, such as cycle times and durations.

Where to get

Usually found alongside the activity or transaction record in system logs or data tables, often labeled as a creation date or system timestamp.

Examples
2023-01-15T09:00:00Z2023-03-20T14:30:15Z2024-05-01T11:21:05Z
Last Data Update
LastDataUpdate
The timestamp indicating the last time the data for this event was refreshed or extracted from the source system.
Description

This attribute provides a timestamp for when the data was last updated or extracted into the process mining dataset. It does not represent when the business event occurred, but rather the freshness of the data itself.

Its primary use is for data governance and validation. Analysts can use this information to confirm that they are working with up-to-date information and to understand the potential latency between an event happening in the source system and it appearing in the analysis. It is essential for managing data refresh cycles and ensuring the reliability of the insights generated.

Why it matters

Ensures data freshness and governance by indicating how current the analyzed information is, which is vital for building trust in the analysis results.

Where to get

This timestamp is typically generated and added during the data extraction, transformation, and loading (ETL) process.

Examples
2023-10-26T02:00:00Z2023-10-27T02:00:00Z2023-10-28T02:00:00Z
Source System
SourceSystem
The name of the information system or application from which the event data originated.
Description

The Source System attribute identifies the origin of the data for each event. In a complex HR ecosystem, different parts of the hire-to-retire process may be managed in separate systems, such as an Applicant Tracking System (ATS) for hiring, a core HRIS for employee management, and a payroll system for compensation changes.

Analyzing data by Source System helps in understanding data integration challenges and process fragmentation. It allows analysts to identify if delays or issues are concentrated within a particular system, which can inform technical improvement or process redesign efforts. It is also crucial for data validation and ensuring a comprehensive view of the end-to-end process is captured.

Why it matters

Identifies the origin of process data, which is crucial for troubleshooting data quality issues and understanding process handoffs between different HR systems.

Where to get

This information is typically added during the data extraction and transformation (ETL) process or may exist as a standard field in system integration logs.

Examples
Workday HCMSAP SuccessFactorsOracle PeopleSoft
Department
Department
The organizational department or unit to which the employee is assigned, such as Sales, Engineering, or Finance.
Description

The Department attribute represents the employee's organizational alignment. It is a critical dimension for segmenting and comparing process performance across the company.

This attribute allows for a comparative analysis of the hire-to-retire process. For example, analysts can compare the 'Time to Hire' for the Engineering department versus the Sales department to identify different hiring challenges. It can also be used to analyze turnover rates by department, highlighting areas with potential management or cultural issues. Filtering the process map by department can reveal unique process variations or bottlenecks specific to certain business functions.

Why it matters

Allows for powerful segmentation and comparative analysis, revealing how HR processes perform across different parts of the organization.

Where to get

Available in the employee's core profile or master data record within the HR system, often linked to the job or position.

Examples
EngineeringSalesHuman ResourcesFinance
Employment Type
EmploymentType
Categorizes the employee's work arrangement, such as Full-time, Part-time, Contractor, or Intern.
Description

Employment Type classifies the nature of the employment contract or arrangement for an individual. This is a key demographic attribute that often has a significant impact on how HR processes are executed.

Analyzing the process by Employment Type can reveal important differences. For example, the onboarding process for a contractor may be significantly shorter and less detailed than for a full-time employee. Similarly, performance review cycles or offboarding procedures might vary. This segmentation is crucial for ensuring compliance and identifying whether processes are appropriately tailored to different types of workers.

Why it matters

Allows for analysis of process variations based on work arrangements, which is key for compliance and optimizing processes for different worker categories.

Where to get

This is a standard field in an employee's core HR profile or employment record.

Examples
Full-TimePart-TimeContractorIntern
End Time
EndTime
The timestamp indicating when an activity with a measurable duration was completed, such as an onboarding or training module.
Description

The End Time attribute marks the completion point of an activity that spans a period of time. While many HR events are instantaneous (e.g., 'Offer Extended'), others have a distinct start and end, such as 'Background Check' or 'Onboarding'. This timestamp, when paired with the Event Timestamp (StartTime), allows for precise duration calculation.

In process analysis, End Time is crucial for calculating the processing time or active work time of specific tasks. This helps differentiate between waiting time (the gap between two different activities) and processing time (the duration of a single activity). Analyzing these durations helps identify inefficient tasks and opportunities for automation or resource reallocation.

Why it matters

Enables the precise calculation of activity durations, helping to distinguish between active work time and idle waiting time in the process.

Where to get

Found in event logs or transaction tables that record both the start and completion of a task. It may need to be derived from a separate 'completed' event if not explicitly provided.

Examples
2023-01-20T17:00:00Z2023-04-01T10:15:45Z2024-05-10T16:00:00Z
Job Requisition ID
JobRequisitionId
A unique identifier for the job opening or requisition that initiated the hiring process for a position.
Description

The Job Requisition ID is a unique key that links all activities related to filling a specific job opening, from its creation and approval to sourcing candidates and extending offers. It often serves as a precursor case ID before an Employee ID is generated upon hiring.

This attribute is particularly useful for analyzing the pre-hire phase of the employee lifecycle. It allows for the measurement of KPIs like 'Time to Fill' and helps in understanding the efficiency of the recruitment process for a specific role. By analyzing processes at the requisition level, organizations can identify bottlenecks in approvals, sourcing, or interviewing stages across different job openings.

Why it matters

Links all pre-hire activities, enabling detailed analysis of the recruitment process and metrics like 'Time to Fill'.

Where to get

Generated by the Applicant Tracking System (ATS) or recruitment module of an HRIS when a new job opening is created.

Examples
REQ-2023-05-112JR-459018001543
Job Title
JobTitle
The specific job title, role, or position of the employee.
Description

The Job Title attribute provides detailed information about the employee's role within the organization. This can range from high-level roles like 'Director' to specific positions like 'Senior Software Engineer' or 'Account Executive'.

In analysis, Job Title is used to filter and analyze processes for specific roles or levels of seniority. It helps answer questions like, 'Does it take longer to hire for senior roles than junior roles?' or 'Is the onboarding process different for technical versus non-technical positions?'. This level of detail is essential for creating targeted process improvements and understanding the nuances of how the employee lifecycle varies across the workforce.

Why it matters

Enables detailed analysis of how lifecycle processes vary by employee role, seniority, and function, supporting more targeted improvements.

Where to get

Found in the employee's job information or position data within the HR master record.

Examples
Software EngineerSales ManagerHR Business PartnerData Analyst
Location
Location
The geographical location, office, or country where the employee is based.
Description

The Location attribute specifies the physical or designated work location of the employee. This can be as broad as a country or as specific as an office building or campus.

Geographic analysis is vital in HR process mining, especially for global organizations. It helps to uncover regional variations in process performance, such as differences in hiring cycle times due to local labor laws or market conditions. It can also be used to compare turnover rates across different sites, potentially indicating issues with local management or work environments. This data is essential for standardizing processes where possible and accommodating local needs where necessary.

Why it matters

Enables geographic analysis to identify regional process variations, assess compliance with local regulations, and compare performance across different work sites.

Where to get

Typically stored in the employee's personal or work address information within the HR system.

Examples
New York, USALondon, UKBerlin, GermanyRemote
Termination Reason
TerminationReason
The documented reason for an employee's departure from the organization, such as voluntary resignation or involuntary termination.
Description

The Termination Reason provides context for why an employee's lifecycle with the company ended. Reasons are typically categorized, for example, as voluntary (resignation, retirement) or involuntary (performance, restructuring).

This attribute is the cornerstone of any employee turnover analysis. By linking termination reasons to other data, an organization can uncover valuable insights. For instance, you can analyze if a particular department has a high rate of voluntary resignations, or if new hires from a certain recruitment source tend to be terminated for performance reasons. These insights are critical for developing effective talent retention strategies and improving hiring quality.

Why it matters

Provides critical context for turnover analysis, helping to distinguish between voluntary and involuntary attrition and identify root causes.

Where to get

Recorded during the offboarding or termination process, typically stored in the employee's final employment record.

Examples
Voluntary - ResignationInvoluntary - PerformanceInvoluntary - RestructuringRetirement
User
User
The name or ID of the user, such as an HR representative, manager, or system agent, who performed or initiated the activity.
Description

The User attribute identifies the person or system responsible for executing a specific step in the process. This could be a hiring manager approving an offer, an HR administrator initiating onboarding, or an automated system triggering a reminder.

This attribute adds a human or system agent dimension to the analysis. It is used to understand workload distribution, identify training opportunities (e.g., if certain users consistently cause delays or errors), and ensure process compliance. For example, it can help verify that sensitive actions like compensation changes are performed only by authorized personnel, which is important for auditing and security.

Why it matters

Identifies who performed an action, which is essential for analyzing workload, compliance, automation levels, and identifying training needs.

Where to get

Available in system audit logs or transaction records, often captured as 'Changed By', 'Created By', or 'User ID'.

Examples
jane.doe@company.comjohn.smithSYSTEM_AUTOMATIONHRServiceCenter
Business Unit
BusinessUnit
The larger business division or segment the employee belongs to, often a level above the department.
Description

The Business Unit represents a major operational division within a company, such as 'Consumer Products', 'Enterprise Software', or 'Global Services'. It provides a higher-level organizational context than the department.

Analyzing the hire-to-retire process at the Business Unit level is useful for strategic, high-level comparisons. It can help senior leadership understand how talent management practices and outcomes differ across major segments of the business. For example, one business unit might have a much faster internal mobility rate, suggesting best practices that could be shared across the organization. This view is essential for aligning HR processes with broader business strategies.

Why it matters

Provides a high-level organizational dimension for strategic analysis, allowing comparison of HR process performance across major business divisions.

Where to get

Found in the employee's organizational assignment data within the core HR system.

Examples
Consumer ProductsCorporate FunctionsResearch & DevelopmentGlobal Services
Employment Status
EmploymentStatus
The current or historical employment status of the employee, such as Active, Terminated, or On Leave.
Description

Employment Status provides a snapshot of the employee's relationship with the company at a given point in time. It's a dynamic attribute that changes as the employee moves through their lifecycle.

In process mining, tracking changes in this status can itself be a key activity (e.g., 'Status Changed to On Leave'). It is also a valuable attribute for filtering and analysis, allowing you to focus on the journeys of currently active employees or to specifically analyze the processes leading up to termination for former employees. It helps ensure the correct population is included in different types of lifecycle analysis.

Why it matters

Defines the employee's current state, which is crucial for filtering analyses to specific populations like active or terminated employees.

Where to get

A core field in the main employee record or job information table in the HRIS.

Examples
ActiveTerminatedOn LeavePaid Leave
Manager
Manager
The name or ID of the employee's direct manager or supervisor at the time of the event.
Description

The Manager attribute identifies the direct supervisor of the employee. The manager is often a key actor in many hire-to-retire processes, responsible for approvals, performance reviews, and initiating role changes.

Analyzing processes by manager can reveal variations in management effectiveness and process adherence. For example, it can help identify managers who are quick to complete performance reviews versus those who are consistently late. It can also be used to analyze team-specific turnover rates, which might indicate leadership issues. This provides an opportunity for targeted manager training and support.

Why it matters

Helps analyze process performance and outcomes at a team or manager level, highlighting variations in management practices and adherence.

Where to get

Stored in the employee's job or position data within the HR system, often as a link to another employee record.

Examples
Robert Smithsusan.jones@company.comMGR-9012
Recruitment Source
RecruitmentSource
The channel, platform, or method through which a candidate was originally sourced, such as a job board, referral, or career fair.
Description

Recruitment Source indicates the origin of a successful hire. This could be an internal source like an employee referral or an external one like a professional networking site, a university career fair, or a third-party recruiter.

This attribute is essential for evaluating the effectiveness of different talent acquisition strategies. By analyzing the entire employee lifecycle based on their recruitment source, organizations can determine which channels produce the highest quality candidates, measured by factors like performance review scores, promotion rates, and retention. This data-driven approach allows the recruitment team to optimize its spending and efforts on the most effective sources.

Why it matters

Enables analysis of hiring channel effectiveness, helping to optimize recruitment strategy and spend based on candidate quality and retention.

Where to get

Typically captured in the Applicant Tracking System (ATS) during the application or sourcing phase.

Examples
Employee ReferralLinkedInCompany Careers PageUniversity Fair
Required Recommended Optional

Hire to Retire - Employee Lifecycle Activities

This section details the essential process steps and milestones to capture, ensuring accurate process discovery and a complete view of your Hire to Retire journey.
7 Recommended 8 Optional
ActivityDescription
Employee Hired
This is the formal transaction where an applicant's record is converted into an employee record in the core HR system. It represents the official start date and the assignment of a permanent Employee ID.
Why it matters

This activity is the primary event that transitions a case from the 'Hire' phase to the 'Retire' phase of the lifecycle. It is the definitive start of employment for analyzing tenure and turnover.

Where to get

This is an explicit event captured from the effective start date on the employee's primary employment record in the core HRIS.

Capture

Use the employee's hire date or the creation date of their core employee profile.

Event type explicit
Employee Terminated
Represents the final, official separation of the employee from the company, when their status becomes inactive. This is the last event in the employee lifecycle and is based on their final day of employment.
Why it matters

This activity is the definitive end point of an employee's tenure. It is essential for accurately calculating turnover rates, length of service, and other key HR metrics.

Where to get

This event is inferred from the effective date of the 'Termination' action that changes the employee's status to inactive.

Capture

Use the effective date of the final termination action that changes the employee's status to 'Terminated', 'Inactive', or a similar value.

Event type inferred
Job Requisition Created
This activity marks the official start of the hiring process when a request for a new or replacement position is created and approved. It is typically captured as an explicit event when a new job requisition is saved and posted in a recruiting module.
Why it matters

This is the primary starting point for measuring the overall time to hire. Analyzing the time from requisition to fulfillment helps identify bottlenecks in the initial stages of talent acquisition.

Where to get

This event is captured from the creation timestamp of a job requisition record, typically found in a recruiting or talent acquisition system.

Capture

Use the creation date of the Job Requisition record, often associated with a specific requisition ID.

Event type explicit
Offer Accepted
Marks the candidate's official acceptance of the job offer, initiating the pre-boarding process. This event is captured when the candidate's application status is updated to 'Offer Accepted' or 'Hired'.
Why it matters

This is a critical conversion point that confirms a successful hire. It serves as the trigger for all subsequent onboarding and new hire setup activities.

Where to get

Inferred from a status change on the candidate's application, or an explicit acceptance timestamp from an e-signature system.

Capture

Use the timestamp when the candidate's status is updated to 'Offer Accepted' or a similar value.

Event type inferred
Onboarding Completed
A key milestone signifying the successful completion of the initial onboarding checklist or workflow. This typically means all required new hire paperwork, system access requests, and initial administrative tasks are finished.
Why it matters

This event marks the point where a new hire is fully integrated from an administrative standpoint. Analyzing the time to complete onboarding helps identify inefficiencies that may impact early productivity and engagement.

Where to get

This is typically an inferred event, derived from the completion timestamp of the final task in an onboarding checklist or a status change on the employee's onboarding plan.

Capture

Identify when the onboarding process or checklist status changes to 'Completed', or use the completion timestamp of the last required task.

Event type inferred
Role Change Processed
Represents any change to an employee's job, including promotions, transfers, or lateral moves. This event is captured from the effective date of the job information change in the employee's core HR record.
Why it matters

This activity is essential for analyzing internal mobility, career pathing, and talent development. Tracking these changes helps identify high-potential employees and understand organizational restructuring.

Where to get

Captured from the effective date of a 'Job Change' or similar transaction in the employee's job history data.

Capture

Use the effective date of a change in the employee's Job Title, Department, Position, or Grade fields.

Event type explicit
Termination Initiated
Marks the formal start of the employee offboarding process, triggered by a resignation or a company decision. This is an explicit event that triggers subsequent offboarding workflows.
Why it matters

This is the starting point for measuring the offboarding cycle time. A timely and well-managed offboarding process is crucial for compliance, security, and knowledge transfer.

Where to get

Captured when a termination transaction is first entered into the system, which often includes a future effective date.

Capture

Use the creation date of the termination request or transaction, not the final termination date.

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

Delays in background checks can significantly impact the new hire start date. Monitoring the cycle time of this step helps ensure a smooth and timely pre-boarding experience.

Where to get

Captured from an integration log with a screening vendor, or a status change or task creation within the HR system.

Capture

Use the timestamp of the task creation or API call that initiates the background check.

Event type explicit
Candidate Applied
Represents the moment a candidate submits their application for an open job requisition. This event is explicitly recorded when a new applicant record is created in the system and linked to a specific job.
Why it matters

Tracking applications is crucial for understanding recruitment channel effectiveness and the volume of the candidate pipeline. It helps measure the time from application to interview and subsequent stages.

Where to get

This is captured when a new candidate or applicant record is created and associated with a job requisition.

Capture

Use the submission timestamp from the candidate application record.

Event type explicit
Compensation Change Approved
Signifies an approved change to an employee's salary, bonus, or other compensation elements. This event is captured from the effective date of an approved compensation change transaction.
Why it matters

Analyzing compensation changes provides insights into salary trends, merit increase cycles, and pay equity. It is a key event for understanding an employee's financial progression.

Where to get

Captured from the effective date of an approved compensation change record in the core HR or compensation module.

Capture

Use the effective date associated with the compensation change transaction.

Event type explicit
Leave of Absence Started
Indicates the start of an employee's approved leave of absence, such as for medical, personal, or family reasons. This is recorded when the employee's status changes to an inactive or on-leave state.
Why it matters

Tracking leaves is critical for workforce planning, resource management, and compliance. It helps in understanding absenteeism patterns and their impact on productivity.

Where to get

Captured from the effective start date of the leave status in the employee's HR record or a dedicated absence management module.

Capture

Use the effective start date of the transaction that changes the employee's status to 'On Leave' or a similar state.

Event type explicit
Offboarding Completed
Marks the completion of all required offboarding tasks, such as asset return, knowledge transfer, and system access revocation. This event is inferred when the offboarding checklist or workflow reaches its final, completed status.
Why it matters

Ensuring all offboarding tasks are completed is vital for mitigating security risks and ensuring compliance. This milestone helps track the efficiency and thoroughness of the separation process.

Where to get

Inferred from the completion of an offboarding checklist or a final status change on the employee's offboarding workflow.

Capture

Identify when the offboarding process status changes to 'Completed', or use the timestamp of the final task's completion.

Event type inferred
Offer Extended
Indicates that a formal job offer has been presented to a candidate, following interviews and internal approvals. This is often inferred from a status change on the candidate's application record, moving to a status like 'Offer Pending'.
Why it matters

This milestone marks the transition from candidate evaluation to the final hiring decision. The duration between offer extension and acceptance is a key indicator of candidate experience and offer competitiveness.

Where to get

Typically inferred from a status change on the candidate's application, or from the creation date of an offer letter document.

Capture

Identify the timestamp when the application status changes to 'Offer Extended', 'Offer Generated', 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 and their manager.
Why it matters

Initiating onboarding promptly is key to a positive new hire experience. This activity marks the beginning of the onboarding cycle time, which is a crucial metric for HR efficiency.

Where to get

Usually captured from the creation date of an onboarding process instance, workflow, or checklist assigned to the new employee.

Capture

Use the assignment date of the onboarding checklist or the start date of the onboarding business process.

Event type explicit
Performance Review Completed
Represents the completion of a formal performance review cycle for an employee. This is a recurring event captured from the completion date of the performance review form or workflow.
Why it matters

Tracking performance reviews helps ensure compliance with company policy and fair talent management. It allows for analysis of review cycle times and adherence rates across departments.

Where to get

Typically inferred from the date a review form's status is changed to 'Completed' or 'Closed' in a performance management module.

Capture

Use the timestamp when the performance review form or workflow status is updated to its final, completed state.

Event type inferred
Recommended Optional

Extraction Guides

How to get your data for process mining.

Extraction methods vary by system. For detailed instructions,

read our ETL guide

or select a specific process and system.