How do school districts track Chromebook repairs?

Intake: capture the device, the symptom, and the custody change

Repair intake happens at a counter with a student standing there, so it needs to be fast. Scan the asset tag, pick the symptom from a short list, note anything the student said, and hand out a loaner. Three of those four steps are the same every time and should be one screen.

Symptom categories matter more than free-text descriptions for reporting. Cracked screen, keyboard or keys, trackpad, hinge or chassis, charging port, battery, won't power on, liquid damage, software or OS. This list is short, it maps to the parts you stock, and after a year it tells you exactly what to buy.

The custody change is the step most often skipped. When the device goes into the repair queue it is no longer in the student's possession, and the loaner is. If those two facts are not recorded together, your custody records now show the student holding two devices and you will find out in June. The loaner handoff should be part of the same intake flow, not a separate task someone remembers to do.

Record condition and, where damage is visible, take a photo. This is what supports a fee assessment later, and it is a five-second step at a moment when the device is already in your hands. If the district charges for damage, the photo at intake is the strongest documentation you will ever have.

Warranty first, then parts

The decision that has the largest financial impact is made in the first minute: is this covered? Standard manufacturer warranty typically covers defects and not accidental damage; many districts also buy accidental damage protection on Chromebooks, often for a fixed number of incidents per device per term. Knowing which applies, per device, before someone opens the case, is worth real money.

This requires warranty data at the device level rather than the purchase level. Two carts bought a year apart have different expiration dates, and if your only record is a purchase order date, technicians will guess and guess wrong. Store the warranty provider, type, and expiration on the asset, and surface it on the repair screen.

When a repair is warranty-eligible, the workflow is different: an RMA number, a shipping date, a vendor, and a wait. Track those as their own state so the ticket does not look like your technician is slow. Vendor turnaround is also a number worth knowing at renewal time.

When it is not covered, the question is repair-versus-replace. The honest math includes the part cost, the technician time, and how much useful life the device has left — a device three months from its ChromeOS auto-update expiration is rarely worth a screen. Districts that track AUE dates alongside repair costs make this call consistently instead of case by case.

Watch for the pattern where a single device accumulates repairs. A machine on its fourth repair is telling you something, and a per-device repair history with cumulative cost makes that visible at the counter rather than in an annual review.

Parts inventory, cost, and the reorder problem

Self-repair only saves money if you actually know what you spent. That means parts come out of a tracked stock: each screen, keyboard, palmrest, hinge kit, battery, and charging port has a quantity on hand and a unit cost, and consuming one on a repair decrements the count and records the cost against that repair.

The cost side is what makes fee schedules defensible and what lets you compare in-house repair against sending devices out. Without it, "we repair in house to save money" is a belief rather than a finding. With it, you can tell your business office that a screen replacement costs a specific amount in parts and roughly a specific amount in labor, and set the family fee to match.

Low-stock alerts prevent the most common operational failure: discovering you are out of the most common screen model in the middle of a repair backlog, with a two-week lead time. Set a reorder threshold per part based on your actual monthly consumption, and let the system tell you rather than relying on someone eyeballing a shelf.

Part compatibility is worth modeling if you have more than one Chromebook model, which every district does eventually. A screen that fits your 2023 fleet does not fit your 2021 fleet, and a technician pulling the wrong one wastes both the part and the visit. Associating parts with the models they fit turns this into a filtered list instead of tribal knowledge.

Harvesting parts from retired devices is standard practice and worth tracking too. When you strip a dead unit, the recovered parts should enter stock at zero cost, which makes your effective repair costs look correctly better.

Loaners and turnaround time

The loaner pool is the buffer that absorbs repair time, and its required size is a direct function of how long repairs take. If your average repair is in the queue for three weeks, you need roughly enough loaners to cover three weeks of intake volume simultaneously. Shortening turnaround is usually cheaper than buying more loaners.

Track loaners as real checkouts with the repair attached, so that closing the repair prompts the swap back. The failure mode here is well known: the original device is fixed, the student never comes to trade back, and the loaner effectively becomes theirs while the repaired device sits on a shelf. A list of repairs completed but not yet swapped back, reviewed weekly, closes that loop.

Measure turnaround as the full elapsed time from intake to the student having a working device back, not from when the technician started work. That is what the family experiences, and the difference between the two numbers is your queue delay, which is the thing you can actually manage.

Split the metric by whether the repair waited on a part or on a vendor. In-house repairs with parts in stock should turn around in days; anything waiting on a shipment is a supply chain problem with a different fix. Averaging them together hides both.

One useful practice: batch by symptom. A technician who does eight screen replacements in a row is dramatically faster than one who alternates between screens, keyboards, and software reimaging. If your queue view can group by symptom, turnaround improves with no other change.

What the repair data tells you at budget time

After a full year of tracked repairs you can answer questions that are otherwise guesswork. Damage rate per hundred devices, by building and by grade, tells you where to focus training or supervision, and whether the middle school's reputation is deserved. Cost per repair by symptom tells you which failure modes dominate.

Model-level failure rates are the most valuable output for purchasing. If one model in your fleet fails at three times the rate of another, that belongs in your next bid evaluation, and you will only know it if repairs are attributed to devices whose model you recorded.

Total annual repair spend against fleet size gives you a per-device annual maintenance cost, which is the number that makes a real comparison between buying cheaper devices more often and buying better devices with longer service life. It also feeds the accidental damage protection decision: if your out-of-pocket repair spend is consistently below the cost of the coverage, the coverage is not paying for itself.

And the warranty runway — how many devices fall out of coverage each quarter over the next few years — converts replacement planning into a schedule you can fund incrementally rather than a cliff.