Ideas

We can distinguish between a pupil's forename and preferred (first) name and have both of these added to the enquiry and registration forms. However, only the (legal) surname field is available for use. It would be great if the preferred surname f...

We would love to be able to export all of the information from a form (Open Morning, Individual Tours) into an Excel document.

It would be useful to know how often staff members are accessing the reports in Central.

We often add applicants into iSams off the back of an event. However, to add them onto the event, we need to create the applicant. Then exit the record, search for them and then add them onto the event via the pink drop-down. It would be good to b...

We would look to anonymise admissions data for pupils who chose not to join us some time ago, so that we can retain the generic statistical information for future analysis whilst being GDPR compliant.

Currently, school email address field is not available for applicants. It would be beneficial if this field were accessible, allowing the school email address to automatically transfer once an applicant becomes a current student.

Is there a roadmap of the priorities for data integration with Central? It would be great to have a timeline to know when new features are being considered. At the recent South East Asia User Group meeting (March 2024), we heard that <30% of iS...

We have a separate front end where parents are able to update their contact and custom information. It would be great to be able to update this information via the API. We currently update this information using direct SQL queries.

Currently the admissions portal forms force the user to add an additional contact. We do get applicants in one-parent/guardian families who, at the application stage, only want to enter the details of that one parent/guardian. We have to advise su...

This would be useful when you need to add the same information to multiple applicants/pupils.