Ideas

Currently all covers are weighted the same, whether a 5 minute registration or a 55 minute lesson. It would help to create a fairer picture of 'load' if some periods could be scored with a different (sometimes zero) wieghting. This is how other so...

When we suspend lessons by year group (not by set), it also effects other year groups if we have a student out of their year in that class/set. Example: I have suspended Upper 6 lessons for study leave. A Lower 6 lesson showing as suspended in cov...

When a timetable is suspended e.g. Y11 go on leave on exams, it marks the room allocated to their lessons as avaliable so that these show up when allocating room changes.

It would be useful if when you added a member of staff as unavailable they system checked if they were already allocated to cover and alerted or removed the cover.

At present when creating a purchase REQ the attachments that someone adds are not automatically carried forward onto a PO when creating this. This causes additional workloads to ensure you have downloaded the REQ attachments and then to upload to ...

The ability to add exact times (e. g. 1pm-4pm) when adding a timetable suspension for a year group in Cover Manager would be really useful, for example when all students in a year are on a trip in the afternoon but are present in the morning.

The description field is not long enough - even if you press F8 for more detail to be added, this is applied to the whole document, not individual lines, and for sales invoices cannot be seen by the customer

Granular permissions for Cover manager widgets. Currently all staff who have access get to see the "Top 5 absent teachers" this goes against the ICO guidance that "An employer must not publish ‘league tables’ of sickness absences of individual wor...

Rota cover does not currently appear in the Master Timetable spreadsheet exported in the Timetable Manager. So these need to be added manually to provide a true picture of staff availability and frees.

Currently if an invoice is started to be processed as a PI, and a subsequent order number is spotted, it has to be cancelled and the data entry has to start again on the purchasing suite. It would be much more efficient if there was a single input...