.png)
Loaner laptops are a vital part of your IT provision because they keep your students, teachers, and coworkers learning and working when their normal device is down.
When you’re managing a fleet of loaner laptops, you’ll know that the difficult part isn’t handing the devices out. The hard part is tracking what happens afterward. Who has it now? Where is it anyway? And when is it supposed to come back?
A loaner device management process gives your IT team answers to those questions, but it shouldn’t cover only the loan period. Effective loaner device management covers the full lifecycle of loaned devices - from checkout and on-loan device security, through device return, reset, and reassignment.
A loaner device is a school- or district-owned device given to someone temporarily rather than assigned permanently.
For instance, you might have:
Because these devices change hands regularly, you’ll need an asset register that can keep up. Accurate inventory records clearly show loan assignments, defined return dates, scheduled cleaning and resets, and a process for handling devices that are overdue, damaged, or missing.
The basic loaner device management lifecycle is:
Check-out → active use → due date → return → reset → reassignment
Loaner devices often change hands. Problems start when you don't record those changes.
Common gaps include:
There’s also a security reason to keep inventory accurate. Accurate hardware inventory is a recognized cybersecurity practice, as shown in the NIST Cybersecurity Framework 2.0, which includes maintaining inventories of organization-managed hardware.
When you don't have a clear picture of where shared devices are or who is using them, it can create real problems.
Healthcare is a good example. A 2026 Journal of Hospital Administration study reported a mean annual shared-device loss rate of 23% among respondents. The healthcare loss rate isn’t a universal benchmark for K12 loaner fleets, but it highlights what can happen when devices move frequently without a clear record of where they’ve gone.
The good news is that most of these challenges can be managed with a straightforward process: start with a clear checkout, keep the device record up to date using a simple checklist, have a plan for overdue or missing devices, prepare returned devices for the next user, and use the right tools to support the whole process. Here’s where to start:
Every loan should start with three things: an identifiable device, a borrower, and a return date.
At minimum, record:
Loan periods should reflect the context. A device issued while a student’s usual Chromebook is in for repair may only be needed for a few days, while a facilities contractor laptop could stay assigned and on loan for weeks or months, depending on the project duration.
A simple workflow is:
Request → approval → checkout → active loan → return reminder → return → inspection and reset → reassignment
Real-world loaner programs use these types of workflow controls. For instance, MIT's laptop loaner guidelines require borrowers to return equipment before the lending period ends, or arrange an extension in advance. MIT also reimages returned laptops before reusing them.
A straightforward loaner process starts with a few basics.
Here are the main things to keep track of:
Every loaner device should have its own permanent asset record, including its serial number, model, asset tag, condition, and loan history.
Keep the record up to date with who has the device and when they received it. You can manage this through your ITAM or ITSM system, a service desk, or an automated locker system.
Every loan should have a return date, even if you allow the borrower to extend the loan.
Don’t mark a loan as complete just because the scheduled return date has passed. Make sure that the device is actually back, and update its status accordingly.
Before loaning the device to someone else, check the hardware, accessories, management status, and software. Remove the previous user’s data, according to your school or district policy.
If IT needs to lock, wipe, request a location, or send an on-screen message, record what was done. This gives a clear history to refer back to.
A clear overdue and missing device policy helps everyone know what to do as a loan nears its end. It should define what happens as a loan approaches and passes its return date. It gives your IT team an agreed process to follow, rather than deciding what actions to take and when each time.
It might look something like this:
These time thresholds and associated actions are examples. The right timing and action for your school can depend on many factors: device value, data sensitivity, and borrower type, and these should be covered in your school loaner policy.
The policy should also explain who can approve extensions, how damaged devices are handled, whether users can transfer devices to others, and what actions IT can take when equipment is lost or stolen.
When a device is returned, it should be checked and prepared before it’s given to someone else. This helps ensure the device is secure, working properly, and free of the previous user's data.
NIST SP 800-88 Revision 2, Guidelines for Media Sanitization, recommends a clear process for securely removing data, based on the sensitivity of the information being protected.
For a loaner device, this could mean that you’d need to:
If you work in K-12, you probably have most of the tools needed to manage a loaner program. The key is how they work together when a device is checked out or overdue.
This is typically where the loaner device record lives. It shows asset information and assignment history.
If your school or district uses ITSM for support requests, the loan can form part of the same workflow of requests, approvals, repairs, loan periods, and escalations.
Your MDM continues to manage the device while it’s on loan, including its configuration, applications, updates, and security settings.
These support self-service checkouts and returns. Temple University's Laptop Share Kiosks, for example, allow students to authenticate and borrow a university laptop for up to 4 hours. The devices are automatically reset after each use to remove personal data.
These can add context, including location, last check-in information, and remote security actions when a loaned device becomes overdue or missing.
Senturo integrates with your existing systems to simplify loaned device management and covers every stage of the loan lifecycle.
When a device doesn’t come back, Senturo gives you more detailed location and security information to support your recovery process. If you use ChromeOS, Windows, macOS, iOS/iPadOS, and Android, Senturo checks in devices every 10 minutes by default. When you switch a device to Missing Mode, check-ins switch to real-time tracking.
Use Senturo to review the device's current or last reported location, location history, check-in status, and geofence activity. Geofence events and missed check-ins can also trigger automated alerts or actions, such as locking a device or sending a message.
For example, if a Chromebook loaned to a student is overdue, you can confirm the assigned borrower in its asset system, review the device's most recent location information, send a return message, and use Senturo Lock to lock down the device, if your recovery policy requires it.
A loaner device management system tracks the lifecycle of devices on loan, e.g., who has each device, when the device was issued, when it should be returned, and its current status.
Typically, you can combine asset management or ITSM records with device management and visibility tools. Asset records track assignment and ownership, while visibility tools show each device’s location, check-in history, geofencing, and recovery information.
It’s best to define and follow a specific overdue device process, which may include borrower reminders, internal notifications, reviews of the device's latest status or location, and remote security actions when required by your school’s policy.
Absolutely. Schools should remove the previous user’s data, in accordance with their user safety policy, before reassigning the device. How you do this (reset, reimage, or sanitize) depends on the device type and the sensitivity of the data.