Attendance: mark, save & export

Attendance is recorded for the relevant batch/class, subject and date shown by the page. These selections identify the population and the session you are editing. Confirm them before changing any student's status.

Admin can manage organization attendance. Teacher updates require the allowed attendance access, including the custom grant where applicable, and are still scoped to permitted work. Students do not receive the organization marking screen; they review their attendance through their own academic reports.

A new attendance session starts unmarked: students must not be assumed Present. Choose each available status deliberately. Present, Absent, Late and Leave represent different outcomes; use the options appropriate to the actual session.

Loading an existing saved session can show recorded statuses. Clearing or changing one is a real attendance correction, not a filter operation. Review any bulk action carefully and distinguish an unmarked record from an explicit absence.

The attendance Save action persists the marked session. Wait for the result before navigating away, then reopen the same date/context if you need to verify it. A visible local selection is not proof that a save reached the server.

If an update fails, preserve the intended context and read the error before retrying. Permissions or enrollment can change while a page is open. Avoid marking a different subject just because it happens to load successfully.

Use the export controls to choose the available Day PDF, Week PDF or Month PDF range and the relevant academic context. The report should reflect the requested students and dates; an unmarked session is different from a fully absent class.

If a PDF is empty, first confirm the chosen class/batch, subject, report range and student enrollment. A successful download with no rows does not by itself mean that the organization has no attendance. Students linked through the current enrollment relationships must be included by the report logic.