Fee Management System for Super Teacher

Overview

As part of our capstone project at 10kdesigners, we worked on a problem statement from Toppr for Super Teacher.

Super Teacher is a platform designed to help independent teachers running coaching centres manage their classes and day-to-day operations.

The challenge was to design a fee management system that would help teachers set up fees, track payments, mark students as paid, and send reminders without adding unnecessary complexity to their existing workflows.

The Challenge

Managing fees is more than just collecting payments.

Teachers need to set different fee structures for different batches, keep track of individual student payments, follow up on overdue fees, and occasionally handle situations such as refunds or fee waivers.

The goal was to create a system that made these frequent actions easy to access while still supporting the different ways teachers manage their batches.

The problem statement focused on three core needs:

Setting up fees for new or existing batches Getting a clear overview of fee collection Making frequent actions like marking students paid and sending reminders easy to access

Design Process

1. User Research
2. Competitive Analysis
3. Workflow Mapping
4. Information Architecture
5. Wireframing
6. Visual Design
7. Prototype testing

Understanding the Problem

We started by understanding how independent teachers currently manage fees and what they needed from a digital system. We brainstormed and structured our interview questions in FigJam, then spoke with teachers running coaching centres and tuition classes.

We also looked at existing fee management solutions to understand how they approached fee creation, payment tracking, dashboards, and frequent actions. The research helped us identify that the system needed to support both batch-level setup and individual student-level actions without making either workflow difficult to navigate.

Mapping the Workflows

We broke the experience into smaller tasks and mapped how they connected. The flow covered: Creating a batch → Setting up fees → Tracking payments → Marking students paid → Sending reminders We also considered less frequent edge cases such as refunds, fee waivers, and restricting students when fees remain unpaid. The flow went through multiple iterations as we explored the different ways these actions could fit together.

Designing the System

The main idea was to make fee management a dedicated part of the teacher's workflow rather than another isolated feature.

The system brought together: A dashboard for an overview of fee collection Flexible fee structure setup for new and existing batches Payment status at the student level Quick actions for marking students as paid Reminder actions for overdue fees Controls for less frequent cases such as refunds and fee restrictions

The design also explored ways to manage fees across multiple students and batches without forcing teachers to repeat the same actions individually.

From Wireframes to Prototype

We started with low-fidelity wireframes to work through the different flows before moving into visual design. The early flows were reviewed by the Toppr design team, which helped us question some of our assumptions and refine the experience.

After several iterations, we created a high-fidelity prototype covering the key fee management workflows.

Testing the Flows

We tested the prototype with one of the teachers we had interviewed earlier. The session focused on realistic tasks: Create a new batch and set up its fee structure Add bank details Send a manual reminder to a student Restrict access for a student Issue a refund

Watching someone work through these flows helped us identify where the experience needed more clarity and led to another round of iterations.

Outcome

The final concept brought the key fee management workflows into one structured experience, from setting up fees to tracking payments and following up with students.

More importantly, the project helped us move beyond designing individual screens and think about how a system should support frequent actions, edge cases, and different levels of information within the same workflow.

What I learned

Design gets better through iteration Our first flow was not our final flow. As we moved from research to wireframes, reviews, and testing, several decisions changed. The project reinforced that a good solution often comes from repeatedly questioning and refining the first idea.

Research changes what you design Talking to teachers made the problem more concrete. Instead of designing a generic payment dashboard, we had to account for the actual situations teachers deal with when managing multiple batches and students.

Systems thinking matters Fee management is a collection of connected workflows rather than a single feature. Thinking about setup, tracking, reminders, payments, and edge cases together helped us design a more coherent experience rather than a collection of individual screens.