In line with the date tagging of schedules, it is critical that the company policies be date-tagged as well. This will ensure that the company policies in a certain period of time will remain as is when clients decide to change their policies moving forward.
For example:
Client A started with Sprout with a grace period of 15 mins and decided to change it today moving forward to 30 mins.
With the date tagging of company policy, if you generate attendance for yesterday, it will still follow the grace period of 15 mins.
But if you generate attendance for today, it will now follow the 30 mins grace period.
And this will follow for all other company policies available in Sprout HR.
The goal for Date tagging of Company Policies is to have data integrity and ensure that the data from the past will be intact and correct once a new set of policies are implemented moving forward.
- For a newly created instance, the first sets of policies will only have the start date for the policies
|
Start Date |
End Date |
Grace Period |
|
01/01/2020 |
Present |
15 |
- When the same company requested a policy to be changed, the old policy will have an End Date and a new set of company policy will be as follows:
|
Start Date |
End Date |
Grace Period |
|
01/01/2020 |
01/20/2020 |
15 |
|
01/21/2020 |
Present |
30 |
- When a policy is changed, and even only 1 policy will change, this will create a record of all policies but the value of that policy will only change. Example:
- Given that we have a set of policies: Grace Period, Deduct ND on Break, Start of Night Shift Hours, and End of Night Shift Hours. When the Grace Period is changed, a new record for all the policies will have a new record:
|
Start Date |
End Date |
Grace Period |
Deduct ND on Break |
ND Hour Start |
ND Hour End |
|
01/01/2020 |
01/20/2020 |
15 |
Yes |
22:00 |
06:00 |
|
01/21/2020 |
Present |
30 |
Yes |
22:00 |
06:00 |
Comments
0 comments
Article is closed for comments.