Student Attendance &
Parent Notifications.

01When One Wrong Tap Causes Panic.

A student marked absent by mistake could trigger an immediate notification to their parents, creating unnecessary anxiety and urgent calls to the school. I redesigned the mobile attendance workflow to introduce verification before absence notifications were sent, giving teachers greater control while improving the reliability of school-parent communication.

02A Small Input Error. A Big Emotional Consequence.

Teachers recorded daily attendance using a mobile interface. Once attendance was submitted, parents of students marked absent could receive notifications immediately. However, an accidental tap could mark a present student as absent. Because the notification was sent without an additional verification step, parents received incorrect information before the teacher had an opportunity to correct it.

03From Attendance Submission to Parent Panic.

The original workflow prioritized speed. Teachers could mark attendance and submit it quickly, but the process lacked safeguards against accidental absence markings.

1. 01🙂

   Open Attendance

   Teacher opens the class list

2. 02😐

   Mark Students

   Selects present and absent

3. 03😶

   Submit

   Attendance is saved

4. 04😟

   Notify Parents

   Absence alert sent immediately

5. 05😰

   Parent Calls

   School receives a concerned call

04The Problem Wasn’t Just an Accidental Tap.

I examined the relationship between attendance entry, absence verification, and notification delivery. The audit revealed that the workflow lacked checkpoints between a potentially incorrect attendance selection and a high-impact message to parents.

Priorities are suggested for this case study, rather than documented backlog classifications.

05Adding Friction Where Accuracy Matters.

Instead of adding more steps to the entire attendance process, I focused on introducing deliberate checks at the moments where mistakes could affect parents. The goal was to preserve fast daily attendance entry while requiring additional confidence before absence information was communicated.

06Four Safeguards Before an Absence Alert.

I introduced four connected improvements to make attendance recording more reliable. Each addressed a different point of failure, from knowing about planned leave to verifying unexpected absences and controlling when notifications reach parents.

07From One-Tap Submission to Verified Communication.

Explore how each improvement changes the attendance experience for teachers and parents, adding safeguards without unnecessarily complicating routine attendance marking.

08Verify First. Notify With Confidence.

The updated workflow introduces advance leave information, explicit absence verification, and configurable notification timing. Teachers retain control over attendance corrections while schools determine when parents receive absence alerts.

1. 01🙂

   Parent Informs Leave

   Planned leave is submitted in advance and made visible to the teacher.

2. 02🧐

   Teacher Marks Attendance

   The teacher records attendance on mobile, with informed-leave details available for reference.

3. 03🔎

   Review Absent Students

   The system displays the students marked absent in a verification checklist.

4. 04✅

   Confirm Each Absence

   The teacher verifies each absence and checks the corresponding confirmation box. Incorrect markings can be corrected.

5. 05😌

   Submit Verified Attendance

   Attendance is saved after the required verification.

6. 06😊

   Dispatch Parent Notifications

   Notifications are sent according to the school’s selected immediate or scheduled delivery setting.

09A 30-Minute Window Can Prevent a Wrong Message.

The redesigned notification settings allow schools to schedule absence alerts rather than sending them immediately. When attendance is taken at 9:00 AM and notifications are scheduled for 9:30 AM, teachers have an opportunity to correct attendance before parents are notified.

Interactive schedule example; 9:00–9:30 AM is not necessarily the default for every school.

10A Safer Process, Not Simply a Faster One.

The redesign deliberately introduced verification at a critical point in the workflow. Although this added an action for teachers, it helped address the risk of incorrect absence information reaching parents.

11Reducing False Alerts. Building Trust.

The redesigned experience introduced multiple safeguards between attendance marking and parent notification. By combining prior leave information, mandatory verification, and configurable notification timing, the workflow was designed to reduce accidental absence alerts and the unnecessary concern they could create.

Intended design benefits. A measured reduction in false alerts would require before-and-after notification error data.

12Good UX Doesn’t Always Mean Fewer Steps.

This project challenged the assumption that every additional interaction creates unnecessary friction. In a school environment, an incorrect absence notification can have a much greater emotional impact than the few seconds required to verify a student’s status.