← Back to Projects
UX Case Study 03School ERP · Self-Service UX

Parent & Staff
Self-Onboarding.

Turning repetitive administrative work into an independent registration experience.

One school linkRecord-based verificationUser-owned onboarding
Case Study 03 · School ERP

01From Manual Data Entry to Self-Onboarding.

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.

My role

UX Design & Workflow Simplification

Users

School Admins, Parents & Staff

Platform

Web ERP & Mobile Web

The Problem

02Thousands of Contacts. One Administrator.

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.

1 student · Open profile

Locate the student and enter parent details.

40 students · Repeat for a section

Perform the same task for every student.

Entire school · Repeat at scale

Hundreds or thousands of manual entries.

Existing User Journey

03One Profile at a Time. For the Entire School.

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.

  1. 01

    Open Students

    Access the student management module

  2. 02

    Find a Student

    Search by name or admission number

  3. 03

    Open Profile

    Navigate to the individual student record

  4. 04

    Enter Parent Number

    Manually input the contact information

  5. 05

    Save Changes

    Update the student profile

  6. 06

    Repeat for All Students

    Continue until the school’s records are completed

Time Behind the Task

04Small Repetitive Tasks Become Hours of Work.

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.

Estimated manual entry effort

Illustrative estimate
Manual updates1,000Student profiles
Estimated admin time12 hr 30 minBefore self-onboarding

The calculation includes estimated time for finding, editing, and saving profiles. It excludes collecting contact numbers and correcting incorrect entries.

UX Audit

05The Workflow Didn’t Scale With the School.

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.

01

Individual profile updates

User impactRepetitive navigation and data entry

02

Admin-dependent parent registration

User impactParents couldn’t independently provide their own details

03

Manual mobile number collection

User impactAdditional coordination with families

04

Potential entry mistakes

User impactIncorrect numbers could affect account access

05

No scalable bulk invitation process

User impactWork increased with school size

06

Similar staff onboarding dependency

User impactMore administrative involvement

Design Strategy

06What If Administrators Didn’t Have to Onboard Everyone?

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.

Shift Ownership to the User

Allow parents and staff to provide their own contact information instead of relying on administrators.

Verify Against Existing Records

Use student and staff information already available in the ERP to identify the correct records.

Make Registration Easy to Distribute

Provide a school-specific link that administrators can share through familiar communication channels such as WhatsApp.

Design Improvement 01

07One Link. An Entire School Can Onboard.

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.

Generate Link

Administrator creates the school’s registration link.

Share via WhatsApp

The link reaches parents and staff through school groups.

Self-Register

Users open the link and complete registration.

Design Improvement 02

08Let Parents Connect Themselves to Their Child’s Profile.

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.

  1. 01

    Open Registration Link

    Parent opens the link shared by the school.

  2. 02

    Enter Student Details

    Parent provides the student’s admission number and date of birth.

  3. 03

    Match Student Record

    The system checks the details against the school’s existing student data.

  4. 04

    Enter Mobile Number

    Parent provides the number they want associated with their account.

  5. 05

    Create Login

    Parent completes account registration and gains access according to the school’s account setup.

Design Improvement 03

09The Same Self-Service Experience, Adapted for Staff.

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.

  1. 01

    Open School Registration Link

    Staff member accesses the school’s onboarding page.

  2. 02

    Enter Verification Details

    Provides date of birth and date of joining.

  3. 03

    Match Staff Record

    The system checks the details against existing staff information.

  4. 04

    Provide Contact Details

    Staff member enters their mobile number.

  5. 05

    Create Account

    Staff member completes registration without requiring manual account creation by the administrator.

Interactive Design Decisions

10One Entry Point. Two Personalized Journeys.

Both parents and staff begin with a school-specific link, but the verification experience adapts to the type of user registering.

Explore the Registration Experience

Step 1 of 5

Illustrative interaction · no personal data is stored or submitted.

9:41● ● ▰
Updated Onboarding Experience

11From Hundreds of Manual Updates to One Shared Link.

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.

  1. 01

    Generate School Link

    Admin creates the registration link

  2. 02

    Share Registration Link

    Distribute through WhatsApp groups

  3. 03

    Open Link

    Parent or staff opens the registration page

  4. 04

    Verify Existing Record

    Enter role-specific matching details

  5. 05

    Provide Mobile Number

    User enters their own contact number

  6. 06

    Create Login

    Account is connected to the matched record

Workflow Transformation

12From Admin-Dependent to Self-Service.

The redesign changed both the number of administrative interactions and who was responsible for completing them.

Parent mobile number entry

Before

Admin enters each number

After

Parent enters their own number

Student identification

Before

Admin searches student profiles

After

Parent verifies against existing records

Staff registration

Before

Admin involvement required

After

Staff completes self-registration

Registration distribution

Before

Individual coordination

After

One school-specific link

Administrative workload

Before

Increases with number of students

After

Focus shifts to link distribution and exceptions

Scalability

Before

Repetitive per-user work

After

Self-service registration across the school

Data ownership

Before

Admin inputs users’ contact information

After

Users provide their own details

Design Impact

13Less Administrative Work. More Independent Onboarding.

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.

Reduced Manual Effort

Administrators no longer need to enter individual parent numbers for every student.

Scalable Registration

A single school-specific link supports self-onboarding across many users.

User-Owned Information

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.
Key Learning

14Sometimes the Best Workflow Is the One You Remove.

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

Explore the case study

Jump to any section