Role
Designing a product to make the school admission process easier and more efficient, with enhanced functionality and a clearer experience for school administration.
Hurrey is an AI-enabled IoT-based SaaS product company providing equal learning opportunities through an interconnected classroom network. I focused on the school administration portal, with parents as the intermediary user.
Role
Primary user
Applications studied

School Admissions platform
School admissions typically last three to four months. The primary user is the school administration, while parents are the intermediary users.
My goal was to make the admission process easier and more efficient while improving functionality and user experience. I was the sole designer from start to finish.
Understood the product, scope and business case.
Understood technical limitations and aligned the final output with implementation.
Understood the data points needed and what could be surfaced to users.
Used different perspectives to challenge and improve design decisions.
Owned the product design from initial problem framing through the final experience.
I mapped the user journey to understand pain points, opportunities and emotions throughout the admission process.

User journey
I interviewed school staff and school principals to understand how the process actually works.
Newly commenced schools looking to establish and scale.
Schools ready to adopt digital workflows.
Affordable Private Schools that may have good infrastructure but struggle to scale.
I reviewed existing patterns across:
These platforms had similar functionality and higher average monthly traffic, but they focused on a limited set of branded schools or specific areas.
In a brainstorming session with the founder, developer and data scientist, we identified new features that could make the product stand out and provide useful business intelligence.
Helps schools estimate the number of students they can target in an area.
An approximate score based on the school's popularity in its area.
After creating an application form, schools receive a QR code to share it effortlessly.
After creating the task flow and user flow, I started approaching the problem statements and created initial wireframes to understand how each screen should work.

User flow
Onboarding had many questions to ask the end user, but the experience should not feel boring.

Onboarding experience
The dashboard shows applications received, shortlisted, rejected and application-fee payments. Because this is a content-heavy page with high cognitive load, information needed the right level of emphasis.

School administration dashboard
Schools can create class-wise application forms with an admission fee, opening date, closing date, extended date and allocated seats.
Physical forms required discussions with administration, creation of labels and fields, government requirements, hiring a typist, printing and issuing forms only to parents visiting the school.
I researched Google Forms, Typeform and Nopaperforms, then studied 20 different schools' online and offline applications. I created pre-built fields categorized into student, parent, previous school and document details.
Select commonly required fields instead of creating everything from scratch.
Add additional fields when the school needs something specific.
Generate a link or QR code after creating the form and share it with anyone.

Create application form
Schools can manage all applications received from parents, filter applications and accept, shortlist or reject an application after viewing the student application.

Manage applications
I also created the school profile page. With school details, the product can suggest potential areas and calculate the correct popularity score.

School profile