Managing contractual sick pay

Myhrtoolkit provides tools for managing Contractual Sick Pay within an organisation as a Controller or Manager with the right level of access.

Settings

Navigating to Config > System > Absence > Sickness absence allows the setting of:

  • The maximum number of days of Contractual Sick Pay (CSP) that your organisation allows;
  • Whether managers are limited to that maximum. If this is active, managers can allow unlimited CSP.


Monitoring Contractual Sick Pay

An employee’s current CSP status is visible by navigating to Management > Absence > Sickness absence.

Monitor contractual sick pay with myhrtoolkit


A summary of each employee’s Year-to-date and ‘rolling 12 month’ CSP is shown at the top of their section.

Note – the figures shown are only as good as data put in – CSP entries must be kept up to date for these summaries to be accurate and meaningful.

Data shown will only be taken from the ‘go live’ date of the CSP feature.


Adding new entries

Once an absence has been registered in the normal fashion, a CSP entry can be added by finding the relevant absence record and ticking the ‘Yes’ box in the Contractual Sick Pay column in that row. The page will reload allowing you to enter the from/to dates and number of CSP days granted for this absence. When ready, Submit the entry.

If the entry pushes the employee over the limit set for CSP, you will be notified. Depending on settings, you may be required to re-enter a new value.

Add contractual sick pay entries

Notes
  • When adding new CSP entries, the number of days between the 'from' and 'to' dates is not calculated automatically by myhrtoolkit. Specific work/rest day arrangements for individuals are not tracked within the system.
  • The 12 month rolling window is based on 'today'. If sickness is entered belatedly, this value could change unexpectedly depending on other previous absences.


Related guides

Sickness absence settings - Controllers

How to manage sickness absence on myhrtoolkit

  • There are no suggestions because the search field is empty.