Over the years we have seen both good and bad time and attendance implementations. Actually, what is below probably relates to most system implementations. So use this as you see fit for any systems in your business.
The question is, what are some of the reasons that system implementations fail?
1. Lack of trust in the system
It is often difficult to trust something that we didn't do ourselves. Especially, when there are real-world consequences. If you get your wages bill wrong, that could lead to a strike (or worse, and yes we have been told stores about events worse than strikes).
If you don't trust a system, in our opinion, what is wrong here is a lack of a process to verify data from the system. You need a quick and easy method to check that what you are getting from your system is correct.
We train our clients on what we call the "Daily Best Practise." It's a rigid set of steps designed to quickly pull-out exceptional data from the timesheets.
Once you have dealt with the exceptions, and more importantly the root cause (for example an employee missing hours because they didn't clock), you start to feel more comfortable with the integrity of the data.
