Here's a scenario IT administrators know well. A student's laptop dies on a Tuesday morning. IT doesn't open until nine. The library opened at seven. So the student walks to the library, explains the situation to whoever's at the desk, and waits while a librarian — whose job description says nothing about device management — figures out what to do.
This isn't an edge case. At Hernando County School District, technicians were spending 60-70% of their working hours managing laptop swaps and one-to-one device issues before they changed how they operated. The library had become an informal triage point, and IT was still doing all the work — just inefficiently, and always a step behind.
The problem isn't that the library is involved. Libraries are well-placed to support device access — they're central, trusted, and open long hours. The problem is that nobody designed it this way. It just happened. And when things happen by accident, they work badly.
This article is about designing it on purpose.
Quick answer
Most school and university libraries already function as a de facto IT help desk for device lending — not by design, but because they're open when IT isn't and students go where the doors are open.
The problem isn't the library's involvement; it's that the library was never built for this role. Formalizing it with self-serve smart lockers turns an accidental, staff-heavy workaround into a 24/7 device access point that requires no staff at the point of transaction — cutting the time per loaner from roughly 30 minutes to under two minutes and removing the bottleneck for students and IT teams alike.
Why the library became the default IT fallback
It started with digital equity. When schools and universities went one-to-one — one device per student — they needed somewhere students could go when their device failed. IT was the obvious answer, but IT has limited hours, limited staff, and a full queue of other work. The library had longer hours, a service desk, and the institutional instinct to say yes.
So device lending started appearing in libraries — quietly, without policy, without infrastructure, and without a budget line. Librarians found themselves checking out Chromebooks the way they checked out books: manually, on a spreadsheet, with a sticky note as a receipt.
The consequence is predictable. Manual lending is slow (roughly 30 minutes of combined staff and student time per transaction, according to LocknCharge's own operational data). It doesn't scale. It breaks down at the start of semester, during exams, and whenever the person who manages the spreadsheet is off sick. And it still doesn't solve the after-hours problem — a student whose laptop dies at 9 PM on a Sunday has no path to a replacement until Monday morning.
The cost lands on everyone. IT technicians handle intake questions they shouldn't be handling. Librarians manage logistics they weren't hired for. And students wait — sometimes for days — for a device they need today. A study published by Indiana University Bloomington found that students whose laptops were unreliable had measurably lower GPAs even after controlling for demographic variables, with students from lower-income backgrounds least likely to report the problem rather than quietly absorb the consequence.
The library didn't ask for this role. But it has it. The question is whether to keep doing it badly or build something that actually works.
What a library device loaner program actually involves
A device loaner program — in a library context — is the formal process of lending school- or institution-owned devices to students on a short-term basis when their primary device is unavailable. It's distinct from a permanent device deployment like a one-to-one program, and different from a repair depot, though a well-designed loaner program can support both from the same infrastructure.
There are five things every loaner program needs to get right. Most programs have all five. The difference between one that works and one that causes everyone grief is almost always the second one on this list.
- Device inventory. A defined pool of loan-ready devices — fully charged, wiped to a standard configuration, and tracked individually by serial number or asset tag. The pool needs to be sized for peak demand, not average demand. Average demand is a Tuesday in October. Peak demand is the first week of semester.
- Checkout workflow. The process for verifying student identity, recording the loan, and handing over the device. This is where most programs fall apart — the workflow is either too slow (manual sign-out sheets that take 30 minutes per transaction), too loose (honor systems that lose devices), or too restrictive (only available during staffed hours).
- Device tracking. Knowing where every device is, who has it, and when it's due back — in real time, not from memory or a spreadsheet that someone updates when they remember.
- Return and reset process. A consistent method for accepting returned devices, checking condition, wiping user data, charging the device, and returning it to the available pool. Without this step, a returned device sits in limbo — unavailable to the next student — until someone manually processes it.
- Policy. Clear rules about who can borrow, for how long, what happens if a device comes back damaged, and how students who borrow repeatedly get directed toward longer-term solutions. A policy isn't bureaucracy — it's what lets the system run without a staff member making a judgement call on every single transaction.
Five components. One weak link — the checkout workflow — is enough to make the other four irrelevant.
The two models — and why one fails
There are really only two ways to run a library device loaner program. Every variation is a version of one of these.
Model 1: Staffed circulation desk.
The student goes to the desk, speaks to a librarian or IT aide, provides ID, the staff member logs the loan manually, retrieves the device from a cupboard or charging cart, and hands it over. Return works in reverse. This model is familiar, requires no upfront infrastructure investment, and gives staff direct visibility into every transaction.
It also costs roughly 30 minutes of combined time per transaction. It doesn't work after hours. It creates queues during peak periods. And it stops functioning entirely when the responsible staff member is unavailable.
Model 2: Self-serve smart locker.
The student authenticates at a kiosk (via student ID, PIN, or single sign-on), selects an available device, and the locker bay opens. The system logs the loan automatically — who took which device, at what time, with a photo record. Return is the student placing the device back in any available bay; the system updates the record and the device begins charging immediately.
Transaction time: under two minutes. Operating hours: 24 hours a day, seven days a week. Staff required at point of transaction: zero.
Staffed circulation desk vs. self-serve smart locker
|
|
Staffed circulation desk |
Self-serve smart locker |
|
Operating hours |
IT/library hours only |
24/7, any day of the year |
|
Time per transaction |
~30 minutes (staff + student) |
~2 minutes or less |
|
Staff required |
Yes — at point of transaction |
No — fully self-serve |
|
Device tracking |
Manual log or spreadsheet |
Automated — logged per transaction |
|
After-hours access |
❌ Not available |
✅ Always available |
|
Accountability |
Honor system / sign-out sheet |
Photo ID verification, audit trail |
|
Scales with demand |
Slowly — needs more staff |
Yes — add bays, not headcount |
|
IT staff burden |
High — Tier-1 tickets pile up |
Low — self-serve removes queue |
The staffed model has one genuine advantage: human judgement. A librarian can notice that a student seems distressed, or that a returned device is damaged in a way that needs documenting before it goes back into circulation. The smart locker model handles this through photo capture on return and audit logs — not perfectly, but well enough for most scenarios.
For most institutions, the practical question isn't which model is theoretically superior. It's which model is actually available at 10 PM on a Wednesday when a student needs a device for a morning submission.
How to build a loaner program that runs itself
The goal is a program that delivers a device to a student — verified, logged, and charged — without pulling a librarian away from the desk or a technician away from their actual work. Self-serve smart lockers are the infrastructure that makes this possible. Here's how to set one up.
Step 1: Choose the right location
Place the locker where students already go when something goes wrong — which is almost always the library. Foot traffic, extended hours, and familiar surroundings matter. The locker doesn't need to be staffed, but it should be visible and easy to find. Avoid locations that are locked outside business hours.
Step 2: Define your device pool
Decide how many devices go into the loaner pool, what spec they need to be (a loaner only needs to do coursework, not run professional software), and how they'll be tagged for tracking. Asset tag every device before it goes into the pool.
Step 3: Configure the locker and integrations
The FUYL smart locker system connects to your institution's student information system so authentication uses existing credentials — no new accounts, no separate passwords. IT sets the loan rules (duration, eligibility, return prompts) once, and the system enforces them automatically. Every transaction is logged to a cloud-based portal that both IT and library staff can access.
Step 4: Set your policy (template below)
Don't let the locker go live without a written policy. Students need to know the rules before they borrow — and you need something to point to when someone returns a device with a cracked screen and says they found it that way. The template below covers the essentials. Adapt it, put your institution's name on it, and post it at the locker and on your IT or library webpage.
Step 5: Establish the return-and-reset workflow
Decide who checks returned devices and how often. With a smart locker, returned devices charge immediately, but someone still needs to wipe and reconfigure them before the next loan. Build this into an existing IT workflow — it's a five-minute job per device, not a 30-minute one, because you're not also handling the checkout queue at the same time.
For more detail on how the loaning and repair workflows operate in practice, see LocknCharge's walkthroughs of the FUYL loaning workflow and repairs workflow.
For the broader context of running a device loaner program in higher education — including staffing models and program governance — see our guide to device loaner programs for universities.
|
Library Device Loaner Program — Policy Template Copy, adapt, and post. Last field in brackets is yours to complete. |
|
|
Eligibility
|
Loaner devices are available to currently enrolled students [and staff] of [Institution Name]. A valid student ID or institutional login is required to borrow a device. |
| Loan period | Devices may be borrowed for up to [24 hours / 3 days / 1 week]. Renewals may be requested [once / up to twice] if no other student is waiting. Devices not returned by the due time may be remotely locked. |
| Device condition | Students are responsible for returning the device in the same condition in which it was borrowed. Damage beyond normal wear must be reported at the time of return. Students may be charged for damage, loss, or theft at the replacement cost of the device. |
| Data and privacy | All loaner devices are wiped and reconfigured between each loan. Do not store personal files or sensitive information on a loaner device. [Institution Name] is not responsible for data left on returned devices. |
| Checkout and return | Devices are available from the self-service locker located [in the library / Building X / Room Y]. Authenticate with your [student ID / institutional login]. Return the device to any available bay in the locker. Late returns will be flagged and may affect future borrowing eligibility. |
| Repeat borrowers | Students who borrow more than [three times] in a semester may be referred to IT or student services to discuss longer-term device solutions, including [institution-specific program, e.g. device grant, subsidized purchase, or permanent loan]. |
What it costs to do this manually — and what you save when you don't
The operational case for self-serve smart lockers isn't complicated. It's arithmetic.
A manually handled device loan takes roughly 30 minutes of combined IT and student time per transaction — LocknCharge's own operational data, consistent across multiple institutional case studies. At industry-standard help-desk labor rates of $1.60 to $2.13 per minute (HDI's annual benchmarking data for North American educational institutions), that's $48 to $64 in staff time per manual loaner transaction — before factoring in the technician's opportunity cost, which is whatever higher-priority work they're not doing.
For an institution managing 4,000 loaner events per year — a volume the University of Washington Library's device lending program has reported in its annual access services statistics — that's a potential $192,000 to $256,000 in annual IT labor consumed by device exchanges alone. Not repairs. Not deployments. Just the logistics of handing a device to a student and taking it back.
The self-serve model changes the unit economics entirely. LocknCharge's FUYL™ smart locker reduces staff time per transaction from 30 minutes to under two minutes — a 93% reduction documented across multiple deployments. Students handle the entire checkout process independently; the system handles authentication, logging, and return tracking. Staff interact with the workflow only when a device needs wiping and recharging between loans.
Here's what that looks like at institutions that've made the switch:
- At Hernando County School District, technicians were spending 60-70% of their working day on laptop swaps and one-to-one device issues before deploying FUYL smart lockers. After deployment, that time dropped to a fraction of what it had been — freeing the IT team to focus on infrastructure, deployments, and genuine Tier-2 and Tier-3 support work that actually requires a technician.
- At SUNY Fredonia, the laptop lending program moved from a staffed desk model to FUYL smart lockers and cut checkout time per transaction by more than 90%. Students now access loaners on demand without queuing at any desk, and library staff no longer manage device transactions at all.
- At Kingsway Christian College, switching from a manually managed loaner system to smart locker infrastructure saved more than $76,000 annually in IT labor — a figure derived from staff time recaptured across the full loan volume — and loan turnaround time dropped by 75%
None of these institutions hired more staff. They changed the system.
FAQs
How do I set up a device loaner program in my school library?
Start with five things: a defined pool of loan-ready devices (fully charged, asset-tagged, and wiped to a standard configuration), a checkout workflow (self-serve locker or staffed desk), a return and reset process, a tracking system, and a written policy. The most common failure point is the checkout workflow — manual sign-out sheets don't scale and don't work after hours. Self-serve smart lockers handle checkout, return tracking, and device charging automatically, and require no staff at the point of transaction. See the full setup walkthrough in the FUYL loaning workflow guide.
Can the library run a device loaner program without adding staff?
Yes — if the checkout process is self-serve. A staffed lending model requires a librarian or aide present for every transaction, which limits operating hours and creates queues during peak periods. A self-serve smart locker lets students authenticate and collect a device independently, at any time. Library staff only interact with the program during scheduled device maintenance (wiping and recharging returned devices), which takes minutes per device rather than hours per day.
What's the difference between a library loaner program and an IT loaner program?
The practical difference is hours and location, not policy. An IT loaner program is managed and staffed by the IT department — which means it's typically only available during IT business hours, often nine to five, Monday to Friday. A library loaner program uses the library's longer hours and central location to extend device access to evenings and weekends. In most institutions, both exist informally — IT manages the devices, the library manages the transactions outside IT hours — but nobody designed it that way, and the seams show. The most effective model integrates both: IT owns the policy and device management, the library provides the location, and self-serve smart locker infrastructure handles the transaction. That eliminates the hours and staffing constraints of both departments without requiring either to take on additional headcount.
How do students borrow a laptop after hours when IT is closed?
With a staffed lending model, they can't — and that's the core problem with after-hours device access in most institutions. Self-serve smart lockers solve this directly. The locker operates 24 hours a day, seven days a week. A student authenticates via student ID or institutional single sign-on, selects an available device, and a bay opens automatically. The transaction is logged, the device is tracked, and no staff member needs to be present. Institutions that have deployed FUYL smart lockers in their libraries report that a significant portion of loans occur outside standard business hours — precisely when the demand exists and the staffed model fails.
What is a smart locker and how does it work for device lending?
A smart locker is a secure, connected storage unit with individual lockable bays, each containing a device. Students interact with a touchscreen kiosk or app to authenticate their identity (via student ID, PIN, or single sign-on), at which point an assigned bay unlocks automatically. The system records who borrowed which device, at what time, for how long, and — on return — captures a photo or condition check before locking the bay and beginning the charging cycle. IT administrators access the full audit log remotely through a cloud portal. The FUYL smart locker system is purpose-built for educational device management, handling both loaner programs and repair intake workflows from the same unit.
How do you track loaner devices in a library — and what happens if one doesn't come back?
Manual programs typically track devices through sign-out sheets, spreadsheets, or library management systems — all of which require staff to maintain and audit. Self-serve smart lockers log every transaction automatically: the student's identity, the specific device (by bay and asset tag), the checkout time, and the return time. If a device isn't returned by the loan period, the system can trigger automated reminders, escalate to IT or student services, and — where MDM integration is in place — remotely lock the device. This creates an accountability trail that sign-out sheets can't replicate and that most institutions find dramatically reduces late and non-returned devices.
The library didn't become an IT help desk by design. It happened because students needed somewhere to go, and the library was there. That's not a problem to solve by pulling the library out of the picture — it's a problem to solve by giving the library the right infrastructure.
Self-serve smart lockers make the library a genuine 24/7 device access point without consuming librarian time or IT technician hours. The technology handles what used to take 30 minutes in under two. And IT gets to spend its time on work that actually requires a technician.
That's not an accident. That's a design choice.
The infrastructure that makes this possible — self-serve smart lockers with built-in authentication, device tracking, and charging — exists and is already running in libraries at institutions across the globe. If you want to see what it looks like in practice, explore the FUYL smart locker system, or read how Pittwater House transformed its IT operations with LocknCharge.
