Solutions · Timetable
A timetable-based attendance system
When attendance is created from a dropdown, lectures get logged twice, marked hours late, or filed under the wrong division. AttendMetric binds every session to a real timetable slot — so it can only be started on its scheduled day, once per date, with the roster already loaded.
What it removes
The problems that come from ad-hoc sessions
The same lecture logged twice for one date
A session maps to one timetable slot on one date. Once it has run, it can’t be started again for that date, whether by accident or on purpose.
Classes marked on holidays or off-semester
A class can’t be started on a holiday, outside its semester dates or on a weekday it isn’t scheduled. There is no “open a session whenever” path.
Wrong course or division picked from a list
There is no dropdown. The session comes from a timetable slot, with course, division, room and professor already set before anyone taps Start.
Students missing from the sheet entirely
Every student in that course and division is on the roster before the class starts, pulled from the same records the timetable is built on.
How it works
The schedule is the system
One source of truth
Departments, branches, courses, classrooms and the full weekly schedule are set up once by your IT-Admin, with bulk CSV import for students, professors and timetables.
Bound to a real room
Because the slot already names the classroom, check-in happens on that room’s actual seat layout, not a generic “present” for an unspecified space.
No sessions off the books
A professor can’t create a class that isn’t on the timetable. If it isn’t scheduled, it can’t be marked, which removes a whole category of disputed attendance.
Absentees marked on end
When the professor ends the class, students who never checked in are marked absent. Nothing is left open to backfill later, from memory or otherwise.
In practice
From schedule to closed session
IT-Admin builds the timetable once
Courses, divisions, rooms and weekly slots go in through the admin console or a CSV import, the schedule the whole institution already runs on.
The scheduled class becomes a live session
The professor taps Start on the scheduled slot for the day. The roster, room and course are already attached, so there is nothing to select.
Students check in, the professor ends class
Check-in is a seat tap on the room’s live map. When the professor ends the class, unmarked students are recorded absent automatically.
Questions
Timetable-based attendance, answered
What is a timetable-based attendance system?
One where every session is tied to a specific slot in the official timetable (a fixed course, division, room, professor and time) rather than created ad hoc. The schedule governs when a class can be marked and who is on the roster.
Can a professor take attendance for an extra class?
Attendance follows the timetable, so an extra or rescheduled class needs to exist as a slot first. The IT-Admin adds or adjusts it, and it then behaves like any other session, keeping every marked class traceable.
How does the roster get filled?
From the same student records the timetable is built on. Every student in that course and division is pre-loaded before the session starts, so no one is missing and no one is added who shouldn’t be there.
What happens to students who never check in?
When the professor ends the class, they’re marked absent automatically. There’s no unmarked state left over and no separate step to chase them, so the record is complete the moment the class ends.
Attendance that follows the schedule
One timetable, every session bound to it — scheduled day only, once per date, with the roster ready.