People Analytics tracks scheduled and recorded hours using employee work patterns to ensure precision and efficiency.
Scheduled hours
The scheduled hours events sent to People Analytics use an employee’s work pattern to determine what hours they are expected to do on a given day.
When the People Analytics integration is first turned on for your company, 3 years’ worth of scheduled hours events are sent for each employee.
On each daily load, the previous 30 days of scheduled hours are sent for each employee.
This is compared with the previous day’s load to add today’s hours and update any hours from the previous 30 days have changed.
Changes to work patterns effective more than 30 days in the past will only have the most 30 days’ hours updated.
All scheduled hours events are based on an employee’s work pattern.
No future data is sent.
People Analytics Field | PeopleHR Field | Notes |
EmployeeId | Employee’s unique ID in PeopleHR | Not the employee id displayed in PeopleHR |
Hours | Work Pattern Day > Hours |
|
Shift Start Time | Work Pattern Day > Start | If no work pattern start time entered, 09:00 is used. |
Shift End Time | Work Pattern Day > End | If no work pattern end time is entered start + hours is used. |
Scheduled Shift Type | Regular |
|
Event Date | Work Pattern Day > Date |
|
Hour recorded
PeopleHR uses an employee’s work pattern alongside planner events to determine what hours recorded events are sent to People Analytics.
When the People Analytics integration is first turned on for your company, 3 years’ worth of hours recorded events are sent for each employee.
On each daily load, the previous 30 days of hours recorded are sent for each employee
This is compared with the previous day’s load to add today’s hours and update any hours from the previous 30 days have changed.
Changes to work patterns effective more than 30 days in the past will only have the most 30 days’ hours updated.
Hours recorded events are based on an employee’s work pattern and events on the planner (except timesheet events).
No timesheet data is included in the hours recorded data.
No future data is sent.
Multiple events may be sent for an employee on one day.
E.g. Emma has a half day annual leave booked and is working the morning.
One event for the annual leave and 1 event for the worked portion of the day.
People Analytics Field | PeopleHR Field | Notes |
EmployeeId | Employee’s unique ID in PeopleHR | Not the employee ID displayed in PeopleHR |
Hours | Work Pattern Day > Hours
Planner Event > Hour | Event hours are calculated from work pattern if booked as day/part day |
Shift Start Time | Work Pattern Day > Start
Planner Event > Hours | If no work pattern start time is entered, 09:00 is used. |
Shift End Time | Work Pattern Day > End
Planner Event > Hours | If no work pattern end time is entered, start + hours is used. |
Pay Code | Work Pattern Day – ‘Regular’
Holiday – ‘Annual Leave’
Sick – ‘Sickness’
Late – ‘Late’
Maternity/Paternity Leave – ‘Family Leave’
Other Events – ‘Other Event Reason’ |
|
Standard Pay Code | Mapped Value | Matches Pay Code except for Other Events, which can be mapped to the relevant Standard Pay Code as described below. |
Absence Reason | Sickness Reason
Other Event Reason |
|
Event Date | Work Pattern Day > Date
Planner Event > Date |
|
Other events mapping
All time and attendance events that are not Other Events are mapped automatically to the corresponding Standard Pay Code in People Analytics. Due to the flexible nature of Other Events, you can choose which Standard Pay Code each other event reason maps to.
To map the other event reasons, follow the below steps.
Click Access Button
then click HR Admin.
Click Settings, then click People Analytics.
Select Mappings, then click Other Events.
For each PeopleHR Code, select a value from the People Analytics Codes dropdown to map to.
Click Save.
All other event reasons will default to ‘Other Absence’ is they haven’t been updated in the mapping page.