AC
BUILDING MACHINES THAT UNDERSTAND | TURNING DATA INTO DECISIONS | TEACHING SYSTEMS TO FIND THE SIGNAL | AI × DATA × CREATIVITY | FROM PROBLEM → SYSTEM → SOLUTION | CODE IS THE TOOL. THINKING IS THE ENGINE. | ENGINEERING INTELLIGENCE, NOT JUST SOFTWARE | WHERE LOGIC MEETS STORYTELLING | BUILD. BREAK. ITERATE. REPEAT. | CURIOUS BY DEFAULT. | ALWAYS BUILDING SOMETHING.
Back to Projects

Case Study

AttendanceIQ

A full-stack attendance management platform with OTP-based verification, session-aware validation, analytics dashboards, and CSV export workflows.

WEB APPSCompleted2026

Overview

AttendanceIQ streamlines classroom and lab attendance with class/session controls, OTP email verification, and reporting workflows.

Problem

Manual attendance processes are error-prone and make it difficult to enforce enrollment, prevent duplicates, and generate reliable reports.

Why It Matters

A validated attendance pipeline improves data integrity for academic operations while reducing administrative overhead.

Role

Built a full-stack platform across backend APIs, frontend dashboards, and attendance verification workflows.

Architecture

Layered architecture: React frontend -> FastAPI routers -> service layer -> repository layer -> Supabase PostgreSQL, with SMTP integration for OTP delivery and optional GitHub export integration.

Architecture Signal

  1. Student

  2. Class Session

  3. OTP Request

  4. OTP Verify

  5. Attendance Mark

  6. Analytics

  7. CSV Export

AttendanceIQ System Flow

Frontend, FastAPI layers, data persistence, and integrations used in OTP-based attendance operations.

Student/Admin UI
React Frontend
FastAPI Routers
Service Layer
Repository Layer
Supabase PostgreSQL
SMTP Email Server
GitHub Export

Stack

FastAPI, Supabase PostgreSQL, React, Vite, Tailwind CSS, Axios, Recharts, Framer Motion, JWT auth, SMTP

Implementation

Implemented class management, attendance session lifecycle handling, OTP request/verify endpoints, enrollment-aware checks, duplicate prevention per session, analytics views, and CSV export paths.

Engineering Decisions

  • Used a router -> service -> repository separation to keep business rules testable and scoped.
  • Modeled attendance with session-aware validation to enforce active-window and per-session constraints.
  • Applied OTP verification over email before attendance write operations to improve identity assurance.

Challenges

  • Maintaining strict validation across class open state, session status, enrollment, and duplicate limits.
  • Handling OTP expiry and delivery dependencies within the attendance flow.
  • Keeping attendance data exportable for downstream reporting needs.

Solutions

  • Introduced a deterministic request-otp -> verify-otp pipeline with guardrails at each stage.
  • Used session-scoped code validation and enrollment checks before OTP generation.
  • Added analytics matrix endpoints and CSV export workflows for operational reporting.

Results

Delivers an end-to-end attendance workflow from class open/close control through OTP-verified marking and report generation.

Evaluation

Validated via documented API workflows for attendance request/verification, session lifecycle handling, and analytics/export routes.

Metrics

Metrics

TODO

Add validated metrics when available.

Lessons

  • Session-aware constraints are essential for preventing duplicate and invalid attendance writes.
  • Clear layering improves maintainability for rule-heavy backend workflows.

Future Improvements

  • Expand operational observability for OTP delivery and verification failures.
  • Harden export automation paths for broader reporting integrations.