All ideas

Currently, the reports on the Registration Manager only display data for AM and PM registration. It would be very beneficial for teachers to view attendance data for students within a specific set group, allowing them to easily monitor attendance ...

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

While the new list is improved, it is still not user friendly and leaves out a number of 'options' we allow for/have notes on. There is no JCQ guidance on restricting what we can use at our centre as an aide memoire - can the list become a global ...

It will be useful to have a tick box next to the current pupil contacts for school to identify which of them are the emergency contact(s) for the pupil on top of the existing Family Circumstances / SOS Pupil Contacts. School can use it as an addit...

We have various processes that happen regularly, pupils joining/leaving, staff joining/leaving, organising school trips, etc. which involves all the usual emails, conversations, setting reminders, etc. However, there is now central overview of the...

Customer has requested that when an employee who has worked in a permanent role and then leaves that role to work in a casual role, the employee record does not at this time move to the "casual staff" tab. This would be ideal if it could be moved ...

It would useful for us to be able to see an audit log of changes made in the Reports Wizard module, i.e. whether a View As Other user or HOD/HOY or other proof reader has made changes to the original teacher input.

As is the Student Widget shows attendance in a nice sreamlined way, but we have no control on the data or how it calculates the percentages. It seems to be considering the "Not yet registered" as absencies. It would be great to be able to select, ...

We’re exploring the introduction of a General Journal Approval workflow to enhance control and oversight in the journal entry process. This potential feature would integrate general journal transactions into the existing workflow approval engine, ...

We’re proposing a new feature that allows users to deactivate GL account codes, removing them from use in future transactions while retaining their historical data for reporting and audit integrity. Once deactivated, a GL code will no longer appea...