Even with clearly documented policies, things can still go wrong. A 2018 study found that 92% of timesheet errors were due to user error, typically forgetting to log their hours. Missed time entries have to be followed up on by another resource, and much time is wasted.
The best way to prevent things from going wrong is to make it easy for them to go right. Here is a list of measures that can eliminate problems before they arise.
Notifications
While you should be wary of solutions that rely too heavily on AI, automatic features can be helpful in countering predictable human errors. Reminders (when a timer hasn’t been turned on) auto-disable (when it has not been turned off), and more advanced features such as Pomodoro can make life much easier, and can be shut down if they are not helpful.
Giving the whole task of time tracking - including categorization of tasks - to AI is not such a good idea, outside the narrow remit of recording how much time has been spent on certain sites or within certain types of file.
Frequent tracking
It’s an ongoing debate whether using a real-time timer is preferable to periodically updating a timesheet manually. The rule of thumb is that if you need accuracy but not precision - such as tracking for compliance or payroll purposes - then manual time tracking is sufficient.
However, if you choose the manual approach, you should encourage workers to book their time daily, as leaving it until the end of the week runs the risk of inaccurate data. People are in general poor at estimating time, and this obviously worsens with distance.
Locking timesheets
While it is good to allow a period during which employees can edit and correct mistaken time entries, it’s good practice to freeze the data after an agreed interval, ideally before the data is used (for analysis or billing). This not only avoids reconciliation problems, but also incentivizes users to book their hours sooner rather than later.
Simplified choices
Cumbersome processes create errors, so simplifying choice architecture is a no-brainer for improving the quality of your time data. Generally, this means getting rid of stuff! For example:
- Showing people only the projects or tasks they are working on or tagged to
- Archiving completed projects/retired categories so that they no longer appear
- Ordering the lists so that the most frequently used items are seen first
If you are - as is likely - using software provided by a 3rd party vendor, you should make the above points a part of your due diligence.
Required fields
Required fields are a powerful way to ensure that certain data points are collected. However, it is important to ensure that only the most vital data is made mandatory in this way. In other words, your aim should be to minimize the number of required fields. Focus on quality over quantity, or you will end up with the reverse!
Approvals
While the above features will improve your chances of success, you can never reduce errors to zero. That’s why, for accounts where there is no room for error (or where an error has already taken place, and no further mistakes can be afforded!), adding a mandatory a human approval step (by a manager or other designated person) is advisable.