Your Employee Onboarding Data Template
Your Employee Onboarding Data Template
- Recommended data attributes to collect for thorough analysis
- Key activities and milestones to track within your process
- Practical extraction guidance for your source system
Employee Onboarding Attributes
| Name | Description | ||
|---|---|---|---|
|
Activity Name
ActivityName
|
The name of the specific task or milestone that occurred at a point in time during the onboarding process. | ||
|
Description
This attribute describes a single step within the onboarding journey, such as 'Offer Accepted', 'Background Check Completed', or 'First Day Orientation Conducted'. Each activity represents an event in the process. Analyzing activities is the core of process mining. This attribute is used to build the process map, identify bottlenecks between steps, measure activity durations, and detect deviations from the standard operating procedure. It helps answer questions about what work is being done and in what sequence.
Why it matters
This attribute defines the steps in the process map, which is crucial for visualizing the process flow, identifying bottlenecks, and analyzing process variations.
Where to get
Derived from status changes, task completions, or specific events recorded against the employee's profile or onboarding checklist in Microsoft Dynamics 365 Human Resources.
Examples
Offer AcceptedBackground Check InitiatedIT Account Provisioning Initiated30-Day Check-in Performed
|
|||
|
Event Time
EventTime
|
The precise date and time when a specific onboarding activity or event occurred. | ||
|
Description
This timestamp marks the occurrence of each activity in the event log. It provides the chronological order needed to reconstruct the process flow for each onboarding case. Timestamps are essential for all time-based process mining analysis. They are used to calculate cycle times between activities, measure the total duration of the onboarding process, identify delays, and analyze process performance over time. Accurate timestamps are critical for the validity of any performance-related findings.
Why it matters
This timestamp is fundamental for sequencing events correctly and for all time-based calculations, including cycle times and bottleneck analysis.
Where to get
This corresponds to the creation or completion date fields associated with tasks, checklists, or status updates in Microsoft Dynamics 365 Human Resources.
Examples
2023-10-01T09:00:00Z2023-10-02T14:30:00Z2023-10-05T11:25:10Z
|
|||
|
Onboarding Case
OnboardingCase
|
The unique identifier for a new employee's complete onboarding process, from offer acceptance to their initial integration period. | ||
|
Description
The Onboarding Case serves as the central identifier that links all related activities, documents, and milestones for a single new hire. Each case represents one employee's journey through the onboarding lifecycle. In process mining, this attribute is fundamental for case-level analysis. It allows the reconstruction of each individual onboarding journey, enabling comparisons of process paths, identification of variants, and calculation of end-to-end cycle times. Without a consistent case identifier, it would be impossible to analyze the process flow accurately.
Why it matters
This is the essential case identifier that groups all related events, allowing for the end-to-end analysis of the onboarding process for each new hire.
Where to get
This identifier is typically generated within the core HR or recruitment module of Microsoft Dynamics 365 Human Resources when a candidate's status changes to 'Hired'.
Examples
ONB-2024-00123ONB-2024-00124ONB-2024-00125
|
|||
|
Compliance Due Date
ComplianceDueDate
|
The deadline by which certain compliance-related activities must be completed. | ||
|
Description
This attribute stores the target completion date for critical, time-sensitive tasks such as completing paperwork or mandatory training. This date is often determined by legal requirements or internal policies. This is a vital attribute for the 'Onboarding Compliance Status' dashboard and the 'Onboarding Phase Adherence Rate' KPI. By comparing the actual activity completion time ('EventTime') with the 'ComplianceDueDate', we can determine if the process is compliant. This helps the organization mitigate risks and ensure all legal and policy requirements are met in a timely manner.
Why it matters
This is essential for measuring compliance and on-time performance for critical tasks, helping to mitigate legal and operational risks.
Where to get
Consult Microsoft Dynamics 365 Human Resources documentation. This may be a 'Due Date' field on specific task or checklist items.
Examples
2023-11-15T23:59:59Z2023-12-01T23:59:59Z2023-11-20T23:59:59Z
|
|||
|
Department
DepartmentName
|
The department or business unit the new employee is joining. | ||
|
Description
This attribute specifies the organizational department, such as Sales, IT, or Finance, that the new hire will be a part of. It is a key organizational dimension for analysis. Segmenting the process by department is critical for the 'Departmental Onboarding Performance' dashboard. It allows for comparisons of onboarding cycle times, compliance rates, and process variants across different parts of the organization. This can reveal which departments have the most efficient processes and which may require additional support or standardization.
Why it matters
Enables performance comparison across different business units, helping to identify best practices and areas needing improvement or standardization.
Where to get
Consult Microsoft Dynamics 365 Human Resources documentation. This information is typically stored in the Position or Job entity associated with the new hire.
Examples
Sales and MarketingInformation TechnologyHuman ResourcesFinance
|
|||
|
Event End Time
EventEndTime
|
The timestamp indicating when a durational activity was completed. For instant events, this may be the same as the start time. | ||
|
Description
While the StartTime marks the beginning of an activity, the EndTime marks its conclusion. This is particularly useful for tasks that have a measurable duration, such as 'Background Check' or 'Mandatory Training'. Having a distinct end time allows for precise measurement of processing time for individual activities. This helps pinpoint exactly how long specific tasks take, rather than just measuring the waiting time between them. It is crucial for analyzing resource efficiency and identifying activities that consume the most time.
Why it matters
Enables the precise calculation of how long each individual activity takes, which is critical for identifying specific time-consuming tasks.
Where to get
Corresponds to the 'Completed On' or 'Resolved Date' fields for tasks or checklist items within Microsoft Dynamics 365 Human Resources.
Examples
2023-10-01T10:15:00Z2023-10-04T11:00:00Z2023-10-06T17:00:00Z
|
|||
|
Hiring Manager
HiringManagerName
|
The name of the manager to whom the new employee will report. | ||
|
Description
This attribute identifies the hiring manager responsible for the new employee. The hiring manager often plays a crucial role in the onboarding process, responsible for tasks like team introductions and setting up onboarding plans. Analyzing the process by hiring manager can reveal variations in how onboarding is handled at a team level. It supports the 'Departmental Onboarding Performance' dashboard by allowing drill-downs from the department to the individual manager, helping to identify managers who may need more training on the onboarding process or those who are champions of an efficient process.
Why it matters
Allows for analysis of process variations at the team level and helps identify managers who are crucial to the success of the onboarding experience.
Where to get
Consult Microsoft Dynamics 365 Human Resources documentation. This is typically stored as the 'Reports to' or 'Manager' field on the employee's Position record.
Examples
John SmithEmily JonesMichael Brown
|
|||
|
Onboarding Status
OnboardingStatus
|
The current overall status of the onboarding case. | ||
|
Description
This attribute indicates the high-level status of an onboarding case, for example, 'Not Started', 'In Progress', 'Completed', or 'Canceled'. It provides a snapshot of where each case is in its lifecycle. This is particularly useful for the 'Real-time Onboarding Progress' dashboard, as it allows for a quick overview of the active onboarding pipeline. It helps stakeholders understand the current workload and identify cases that might be stalled. It also allows for filtering out incomplete or canceled cases from cycle time analysis to avoid skewing the results.
Why it matters
Provides a high-level summary of a case's progress, enabling filtering for active or completed cases and supporting operational monitoring.
Where to get
Consult Microsoft Dynamics 365 Human Resources documentation. This may be a status field on a primary onboarding entity or derived based on the last completed activity.
Examples
In ProgressCompletedDelayedCanceled
|
|||
|
Position Title
PositionTitle
|
The official job title of the new hire. | ||
|
Description
This attribute specifies the role or job title for which the employee was hired, for example, 'Software Engineer', 'Account Manager', or 'Financial Analyst'. This is a valuable dimension for analysis, particularly for the 'New Hire Onboarding Throughput' dashboard. It allows for segmenting onboarding performance by job role or seniority, which can reveal if certain types of roles have longer or more complex onboarding processes. This insight can help in tailoring onboarding plans to specific job families.
Why it matters
Allows for filtering and comparing the onboarding process for different roles, which may have unique requirements and durations.
Where to get
Consult Microsoft Dynamics 365 Human Resources documentation. This information is available in the Job or Position entity linked to the new hire.
Examples
Senior Software EngineerMarketing CoordinatorHR Generalist
|
|||
|
Background Check Lead Time
BackgroundCheckLeadTime
|
The total time taken to complete the background check, from initiation to completion. | ||
|
Description
This calculated metric measures the duration of the background check process. This is often a critical path activity that can cause significant delays, as it may involve third-party vendors and is a prerequisite for the official start date. This metric supports the 'Critical Path Activity Durations' dashboard and is a key KPI for measuring a common bottleneck. By analyzing this lead time, HR can evaluate the performance of their background check provider and identify opportunities to expedite this crucial step.
Why it matters
Measures the duration of a common bottleneck, helping to manage dependencies and reduce delays in the new hire's start date.
Where to get
This is calculated from the event log by finding the time difference between the 'Background Check Initiated' and 'Background Check Completed' activities for each case.
Examples
5 days 10 hours8 days 2 hours12 days 1 hour
|
|||
|
Employment Type
EmploymentType
|
The classification of the new hire's employment, such as full-time, part-time, or contractor. | ||
|
Description
This attribute categorizes the new hire based on their employment contract. Different employment types may follow slightly different onboarding paths, for example, contractors might skip certain benefits-related steps. Analyzing the process based on employment type can help validate that the correct process variants are being followed for each category. It can also uncover opportunities to streamline the process for temporary or part-time staff, who may not require the full onboarding experience.
Why it matters
Helps in analyzing process variants for different worker categories, ensuring that appropriate onboarding procedures are followed for each.
Where to get
Consult Microsoft Dynamics 365 Human Resources documentation. This is a standard field on the Worker or Employment entity.
Examples
Full-time EmployeePart-time EmployeeContractorIntern
|
|||
|
Is Rework
IsRework
|
A boolean flag that indicates if an activity is part of a rework loop. | ||
|
Description
This calculated attribute flags activities that represent a step backward or a repetition in the process. For example, if 'Paperwork Sent To New Hire' occurs after 'Paperwork Completed By New Hire', it indicates a rework loop, likely due to errors or missing information. This flag is crucial for the 'Process Variant and Rework Analysis' dashboard. It allows for the direct quantification of rework, helping to highlight process inefficiencies, training gaps, or data quality issues. By filtering for rework activities, analysts can focus on the root causes of these wasteful loops.
Why it matters
Directly quantifies process inefficiency by flagging repeated or out-of-sequence activities, helping to identify the root causes of errors and delays.
Where to get
This attribute is not in the source system. It's calculated by analyzing the sequence of activities for each case in the event log and applying business rules to identify rework.
Examples
truefalse
|
|||
|
IT Provisioning Lead Time
ITProvisioningLeadTime
|
The time taken from when IT account provisioning is initiated until the new hire's equipment is delivered. | ||
|
Description
This metric calculates the duration of a critical sub-process within onboarding: getting the new hire the necessary IT access and tools. It specifically measures the time from the 'IT Account Provisioning Initiated' event to the 'Equipment Delivered' event. This is a key KPI for the 'Critical Path Activity Durations' and 'IT & Equipment Readiness Cycle' dashboards. A long lead time here directly impacts a new hire's ability to be productive from day one. Monitoring this metric helps identify bottlenecks within the IT department or with external equipment vendors.
Why it matters
Measures the efficiency of the critical IT setup process, which directly impacts a new hire's ability to be productive on their first day.
Where to get
This is calculated from the event log by taking the timestamp difference between the 'IT Account Provisioning Initiated' and 'Equipment Delivered' activities for each case.
Examples
7 days 3 hours10 days 1 hour5 days 6 hours
|
|||
|
Last Data Update
LastDataUpdateTime
|
The timestamp indicating when the data was last refreshed from the source system. | ||
|
Description
This attribute provides the date and time of the most recent data extraction from Microsoft Dynamics 365 Human Resources. It gives context to the freshness of the data being analyzed. This is important for reporting and dashboarding, as it informs the user how up-to-date the analysis is. For real-time monitoring, a recent timestamp is critical, while for historical analysis, it provides a reference point for the data's timeframe.
Why it matters
Informs users about the freshness of the data, which is essential for understanding the relevance and timeliness of the process insights.
Where to get
This timestamp is generated by the data pipeline or ETL tool at the time of data extraction.
Examples
2024-05-21T02:00:00Z
|
|||
|
Location
Location
|
The physical office, city, or country where the new hire is based. | ||
|
Description
This attribute provides the geographical location of the new employee. Location can influence the onboarding process due to different local regulations, office procedures, or logistical challenges. Segmenting by location allows for comparison of onboarding efficiency across different sites or regions. This can highlight regional bottlenecks, such as slower equipment delivery in certain countries, or identify offices that have highly optimized local onboarding procedures that could be adopted elsewhere.
Why it matters
Enables geographical analysis of the onboarding process, revealing regional variations in performance and compliance.
Where to get
Consult Microsoft Dynamics 365 Human Resources documentation. This can be found in the address or location information associated with the Worker or Position entity.
Examples
New York, USALondon, UKSingaporeRemote
|
|||
|
New Hire Name
NewHireName
|
The full name of the employee being onboarded. | ||
|
Description
This attribute contains the name of the new employee associated with the onboarding case. It provides a human-readable identifier for each case. While not typically used for statistical analysis to protect privacy, it is invaluable for operational use cases, such as drilling down to a specific employee's onboarding journey to investigate a delay or an issue identified in the high-level process analysis. It connects the abstract process data back to a real-world individual.
Why it matters
Provides a clear, human-readable reference for each case, making it easier to investigate specific onboarding journeys and discuss findings with stakeholders.
Where to get
Consult Microsoft Dynamics 365 Human Resources documentation. This would be sourced from the Employee or Worker entity, linked to the onboarding case.
Examples
Alice JohnsonDavid ChenMaria Garcia
|
|||
|
Overall Onboarding Cycle Time
OverallOnboardingCycleTime
|
The total time elapsed from the 'Offer Accepted' activity to the '30-Day Check-in Performed' activity for an onboarding case. | ||
|
Description
This calculated metric measures the end-to-end duration of the entire onboarding process for a single new hire. It is a key performance indicator (KPI) that reflects the overall efficiency of the process. This metric is the primary measure for the 'Onboarding End-to-End Cycle Time' dashboard. By tracking this KPI over time and across different departments or roles, the organization can monitor the impact of process improvement initiatives. Reducing this cycle time is often a primary goal, as it leads to faster new hire productivity.
Why it matters
This is a critical KPI for measuring overall process efficiency and directly supports strategic goals like reducing onboarding time.
Where to get
This is not a field in the source system. It is calculated during data transformation by finding the time difference between the first and last relevant events for each case.
Examples
35 days 4 hours42 days 8 hours29 days 2 hours
|
|||
|
Source System
SourceSystemName
|
The name of the information system from which the data was extracted. | ||
|
Description
This attribute identifies the origin of the process data. In a modern enterprise, data for a single process might come from multiple systems, so tracking the source is important for data governance and validation. In analysis, it helps confirm data lineage and can be used to filter data if multiple systems are involved. For this specific view, the value will consistently be 'Microsoft Dynamics 365 Human Resources', confirming the data's origin.
Why it matters
Identifies the data's origin, which is crucial for data governance, troubleshooting, and understanding the context of the data, especially in multi-system environments.
Where to get
This is typically a static value added during the data extraction and transformation process to label the dataset's origin.
Examples
Microsoft Dynamics 365 Human Resources
|
|||
|
User Performing Action
UserPerformingAction
|
The user or system agent who executed the activity. | ||
|
Description
This attribute identifies the person or automated system responsible for completing a given task in the onboarding process. For example, it could be an HR specialist, a hiring manager, or an IT automation bot. Analyzing who performs which tasks is key to understanding resource allocation and automation levels. It can help identify bottlenecks caused by specific teams or individuals and highlight opportunities for automation. For instance, if IT account provisioning is a manual task performed by one person, it represents a potential single point of failure and a candidate for automation.
Why it matters
Helps analyze workload distribution, identify resource-specific bottlenecks, and track the level of automation within the process.
Where to get
This information is typically found in audit trail or history logs, often as a 'Modified By' or 'Completed By' field on task records.
Examples
hr.specialist@company.commanager.jane.doe@company.comIT Service Accountrecruiter.bob@company.com
|
|||
Employee Onboarding Activities
| Activity | Description | ||
|---|---|---|---|
|
30-Day Check-in Performed
|
This event marks the completion of the scheduled 30-day follow-up meeting between the new hire and their manager or HR. It is often tracked as a final task in the extended onboarding process. | ||
|
Why it matters
This activity serves as the defined end event for the process analysis. Tracking its completion rate helps measure engagement and provides an early opportunity to address any new hire concerns.
Where to get
Inferred from the completion timestamp of a '30-Day Check-in' task within the Onboarding checklist or performance management module of Dynamics 365 HR.
Capture
Inferred from the completion timestamp of a specific task related to the 30-day review.
Event type
inferred
|
|||
|
Background Check Completed
|
Represents the successful completion and clearance of the new hire's background check. This event is usually captured when a checklist item is marked as complete or a specific status field is updated. | ||
|
Why it matters
This is a critical milestone that often serves as a gate for proceeding with employment. Measuring the lead time to this activity helps pinpoint bottlenecks.
Where to get
Inferred from the completion timestamp of the background check task in the Onboarding checklist or a status change to 'Completed' or 'Cleared' on the worker's record.
Capture
Inferred from the timestamp when the 'Background Check' checklist item status changes to 'Completed'.
Event type
inferred
|
|||
|
First Day Orientation Conducted
|
This activity represents the completion of the new hire's initial orientation session on their first day. It is a key milestone recorded by completing a task in their onboarding plan. | ||
|
Why it matters
This is a major milestone in the new hire's journey. Analyzing the time from 'Offer Accepted' to this point helps measure the efficiency of pre-boarding activities.
Where to get
Inferred from the completion date of the 'First Day Orientation' task in the employee's assigned Onboarding checklist or guide.
Capture
Inferred from the completion timestamp of the 'Orientation' checklist item.
Event type
inferred
|
|||
|
HR Profile Created
|
This activity represents the creation of the new hire's official employee record within Dynamics 365 Human Resources. It is an explicit system action that generates the core data foundation for all subsequent onboarding steps. | ||
|
Why it matters
The timing of this activity is critical as many downstream processes, like payroll and IT provisioning, depend on it. Delays here create a significant bottleneck for the entire onboarding journey.
Where to get
This is an explicit event logged in Dynamics 365 Human Resources. The creation timestamp of the primary worker record, for example in the HcmWorker table, can be used.
Capture
Use the createdDateTime system field on the core worker or employee entity.
Event type
explicit
|
|||
|
Mandatory Training Completed
|
Represents the completion of all mandatory training assigned to the new hire. This event is recorded when the employee's status for the required courses is updated to 'Completed'. | ||
|
Why it matters
This is a critical compliance checkpoint used to measure the training completion rate and ensure the organization meets policy requirements.
Where to get
Captured from the completion date of assigned courses in the learning module of Dynamics 365 HR. The last completion date of all mandatory courses could be used.
Capture
The completion timestamp on the worker's assigned course record.
Event type
explicit
|
|||
|
Offer Accepted
|
This event marks the official start of the onboarding process, triggered when a candidate accepts their job offer. It is typically recorded when the candidate's status is updated in the recruiting module or when a new hire record is initiated in the HR system. | ||
|
Why it matters
It serves as the primary start event for the onboarding case, enabling the calculation of overall cycle time. Analyzing this starting point is crucial for understanding the entire process timeline.
Where to get
In Dynamics 365 Human Resources, this is often captured when a candidate's record is moved to a hired state or when a new worker record is created with an accepted offer date.
Capture
Inferred from the creation date of the new worker record or a status change in the candidate record.
Event type
inferred
|
|||
|
Paperwork Completed By New Hire
|
This activity indicates that the new hire has completed and returned all required pre-employment paperwork. This is typically captured by marking a checklist item as complete in Dynamics 365 HR. | ||
|
Why it matters
This is a key compliance milestone. Measuring its completion time against due dates is crucial for ensuring a smooth start and tracking compliance.
Where to get
Inferred from the completion timestamp of the relevant checklist item in the Onboarding feature of Dynamics 365 HR.
Capture
Inferred from the timestamp when the onboarding task for completing paperwork is marked as 'Completed'.
Event type
inferred
|
|||
|
Background Check Initiated
|
This activity marks the point when the background check process is formally started for the new hire. This is often recorded by updating a status field or creating a specific task within an onboarding checklist in Dynamics 365. | ||
|
Why it matters
This marks the beginning of a critical and often lengthy subprocess. Tracking its duration is essential for identifying third-party or internal delays that can stall the onboarding process.
Where to get
Can be inferred from the creation date of a background check task in the Onboarding checklist or a status change on the worker's onboarding record.
Capture
Inferred from the timestamp when an onboarding checklist item for 'Background Check' is created or its status changes to 'In Progress'.
Event type
inferred
|
|||
|
Equipment Delivered
|
This activity marks the confirmation that the new hire's equipment has been delivered to their work location. It is usually captured by updating the status of a checklist item in the onboarding process. | ||
|
Why it matters
This is a critical endpoint for calculating IT provisioning lead time. It confirms that the physical tools needed for work are available to the new hire.
Where to get
Inferred from the completion timestamp of an 'Equipment Delivery' task or checklist item within the Onboarding feature of Dynamics 365 HR.
Capture
Inferred from the timestamp when the 'Deliver Equipment' checklist item is marked 'Completed'.
Event type
inferred
|
|||
|
Equipment Ordered
|
Represents the point in time when necessary hardware, such as a laptop or phone, has been ordered for the new employee. This is typically an activity within a larger IT provisioning checklist. | ||
|
Why it matters
Tracking this specific step helps to differentiate between delays in requesting equipment versus delays in shipping and delivery. It provides a more granular view of the IT readiness cycle.
Where to get
Can be inferred from the timestamp when a sub-task for ordering equipment within the onboarding checklist is marked as completed or started.
Capture
Inferred from a status change or completion of a 'Order Hardware' checklist item.
Event type
inferred
|
|||
|
IT Account Provisioning Initiated
|
Marks the start of the IT onboarding process, where requests are sent to create system accounts, email, and other access. This is often tracked via a specific task in an onboarding guide or checklist. | ||
|
Why it matters
This is the starting point for measuring IT provisioning lead time. Delays in initiating this step directly impact the new hire's ability to be productive on their first day.
Where to get
This is likely inferred from the creation date of an 'IT Setup' or 'Account Creation' task within the Onboarding checklist feature in Dynamics 365 HR.
Capture
Inferred from the creation timestamp of the IT provisioning task in the onboarding checklist.
Event type
inferred
|
|||
|
Mandatory Training Assigned
|
This event marks when required compliance or role-specific training courses have been assigned to the new hire. This is often managed through the learning management features within Dynamics 365 HR. | ||
|
Why it matters
This activity initiates the compliance training phase. Tracking it helps ensure training is assigned in a timely manner, allowing employees time to complete it before deadlines.
Where to get
Can be captured from the creation date of course assignments in the employee's learning record within Dynamics 365 HR.
Capture
Timestamp of when a course is added to the worker's assigned courses list.
Event type
explicit
|
|||
|
Onboarding Plan Completed
|
This milestone represents the completion of all assigned tasks within the new hire's formal onboarding checklist. It is captured when the overall status of the onboarding guide is marked as complete. | ||
|
Why it matters
This provides a clear administrative endpoint for the initial onboarding phase. It signifies that all required logistical and training steps are finished.
Where to get
This can be inferred when all tasks within an Onboarding guide or checklist for a specific employee have a 'Completed' status and timestamp.
Capture
Derived by checking if all assigned onboarding checklist items for a worker are marked as complete.
Event type
inferred
|
|||
|
Paperwork Sent To New Hire
|
This event signifies that necessary pre-employment documents have been dispatched to the new hire. It can be captured when a specific onboarding task is initiated or through integration with a document management system. | ||
|
Why it matters
Tracking this activity helps analyze the efficiency of the administrative part of onboarding. It's also the first step in a potential rework loop if documents need to be resent.
Where to get
Inferred from the creation or start date of a checklist item related to sending new hire documents in the Onboarding module.
Capture
Inferred from the timestamp when an onboarding task for sending paperwork is marked as started or created.
Event type
inferred
|
|||
|
Team Introduction Completed
|
This activity signifies that the new hire has been formally introduced to their immediate team. It is often a soft-onboarding step tracked as a checklist item for the hiring manager. | ||
|
Why it matters
This activity is important for analyzing the new hire's integration and experience. Consistent completion can correlate with higher employee satisfaction and faster team integration.
Where to get
Inferred from the completion of a 'Team Introduction' task within the hiring manager's view of the onboarding checklist in Dynamics 365 HR.
Capture
Inferred from the completion timestamp of a specific checklist item assigned to the manager.
Event type
inferred
|
|||
|
Workspace Setup Completed
|
Signifies that the new hire's physical or virtual workspace, including desk setup and system access, is fully prepared. This is often the final step in the pre-arrival preparations. | ||
|
Why it matters
This activity completes the IT and facilities readiness cycle. Ensuring this is done before day one is critical for a positive new hire experience and immediate productivity.
Where to get
This can be inferred from the completion timestamp of a 'Workspace Setup' task within the Onboarding checklists in Dynamics 365 HR.
Capture
Inferred from the completion of a specific checklist item related to workspace or desk setup.
Event type
inferred
|
|||