This idea has been merged into another idea. To comment or vote on this idea, please visit K12OC-I-2274 Attendance Per Class vs. Per Period, Per Day.
We need the ability to track attendance/tardiness by individual course sections and automatically trigger notifications or conduct records when a student reaches a specific threshold for that specific class.
The Problem
Currently, while Blackbaud tracks class-by-class attendance, setting up automated notifications or linking attendance patterns to the Conduct Manager is largely global. For example, if a student misses three classes across different subjects, that’s one type of behavior. However, if a student misses the same specific course (e.g., Math) three times, it signals a subject-specific issue that requires immediate intervention from the Advisor, Teacher, or Conduct Manager.
Right now, catching these course-specific chronic absence patterns requires manual monitoring, Advanced Lists, or external workflows.
Proposed Feature
We would like to see an enhancement in the Attendance/Conduct Manager setup that allows schools to define rules based on course-specific counts.
Course-base Threshold Trigger: Allow us to set a rule such as: "If a student accumulates X number of absences/tardies in the same course, trigger an infraction/consequence." So that we can set up automated notification to alert Course Teacher, assigned Advisor, or Conduct Manager.
Value to Schools
This feature would allow schools to intervene much faster when students are struggling with, or avoiding, specific classes. It moves attendance management from a reactive administrative task to a proactive academic intervention tool.