Progress Report Automation

How the system identifies students and generates recommendations

1) No Established Attendance

A student is flagged as No Established Attendance when the system determines there is no evidence of the student's participation in the course.

This flag is intentionally strict and is only applied when all applicable indicators point to non-participation.

Data evaluated

Depending on course modality (online vs. in-person/hybrid), the system evaluates:

• D2L access and login activity
• Discussion activity and discussion recency
• In-person attendance status (for in-person or hybrid courses only)

All indicators are evaluated relative to class norms (for example, below 75% of the class average).

Decision logic

A student is flagged as No Established Attendance only when both conditions are met:

1. The system finds no evidence of meaningful activity, such as:
   • No D2L logins, In-person attendance, or
   • No discussion/assignment activity from a graded activity

Progress Report Recommendation

When this condition is met, the system adds:

• Subject: No Established Attendance
• Type: Action Requested
• Reason: The system determined the student has not established attendance in the course

Safeguards and edge cases

• This flag takes precedence over all other attendance flags
• A student flagged as No Established Attendance cannot also be flagged as Low Attendance
• Students with any evidence of participation are excluded from this category
• If attendance or engagement data is unavailable, no flag is applied

2) Low Engagement

A student is flagged as Low Engagement when their participation, attendance, academic performance, or a combination of these is below the class average. This category captures students who have lower engagement than their peers but have demonstrated measurable activity. Low Engagement may be driven by attendance-related behavior, academic performance, or a combination of both.

Data Points

Attendance/Participation

• Low D2L logins, in-person attendance
• Discussion/graded-assignment activities’ participation

Academic Performance

• All graded assignment categories in the course
• Performance in each category relative to the class average
• Presence of missing assignments

Decision logic

A student is flagged as Low Engagement when either of the following conditions are met:

1. Attendance-based Low Engagement
   • The student’s combined attendance and participation indicators meet or exceed a defined low-engagement threshold, and
2. Performance-based Low Engagement
   • At least one graded assignment category is identified as low-performing, and
   • Approximately one-third or more of the student’s total graded categories are flagged as low

When flagged, the system records the specific reason(s) for Low Engagement (attendance-based, performance-based, or both), along with the contributing indicators or assignment categories.

Progress Report Recommendations

Once a student is flagged for performance-based Low Engagement, the system evaluates the student’s current overall course grade and missing assignments to determine which recommendation(s) to add:

• Grade below 20%
• Subject: Communicated to Student Unable to Pass
• Type: Action Requested
• Grade between 20% and 60%
• Subject: Currently Failing but Able to Pass
• Type: Student Notifications
• Grade between 60% and 80% with missing assignments
• Subject: Missing Assignments
• Type: Student Notifications

Students with grades of 80% or higher do not currently receive engagement-based recommendations.

Safeguards and edge cases

• Low Engagement is mutually exclusive with No Established Attendance
• Discussion indicators are suppressed if more than 50% of the class shows no discussion activity
• Students without a current grade are excluded from grade-based logic>
• Missing assignment checks apply only to students in the 60–80% grade range
• Students not flagged as Low Engagement are excluded from all grade-based recommendations
• Performance data errors or missing records result in no flag rather than incorrect flagging

Additional consistency rules applied across all categories

• Flags and concerns are deduplicated per student and course
• All logic is applied independently per course (CRN)
• The system favors conservative flagging when data is incomplete or ambiguous