My role
UX Design & Workflow Simplification
Turning repetitive administrative work into an independent registration experience.
School administrators previously had to manually enter parent contact details into individual student profiles, repeating the process across hundreds or thousands of students. I redesigned the onboarding experience by introducing school-specific registration links that allow parents and staff to verify their identity and create their own accounts, significantly reducing the manual work required from administrators.
UX Design & Workflow Simplification
School Admins, Parents & Staff
Web ERP & Mobile Web
Although student information was already available through imported EMIS records, administrators still had to open individual student profiles and manually enter parent mobile numbers to enable parent access. This created a repetitive task that grew with the number of students. The same dependency on administrative involvement also made staff account onboarding less efficient.
Locate the student and enter parent details.
Perform the same task for every student.
Hundreds or thousands of manual entries.
The existing workflow required administrators to locate each student, open their profile, enter the parent's mobile number, and save the changes before moving to the next student.
Access the student management module
Search by name or admission number
Navigate to the individual student record
Manually input the contact information
Update the student profile
Continue until the school’s records are completed
Entering one mobile number may take only a short time, but searching for students, opening profiles, updating information, and saving records creates significant cumulative effort. The following calculator illustrates the potential workload. The per-student time is an assumption, not a measured result.
The calculation includes estimated time for finding, editing, and saving profiles. It excludes collecting contact numbers and correcting incorrect entries.
The audit revealed that the primary problem wasn't the complexity of entering a phone number. It was the dependency on administrators to complete the same action for every student.
User impactRepetitive navigation and data entry
User impactParents couldn’t independently provide their own details
User impactAdditional coordination with families
User impactIncorrect numbers could affect account access
User impactWork increased with school size
User impactMore administrative involvement
Rather than optimizing the existing data-entry form, I reconsidered who should own the onboarding task. Parents and staff already knew their personal information, while the school already had the records required to identify them. The solution was to connect these two sources through a self-service registration experience.
Allow parents and staff to provide their own contact information instead of relying on administrators.
Use student and staff information already available in the ERP to identify the correct records.
Provide a school-specific link that administrators can share through familiar communication channels such as WhatsApp.
Instead of collecting and entering individual contact numbers, administrators can generate a school-specific onboarding link and share it through existing WhatsApp groups. Parents and staff can then open the link on their own devices and complete registration independently.
school.example/onboard/greenfieldIllustrative URL, not a live registration link.
Administrator creates the school’s registration link.
The link reaches parents and staff through school groups.
Users open the link and complete registration.
Parents access the school-specific onboarding link and enter the student's admission number and date of birth. These details are checked against the existing student records imported into the ERP. After the student is identified, the parent can provide their mobile number and create an account.
Parent opens the link shared by the school.
Parent provides the student’s admission number and date of birth.
The system checks the details against the school’s existing student data.
Parent provides the number they want associated with their account.
Parent completes account registration and gains access according to the school’s account setup.
The same approach was extended to staff onboarding. Instead of relying on administrators to enter staff contact details individually, employees can use the school-specific registration link and verify themselves using information already available in their staff records. For staff, the matching details are their date of birth and date of joining the current school.
Staff member accesses the school’s onboarding page.
Provides date of birth and date of joining.
The system checks the details against existing staff information.
Staff member enters their mobile number.
Staff member completes registration without requiring manual account creation by the administrator.
Both parents and staff begin with a school-specific link, but the verification experience adapts to the type of user registering.
Illustrative interaction · no personal data is stored or submitted.
The redesigned workflow shifts individual registration tasks from administrators to parents and staff. Administrators initiate onboarding once, while users independently verify their records and complete account creation.
Admin creates the registration link
Distribute through WhatsApp groups
Parent or staff opens the registration page
Enter role-specific matching details
User enters their own contact number
Account is connected to the matched record
The redesign changed both the number of administrative interactions and who was responsible for completing them.
Admin enters each number
Parent enters their own number
Admin searches student profiles
Parent verifies against existing records
Admin involvement required
Staff completes self-registration
Individual coordination
One school-specific link
Increases with number of students
Focus shifts to link distribution and exceptions
Repetitive per-user work
Self-service registration across the school
Admin inputs users’ contact information
Users provide their own details
By introducing school-specific registration links and record-based verification, the onboarding experience no longer depended on administrators manually updating every student and staff profile. The new approach made registration more scalable and gave parents and staff greater control over providing their own account information.
Administrators no longer need to enter individual parent numbers for every student.
A single school-specific link supports self-onboarding across many users.
Parents and staff provide their own mobile numbers and create their accounts.
The redesign didn’t just make data entry faster. It eliminated the need for administrators to perform most of that data entry in the first place.
Initially, the problem appeared to be a slow administrative task. But improving the student profile form would only make the existing process slightly faster. By questioning who needed to perform the task, I identified an opportunity to remove the administrative dependency altogether. The result was a self-service approach that reused existing school records, reduced repetitive work, and made onboarding more convenient for parents and staff.
← Back to all projects