Improve application relationship mapping

Every time we process applications, we end up with duplicate users, particularly siblings, and grandparents. We also often get a single person listed as both parent and grandparent.

I believe this is due to a couple of factors regarding the application:

 

1) The completely linear flow with no styling whatsoever makes it difficult to see where you are in the application. You can't tell if you are in the parent or grandparent section.

 

2) It's too easy to start an application for a sibling by selecting "New User". Users should be prompted to confirm starting an application for a NEW child if they already have children listed who have not applied.

 

The second part is easy to fix, and I have already submitted it as its own request (K12OB-I-1410).

The first part requires an overall rethinking of the way the application is put together. This should be a priority for development, because every single non-staff constituent in the system comes through this workflow.

  • Guest
  • Dec 6 2018
Blackbaud Enrollment Management / Application
  • Attach files
  • Daniel commented
    September 20, 2023 14:43

    This is sorely needed. It's confusing for parents and adds so much extra work when processing applications. The relationships don't even pull for grandparents, so parents have to input grandparent info again when applying for another child. If we've already mapped the relationships for the previous candidate (or current student sibling), this shouldn't be necessary.

    Suggested in 2018 with no progress...!

    ×

    Attachments Open full size

  • Hannah Falchuk commented
    February 16, 2021 17:26

    This is happening at our school, particularly with applicants who were first listed on an application as a sibling (and automatically given an account) only to be applied as a candidate in later years (and given new account).


    A chat support agent showed me that "Do Not Create a User Account" can be checked off for siblings who are included on an application, but this must be done for each application as it is processed. It would be nice to have the setting default to NOT creating a new user or to have this as a global setting for the entire application.


    We find ourselves removing many of these "empty" sibling accounts once the new one is created for the candidate.

    ×

    Attachments Open full size

Related ideas