Ideas

Dear iSAMS, On the Reward and Conduct Manager, teachers have been feedback whether the pupil name can be displayed as Preferred Forename and Surname rather than Forename and Surname when they are given a merit ticket etc. As always, pupils are kno...

The integration is not fully integrated as it is with other MIS platforms such as SIMS or Arbor. For example, we currently need to manually upload certain data fields – such as “SEN Stages” and “SEN Needs” (which are equivalent to our “SEN Flag” a...

Currently there are no fields that you can use in Letter Templates to pull out medical information on a pupil. So when we are sending home a letter of consent we have to ask the parents to complete all the medical information from scratch rather t...

When coming up to a detention can a reminder email be sent to the teacher (maybe also the pupil). E.G. Detention is at 4pm, email is sent at 3pm to teacher (maybe also pupil) about the detention.

Occasionally, we have to delete Reward and Conduct entries that have been added in error, eg to the wrong student, or a sanction that is then rescinded. Is there any way that the staff who had notification of the entry in the first place can then ...

When putting a pupil in detention, the detention "Type" gets its own column. When on "View Detentions" or "Manage Detentions" in Discipline Manager, the "Type" gets lumped in with the detention name (along with the room for the detention). I feel ...

.

An idea to address two current issues around Action visibility. Currently, if you are assigned an action, you are emailed but can only see the action if you are also given visibility of the concern. The wider list of staff with visibility of the c...

At present, there will only be a concern raised if it is 3 instances in a day/week/month - it would make it much more useful if it were 'year' also, because unless it happens within the day/week/month, it won't be a record and that means the conce...

Let users first select the location to filter the supplier list when raising req/po etc. Relevant for users who have access to multiple locations, mainly Central teams. Makes it easier to find a location supplier, rather than scrolling through 20+...