How do schools manage a Chromebook 1:1 program?

Get the custody record right before you hand out a single device

The single most consequential decision in a 1:1 program is what counts as the authoritative record of who has a device. If the answer is "the Google Admin console," you have a problem: Google records the last user who signed in, which is a usage signal, not a custody claim. A student who borrows a friend's Chromebook for one period becomes the recorded user. A device sitting in a closet keeps showing the last kid who touched it in May.

What you want instead is an explicit checkout event: a staff member scanned or selected a serial, attached it to a student record, stamped a date, and captured an acknowledgment. That record survives the summer, survives a re-enrollment, and holds up when a parent says their child returned the device in October.

Practically, this means the assignment happens through a system that knows your roster. If your student list comes from your SIS — PowerSchool, Infinite Campus, Skyward, or a OneRoster feed — the checkout should draw from that same roster so that a student who transfers buildings does not become an orphaned assignment. Keying custody off manually typed names is the most common reason a district's 1:1 records rot within a semester.

Decide up front how granular you want to be. Most districts assign by student. Some assign by seat or cart for grades K-2, where devices stay in the classroom. Both are legitimate; mixing them accidentally is not. Write down which grades are take-home and which are cart-based before deployment day, because the collection process differs completely.

Deployment day: batch the work, capture the signature

Deployment is a throughput problem. A high school handing out 1,400 devices in two days needs to average one student every few seconds per station, which rules out anything that requires typing. Barcode or QR scanning of the asset tag is the only approach that holds up at that volume — and modern tooling lets a staff member use a phone camera as the scanner, so you can add stations without buying hardware.

Capture three things at handoff: the device identity (serial and asset tag), the student identity (pulled from the roster, not typed), and an acknowledgment of the responsible-use agreement. The acknowledgment matters more than districts expect. When a fee is later disputed, the question is always whether the family was informed of the terms, and a stored e-signature with a timestamp answers that question in one screen.

Record condition at issue, even briefly. A dropdown with "new / good / scuffed / has existing damage" plus an optional photo takes five seconds and eliminates the entire class of arguments that begin "it was already cracked when I got it." If you do nothing else differently this year, do this.

Have a plan for the students who are not there on deployment day — new enrollments, absences, late registrations. These trickle in all year and are the most common source of untracked devices, because the careful process built for deployment day does not exist in November. Whatever the day-one workflow is, make sure the front office can run it for one student at a time.

Keeping records honest during the year

Devices move constantly during the school year: swaps at the help desk, loaners during repairs, transfers between buildings, students who withdraw. Each of these is a custody change, and each one that goes unrecorded is a device you will spend June hunting for.

The loaner pool deserves particular attention. The standard failure mode is that a student brings in a broken device, walks out with a loaner, gets the original back two weeks later, and no one closes the loop — so the district's records show that student holding two devices forever. A loaner should be a checkout with its own expected return, tied to the repair that caused it, and the repair's completion should prompt the swap back.

Mid-year attestation is the cheapest insurance available. Once or twice a year, ask every student or staff member to confirm they still have the device the system says they have. This surfaces the quiet discrepancies — the device that was handed to a sibling, the one that went home with a teacher who changed rooms — while there is still time to fix them. A campaign that sends the prompt and tracks who has responded turns this from a week of emails into a dashboard.

Withdrawals are the other leak. Ideally the exit process includes a device return step that the registrar can see, because once a family has moved out of district, the recovery rate falls sharply.

Year-end collection that actually finishes

Collection is where 1:1 programs are judged. The goal is not "we collected most of them" — it is a short, specific, defensible list of what is outstanding and who has it.

Run collection as the mirror image of deployment: scan the device, confirm it matches the expected student, record condition on return, and close the checkout. Condition-on-return is what makes fee assessment possible at all, and comparing it to condition-at-issue is what makes the fee fair.

Build your outstanding list continuously rather than at the end. If the system can tell you at any moment which students still hold devices, filtered by building and grade, then the last week of school becomes targeted follow-up instead of a spreadsheet reconciliation. Seniors need their own timeline, since leverage disappears at graduation — most districts tie device return to the diploma or cap-and-gown pickup, which is legitimate as long as it is communicated in advance and is not a debt-collection hold on the transcript itself, which many states restrict.

Decide before June what happens with summer take-home. Districts running summer school or extended-year programs often let a subset of devices stay out, and that subset needs to be explicitly modeled, not just quietly ignored during collection. Otherwise your outstanding list is polluted with devices that are legitimately out, and staff stop trusting it.

Finally: reconcile. A physical scan sweep of your storage and carts after collection tells you whether the devices your records say are back are actually on the shelf. This is the step that catches the difference between "marked returned" and "returned."

What to measure

A handful of numbers tell you whether the program is healthy. Percentage of fleet with a current custody record is the foundation — if that is below the high nineties, nothing else you measure is trustworthy. Outstanding devices at the end of collection, expressed as a count rather than a percentage, is what your business office will ask about.

Damage rate per hundred devices per year, tracked by building and by grade band, is the number that drives budget conversations. It also tends to expose real differences in building practice — one middle school with triple the damage rate of its peer usually reflects a difference in supervision or storage, not in students.

Repair turnaround time matters because it drives loaner pool size. If your average repair takes three weeks, you need a much bigger loaner pool than a district that turns them in three days, and that is a purchasing decision you can make deliberately once you can see the number.

Lastly, track how much of the fleet is still under warranty and when that coverage expires. A warranty runway view — how many devices fall out of coverage in each of the next several quarters — turns replacement planning from an annual panic into a schedule.