Coaching Class Attendance and Fee Reminder Android App

A coaching class attendance and fee reminder Android app is a single phone-based system that replaces two paper records a coaching class owner keeps by hand: the daily attendance register and the fee diary. The teacher opens the app, picks a batch, and marks each student present or absent for that session, while the app keeps a separate fee record for every student showing what is paid, what is due, and how many days overdue it is. When a fee crosses its due date, the teacher sends a parent reminder from the fee screen, and the app logs the reminder with its time, student name, and message text so the owner can see exactly who was reminded and when. A dashboard pulls both sides together, showing today's attendance percentage, this month's collection, and the total amount overdue, so one screen answers both daily questions: who came today, and who still owes fees.

End to end, the app moves in a short loop that repeats every class day and every fee cycle. The class owner first sets up batches and adds students to them, with each student's monthly fee recorded once. On a class day, the teacher opens that day's batch, taps Present or Absent beside each name, and saves the session, which updates the batch's attendance percentage and the student's personal attendance history at the same time. Separately, the fee screen watches due dates: when a student's fee passes its due date, that student appears on the batch-wise due list with the amount and days overdue. The teacher picks the student, sends an SMS-style reminder to the parent, and the reminder log stores the time and message text. When the parent pays, the teacher marks the fee paid, the student leaves the due list, and the next reminder round skips them automatically.

1. The class owner creates a batch for each subject and class, then adds that batch's students with their monthly fee recorded once.
2. On a class day, the teacher opens that day's batch and taps Present or Absent beside each student's name on the register screen.
3. The teacher saves the session, which updates the batch's attendance percentage and each student's personal attendance history at the same time.
4. The fee screen watches due dates and lists every student past the due date, batch by batch, sorted by days overdue with the amount beside each name.
5. The teacher picks a student and sends an SMS-style reminder to the parent naming the amount and batch, and the reminder log records the time, student, and message text.
6. When the parent pays, the teacher marks the fee paid in the app, the student leaves the due list at once, and the next reminder round skips that student automatically.

Tech stack:

• Android app in Kotlin · batch attendance and fee screens
• Android Studio · app build and testing environment
• Room local database · batches students attendance and fee records on the device
• RecyclerView lists · batch student and due-list screens
• SMS-style reminder sending · parent reminders from the fee screen
• Material Design components · buttons cards and navigation
• Date and due-date logic · overdue calculation and reminder timing
• Demo web build · browser screens showing the app's flows

The app's three strongest capabilities are the ones a coaching class owner uses every day: batch-wise attendance marking, a batch-wise fee due list, and parent reminders with a log. Attendance marking works batch by batch, so a teacher teaching three batches never mixes their registers, and the session summary counts present, absent, and not-marked students live as each name is tapped. The fee due list turns the fee diary into a working list: it shows only students who still owe money, sorted by how long overdue they are, with the amount and batch beside each name. The reminder step closes the loop: one tap sends an SMS-style reminder to the parent, and the reminder log records the time, student, and message text, so the owner never has to remember who was already reminded.

• [Batch-wise attendance marking] The teacher picks a batch and taps Present or Absent beside each student's name for that session, so each batch keeps its own register and no batch's attendance mixes with another's. Implemented in the base app.
• [Live session summary] Present, absent, and not-marked counts update on every tap, so an unmarked student is visible before the session is saved. Implemented in the base app.
• [Batch-wise fee due list] Students who still owe money appear batch by batch with the amount and days overdue, sorted longest-overdue first, so the teacher works through the most urgent cases first. Implemented in the base app.
• [Parent reminders with a log] One tap sends an SMS-style reminder naming the amount and batch, and the reminder log records the time, student, and message text for every reminder sent. Implemented in the base app.
• [Dashboard] Today's attendance percentage, this month's collection, and the total overdue amount sit on one screen, with per-batch attendance and a weekly timetable below. Implemented in the base app.
• [Student and batch records] The owner creates batches, adds students with their monthly fee once, and edits records when a student joins or leaves, so the registers always match the real class. Implemented in the base app.
• [WhatsApp-style reminder channel] Reminders go out over a chat channel instead of SMS-style messages, for parents who respond faster there. Optional extension, not in the base app: it needs a messaging provider account.

• Working demo of the app's three screens: dashboard with attendance and collection totals, batch attendance marking with a live session summary, and the fee due list with a reminder log
• Android app source code for batches, students, attendance marking, fee records, and reminders, with a local database for on-device records
• Demonstration procedure, including marking a batch's attendance, saving a session, sending a reminder from the due list, and marking a fee paid so the student leaves the list
• Screens and data-model documentation covering the batch, student, attendance, fee, and reminder-log records and how the reminder flow moves between them
• Builder note from the demo build: the attendance screen keeps a live present, absent, and not-marked count that updates on every tap, so a teacher spots an unmarked student before saving — the demo's Batch A register opens at 5 present, 1 absent, and 2 not marked
• Project report PDF (background, attendance and fee workflows, data model, methodology, limitations)
• PPT presentation for final review
• Viva Q&A preparation document (batch data model, due-date logic, reminder flow, demo-vs-live SMS boundary)