Why ClassSpark Attendance Is Tied to a Specific Lesson Period

A class can meet twice on the same day. A learner may attend the morning period and miss the afternoon one, while another arrives late only to the second lesson. A date-only register cannot represent those facts safely. ClassSpark therefore ties attendance to the exact scheduled occurrence identified by its scheduled class record, not merely to the class name and calendar date.

One period needs one attendance identity

The occurrence identifies the timetable slot, assigned class, organization-local date, and authorized staff context. Two slots for the same class remain separate even when they share a date. Teachers and assistants start from Today Schedule or select an existing occurrence in the ClassSpark header. The selector does not create a session. If no valid occurrence is available, Attendance sends the teacher back to Today Schedule instead of inventing an ad-hoc identity.

One period needs one attendance identity.

The register freezes the right roster

Opening the register loads the academic enrollment roster for that occurrence. Guests are excluded because they do not have an enrollment attendance identity. Before the first save, every learner begins as Unrecorded rather than being assumed Present. The teacher explicitly chooses Present, Late, or Absent for every student. Saving fails closed if the roster could not load, an enrollment identity is missing, or any learner is still Unrecorded.

The register freezes the right roster.

Corrections stay attached to the same period

A submitted register can be reopened by the scheduled teacher, assistant, or confirmed cover until the end of its organization-local date. Changing saved attendance requires a 3–500 character reason and creates a new immutable revision rather than rewriting history. If another authorized user changed the register first, a revision conflict keeps the local draft until Review latest loads the current server revision. Repeating identical content is a true no-op.

1. Open the exact card in Today Schedule.
2. Check the displayed lesson time and class.
3. Open Attendance for that occurrence.
4. Mark every enrolled learner explicitly.
5. Review the register before saving.
6. Use correction mode and a reason when facts change.

Period-specific safeguards

Period-specific identity prevents an afternoon absence from overwriting a morning presence. ClassSpark does not use biometrics or location tracking to decide attendance. The normal default is no-lesson mode, never an arbitrary timetable slot. Restored occurrence identifiers are validated before they are reused. The organization timezone determines the relevant teaching day. Historical ad-hoc rows remain readable but new ad-hoc attendance payloads are rejected. Late arrival time and student attendance notes are optional context. Correction reasons are separate from optional notes. Draft data is scoped to the user and occurrence in session storage. Saved revisions preserve who changed the register and when. Attendance remains usable for classes that are not session billed. One atomic save updates attendance and its related ledgers consistently. Period-specific identity prevents an afternoon absence from overwriting a morning presence. ClassSpark does not use biometrics or location tracking to decide attendance.

Why ClassSpark Attendance Is Tied to a Specific Lesson Period