Ideas

When first adding an allocation, we can quickly allocate multiple year/subject/form to one report template. However from the list of allocations set, we cannot select multi-select allocations and change the set report template in one go. Neither c...

Would it be possible to schedule emails to go at certain points of the year to a certain type of person/group of people on the database to aid the admissions process? For example every January, on a set date, those who have accepted a place to joi...

When configuring the Type Properties of a Module Type it would be helpful if the year groups to which this Module Type were applicable could be specified. We have awards specifically for each of Lower School (years 7-8), Upper School (years 9-11) ...

When processing lodgments from the bank feed, it would be good to be able to enter negative values, as most of our lodgments have card transaction fees included, so the full income needs to be posted separate from the fee. Currently, we process th...

To be able to view 'what register' if any, a student is on - presently there is no easy way to see which register any particular student is

It would be amazing to be able to select multiple templates to delete, copy or archive together and not have to do it to each individual template.

Following on from what I said at yesterday's Southern User Group: As courses are looking like a main driver within Curriculum Manager, please link the course type to a Global List where we could map courses against the DfE requirements for the SLA...

Make Preferred Surname available on Export Wizard. As this is a field in the student's core details it should be available to export to export wizard to run reports. We have a few families who have a preferred surname which they insist we use inst...

We have a family where they have one shared child, and 2 step kids. I wanted to add the father who is the father of 2 kids and step father of one. But I could not use the same contact as Contact Type = Father for one and Contact Type = Stepfather ...

It will be useful to simply hide a custom field instead of having to delete it. I assume by hiding we'll be able to maintain the historical data and also reactivate it if the need arises.