@Belcher.shane or @TAnders - do you have a process for loaner devices that works well for your district?
We don’t have a standard workflow set up for loaners, mainly since our district is 1:1 with Chromebook carts, but when we were doing 1:1 take home, the site technicians would track them by just checking them out to the students that forgot theirs, then we would pull the timeline revisions if we needed any information on who was using it and which day. The asset timeline will give you the history of who the Chromebook was checked out to. If you keep the same loaner devices, then you can manage them that way.
If you wanted more tracking than that, you could possibly set up a rule that fires an email off any time the loaner devices are checked in/out, unfortunately there is not currently an option to create a ticket based off a rule for a check in/out. I’m pretty sure that option has been suggested in the Idea Exchange.
@TAnders and @mfischer There is an idea in our Idea Exchange. Please vote and comment on it if this is an enhancement you are still interested in 
We simply created a ticket category “Left Chromebook at home”, so a ticket is created for that user with all their pertinent info, and in a matter of a few quick clicks a spare is assigned to the user. In and out in less than 2 minutes. We are now looking at a way to limit the number of times a user can use “left at home” excuse to get a spare in a given time period as we have some users that check one out daily.
@mdonoho Thank you for adding your experience to this thread! We love to see community members sharing their knowledge!
We simply created a ticket category “Left Chromebook at home”, so a ticket is created for that user with all their pertinent info, and in a matter of a few quick clicks a spare is assigned to the user. In and out in less than 2 minutes. We are now looking at a way to limit the number of times a user can use “left at home” excuse to get a spare in a given time period as we have some users that check one out daily.
@mdonoho, is a random Spare assigned or do you pick a specific Chromebook spare?
We simply created a ticket category “Left Chromebook at home”, so a ticket is created for that user with all their pertinent info, and in a matter of a few quick clicks a spare is assigned to the user. In and out in less than 2 minutes. We are now looking at a way to limit the number of times a user can use “left at home” excuse to get a spare in a given time period as we have some users that check one out daily.
This is what we need. We do a 3 strikes rule per semester for students and after that they have to have a conversation with the Dean’s about what is going on. But there is no way to track the 3x so we have to add comments in the tickets, or edit the Issue to add Strike 1, Strike 2, etc. Would be nice to have a condition where you can enable Spare Limits-set the date ranges for your terms or semesters, then the issues it applies to, then how many spares you want to be allowed. Then if a ticket is created for that student for that issue on the 4th time a warning will pop up saying they’ve reached their limit. It should still allow you to assign them a spare, but a warning should pop up so we can be aware they have to go and see the Dean’s.
This idea stemmed from this original thread:
Yesssss. We dont have a good system either. IIQ, steal all of Cheqrooms features. They do this so well but they are expensive!
Due dates and email reminders for short term loaners IE dead battery, left at home.
What are your steps to check in and out devices for daily loaners?
Currently, using cheqroom, it takes me about 20-40 seconds to process a student and have them headed back to class.
- Scan device asset tag
- Scan student ID
- Enter due date and time
- Reason IE dead battery, left at home
We would like to be able to have a way to track the number of times Student A checked out a loaner device(chromebook, Laptop, charger, tablet) and once they hit a threshold be able to flag their account to notify us they have used say 5 spare device checkouts this semester. At that point each time they checkout an additional spare we would generate a ticket for our agents/admin to notify them and their parent so they can charge the appropriate fee etc.
We use spare pools and have chargers entered into our parts system. We have notifications set up to email the requestor each day, after 1 day has gone, by if it has not been returned. We also have an issue category for Forgot charger.
Please check out the two ideas set for this workaround:
Hi everyone! @nburke Just posted a WONDERFUL post about how she is tracking her daily loaners! Please go check it out and comment!
We simply create a spare pool for our school if a kid leaves theirs at home and just check out devices that are in the spare pool.
We then just go back to the manage section at the end of the day to see who still hasn’t turned theirs in and then brick their loaner AND checked out device to force them to come see us the next day. We don’t really have a ton of loaners going out so its easy to manage, and tend to also not loan them out to repeat offenders.
@JRood 877c5a lvpioneers Thank you for adding your workflow. I am curious how you are documenting your repeat offenders. Additionally, how are you locking their loaner devices? I would love to hear more about your workflow!
@JRood 877c5a lvpioneers Thank you for adding your workflow. I am curious how you are documenting your repeat offenders. Additionally, how are you locking their loaner devices? I would love to hear more about your workflow!
We don’t have any real way to document repeat offenders. We get the same kids coming in an out on a regular basis and tend to recognize faces.
When we lock devices we just pull up our spare pool that we use and then sort those by owner. Then we just go to the owner and in the devices that are currently checked out we can disable/renable their chromebooks in the asset page.
@JRood 877c5a lvpioneers Are y’all interested in implementing a system or would you rather continue the system you have?
I love y’all locking the devices! What a great use of that feature!!!
