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

Parent & Staff Self-Onboarding.

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.

Project overview

Beta release
My role
UX Design & Workflow Simplification
Users
Administrators, Parents & Staff
Platform
Web ERP & Self-Service Registration
Design team
3 designersMe + 2 junior designers
Location
Tamil Nadu, India
Released
About the product

01One Platform. Multiple School Operations.

School ERP is a centralized platform designed to simplify academic, administrative, and financial operations. It brings timetables, attendance, examinations, fees, accounts, and school services into one connected system.

However, before schools could benefit from these features, they had to complete one essential task: onboard their student data.

What should have been a straightforward first step became one of the most frustrating experiences in the product.

School ERPConnected school operations
Module overview01 / 06
The Challenge

02Thousands of Contacts. One Administrator.

Student records were already available in the ERP through imported EMIS data. But enabling parent access still required an administrator to open each student’s profile, enter the parent’s mobile number, and save the changes.

Collecting contact details and repeating this update across hundreds or thousands of students created a growing administrative workload and opportunities for entry mistakes. Staff registration also depended on administrative involvement.

The challenge was to remove this per-user dependency: let parents and staff provide their own contact details and connect to existing school records through a simple self-service registration experience.

RepetitiveIndividual profile updates
Admin-dependentAccount onboarding
School-wideRegistration workload
A school administrator repeatedly enters parent contact details into individual student profiles.
UX AUDIT
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.

Read the workflow shown in this video

Existing parent contact entry workflow

  1. The administrator finds and opens a student profile.
  2. They enter the parent’s mobile number and save the student record.
  3. This profile-by-profile process must be repeated across the school; the calculator below illustrates the resulting effort.
Existing workflow · Adding a parent’s mobile number to an individual student profile.
  1. 🙂

    Open Students

    01

    Access the student management module

  2. 😐

    Open Profile

    03

    Navigate to the individual student record

  3. 😟

    Enter Parent Number

    04

    Manually input the contact information

  4. 😮‍💨

    Save Changes

    05

    Update the student profile

  5. 😩

    Repeat for All Students

    06

    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.

Audit Findings

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 IMPROVEMENTS
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.

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.

Share the registration link

The administrator generates a school-specific registration link or QR code to share with parents.

Read the workflow shown in this video

Parent self-onboarding workflow

  1. The parent opens the school link and provides the requested student information.
  2. The flow matches an existing student record and asks the parent to confirm their child’s profile.
  3. The parent supplies their mobile details and completes the account-linking steps.
  4. The interactive parent and staff journey below describes the sequence in more detail.

Parent self-onboarding

Parents identify their child, verify their mobile number, and link one or more children.

  1. 🙂

    Share & Open the Link

    01

    The school shares its registration link or QR code, and the parent opens it.

  2. 🤔

    Find the Student

    02

    The parent enters the child’s admission number and date of birth.

  3. 😊

    Confirm the Child

    03

    The parent reviews the matching student’s details and continues.

  4. 🔐

    Verify the Mobile Number

    04

    The parent enters a mobile number and verifies it using the OTP.

  5. 😌

    Link the Parent & Child

    05

    The verified number is connected to the existing student profile.

  6. 🤗

    Add a Child or Get the App

    06

    The parent can link another child or download the app to continue.

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. Open School Registration Link

    01

    Staff member accesses the school’s onboarding page.

  2. Enter Verification Details

    02

    Provides date of birth and date of joining.

  3. Match Staff Record

    03

    The system checks the details against existing staff information.

  4. Provide Contact Details

    04

    Staff member enters their mobile number.

  5. Create Account

    05

    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● ● ▰
Workflow Transformation

11From 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

Accessibility · WCAG 2.2

12Making Self-Onboarding Easier to Follow.

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.

SC 3.3.2Level A

Explain each requested input

Labels or Instructions

The flow separates student lookup, profile confirmation, and mobile verification instead of presenting one undifferentiated task.

Implementation check

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)
SC 2.4.6Level AA

Keep parent and staff journeys distinct

Headings and Labels

Separate parent and staff paths give each audience a clearer purpose and sequence of actions.

Implementation check

Verify that headings and action labels describe the relevant role and the step being completed.

Read W3C guidance (opens in a new tab)
SC 3.3.7Level A

Reuse information within the journey

Redundant Entry

Finding an existing student profile allows the parent to confirm that information rather than recreate the profile.

Implementation check

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)
SC 3.3.8Level AA

Make mobile verification usable

Accessible Authentication (Minimum)

The mobile-verification step is the point where accessible authentication needs explicit developer attention.

Implementation check

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.

Interactive prototypes

13Explore the School ERP prototypes.

Open the existing and redesigned School ERP prototypes in Figma. These shared links show the student-onboarding flows from the first case study.

Before · Existing flow

Experience the original workflow

Follow the previous upload and validation journey to understand where administrators lost context and had to recover manually.

Open existing prototype
After · Updated flow

Experience the redesigned workflow

Explore the revised onboarding experience designed around clearer guidance, recoverability and scalable error handling.

Open updated prototype

Explore the case study

Jump to any section