Sort By

Sort by either:

• Date, with the oldest date and time first
• Alphabetically, in ascending order.

For example, you might sort records alphabetically to group together absence events for a student that has missed several periods but which can be explained by them having been in the sick bay.

Filter

Filter the absence events further based on whether they are:

• unexplained
• unexplained with possible sickbay or co-curricular reasons
• confirmed
• expected out/in absence events.

  

The Unexplained Absence Events filters are useful to the administration person working through the students with unexplained absences. As each is explained, the list gets smaller.

Count

The number of absence events records for the selected criteria.

Comment

Type in a comment to apply to the highlighted records.

Out Time

The out date and time for the absence event, if relevant (see In/Out below):

• The date is derived from the Absent Date field when creating an absence event.
• The time is derived from the time that the event is recorded for. For example, some organisations record attendance in the morning and the afternoon only. If the Period field is selected, when creating an absence event, the start time of the period is used.

The Out Time is blank when it is not available, such as for Expected In absence events.

In Time

The in date and time for the absence event, if relevant (see In/Out below).

For example, for an Excursion Out and In absence event, the:

• date is derived from the Excursion In Date field
• time is derived from the corresponding Time field.

Per

Period of the absence, if available.

Period 0 is either the:

• home group period
• all day absence
• AM absence, if the roll is marked twice a day at your organisation
• PM absence, if the roll is marked twice a day at your organisation.

Refer to the luAbsencePeriod lookup table. See luAbsencePeriod lookup table in the System maintenance manual.

Name

Student's name. The name is formatted as:

<Last name>,<Preferred first name> (<campus><year level>).

Type

The type of absence for the absence event. For example, school camp.

Absence types are defined in the luAbsenceType lookup table.

Note: New Zealand schools use the absence codes required by the New Zealand Board of Studies. See Attendance and absence codes for New Zealand schools.

AE Type

The type of absence event or mode. For example, absence slips.

In/Out

If available, whether an absence event is either a student:

• expected out (out)
• out (out)
• returning (in)
• arriving late (in)
• whose absence is unexplained (blank)
• who we entered a slip or auto slip for (blank).

Contact Phone

Home phone number for the primary contact (SC1 contact), as specified on the Contacts tab for the student. See Current Student Maintenance - Contacts tab in the Current students manual.

Contact Name

Person who is the primary contact for the student (SC1 contact), as specified on the Contacts tab for the student. See Current Student Maintenance - Contacts tab in the Current students manual.

Reason

Reason code given for the absence, if available.

See the Reason field in the Modify Absence Event window.

Comment

Any extra comments entered about the absence in the Modify Absence Event window.

ID

Synergetic ID of the student.

Seq

Unique order number assigned to the absence event.

Notification status

Status of the absence event notification when

• event first created: blank
• queued for processing: "{Email/SMS} to {email address} queued for sending"
• sent: "{Email/SMS} to {email address} queued send {date time}.

Refresh the absence events displayed.

Launch into Current Student Maintenance for the selected student.

See Maintaining current students in the Current students manual.

Launch the Create Absence Event window to add a new absence event. Depending on the mode, see:

• Recording absence slips
• Recording late sign ins
• Recording a student signing in manually
• Recording a student signing out manually
• Recording a student's expected arrival
• Recording a student's expected departure
• Recording a student's expected departure and return
• Recording all day absences
• Recording excursions
• Recording a student signing in automatically
• Recording a student signing out automatically
• Recording student movements using default absence type codes.

Modify an existing absence event.

If the existing absence event is an Absence slip, you can change its mode to either:

• Expected in, when the parent or guardian is contacted and they confirm that the student is attending later in the day.
• All day absence, when the parent or guardian is contacted and they confirm that the student is away all day.

In all other cases, either:

• Modify the details of the existing entry.
• Add a second absence event and supersede the current absence event. See Superseding unknown absence events.

  Note: Custom icons are now displayed on the Modify Absence Events window. See Maintaining custom maintenance window icons.

Delete an existing absence event.

This button is only displayed if the configuration setting is set to True. See the AbsenceEvents:ShowDeleteButtonFlag configuration setting in the System maintenance manual.

Button

Description

Opens the Attendance Details window detailing the attendance details for the class missed by the currently selected student.

Select the entry and click to launch the Attendance window. See Attendance window.

Tip: Double click the entry to open it quickly.

Change the criteria used to display. See Searching for absence events.

Exit from the window.