ClassTrack

ClassTrack monitors whether scheduled classes are conducted according to the approved routine, and manages what happens when they are not: late arrivals, missed classes, gaps in staff checking, makeup scheduling and online-class approval. It ingests the department's routine PDF, generates every class for the semester, gives office staff a fast checking interface, and produces teacher-wise and summary reports. I designed and built the system end to end — the FastAPI backend and its status engine, the Next.js dashboards for department heads, staff and teachers, routine ingestion, reporting and the Docker deployment.

1. 1Routine PDF ingestion with a review step before a routine goes live
2. 2Status engine that separates teacher absence from classes nobody checked
3. 3Staff checking, late-arrival tracking and missed-class follow-up
4. 4Makeup scheduling with room-conflict checks and online-class approval
5. 5Teacher-wise and summary reports by term, exported as PDF
6. 6Role-based dashboards for department heads, coordinators, staff and teachers

Reporting had to be fair to teachers. A class is only marked missed on positive evidence that the teacher was absent; a class nobody checked is a monitoring gap on the staff side, never the teacher's fault. Keeping six independent questions — conducted, late, checked, recovered, physical or online, approved — from collapsing into a single status shaped the status engine. Modelling the routine as a fixed 6 × 6 grid of days and slots turned conflict detection into indexed lookups instead of interval arithmetic.

Live at class.bitstreamhq.com. Version 1 covers every module in the requirements end to end, with all ten acceptance criteria verified and 25 automated tests passing.

• Next.js
• TypeScript
• Tailwind CSS
• FastAPI
• Python
• SQLAlchemy
• SQLite
• pdfplumber
• Docker