Individual profile updates
User impactRepetitive navigation and data entry
School administrators had to find individual records, enter contact details, and repeat the process for every parent and staff member. The business objective was to reduce setup effort and help schools activate users more efficiently. I designed a self-service registration flow using a school link and record-based verification, allowing parents and staff to complete onboarding independently while administrators retained oversight.
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.
The school shares a registration link or QR code. Parents enter their child’s admission number and date of birth, confirm the matching student, and verify their mobile number with an OTP. The number is then linked to the child’s profile, with an option to add another child or download the app.
The administrator generates a school-specific registration link or QR code to share with parents.
Parents identify their child, verify their mobile number, and link one or more children.
The school shares its registration link or QR code, and the parent opens it.
The parent enters the child’s admission number and date of birth.
The parent reviews the matching student’s details and continues.
The parent enters a mobile number and verifies it using the OTP.
The verified number is connected to the existing student profile.
The parent can link another child or download the app to continue.
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 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
The self-service journey separates finding a child, confirming the profile, and linking a parent account. These WCAG 2.2 references support clearer inputs and less avoidable effort throughout that process.
Labels or Instructions
The flow separates student lookup, profile confirmation, and mobile verification instead of presenting one undifferentiated task.
Check that each input explains the information required and any expected format before the user submits it.
Read W3C guidance (opens in a new tab)Headings and Labels
Separate parent and staff paths give each audience a clearer purpose and sequence of actions.
Verify that headings and action labels describe the relevant role and the step being completed.
Read W3C guidance (opens in a new tab)Redundant Entry
Finding an existing student profile allows the parent to confirm that information rather than recreate the profile.
Within the same process, make previously supplied information available for reuse unless a WCAG exception applies; verify this across every step.
Read W3C guidance (opens in a new tab)Accessible Authentication (Minimum)
The mobile-verification step is the point where accessible authentication needs explicit developer attention.
Allow code paste or supported autofill so users are not forced to memorize and manually transcribe the OTP. OTP alone is not evidence that this criterion is met.
Read W3C guidance (opens in a new tab)These are design-to-guideline mappings, not a WCAG conformance certification. The implementation checks identify what must be verified in the working product.
Open the existing and redesigned School ERP prototypes in Figma. These shared links show the student-onboarding flows from the first case study.
Follow the previous upload and validation journey to understand where administrators lost context and had to recover manually.
Open existing prototypeExplore the revised onboarding experience designed around clearer guidance, recoverability and scalable error handling.
Open updated prototype