Check In Check Out Students

We have some students who are not permitted to take their district devices home for various reasons, including outstanding balances for damage or repairs, parent requests, behavior concerns, or other circumstances. These students are placed on **CICO (Check-In/Check-Out)** and are expected to return their devices each day.

Currently, our Media Center staff maintain their own lists of CICO students, but it can be difficult to consistently track whether every device has been returned each day. It would be helpful to have a built-in way to track daily device check-ins and automatically notify designated staff when a CICO device has not been returned.

It would also be useful to have the ability to automatically place a student on CICO based on configurable criteria. For example, we could set an outstanding balance threshold, and once a student reaches that amount, the system could automatically place them on CICO and notify the appropriate Media Center staff, administrator, parent/guardian, or other designated users.

Another challenge occurs when students transition between buildings. For example, a student may have been on CICO in 8th grade at the Middle School and then move to 9th grade at the High School. It would be helpful if the system could automatically notify the new building's Media Center staff, administrators, and possibly teachers that the student was previously on CICO. Staff could then review the student's status and determine whether CICO should continue at the new building rather than relying on someone to manually communicate that information.

It would also be helpful to have a **CICO dashboard within Manage** for staff who have permission to manage these students. The dashboard could provide an at-a-glance list of all students currently on CICO, including their building, grade, reason for CICO, date added, who requested it, current device, and whether their device has been checked in for the day. Being able to filter this list by building, grade, or status would make it much easier for staff to manage.

An additional integration with **Jamf School** could make this even more useful. If the Jamf School API supports commands such as **Lock Device** or **Lost Mode**, the system could automatically send a command to devices that have not been checked in by a configurable time each day. The Lock Device command could potentially display a message explaining why the device was locked and where it needs to be returned.

Ideally, we would be able to configure the CICO criteria, notification recipients, daily cutoff time, annual/building-transition review, and automated device actions. This would provide a centralized way to manage CICO students, reduce manual tracking by Media Center staff, ensure CICO information follows students appropriately between buildings, and quickly identify devices that were taken home when they should have been returned.