Running a device and hotspot lending program at a public agency

Reference article · 5 min read

A lending program puts agency-owned laptops, tablets and mobile hotspots into residents' hands for weeks or months at a time. Libraries run the largest share of them, but schools, senior centers, workforce boards and housing authorities operate versions of the same service. The hard parts are rarely the devices: the recordkeeping, the eligibility rules, the configuration that keeps a unit usable across many borrowers, and the willingness to fund replacements after the launch money is spent.

Treat it as a small fleet operation with a service desk attached. The program department usually owns eligibility and the borrower relationship; IT owns imaging, management and security. Write that split down before launch.

Inventory, asset tags, and one system of record

Every unit needs a durable asset tag, a serial captured at receiving, and a record tying it to a borrower, a location and a status. Decide whether that record lives in the library system, the IT asset management system, or both with a defined direction of sync. Two disconnected spreadsheets is the usual failure.

• Circulate or assign. Short loans through a catalog behave like any other item, with holds and due dates. Semester-long assignments are closer to an IT deployment and fit an assignment record.
• Kits, not loose parts. Bag the charger, cable, case and a quick start guide together, and inventory the kit as one item.
• Status codes that mean something. In repair, awaiting wipe, held for non-return, retired and surplus should be distinct. You cannot report on loss if lost and overdue share a code.

Eligibility and the borrower agreement

Write eligibility in plain language and apply it consistently. Residency, a card in good standing, enrollment or program participation are common gates. Watch for conditions that screen out the people the program exists for, such as large fines or proof of address that unhoused residents cannot produce. If you prioritize, do it by a stated criterion rather than desk discretion.

The agreement should cover loan length and renewal, expected care, liability for loss or damage, that the device remains agency property, and what filtering or management is in place. State the privacy posture directly: what the agency can see and what it keeps. Many states protect the confidentiality of library patron records, and lending records may fall within those protections, so confirm with counsel how your state law and retention schedule apply.

Device management, filtering, and wiping between borrowers

Enroll every device in mobile device management before it circulates, using an enrollment method the device returns to automatically after a reset; otherwise a borrower's factory reset strips your management. Standardize one image, a small application set, and automatic patching.

Filtering deserves a deliberate decision, not a default. Schools and libraries receiving certain federal discounts, including E-Rate, carry obligations under the Children's Internet Protection Act, and FCC guidance on how those apply to devices used off premises has changed over time. Confirm current requirements with the official program source and your counsel, then document your choice.

Between borrowers, wipe and re-provision every unit as a mandatory checkpoint in the return workflow: condition, accessories present, wipe completed, re-imaged, back on the shelf.

Hotspot lines, data plans, and non-return

Hotspot lines are a recurring bill, so an unreturned unit costs money every month it stays out. Decide in advance what triggers suspension of a line and after how long, and put it in the agreement so the first suspension is not a surprise. Suspension is usually more effective, and less punitive, than collections.

• Keep an accurate line-to-asset mapping so you suspend the right number.
• Ask whether a line can be suspended and restored without a new activation charge or restarted term.
• Watch for units showing no data use; that is usually a device sitting in a drawer.

Budgeting for the full lifecycle

Annual cost per device is not the purchase price divided by expected life. Build it from hardware amortized over a realistic service life, monthly connectivity, management and software licensing, accessories and consumables, staff time for enrollment and support, repair and replacement, losses from non-return, and compliant disposal. Loss and damage rates vary by population and loan length, so use your own first-year data rather than a borrowed figure. If the program launched on one-time grant funding, raise the ongoing cost in the general fund conversation early: connectivity and replacement do not stop when the grant does.

Support and digital literacy

Lending without support produces returned devices and no outcomes. Fund a plain help path: a staffed desk or phone number during hours borrowers can use, a short printed guide, and drop-in sessions. Train frontline staff on the few issues that generate most calls, and partner with organizations already teaching adult digital skills. Confirm that assistive features work and that staff can show a borrower how to turn them on.

What to ask vendors, and what a board will ask at renewal

Ask carriers and resellers how lines are suspended and restored and at what cost, whether devices are carrier-locked, what coverage looks like at the addresses you serve rather than statewide, and whether staff can activate and deactivate in bulk. In the contract, require asset-level reporting you can export, a defined process for lost or stolen units, clear early-termination terms, and limits on vendor retention of borrower data.

At renewal, expect questions about units in circulation and how heavily they are used, waitlist length, who is being served against the stated purpose, loss and damage counts, annual cost per active borrower, and what changed for the people served. Decide those measures before launch and instrument for them; reconstructing them later from circulation logs rarely convinces anyone.

HQT works with state and local agencies on device management, connectivity and support operations.

Frequently asked questions