Student Device Damage: Planning Spares, Repairs and Protection

The unit that makes planning possible is incidents per hundred devices per year, segmented. A single district-wide percentage is not actionable, because a fifth-grade cart and a high-school take-home fleet are different programs sharing a purchase order.

Record five fields on every device ticket and you will have everything you need after one year. First, the device model and cohort year — this separates a fragile model from a fragile grade. Second, grade band. Third, whether the device goes home. Fourth, the damage type, using a short fixed list rather than free text: screen, hinge, keyboard, port, chassis or cosmetic, battery, liquid, lost or stolen. Fifth, two dates — the day the device left service and the day it returned. Nothing else is required, and adding more fields reliably reduces the completeness of the first five.

That fifth field is the one districts skip and the one that matters most. Incidents per year tells you how much repair capacity to fund. Days out of service tells you how many spares you need. They are different questions and only one of them is usually asked.

Segment the result by grade band and by take-home status when you present it. A rate that is acceptable district-wide can conceal one building or one grade doing something the program can address — a carry policy, a bag requirement, a stairwell — and that finding is worth more than the headline number.

Once you have incidents per year and average days out of service, the pool size is arithmetic rather than judgment. Devices out of service at any moment is approximately the incident rate per school day multiplied by the average days a device spends out of service.

Worked as a method: take annual incidents for a cohort, divide by the number of school days to get incidents per day, then multiply by the average days-out-of-service from your ticket data. That product is the steady-state number of devices sitting in the repair loop. The spares pool must cover it, plus a buffer, because arrivals are not evenly spaced.

Two adjustments are not optional. The first is the opening spike: the first two weeks of the year produce a burst of devices that were damaged in June, stored over the summer and reported in August, plus devices that fail on first power-on. Size the pool for that two-week period, not for the January average. The second is the tail: end of year, when devices are collected and every deferred fault surfaces at once. Neither spike is a surprise, so neither should be an emergency.

The lever with the largest effect on this number is not the damage rate — it is turnaround. Halving average days out of service roughly halves the steady-state pool. That is why the repair model decision below is a budget decision and not an operational preference.

Four things decide this, and price is not first.

Volume comes first. Below a certain number of annual incidents, a district cannot justify trained staff, a parts inventory and a bench, and depot repair — shipping units to a service provider under a defined turnaround — is both cheaper and more predictable. Above it, in-house repair wins on turnaround, which as shown above is the same thing as winning on spares budget.

Second is parts. In-house repair depends entirely on being able to buy screens, keyboards, hinges and batteries for the specific models in the fleet, at reasonable lead times, for as long as the fleet is deployed. This is a question to ask before the device purchase, not after: a fleet standardized on two or three models with good parts availability is dramatically easier to service than the same number of units spread across seven models from a bidding process.

Third is warranty. Accidental damage coverage, where purchased, usually routes through the manufacturer's process, and opening a device in-house can affect it. Know which faults go which way before the first repair, and write it in the workflow.

Fourth is people. In-house repair is a skill that has to exist in the building or the district office, survive staff turnover, and be scheduled around everything else those staff do. Districts that succeed at it typically make it a defined role, sometimes with a supervised student technician program. Districts that treat it as something the network administrator does between other tasks end up with a repair backlog that is indistinguishable from a spares shortage.

Most districts land somewhere in between: the three or four common, fast repairs in-house — screens, keyboards, batteries — and everything else to depot. That is a reasonable design as long as the split is written down and the turnaround for each path is measured.

The case decision is usually framed as a durability question. It is more useful as a queue-management question: which failures does this choice prevent, and does it make the failures that still happen faster or slower to fix?

An always-on shell that stays attached to the device is the strongest protection for the failures that dominate elementary and middle-grade fleets — dropped-while-open, corner impacts, lid pressure. MAXCases Extreme Shell and Gumdrop's DropTech and SlimTech lines are both built around that model, with fitments specific to individual Chromebook and notebook models rather than generic sizes, and both carry bump- and drop-resistance claims in their product descriptions. The fitment specificity is the point: a shell for the Dell Chromebook 3100-series clamshell is not the shell for the 2-in-1 variant, and ordering by screen size alone produces a box of returns.

A sleeve or carry case protects a device in transit and does nothing once the device is open on a desk — a Brenthaven Tred sleeve for an 11-inch notebook or Chromebook is the right tool for a take-home program where the risk is the backpack, and the wrong tool for a program where devices are dropped in class. Many districts need both, and pairing them is a reasonable answer rather than an indulgence.

The second question — does the choice slow repairs — is the one districts discover late. A shell that has to be fully disassembled to reach a keyboard or battery adds labor to every service event. A case with poor port access produces charging failures that read as battery faults. A keyboard-integrated folio adds a second failure point that is now inside your repair queue. None of these are reasons to avoid protection; they are reasons to test one unit through a full repair before ordering four thousand.

Tablet fleets follow the same logic with different fitments — OtterBox and Brenthaven both build education-oriented tablet cases — and the same rule applies: order by exact model and generation, not by screen size.

A spares pool that is not tracked stops being a spares pool within a year. Four controls keep it intact, and all four are process rather than product.

Scan out and scan in by asset tag, against the student record, every time — including for a same-day swap. Define a return trigger that does not depend on anyone remembering: the loaner is returned when the repaired device is collected, and the repaired device is not handed over until the loaner is scanned back. Give the pool a physical home with charging, because uncharged spares are functionally unavailable. And audit the pool on a schedule, at minimum at the end of each term, so a drift of five units is found while it is still five.

Fee and protection-plan programs sit alongside this and are worth mentioning honestly: many districts run a family-paid damage-fee or optional protection scheme to fund part of the repair budget. The structures vary widely by state and by district policy, they interact with rules about fees for required instructional materials, and we are not qualified to advise on them. We supply hardware, cases and spares; the fee policy is a district and counsel question.