Case study EduFlask
eduflask.comDesigning a Unified Education ERP from Multi-Role Complexity to Daily Clarity
A case study covering research-led strategy, Role-Based Access Control, Analytics & Reports systems, Fee management, Geofencing attendance, and a single mobile app with OTP authentication.
Context
Context & Opportunity
Indian schools and colleges still run on fragmented tools spreadsheets for fees, WhatsApp for announcements, paper registers for attendance, and multiple logins for different stakeholders. The result is data silos, delayed decisions, frustrated parents, and administrative overhead that pulls leadership away from academic outcomes.
EduFlask set out to become the all-in-one school & college management platform: attendance with geofencing, integrated HRMS, flexible fee plans, automated timetable generation, analytics dashboards, report automation, and real-time parent communication delivered through a single coherent product.
The Challenge
The Strategic Challenge
Education ERPs fail when they treat every user the same. EduFlask had four primary audiences with conflicting needs, literacy levels, and usage frequency:
Administrators / Principals
Need oversight, fee collection health, staff compliance, and institutional analytics. They want power without cognitive overload.
Teachers
Need sub-20-second attendance marking, clear timetables, and homework tools often while standing in a classroom between periods.
Parents
Need transparency on fees, attendance, and school updates. Many have limited digital literacy and already live inside WhatsApp.
Students
Limited self-service for timetable, assignments, and results.
The core design problem was not feature volume. It was coherence: how to create one product that feels simple and role-appropriate for each user while enforcing secure Role-Based Access Control, supporting modular activation, and driving daily engagement on mobile.
Research
Research Approach & Synthesis
I owned the end-to-end research program. Methods were chosen for speed and decision quality rather than academic completeness:
- Stakeholder interviews (n=14) School owners, principals, admin staff, and class teachers across CBSE, state-board, and private institutions. Focused on actual daily workflows and points of abandonment.
- Contextual observation Shadowed attendance marking during class transitions and fee collection cycles at two partner schools.
- Competitive teardown Analyzed 8 Indian and global school ERPs for navigation patterns, fee plan presentation, attendance flows, and mobile depth.
- Support ticket & WhatsApp analysis Reviewed recurring parent and teacher queries to surface friction that never appears in feature request lists.
- AI-assisted synthesis Used LLM tools to cluster interview transcripts, surface recurring language patterns, and generate early job stories. Human judgment remained final.
Key insights that directly shaped product strategy
Parents do not “log in”
Parents respond to WhatsApp and push notifications. Complex portals are abandoned. The mobile app had to feel as light and glanceable as a messaging thread, not a desktop dashboard shrunk to phone size.
Teachers have a 15–20 second window
Any attendance flow longer than that window was abandoned or completed after class with lower accuracy. Speed and bulk actions were non-negotiable.
Fee plans create silent distrust
Yearly / half-yearly / quarterly / monthly options, when poorly visualized, generated the majority of support tickets. Transparency of what is due, paid, and upcoming reduced friction more than any discount mechanism.
Geofencing is only as good as its edge cases
Multi-building campuses, temporary network loss, and staff who legitimately move between zones required clear feedback and fair override paths. Otherwise the feature becomes a source of disputes rather than trust.
Instant setup is a myth without progressive disclosure
Non-technical admins abandoned pure self-serve onboarding. Guided, modular activation that delivered value in the first 15 minutes was essential.
Success Metrics
Defining Product Success
Instead of a generic goal list, success was framed as measurable shifts in real behavior:
Reduce average attendance marking time to under 20 seconds per class.
Make the mobile app a daily habit, not a once-a-month fee portal.
Cut fee-related support queries by making status, plans, and receipts immediately understandable.
Surface institutional health (attendance, fees, staff) on a single Analytics dashboard so principals act instead of compile.
Enforce RBAC so each role only sees what it needs, while keeping navigation feel natural rather than bureaucratic.
New schools should reach first meaningful use (students + attendance + fees live) in under 15 minutes of guided setup.
Design Strategy
Four principles. Every major decision had to survive them.
Written before the first wireframe. Navigation, surface, trust, and growth each had a rule — and a screen only shipped if it could live with all four.
Role-first, not module-first
Navigation and home screens are determined by who is logged in, not by a flat list of features.
Mobile as primary surface for high-frequency users
Teachers and parents live on phones. The single mobile app is not a secondary view of the web product.
Transparency builds more trust than features
Especially true for money (fees) and location (geofencing). Showing due, paid, and next — or why a punch was rejected — earned more confidence than adding another module.
Progressive complexity
Show value early; unlock depth only when the institution is ready. Matches modular pricing and multi-campus growth.
Final Product Design
Solution Architecture Key Systems
01 Access
Role-Based Access Control & Navigation Architecture
I designed the RBAC model and the corresponding information architecture so that access control felt invisible rather than restrictive. Upon OTP-based login, the system resolves the user’s primary role and surfaces a role-specific home:
Insight dashboard with fee collection health, attendance overview, staff status, and pending actions.
Today’s classes, one-tap attendance entry, homework queue, and leave status.
“My Child” overview: fee status, today’s attendance, pending homework, and recent school notices.
Timetable, assignments, and results.
Deep configuration and multi-module controls remain primarily on web. Mobile surfaces only the high-frequency, high-urgency tasks for each role. This prevented the classic ERP failure mode of a dense left sidebar that overwhelms non-admin users.
02 Insight
Analytics Dashboard & Reports System
School leaders were previously compiling reports from multiple spreadsheets and WhatsApp groups. I designed two complementary surfaces:
- Analytics Dashboard (Admin home) Real-time institutional pulse: attendance trends, fee collection rate, pending dues, staff geofence compliance, and at-risk students. Designed for glanceable decision-making rather than data exploration.
- Reports Engine Automated generation of attendance reports, grade reports, fee statements, and compliance certificates. Admins can schedule, filter by class/section/date range, and export. Reduced the weekly reporting burden from hours to minutes.
The design prioritised progressive disclosure: high-level KPIs first, with the ability to drill into class or student level without leaving the decision context. Color and hierarchy were used to surface exceptions (low attendance, overdue fees) rather than requiring the user to hunt for them.
03 Trust
Fee Management Experience
Fee management was redesigned end-to-end around transparency. Admins configure flexible payment plans (yearly, half-yearly, quarterly, monthly) with clear installment structures. Parents see a single, unambiguous view of:
- What is currently due
- What has already been paid
- Upcoming installments and total remaining
- One-tap payment with automatic receipt generation
On the admin side, fee analytics surface collection trends, pending dues by class, and students at risk of default enabling proactive outreach instead of reactive chasing. This system directly addressed the insight that poorly visualized plans were the largest source of support tickets.
04 Fairness
Geofencing-Enabled Attendance & HRMS
Staff attendance combined traditional marking with smart geofencing. I designed the full flow:
- Campus zone definition (search location, set radius, multi-building support)
- Location-verified check-in with clear success / failure states
- Fair handling of edge cases (network loss, temporary zone exit, multi-campus staff)
- Admin visibility into compliance without turning the feature into a surveillance tool
The UX priority was clarity and fairness. Staff needed to understand why a check-in was accepted or flagged. Without that transparency, geofencing creates disputes rather than trust. The system integrates with the broader HRMS (leaves, departments, shifts, payroll inputs).
05 Daily Surface
Single Mobile App with OTP Login
A deliberate product decision: one mobile application for all roles rather than separate parent and teacher apps. This reduced maintenance, simplified branding, and allowed role switching for users who wear multiple hats (e.g. a teacher who is also a parent).
Authentication uses OTP login removing password friction for parents and teachers who rarely remember credentials. After OTP verification, the app resolves role and lands the user on the appropriate home screen.
Impact
Validation, Outcomes & Impact
Exact live metrics remain confidential. Directional outcomes from usability testing and early rollout:
Faster attendance marking (teachers)
Reduction in fee-related support queries
Parent app daily active engagement
Time-to-value for new school setup
Usability testing showed strong preference for role-specific home screens over generic module lists. Parents particularly valued fee status clarity and the WhatsApp-integrated notification model. Teachers consistently completed attendance within the target window once bulk actions and clear class context were introduced.
Admin users reported that the Analytics dashboard reduced the need to assemble weekly reports manually. The Reports engine further compressed recurring compliance and parent communication tasks.
Key Learnings
Leadership Reflections
This project reinforced several principles I now carry into every multi-stakeholder system:
Design for the least powerful frequent user first.
Optimizing only for the admin power user produces low adoption. Parents and teachers on mobile determine whether the product becomes daily infrastructure or shelfware.
Transparency outperforms features in trust-sensitive domains.
Clear fee plans and geofencing feedback reduced friction more effectively than additional capabilities.
RBAC should feel natural, not bureaucratic.
When role resolution is done well, users never feel restricted they simply see a product that makes sense for them.
AI is a force multiplier for research synthesis, not a replacement for judgment.
The highest leverage came from compressing the path from raw transcripts to testable insights while keeping human accountability for strategy.
Modular products require progressive disclosure in both UX and onboarding.
Show value early; unlock depth later. This aligns product experience with commercial packaging.
Closing
Closing
EduFlask was a high-stakes opportunity to apply modern product design thinking inside the education ERP space balancing institutional complexity with the simplicity that teachers and parents actually need every day.
By grounding decisions in primary research, treating the single mobile app as a first-class surface, enforcing coherent RBAC, and designing Analytics and Fee experiences for clarity rather than completeness, we created a platform that feels both powerful and approachable.
The best education technology does not merely digitize existing processes. It reduces cognitive and administrative load so educators can focus on teaching and parents can stay meaningfully connected to their child’s school life.
End of case study
Want to discuss this project?
Happy to go deeper on the RBAC model, the fee transparency system, or the geofencing edge cases and how they were resolved.
Connect with me