Overview of the Absences module

The Absence management module centralizes the declaration and tracking of unavailability that must change how timetables are displayed: teachers, classes, students and, if the Staffing module is enabled, staff members.

Managed entities

The year's school holidays are not entered as absences: they are managed in the school year.

Supporting documents

The module does not handle document upload: timetable management is not meant to store sensitive data (medical certificates, confidential information), it focuses on planning. If you still need to attach a document, store it in your usual storage space and paste the link in the comment field of the absence.

Statuses

• accepted: the absence is validated and reflected in the displays.
• pending: request declared by the user concerned, to be validated by an administrator.
• rejected: rejected request.
• aborted: request canceled by its requester.

Only absences with the accepted status have an effect: they change how timetables are displayed, mark the affected lessons (canceled where applicable) and feed the absence statistics and exports (see Tracking and exporting absences). The other statuses — pending, rejected, aborted — have no effect on the timetable.

Screen layout

The module offers one tab per entity type:

• Teachers: teacher absences and substitution management.
• Classes: class absences, managed by administrators.
• Students: individual student absences.
• Staff: staff absences, if the Staffing module is enabled.

Each screen shows the absences of the period, their status, the affected lessons when the information is available, time navigation and an exportable list for administrators.

Prerequisites

• At least one timetable published for the school year concerned.
• For teacher absences: teachers must be assigned to courses.
• For student absences: students must be assigned to classes.
• For staff absences: the Staffing module must be active.