Ideas

Currently if an employee has a planned absence at any point in the future, you cannot add sickness with an open ended date, meaning its impossible to accurately monitor sickness when almost 50% of staff have planned absences at some point in the f...

The option to download all documents related to a case as bundle rather than individually. Would also be nice to have the option as to what to include in the bundle rather than just all the docs depending on recipient.

The calculation of amount claimed for a time claim to be done to two decimal places. When calculating the amount claimed this has increased due to the four decimal places. If this is calculated to two decimal places the amount claimed is correct.

The approval process for Teaching, Non-Teaching and Prep School general absences differs so we have had to triplicate the reasons. Because the list is not alphabetically sorted (I'm pretty sure they used to be), staff have to trawl through a list ...

Currently the custom report builder does not link to performance module so you cannot run any custom reports. Adding in this link to performance module would massively improve the reports produced for performance module.

There has been a request that the attendance % statistic and the absence heat map on the record should not take general absences or family leave into consideration. This should only consider the sickness type. Is this possible to look at giving th...

For the fields which require mapping to CTF, DfE, ISC, (e.g Nationality) update the Post / Put Rest API calls to allow updating of the mapping's required. Currently the Rest API only creates the object, but doesn't do anything with the mapping.

It would be helpful if we could set permissions so that some admin / reception staff can see who is on the Single Central Record, without being able to see the details or the reports. If we give staff access to the details page, they can also use ...

Customer has requested that pay awards do not update the salaries of employee's who have left the business but are still held in EveryHR as a previous employee record.

Customer believes this is a sensitive field by nature and this should be moved into the sensitive information section of the employee record on EveryHR