Absence reasons from SafeArrival can be written back to PowerSchool SIS only when there is a corresponding absence recorded in the student information system (SIS). To enable this feature, contact PowerSchool Support.
Partial-day write-backs are recommended only for PowerSchool SIS customers. Other student information systems may not correctly support the attendance mark time calculations required for partial-day absences.
Write-back requirements
Write-back occurs only when:
-
Write-Back is configured and enabled at the district, school, grade, or absence-code level.
-
Absence options in SafeArrival are mapped to corresponding PowerSchool attendance codes.
-
An absence has already been recorded in PowerSchool SIS. SafeArrival does not prepopulate absence codes in the SIS.
-
The reported SafeArrival absence matches the attendance information recorded in PowerSchool SIS.
Full-day and multi-day absences
When a guardian reports a full-day or multi-day absence and a corresponding absence is recorded in PowerSchool SIS, SafeArrival can write the configured attendance code back to the student's attendance record.
Partial-day absences
SafeArrival also supports write-back for the following partial-day absence types:
-
Late arrivals
-
Early departures
-
Leave and return absences
When a guardian reports a partial-day absence, SafeArrival compares the reported absence details with attendance information received from PowerSchool SIS before determining whether to write back an attendance code.
Late arrivals
For reported late arrivals, write-back behavior is determined by the district's configured absence notification settings:
-
Strict: Absences occurring after the reported arrival time are treated as new unexcused absences.
-
Loose: The reported late-arrival excuse continues to be applied to subsequent absences even if the student does not arrive.
-
Grace Period: A configurable grace period can allow absences shortly after the reported arrival time to receive the late-arrival excuse code.
The Loose setting can excuse additional absences without further guardian verification and should be used with caution.
Early departures
For reported early departures, SafeArrival compares the reported departure time with the attendance mark time.
-
If the student is marked absent before the reported departure time, the absence remains unexcused.
-
If the student is marked absent at or after the reported departure time, SafeArrival writes back the configured attendance code.
Early departures do not use Strict, Loose, or Grace Period settings.
Leave and return absences
For leave and return absences, SafeArrival compares attendance marks with the reported absence window.
-
If the absence occurs within the reported time range, SafeArrival writes back the configured attendance code.
-
If the absence occurs outside the reported time range, the absence remains unexcused.
Auto-Notifications
Partial-day write-backs work best when Auto-Notifications are enabled.
When an Auto-Notification schedule is configured,
-
SafeArrival regularly checks attendance data from PowerSchool SIS.
-
New unexplained absences can generate guardian notifications.
-
Guardians can explain absences that occur outside previously reported times.
Without Auto-Notifications:
-
New absences may remain unverified.
-
Guardians are not automatically notified of unexpected absences.
-
Schools may not be alerted when a student fails to arrive after a reported late arrival.
Recommended configuration
PowerSchool recommends:
-
Enabling Auto-Notifications throughout the school day.
-
Using partial-day write-backs together with Auto-Notifications.
-
Carefully evaluating the use of the Loose setting before enabling it.
-
Configuring an appropriate grace period when students frequently arrive shortly after their reported arrival time.