Ideas

When creating a form that will be used across more than one school, Prince Regent Street Trust would find it really useful to be able to share that form with other sites instead of having to create multiple forms for each school.

With all the web browser info, filters, banners and on Gradebooks frozen info panes, the actual area of viewing info/data is significantly squashed for a normal user (most users I would guess) on a 15' laptop screen. It would be really useful to h...

We have noticed that once Gradebooks have been archived, which is the reasonable process to do after rolling over every year. The report mapping to previous/historical report cycles are removed. This means that all gradebook data is removed from s...

Currently, when Gradebook columns are mapped incorrectly to reporting template elements, each mapping must be removed individually and with a confirmation prompt. This can be very time-consuming when multiple mappings have been created in error. I...

Absence reporting - The details box which you can't report on from within an absence instance. For example, when an absence request is made and details for the absence are added to the details box, I cannot report on this information as there is n...

There has been a request for the SCR module report to provide a more concise / reduced report. The customer has provided the attached as an example for future developments.

Please can Force Review be enabled as default to prevent human error and notifications being sent from the system prematurely. Whilst Implementation consultants should be enabling this, it is easy to miss and always needs to be enabled at the begi...

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 ...

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