The Student Attendence Management System is a web application for a school to keep one clear, daily record of who was in class. Teachers mark attendance for a class on a given date, correct mistakes in records they have already made, and review who was absent. Students check their own attendance history and absence totals so they can confirm the school recorded them correctly. School administrators set up the classes and student lists that attendance work depends on, and read attendance reports for a class or a date range.
The product is deliberately narrow: it is a register and a reporting surface, not a school management suite. Its audience is the three people who touch a register every day — the teacher at the front of the room, the student who wants to know their record is right, and the administrator who needs the school-wide picture.
The system is delivered as a first-party web application: a React front end, a shared FastAPI backend that owns all attendance APIs and domain logic, and a MariaDB database for application-owned persistent data. All three run as the provisioned services frontend, backend and database; the backend is a single process serving every domain module rather than one service per feature.
Access is application-owned. The public entry surface (Landing) and the identity surface (Login) are reachable anonymously; everything that touches a student's record is protected. Identity is established by self-service enrollment on Login and verified on return visits, because attendance records are durable, person-specific state: a teacher's marks must stay bound to the class and date they were made for, a student's history must stay bound to that student, and an administrator's setup must stay bound to the school's classes. The three roles see different working surfaces — Attendance for teachers, My Attendance for students, Reports and Classes for administrators — and that separation is part of the accepted access contract, not an optional convenience.
Nothing in this document is deferred: every requirement below is current. There is no provider-owned or external surface; the school's own deployment owns the data.
FR-1 — Record attendance for a class and date (explicit) As a Teacher, I should select a class and a date, see that class's roster, and set each student's status to Present, Late or Absent, so that the day's register is captured.
FR-2 — Correct or update an existing attendance record (explicit) As a Teacher, I should reopen a class and date that already has a saved register and change a student's status, so that mistakes are fixed.
FR-3 — Review absence for a class and date (explicit) As a Teacher, I should see which students are absent for the selected class and date, so that I can follow up.
FR-4 — View own attendance history and absence totals (explicit) As a Student, I should see my own attendance records and my absence total, so that I can check the school recorded me correctly.
FR-5 — View attendance reports for a class or date range (explicit) As a School administrator, I should run a report for a class or a date range and read per-student and per-date attendance, so that I can review the school's attendance.
FR-6 — Set up classes and student lists (required_inference) As a School administrator, I should create classes and add students to each class's roster, so that teachers have a roster to mark and students have a record to check.
FR-7 — Self-service enrollment (required_inference) As a Teacher, School administrator or Student, I should create my own account on Login by giving my name, email, password and role, so that I can reach the surfaces my role covers.
FR-8 — Verify identity before protected work (required_inference) As a Teacher, School administrator or Student, I should sign in with my email and password on Login, so that protected records are reachable only by the right person.
The teacher is at the front of the room at the start of a class, with a roster in front of them and a date that must be recorded before the next period. Their work is a single pass: pick the class, pick today's date, and mark each student. Most students are present, so the fastest path is to mark all present and then change the few who are late or absent. Their second job is correction: a mark made in haste is wrong, and they need to reopen the same class and date and change it without disturbing anything else. Their third job is follow-up: seeing who is absent today so the absence can be acted on.
The administrator owns the structure the register runs on. Before any teacher can mark a class, the class must exist and its students must be on the roster; the administrator creates both. Their second responsibility is oversight: reading attendance for a class or a date range to see patterns of absence and lateness across the school. They do not mark attendance themselves and do not edit a teacher's marks.
The student is the subject of the record and its most interested reader. They want to know that the school recorded them correctly — that a day they attended is not marked absent, and that their absence total is what they expect. Their work is read-only and personal: a strip of recent days, a list of dated entries, and a total. They cannot see any other student's record and cannot change their own.
The visual system follows the supplied creative direction: typographic infrastructure for the school day, after Erik Spiekermann — orderly, fast and trustworthy, like a transit system that never misses a stop.
Colour tokens (light mode)
| Role | Hex | Use |
|---|---|---|
| Background | #F4F1EA | Warm paper ground covering most of every page |
| Surface | #FFFFFF | Tables, roster rows, form fields |
| Text | #1C1B19 | Ink for all body and heading text |
| Primary | #D7261E | Signal red: Present status, primary actions, CTA bar |
| Accent | #F2B300 | Signal yellow: Late status, warnings |
| Absent rule | #1F7A4D | Green, used only as a thin rule and the A chip |
| Muted | #6E6A63 | Secondary text, unmarked day cells, legends |
Typography
clamp() so it never overflows its container at 375px, 768px or 1280px.Shape and layout
Imagery
Motion
The public entry is a transit map of the school day. A full-width band fills the hero: colour lines run left to right across it, each line a class, each station dot a date on that class's route. The band is drawn in flat vector strokes on the paper ground, with the line colours drawn from the status palette so the map reads as attendance itself — red for present, yellow for late, green as a thin rule for absent.
Below the band, flush left on #F4F1EA, sits the 96px Fira Sans Heavy headline "Every class. Every day. One clear record." Under it, the subline "Teachers mark attendance, students check their record, and administrators read the reports." Under that, the call to action is a solid signal-red bar — hard corners, no shadow — reading "Open the register".
The signature moves carry through the product: section titles sit on a numbered rail with a 2px rule above each title; attendance rows use the three-state chip (red P, yellow L, green A, each a letter and a small square); the student record is a horizontal strip of 30 day cells coloured by status, like a line diagram; and every value sits under a small-caps label with wide tracking. Nothing is rounded, nothing glows, nothing bounces.
Interaction Model: Static Motion Tempo: restrained Hero Dimensionality: flat
Landing Hero Motion Brief
prefers-reduced-motion, the band renders fully drawn in its final state with no line-draw animation; the headline, subline and CTA are unchanged and fully readable.prefers-reduced-motion, the hero renders in its final static arrangement and no decorative animation runs.frontend service.backend service, owning all attendance, class, roster, identity and report APIs as domain modules within that one process and port.database service, for application-owned persistent data.
Student attendance register
Teachers mark attendance, students check their record, and administrators read the reports.
Who rides the register
Mark the register for a class and date.
Check the 30-day record and the absence total.
Set up classes and read reports.
The daily rhythm

Student attendance register
Teachers mark attendance, students check their record, and administrators read the reports.
Who rides the register
Mark the register for a class and date.
Check the 30-day record and the absence total.
Set up classes and read reports.
The daily rhythm
No comments yet. Be the first!