Feature Requests

Please could you make it possible to export the event attendance fields, i.e. Registered, Attended, Did Not Attend, Cancel, as opposed to having to filter by each one and export each status separately?

I should be able to export Event Attendance and Event Dates

Recurrent issues with the ‘Send Reference Request’ message option: Sometimes an ‘alert icon’ pops up next to a school name with more than two applicants, but when we check their applications’ feeder school details we can’t see any discrepancies. We even check for spaces before or after the headteacher name or surname or the school email address, as those blank extra spaces can cause an alert to pop up, but most of the time we can’t find any discrepancies. We have reported this issue to the OA support team and they don’t find any discrepancies either and have no idea why the alert is there, which makes us feel very insecure at the time of sending the reference request, as we can’t preview the messages or see how they have been sent, therefore we can’t know if all the students of that school with the alert were on the list that the school has rec’d (see image attached) If a school replies to the message we send through the ‘Send Reference Request’ button we NEVER receive those messages. This issue has caused us big headaches and huge problems this year during the busiest time of the year for admissions. We NEED TO BE ABLE TO RECEIVE REPLIES TO THOSE MESSAGES. We have reported this issue several times to the OA support and development team and nothing has been done. This is a big concern for us.

Would be nice to have the "tag rules" to be activated by a checklist item. Say: completed privacy form -> "privacy ok" tag added. This is very useful when you have to filter the roster, because you can filter by tag but not by checklist status.

We would like to request a new feature in OpenApply that allows us to email feeder school heads directly from the system—not just for reference requests. Currently, we need to export data or manually copy contact details to send bulk communications regarding applicant outcomes, enrolment updates, safeguarding forms, or other ad-hoc matters. Could you please consider adding an email facility, similar to the reference request function, that supports customisable email templates for use with feeder school contacts? Thank you.

We would like to have the possibility of customising the automated email that is sent to parents along with the invoice. We understand that Flywire has been in touch with you about this matter for a few months now. At present, the email parents receive simply instructs them to make the payment via Flywire, without providing a link to Flywire/to their account, or further explanation. This has caused confusion and frustration among our clients. We would be very grateful if you could prioritise this matter. Many thanks and kind regards,

We would like to request a feature improvement that would facilitate our daily work. When the parents upload the headshot of the child, we ask them to upload an only head and shoulders image, but if they don't have a head and shoulders one, they upload a full body picture and then we, admissions, have to download that pic edit it and upload it again to their profile to make it only head and shoulders. It would be very helpful, like in many other apps, if the Open Apply ‘upload image’ field could have the option to adjust the frame in the picture, so that the parents can adjust the pic to only head and shoulders when the upload the headshot of their child.

It would be beneficial to have a sibling tb under review mode to see if the applicant has a sibling and what their current status is

Admins and parents will be able to link their OpenApply accounts to Google or Apple to make sign-in easier.

We understand that we have to ask for the parent gender on the registration form and that this field is used when importing data. We would like to ask if this could be changed. Given that we already request the parent prefix and the relationship to the child, we do not see a direct reason to ask for this additional information. To ensure we remain data compliant, we would like to have the option to remove this field from the registration form.