Product
Teachers don't fill in the list from scratch; they only correct the differences
Gate records pre-fill attendance; the teacher simply confirms it and corrects any differences. This page sets out what happens automatically and what never does.
Every row shows its source
Every row shows where its data came from. If anyone asks why a row looks the way it does, the answer is in the row itself.
- Gate: it came from the reader at the gate.
- Teacher: the teacher marked it in class.
- Manual: the school office corrected it later.
- Import: the record came from a file.
Period-level attendance
Day-level attendance shows whether a student was at school that day; period-level attendance shows which lessons they missed. Both are kept, and any conflict between them is flagged on screen.
Partial absence
A student can be excused for part of the day, for example two lessons for a dentist appointment before returning. The row shows when they are due back.
Calculating lateness
Lateness is calculated to the minute, not estimated. The three lists are kept separate and never mixed.
- Late: came through the gate after the lesson started.
- Left early: exited before the end of the day.
- Absent: no gate record at all that day.
Approved bulk entry preparation
Entering data into the official system is a job for a person, and it will stay that way. Our job is to prepare that entry, flag errors in advance and record who entered what, and when.
- When attendance closes, the records go into the queue.
- Each record appears in the panel and can be corrected.
- The user presses “Prepare” and a package is created.
- A staff member enters the records into the official system.
- The package is marked as “entered”; who marked it and the number of rows are written to the ledger.
The queue holds only that day's absence rows; unconfirmed rows are never added to the package.
When a row is corrected, the old value is kept; who corrected it and when is shown under the row.
It creates the package and locks the rows confirmed up to that point; any later changes go into the next package.
The institution's own staff. None of our components connect to the official system.
The declaration is not just a checkbox; it is a record: who, when, how many rows. A package without a declaration stays open.
The two buttons above have the same names as in the product panel; here they are shown for illustration only.
What we don't do
Early warning from absence patterns
Warnings are built from the absence records already kept: repeated absence from the same lesson on the same weekday, consecutive late arrivals, or absences concentrated on one day of the week. No separate count is made and students are not given a score.
Substitute teachers
A substitute teacher can take attendance in place of the regular teacher. The row shows both the lesson's teacher and the person who took attendance, so the record trail is kept.