Ability to drop a student from a class which also removes them from the Attendance

I believe we used to be able to drop a student, retain their academic record, and have them removed from future Attendance. Now, evidently, that is not the case, and the Student - though removed from the roster - still appears in the Teacher's Attendance

  • Kris Singer
  • Jan 30 2025
  • Implemented
  • Feb 4, 2025

    Admin response

    Hello!

    We have made a tweak to how the transfer process works that should be making the drop/add transfer function more as you expect.

    For attendance within SIS/LMS, we are inclusive of dates. That means that if a student is listed with a drop date of 2/4, they will remain on attendance roster for 2/4 and will no longer show beginning on 2/5.

    If you use the Drop function and then manually Add to another class, you will want to be sure to set your Drop date for the last date the student should appear on the original roster and your Add date as the one the student should begin showing in the new class section.

    If you use the Transfer function, it previously set the Drop and Add date to the same date causing an overlap. With a change released today, the date set when transferring will be the Add date and the day previous to that will be set as the drop date.

    Please note: The change mentioned above will only impact schedule changes made moving forward.
    For existing or new schedule changes if you are seeing the student listed for attendance on a date after the drop date, that is not expected functionality and should be reported to support. For example, if a student has a drop date of 2/1 but is still showing in attendance on 2/2, that is not expected functionality.

    Thanks so much!
    Jacqueline Koca
    Senior Product Manager - Student Information System

  • Attach files
      Drop here to upload
    • Dino Vandenheede commented
      30 Jan 18:22

      I concur with the previous comments. Removing a student from a class should also remove them from future attendance records, while preserving their past attendance data. The current setup, where withdrawn students still appear in attendance, leads to inaccurate records and unnecessary work for staff. It's essential to maintain the integrity of our academic records without compromising data accuracy.

    • Diane Rognlien commented
      30 Jan 16:51

      The change isn't even common sense. In many states the law reads that school attendance records have to be maintained for a certain number of years. Also, when students transfer to another school the receiving schools usually ask for attendance for the complete year. BB needs to change this "improvement/upgrade" back to the original function.

    • Maria Haering commented
      30 Jan 15:56

      I agree with Andrea's comment below. Having the student keep appearing on attendance is not beneficial for anyone. Deleting the previous attendance is not an option. I have many times received requests for attendance records, so deleting attendance from the record is ridiculous at best and causes an academic integrity issue for the database.

    • Andrea Eckler commented
      30 Jan 15:49

      This recent change is incredibly unhelpful. We can't be falsifying student record in order to remove a student from a class. And leaving a student on the attendance who has withdrawn from the class creates inaccurate data and extra work for faculty & staff. I don't understand why you all chose to break something so thoroughly that worked well before.