Your Employee Onboarding Data Template
Your Employee Onboarding Data Template
- Recommended attributes to collect
- Key activities to track for process discovery
- Step-by-step extraction guidance for BambooHR
Employee Onboarding Attributes
| Name | Description | ||
|---|---|---|---|
|
Activity Name
ActivityName
|
The name of the specific task or milestone that occurred in the onboarding process. | ||
|
Description
This attribute records the name of each distinct event or step within the employee onboarding journey. Examples include 'Offer Accepted', 'Background Check Completed', and 'First Day Orientation Completed'. In analysis, the Activity Name is used to build the process map, showing the sequence of events and the flow of work. It is crucial for identifying bottlenecks, analyzing activity frequencies, and understanding the different paths, or variants, that new hires take. By examining the sequence of these activities, analysts can identify deviations from the standard process and opportunities for improvement.
Why it matters
It defines the steps of the process, forming the backbone of the process map and enabling analysis of workflow, bottlenecks, and variations.
Where to get
Derived from status changes, task completions, or specific date fields within BambooHR's onboarding checklists or hiring workflows.
Examples
Offer AcceptedPaperwork Packet SentIT Provisioning Requested30-Day Check-in Completed
|
|||
|
Event Timestamp
EventTimestamp
|
The precise date and time when an onboarding activity was completed or occurred. | ||
|
Description
The Event Timestamp marks the exact moment a specific activity took place. This temporal data is essential for ordering events chronologically and for calculating durations between different steps in the process. This attribute is the foundation for all time-based analysis in process mining. It is used to calculate cycle times, wait times, and overall process duration. By analyzing timestamps, organizations can identify which stages are taking the longest, measure performance against service level agreements, and pinpoint delays that negatively impact the new hire experience.
Why it matters
This timestamp provides the chronological order of events and is essential for all performance and duration analysis, such as calculating cycle times and identifying delays.
Where to get
Extracted from various date fields in BambooHR that correspond to activity completions, such as 'Offer Acceptance Date', 'Background Check Completion Date', or system logs recording status changes.
Examples
2023-10-01T10:00:00Z2023-10-05T14:30:00Z2023-10-15T09:00:00Z
|
|||
|
Onboarding Case
OnboardingCase
|
The unique identifier that groups all onboarding activities for a single new employee. | ||
|
Description
The Onboarding Case serves as the central identifier for the entire employee onboarding process. It links all related events, from the initial offer acceptance to the completion of the 30-day check-in, into a single, cohesive journey. In process mining analysis, this attribute is fundamental for reconstructing the end-to-end process flow for each new hire. It allows for the visualization of process maps, calculation of case-level KPIs like total cycle time, and analysis of different process variants. Without a consistent case identifier, it would be impossible to track how a single employee moves through the various onboarding stages.
Why it matters
This is the primary key that connects all related events, making it possible to analyze the complete onboarding journey for each new hire.
Where to get
This is a conceptual identifier, often derived by combining the Employee ID with the hiring instance or date, as BambooHR may not have a single explicit 'Onboarding Case ID'. It needs to be constructed during data preparation.
Examples
ONB-00123ONB-00124ONB-00125
|
|||
|
Last Data Update
LastDataUpdate
|
The timestamp indicating when the data was last refreshed from the source system. | ||
|
Description
This attribute records the date and time of the most recent data extraction or update. It provides users with a clear understanding of the data's freshness and relevance. In any analysis, particularly those monitoring ongoing processes, knowing the timeliness of the data is critical. This timestamp helps users trust the data they are viewing and understand if it reflects the current state of operations or is from a previous point in time. It is essential for dashboards that track active onboarding cases.
Why it matters
Informs users about the timeliness of the data, ensuring they understand how current the process analysis is.
Where to get
This timestamp is generated and appended to the dataset at the time of data extraction and loading.
Examples
2024-05-21T08:00:00Z
|
|||
|
Source System
SourceSystem
|
Indicates the system of record from which this data was extracted. | ||
|
Description
This attribute specifies the origin of the data, which in this case is BambooHR. It helps in data governance and provides context, especially when data from multiple systems is combined. While it may seem straightforward, explicitly stating the source system is important for data lineage and troubleshooting. In larger analytical environments, it ensures that users understand the context of the data and can trace it back to its origin if questions or inconsistencies arise.
Why it matters
Provides crucial context about data origin, which is important for data governance, validation, and when integrating data from multiple sources.
Where to get
This is a static value, 'BambooHR', that is added during the data transformation process.
Examples
BambooHR
|
|||
|
Department
Department
|
The department that the new employee is joining. | ||
|
Description
This attribute specifies the organizational department, such as 'Engineering', 'Sales', or 'Marketing', to which the new hire belongs. It is a key dimension for segmenting and comparing process performance. Analyzing the onboarding process by department is critical for understanding performance variations across the organization. It helps answer questions like, 'Which departments have the longest onboarding cycle times?' or 'Are compliance rates for mandatory training lower in certain departments?'. These insights enable targeted interventions and the sharing of best practices between departments.
Why it matters
Enables comparison of onboarding efficiency, cycle times, and compliance rates across different parts of the organization.
Where to get
A standard field associated with the employee's job information in BambooHR.
Examples
EngineeringSalesMarketingHuman Resources
|
|||
|
Employee ID
EmployeeId
|
A unique identifier assigned to each employee within BambooHR. | ||
|
Description
The Employee ID is the unique key that identifies a specific employee in the HR system. It remains constant for the employee throughout their tenure. While the Onboarding Case is the primary identifier for the process, the Employee ID is crucial for linking the onboarding data back to the employee's master record. This allows for enrichment with other employee attributes like job title or department, and enables a more comprehensive analysis of how the onboarding experience varies for different types of employees.
Why it matters
Uniquely identifies the new hire, allowing for enrichment with other employee data and for tracking their entire lifecycle beyond onboarding.
Where to get
Available as a standard field in the employee record in BambooHR.
Examples
601856018660187
|
|||
|
End Timestamp
EndTimestamp
|
The completion timestamp of an activity, if it has a measurable duration. | ||
|
Description
While StartTime (EventTimestamp) marks when an activity occurs, EndTimestamp marks its completion. This is most relevant for activities that are not instantaneous, such as 'Background Check', which has an initiated and a completed state. Using both a start and end timestamp allows for a more precise calculation of processing time for individual activities. This helps differentiate between the time spent actively working on a task versus the time spent waiting for the next step to begin. This level of detail is crucial for in-depth bottleneck analysis.
Why it matters
Enables precise calculation of activity processing times, distinguishing active work time from waiting time.
Where to get
Derived from the timestamps of sequential activities. For example, the EndTimestamp for 'Background Check Initiated' would be the timestamp of 'Background Check Completed'.
Examples
2023-10-02T11:00:00Z2023-10-06T16:45:00Z2023-10-16T10:00:00Z
|
|||
|
Hiring Manager
HiringManager
|
The name of the manager to whom the new employee reports. | ||
|
Description
This attribute identifies the direct manager of the new hire. The hiring manager often plays a crucial role in the onboarding process, responsible for tasks like team introductions and setting initial goals. Analyzing onboarding performance by hiring manager can highlight which managers are most effective at integrating new team members and which may need additional support or training. It can help identify best practices from successful managers that can be shared across the organization, improving the overall consistency and quality of the new hire experience.
Why it matters
Allows for performance analysis by manager, identifying those who are effective at onboarding and those who may require more support.
Where to get
Typically found in the employee's job information or reporting structure details in BambooHR.
Examples
Jane DoeJohn SmithEmily Jones
|
|||
|
Job Title
JobTitle
|
The specific role or position of the new hire. | ||
|
Description
This attribute contains the official job title of the new employee, for example, 'Software Engineer', 'Account Executive', or 'Product Manager'. It provides another important dimension for analyzing the onboarding process. Different roles may have unique onboarding requirements, such as specialized training or equipment provisioning. Analyzing by job title can reveal if certain roles experience longer delays or follow different process paths. This helps in tailoring and optimizing the onboarding experience based on the specific needs of the position.
Why it matters
Allows for analysis of the onboarding process based on role complexity and requirements, helping to tailor the experience for different positions.
Where to get
A standard field associated with the employee's job information in BambooHR.
Examples
Senior Software EngineerMarketing CoordinatorRegional Sales Director
|
|||
|
Location
Location
|
The primary work location or office of the new hire. | ||
|
Description
This attribute identifies the physical office or geographical location where the new employee will be based. This can be a city, office building, or a 'Remote' designation. Analyzing by location is important for identifying regional differences in the onboarding process. For instance, equipment delivery times may vary significantly between locations, or different offices might have their own local orientation procedures. This analysis helps in standardizing the process where possible while accommodating necessary local variations.
Why it matters
Helps identify regional variations in process performance, such as delays in equipment delivery or differences in local orientation procedures.
Where to get
A standard field in the employee's profile in BambooHR, typically under employment or location details.
Examples
New York OfficeLondon, UKRemote (US)San Francisco HQ
|
|||
|
Country
Country
|
The country where the new hire is employed. | ||
|
Description
This attribute specifies the country of employment. For global organizations, this is a critical dimension for analysis. Onboarding processes and regulations can vary significantly from one country to another. Analyzing the process by country helps organizations understand these differences, ensure compliance with local laws, and identify opportunities to standardize practices across regions where appropriate. It can also explain variations in cycle times related to country-specific holidays or administrative procedures.
Why it matters
Essential for global organizations to analyze process variations, ensure local compliance, and manage region-specific onboarding requirements.
Where to get
A standard field within the employee's location or address information in BambooHR.
Examples
United StatesUnited KingdomGermanyCanada
|
|||
|
Employment Status
EmploymentStatus
|
The current status of the new hire in their employment lifecycle. | ||
|
Description
This attribute tracks the new hire's status as they progress, for example, from 'Offer Accepted' to 'Pre-Hire' to 'Active'. This provides a high-level view of where the employee is in the overall process. In process mining, this can be used as a case-level attribute to filter for active onboarding cases or to analyze how long cases remain in a particular status. It is particularly useful for dashboards that provide a real-time overview of all ongoing onboarding processes, helping HR and managers monitor progress.
Why it matters
Provides a high-level status of the onboarding case, enabling filtering for active cases and monitoring overall progress.
Where to get
This is a standard field in the employee's record in BambooHR.
Examples
ActiveInactiveTerminatedOn Leave
|
|||
|
Event Performer
EventPerformer
|
The user or system that executed the onboarding activity. | ||
|
Description
This attribute identifies the individual, team, or automated system responsible for completing a given activity. For instance, an HR specialist might complete the 'Paperwork Packet Sent' activity, while the hiring manager completes the 'Team Introduction'. This information is invaluable for resource analysis and understanding workload distribution. It helps identify which teams or roles are involved in the most time-consuming or bottleneck activities. It also allows for the analysis of tasks performed by specific user groups, which can inform resource allocation and automation strategies.
Why it matters
Identifies who is performing each task, which is essential for workload analysis, resource optimization, and understanding user-specific behavior.
Where to get
This information might be captured in audit logs or task completion details in BambooHR, often associated with the user who made the update.
Examples
HR AdminDavid Chen (Hiring Manager)System AutomationIT Support
|
|||
|
Is Rework
IsRework
|
A flag that indicates if an activity is a repetition of a step that already occurred. | ||
|
Description
This calculated boolean attribute is set to true if an activity, such as 'Paperwork Packet Sent', appears more than once within the same onboarding case. It signals that a process step had to be repeated, which typically indicates an error, missing information, or an inefficiency. Identifying rework is a key capability of process mining. This flag allows for easy filtering and quantification of rework instances. It directly supports dashboards and KPIs focused on rework, helping to highlight process friction and waste. Reducing rework leads to faster cycle times and a smoother experience for both the new hire and the HR team.
Why it matters
Highlights process inefficiencies, errors, and wasted effort by flagging activities that had to be repeated.
Where to get
This is a calculated field. The logic is implemented within the process mining tool to detect repeated sequences of activities within a case.
Examples
truefalse
|
|||
|
New Hire Name
NewHireName
|
The full name of the employee being onboarded. | ||
|
Description
This attribute contains the name of the new employee. It is primarily used for operational purposes, such as in reports or dashboards that require identifying specific individuals. In process mining analysis, names are often anonymized or replaced with Employee IDs to comply with data privacy regulations. However, for operational dashboards used by HR or managers to track active cases, having the name can provide immediate and user-friendly context.
Why it matters
Provides easy-to-read, human-friendly context for specific cases, especially in operational dashboards for HR and managers.
Where to get
A standard field in the employee's personal information in BambooHR.
Examples
Alice JohnsonRobert WilliamsMaria Garcia
|
|||
|
Onboarding Cycle Time
OnboardingCycleTime
|
The total duration of the onboarding process for a single case. | ||
|
Description
This calculated metric measures the end-to-end cycle time for each onboarding case, typically from 'Offer Accepted' to '30-Day Check-in Completed'. It represents the total time elapsed for the entire process. This is a primary key performance indicator (KPI) for assessing overall process efficiency. It is used in dashboards to track average onboarding times, compare performance across departments or roles, and measure the impact of process improvement initiatives. A lower cycle time generally correlates with a better new hire experience and lower administrative costs.
Why it matters
This is a critical KPI for measuring overall process efficiency and tracking improvements over time.
Where to get
Calculated by taking the time difference between the timestamp of the first and last activity in the case.
Examples
35 days42 days28 days
|
|||
|
Pre-Hire Cycle Time
PreHireCycleTime
|
The duration of all activities that occur before the employee's official start date. | ||
|
Description
This calculated metric measures the time taken to complete all pre-hire tasks, such as paperwork and background checks. It is typically calculated from 'Offer Accepted' to the last activity before the employee's Start Date. This KPI is crucial for the 'Pre-Hire Activity Completion Time' dashboard. It helps organizations identify and address delays that occur before the employee even starts, ensuring that new hires are ready to be productive on day one. Reducing pre-hire cycle time improves the candidate experience and reduces administrative friction.
Why it matters
Helps measure and optimize the efficiency of administrative tasks that must be completed before the new hire's first day.
Where to get
Calculated by taking the time difference between the first pre-hire activity and the last pre-hire activity.
Examples
10 days14 days7 days
|
|||
|
Start Date
StartDate
|
The new employee's official first day of work. | ||
|
Description
The Start Date is a critical milestone in the onboarding process. It separates pre-hire activities, such as background checks and paperwork, from post-hire activities like orientation and training. This date is used as a key reference point in many analyses. For example, it is used to calculate the 'Time to First Day Readiness' KPI, which measures whether all necessary pre-hire tasks were completed before the employee's first day. It also helps to analyze the timeliness of pre-hire activities and their impact on day-one productivity.
Why it matters
Acts as a critical milestone to differentiate pre-hire from post-hire activities and measure if new hires are ready on day one.
Where to get
This corresponds to the 'Hire Date' field which is a standard part of an employee's record in BambooHR.
Examples
2023-11-012023-11-152023-12-01
|
|||
|
Team
Team
|
The specific team the new hire is assigned to within a department. | ||
|
Description
This attribute provides a more granular level of organizational detail than the department. It specifies the immediate team, such as 'Frontend Developers' or 'Enterprise Sales Team'. While department-level analysis is useful, team-level analysis can uncover more specific insights. It can reveal performance differences between teams with similar functions and help identify how team-specific practices, such as local introductions or training, impact the overall onboarding journey. This is particularly useful for large departments where a more detailed breakdown is needed.
Why it matters
Provides a more granular view than department, allowing for analysis of performance and process variations between individual teams.
Where to get
This may be a standard or custom field in BambooHR, often part of the employee's organizational assignment.
Examples
Platform EngineeringMid-Market SalesContent Marketing
|
|||
Employee Onboarding Activities
| Activity | Description | ||
|---|---|---|---|
|
30-Day Check-in Completed
|
Represents the completion of the first formal check-in between the new hire and their manager, typically occurring around the 30-day mark. This is captured when a '30-Day Check-in' task or performance review form is marked as complete in BambooHR. | ||
|
Why it matters
This milestone is crucial for early feedback, addressing concerns, and improving employee retention. Tracking its completion ensures consistent engagement with new hires during a critical period.
Where to get
Captured from the completion timestamp of a '30-Day Check-in' task or a performance review form in BambooHR.
Capture
Event is logged when a manager marks the check-in task or form as 'Completed'.
Event type
explicit
|
|||
|
Background Check Completed
|
This activity signifies that the new hire's background check has been successfully completed and the results are available. In BambooHR, this is recorded when the 'Background Check' task in the onboarding checklist is marked as 'Completed'. | ||
|
Why it matters
This is a key compliance milestone. Delays between initiation and completion can be a major bottleneck, and tracking this helps ensure pre-hire requirements are met before the start date.
Where to get
Captured from the completion timestamp of the 'Background Check' task within the new hire's Onboarding Task List.
Capture
Event is logged when the background check task status is updated to 'Completed'.
Event type
explicit
|
|||
|
First Day Orientation Completed
|
Marks the completion of the new hire's initial orientation session, which covers company culture, policies, and introductions. This is captured when a 'First Day Orientation' task is checked off as complete by HR or the hiring manager in the BambooHR onboarding checklist. | ||
|
Why it matters
This is a crucial milestone for employee engagement and integration. Ensuring it happens consistently and on time is vital for setting up new hires for success and a positive experience.
Where to get
Captured from the completion timestamp of the 'First Day Orientation' task within the Onboarding Task List.
Capture
Event is logged when the orientation task is marked as 'Completed'.
Event type
explicit
|
|||
|
Mandatory Training Completed
|
Marks the successful completion of a required training course by the new employee. BambooHR records this event when the status of an assigned training is updated to 'Completed' in the training tracking module. | ||
|
Why it matters
This is a critical compliance milestone. Tracking its completion ensures the company meets legal and internal policy requirements and that employees have the necessary knowledge for their roles.
Where to get
Captured from the timestamp when a training record's status is changed to 'Completed' in the BambooHR Training module.
Capture
A discrete event is logged when the status field of a training record is updated to 'Completed'.
Event type
explicit
|
|||
|
Offer Accepted
|
This activity marks the official start of the onboarding process, occurring when a candidate formally accepts their job offer. In BambooHR, this is typically captured when a candidate's status in the Applicant Tracking System (ATS) is changed to 'Hired', which triggers the creation of their employee profile and onboarding checklist. | ||
|
Why it matters
This is the critical starting point for every onboarding case. Analyzing the time from this event to others helps measure the overall efficiency and speed of the pre-hire process.
Where to get
Inferred from the date the candidate's status is updated to 'Hired' in the BambooHR ATS module or the employee's hire date field is populated.
Capture
Identify the timestamp when the 'status' field for an applicant changes to 'Hired'.
Event type
inferred
|
|||
|
Onboarding Tasks Completed
|
This activity marks the completion of all assigned tasks within the new hire's onboarding checklist. This event can be inferred when the completion percentage of the onboarding task list reaches 100% or a final 'Complete Onboarding' task is checked off. | ||
|
Why it matters
This serves as a definitive end-point for the structured, task-driven portion of the onboarding process. It confirms that all administrative and preparatory steps have been successfully executed.
Where to get
Inferred from the timestamp of the last completed task in an employee's Onboarding Task List or when the overall onboarding process status is marked as 'Complete'.
Capture
Identify the latest completion timestamp among all tasks associated with a single onboarding case.
Event type
inferred
|
|||
|
Paperwork Packet Completed
|
This event occurs when the new hire has finished signing all the required documents in their onboarding packet. BambooHR records this automatically when all e-signatures in a sent packet are completed by the employee. | ||
|
Why it matters
Completion of paperwork is a critical prerequisite for a new hire's first day. Analyzing this milestone is essential for ensuring compliance and readiness, preventing rework and start date delays.
Where to get
Captured from the timestamp when the status of the sent new hire packet changes to 'Completed' in BambooHR.
Capture
A discrete event is logged when the final required e-signature is completed in a new hire packet.
Event type
explicit
|
|||
|
Background Check Initiated
|
Represents the point at which a background check is requested for the new hire through an integrated service. This is usually captured when a specific 'Background Check' task is created or marked as started within the new hire's onboarding task list in BambooHR. | ||
|
Why it matters
Tracking the initiation of background checks helps identify delays in the pre-employment screening process, which is often a critical path item for compliance and timely hiring.
Where to get
Captured from the creation or start date of the 'Background Check' task within an Onboarding Task List in BambooHR.
Capture
Event is logged when the background check task is created or its status changes to 'In Progress'.
Event type
explicit
|
|||
|
Employee Profile Created
|
Represents the official creation of the new hire's record in the HRIS, moving them from a candidate to an employee. This is inferred from the creation date of the employee record in the main BambooHR database, which typically happens after the offer is accepted. | ||
|
Why it matters
This activity is the foundation for all subsequent onboarding steps, like IT provisioning and payroll setup. It provides a clear timestamp for when the employee officially enters the system.
Where to get
Inferred from the system creation timestamp of the new employee's record in the core employee data tables.
Capture
Use the 'created_at' or equivalent metadata timestamp from the employee's primary record.
Event type
inferred
|
|||
|
Equipment Delivered
|
This activity signifies that the ordered equipment has been physically delivered and is ready for the new hire. This is often tracked as a separate 'Equipment Delivered' or 'Workspace Setup' task being marked complete in the BambooHR onboarding checklist. | ||
|
Why it matters
Tracking the time between ordering and delivery highlights potential supply chain or logistics bottlenecks. This helps ensure all physical assets are in place before the employee's start date.
Where to get
Captured from the completion timestamp of an 'Equipment Delivered' or 'Workspace Setup' task in the Onboarding Task List.
Capture
Event is logged when the status of the delivery or setup task is updated to 'Completed'.
Event type
explicit
|
|||
|
Equipment Ordered
|
Represents the point when necessary hardware, such as a laptop or phone, is ordered for the new hire. This is typically captured when an 'Order Equipment' task is marked as completed in the BambooHR onboarding checklist. | ||
|
Why it matters
This activity is a key milestone in ensuring the new hire has the physical tools they need. Delays here directly impact first-day readiness and productivity.
Where to get
Captured from the completion timestamp of an 'Order Equipment' task within the Onboarding Task List in BambooHR.
Capture
Event is logged when the status of the 'Order Equipment' task is updated to 'Completed'.
Event type
explicit
|
|||
|
IT Provisioning Requested
|
This activity marks the formal request sent to the IT department to create necessary accounts and access for the new hire. In BambooHR, this is typically captured when a predefined 'IT Provisioning' task is created and assigned within the onboarding checklist. | ||
|
Why it matters
Timely IT provisioning is crucial for a productive first day. Tracking this event helps measure IT's responsiveness and diagnose delays in getting new hires system access.
Where to get
Captured from the creation date and time of the 'IT Account Provisioning' or similar task in the new hire's Onboarding Task List.
Capture
Event is logged when the IT provisioning task is created in an onboarding checklist.
Event type
explicit
|
|||
|
Mandatory Training Assigned
|
This event occurs when required compliance or role-specific training is assigned to the new employee. In BambooHR, this is explicitly logged within its training tracking module when a new training is added to an employee's record. | ||
|
Why it matters
This is the starting point for measuring training compliance. Analyzing the time from assignment to completion helps ensure employees meet regulatory and company requirements promptly.
Where to get
Captured from the creation date of a training record assigned to a specific employee in the BambooHR Training module.
Capture
A discrete event is logged when a new entry is created in the employee training tracking table.
Event type
explicit
|
|||
|
Paperwork Packet Sent
|
Marks the moment when the new hire packet, containing documents like the I-9, W-4, and company policies, is sent to the new hire for review and signature. BambooHR logs this event when an HR administrator sends the packet through the system's document management features. | ||
|
Why it matters
This activity initiates a critical administrative workflow. Measuring the time from this point to paperwork completion helps assess the efficiency of the documentation process.
Where to get
Captured from the timestamp when a new hire packet is sent to an employee for e-signature within BambooHR.
Capture
A discrete event is logged in the system when the 'Send Packet' action is executed.
Event type
explicit
|
|||
|
Team Introduction Completed
|
Represents the formal introduction of the new hire to their immediate team members. This is typically a softer, manager-led activity that is captured by the completion of a corresponding task in the BambooHR onboarding checklist. | ||
|
Why it matters
Social integration is a key part of successful onboarding. Tracking this activity helps ensure managers are completing important steps to welcome new hires and foster team cohesion.
Where to get
Captured from the completion timestamp of a 'Team Introduction' task in the Onboarding Task List, usually assigned to the hiring manager.
Capture
Event is logged when the manager marks the 'Team Introduction' task as 'Completed'.
Event type
explicit
|
|||