Ideas

We have three parts of the school, Pre Prep, Prep and Senior, but I can't view all the cover needed across the entire school on one page, only one page for each section. If there was a way to show all cover needed in the day across the entire scho...

Frequently when cover is required due to part of a year group being out on a trip, we may combine classes. We couldn’t find an obvious way of combining classes and notifying teachers that this has happened. We found that we could get the same memb...

Email reminders regarding outstanding training are sent at 3am. I have asked if this can be changed as this is not ideal. I have been told that this is not something that can be changed and to submit a feature request. Please can this be amended.

We switch timetables during our academic year (as many schools do e.g. during exam periods). When we do that, it wipes out any historical data from the cover module, rendering the statistics meaningless. Is there a way we could retain the stats of...

We would benefit from a quick add option in the cover module. I would have the opportunity to create an "absence" add a name and the time required. It would be great for invigilation and random duties we need to cover. It would generate a cover sl...

The ability to sync contracts data from the BM module to IRIS Financials in a digital way.

Having completed rollover today I've realised I'm wasting quite a bit of time with form groups. Our sixth form has form names based on the year and the tutor's initials eg 12ABC. When they move up to Y13 we create a new group 13ABC, and delete the...

We often have events which need the Timetable to be suspended for part of a day, e.g. One year group for the afternoon. We can then use 'spare' teachers to cover lessons.

Some staff at the school currently do not have access to iSAMS, either because they are third-party contractors or for other reasons. However, they require access to information regarding the number of students per form, as well as the total by ye...

Allow any changes made in Every HR, from absences, contract changes and address changes, to be synced back into Arbor. Any changes to Arbor to be reflected in Every HR after the initial sync.