e-days blog

Managing staff absence effectively – System considerations: Introduction

Authorby 06 July, 2012


Staff absence in any organisation is a serious matter. Here’s the bottom line: Staff absence costs you money.

Thus – the system you use to record and manage your staff absence is of paramount importance. Give it thorough consideration.

A variety of absence management systems are available to companies; paper-based, spreadsheet, desktop-based systems, online systems and wider HR systems. However – this series will focus on the latter: online and wider HR systems.

Many wider HR systems exist which have a built-in absence management module. Such systems cover other HR aspects like clocking in systems and payroll.

For some, the function provided by these systems may be sufficient. But for many, it won’t be. To demonstrate this, at e-days we have a track record of corporate customers approaching us because they’ve discovered limitations with their HR systems.

You may think: With a wider offering, a larger HR system is a better option. But is it really?

To larger HR systems, staff absence is one module out of many. The effectiveness of managing your company’s staff absence may be compromised by it simply being a module.

Staff absence management systems – take our software solution e-days for example – consider staff absence as their primary focus. They are much more flexible when it comes to managing absence. Say, for example, you have complex working patterns in your organisation – these absence-focussed systems are likely to be much more capable in managing absence in line with these patterns, whereas a larger HR system may not have the functionality to adequately cope.

That breaks me nicely into this series which considers why managing staff absence separately from wider HR may be of benefit to your organisation.

Some interesting arguments and evaluation points in the following topic areas will be visited in this series:

  • Company structure
  • Working patterns
  • Self-service
  • Admin tools
  • Cost
  • On-going development

Until next time…

comments powered by Disqus