Correct Attendance While Keeping a Visible Change History

Attendance sometimes needs to change after it has been saved. A learner marked Absent may arrive late, a status may have been tapped incorrectly, or a note may need clarification. A dependable register should allow the correction without making the first record disappear. ClassSpark keeps the change visible by attaching it to the same scheduled lesson occurrence and adding a new revision.

Reopen the exact saved register

The scheduled teacher, assigned assistant, or confirmed cover can reopen that occurrence through 23:59 on the organization’s local date. Another teacher who is merely linked to the class sees it read-only. Because the register belongs to an exact timetable occurrence, a correction to an afternoon period cannot alter the morning period. Opening a submitted register enters correction mode and keeps the complete enrolled roster in view.

See how ClassSpark supports a live lesson.

Explain the change before saving

As soon as a saved status changes, ClassSpark requires a correction reason between 3 and 500 characters. The reason is separate from an optional late-arrival time or student note. A visible “Reason required” control and inline field make the requirement hard to miss. A saved Absent card cycles directly through Present, Late, and Absent, so the teacher can reach the intended corrected state without passing through Unrecorded and blocking the whole register.

1. Reopen Attendance for the correct scheduled lesson.
2. Change only the student states or details that need correction.
3. Review the impact summary for the pending changes.
4. Enter a concise reason for changing the saved register.
5. Save and confirm the new revision in History.

Explore classroom management workflows.

The earlier record stays visible

Once a register has a saved revision, a History control appears inside attendance mode. It opens the same immutable attendance revision log used by the school office. Entries show who took or changed the register, the timestamp, the stored reason, and each student’s before-to-after status. If only a note, arrival time, or excuse changed, the history says that details were updated. Larger changes can expand beyond the initial summary. Teachers and administrators therefore see the same story rather than separate versions.

Revision conflicts protect newer work

Draft statuses, notes, reason, and base revision survive refresh or navigation for that user and occurrence. If another authorized person saves first, a revision conflict keeps the local draft instead of overwriting the server. “Review latest” loads the current revision so the teacher can compare and decide what still needs changing. A repeated submission with identical content is a true no-op.

ClassSpark does not use biometrics, device location, or automatic detection to decide attendance. The teacher remains responsible for every status and correction. One complete-register request updates the attendance record and its related revision history consistently. The result is a practical correction workflow: fix the fact, state why it changed, preserve what came before, and keep a visible trail for later review.

The reason belongs to the register correction, not to a single attendance label. An unchanged student remains part of the complete saved roster without creating a false change. The history refreshes after every successful save. The log is fetched only while attendance mode is open. Draft data is cleared after a successful save or when the browser session ends. Shared devices therefore do not retain student notes indefinitely. An identical correction does not create another revision. The visible trail supports later questions without rewriting the past.

Try KiwiBee for your next class