Our check-our process may be different than others, I don’t know.
For various reasons, our students keep the same chromebook year over year.
We have found that the most efficient method of checking out chromebooks each year is to call the students down to the cafeteria by grade level, and then calling them up by name as we come to their chromebook in the stack. For this to work, we have to know which student the chromebook belongs to before we call the student forward.
In years passed, we have placed a physical label with the student’s name on each chromebook and case in order to make this work. This is very cumbersome, and prone to error. Because IIQ allows us to check in devices while leaving them assigned to the user, we felt this was an idea solution to our organizational problems at the beginning of the year.
The problem we are running into as we try things out is that the Batch Check-Out requires that we scan the Student first, then scan a device to the student. (this scenario works, if chromebooks change hands year over year. In our scenario, this doesn’t work, because students get the same chromebook every year...that way, if they trash it, they live with the trashed device, and vice versa)
We would like to be able to grab a chromebook from the stack, and using the batch check-out, scan the chromeook and have it show who it is currently checked out to, so what we can call that student forward, get their ID # and finish the check-out process. Basically, we want to be able to reverse the current Batch Check-out process.
Are we alone in requiring students keep the same device year over year?
If not, is there a better method for checking out the devices that works within IIQ?
I hope this makes sense. If not, my apologies.
Thanks everyone.
