Three hundred Chromebooks look like one Chromebook, three hundred times. Identical lids, identical chargers, and a student body that swaps, drops and forgets them daily - the only thing separating CB-0147 from CB-0148 is the tag on the lid and the record behind it. Schools running 1:1 programs or class carts lose devices not to theft but to ambiguity: the repair swap nobody wrote down, the leaver whose device went home in June, the loaner that became permanent. This guide covers the tagging, issuing and collection routines that keep a school fleet accounted for from August to June.
What you will learn
- Why Chromebook fleets drift
- The device record
- Asset tags that survive students
- Issuing devices: 1:1 and carts
- Repairs, loaners and mid-year swaps
- Year-end collection
- Tools that make this easier
- FAQ
Why Chromebook fleets drift
A school’s device register is usually accurate for exactly one week - the week of the rollout. Then:
- Repair swaps go unrecorded. A cracked screen comes in, a loaner goes out, the repaired unit returns to the wrong student or the spare shelf. Three devices have now moved; the list shows none of them.
- Identical devices invite quiet swapping. Students trade devices with friends, pick up the nearest one from the cart, or take home a classmate’s by honest mistake. Without a tag check, nobody notices for months.
- Transfers and leavers slip through. A student changes school mid-year; the device leaves with them, or sits in a former classroom, and the record still says “issued”.
- Chargers and cases evaporate. They are issued as part of the kit but tracked as part of nothing, so replacement chargers quietly become a budget line of their own.
None of this needs better students. It needs every device movement - issue, swap, repair, return - to leave a record at the moment it happens.
The device record
| Field | Why it matters for school Chromebooks |
|---|---|
| Asset tag ID | The human-readable identity - what teachers read out and labels show |
| Serial number | What repair shops, insurers and police reports require; pair it with the tag once, at enrolment |
| Model + purchase year | Fleets are bought in waves; the year tells you which devices age out together |
| Purchase price + funding source | Grant-funded devices often carry their own reporting and disposal rules |
| Status | Issued, in cart, in repair, loaner pool, retired - so the spare shelf is real |
| Issued to | The student, teacher or cart currently responsible |
| Condition notes + photos | The cracked corner that predates this student, documented fairly |
| Charger + case | Issued as a kit, returned as a kit - or visibly not |
Pair the asset tag with the serial number once, at rollout, while devices are still in the cart. Doing it later means handling every device a second time.
Asset tags that survive students
- Same spot on every device. Lid corner or underside near the hinge, clear of vents and the supplier’s own barcode. Consistency is what makes checking a class cart take minutes instead of a lesson.
- Durable stock only. Polyester or laminated labels with strong adhesive; paper tags lose to bored fingers within a term. Tags going under a protective case last longest of all.
- QR labels over numbers alone. A QR code scanned with any phone camera opens the device’s record on the spot - which is how a hallway “whose is this?” gets answered without a walk to the office.
- Tag chargers and cases with the device ID. A simple printed label is enough; the goal is reuniting kits, not tracking cables individually.
Tip: when tagging the fleet, photograph each device’s existing damage and attach the photos to its record. At year-end collection, “was that crack already there?” becomes a look-up instead of a standoff with a parent.
Issuing devices: 1:1 and carts
The check-in/check-out model fits schools naturally because the school year already has a built-in loan period:
- 1:1 issue. Device, charger and case are checked out to the named student - against a signed loan agreement where your policy requires one - with the last week of term as the due date. One scan per student keeps a rollout day moving.
- Cart devices belong to the cart. A cart is a location; its thirty devices are assigned to it. Daily classroom use needs no paperwork - the discipline is that any device leaving the cart for longer (a take-home exception, a repair) becomes a recorded check-out.
- Staff devices follow the same rules, which keeps the register complete and the policy fair.
- Transfers are events. A student moving classes or schools triggers a check-in or a recorded transfer - never a pencil edit to a name column.
The same pattern covers iPads and other 1:1 hardware; build the routine once and every device type rides on it.
Repairs, loaners and mid-year swaps
The repair loop is where most school registers die, because one broken screen moves three devices. Run it as paired events: the damaged device is checked in with the fault noted, a loaner is checked out to the same student, and the returning repair goes back to the student or the shelf - each step recorded. The loaner pool keeps its own status so it cannot silently shrink, and the repair history accumulating on each record is what tells you in year three that a particular model is not worth fixing again.
Year-end collection
Collection works from the register, not the hallway. The list of devices still checked out is the collection list: each device is checked in with charger and case confirmed and condition noted, and summer repairs are queued from the damage log. Whatever remains outstanding after the last day carries a student name, which is exactly what letters home require. Graduating years’ devices get marked retired or returned to the pool - never deleted, because the history answers questions long after the student has gone.
Tools that make this easier
Most schools start in a spreadsheet, and most discover the same thing: a sheet can hold the rollout list, but it cannot keep up with a year of swaps, repairs and transfers entered by busy staff in stolen minutes - the reasons are laid out in why Excel fails for asset tracking.
AMPthilly is built for the event-driven version: every device gets a profile with serial, purchase details, photos and documents; the fleet imports from CSV and labels print in bulk; the QR tag on each lid opens the device record in any phone browser - no app for staff to install; issues, returns, swaps and transfers are logged events with a permanent audit history; and damage is reported with photos straight from a scan. The free plan covers 3 users and 25 assets - enough to pilot the routine on one device cart before a whole-school rollout.
FAQ
How do schools keep track of Chromebooks? A tag on every device, a register pairing tag to serial to student, and a recorded check-out or check-in at every hand-over.
What asset tags work best on Chromebooks? Durable polyester QR labels in the same spot on every device - lid corner or underside near the hinge, clear of vents and the supplier barcode.
How does a Chromebook check-out system work in a 1:1 program? Device, charger and case are checked out to the named student with the end of year as the due date; swaps and transfers during the year are recorded events.
What should a school Chromebook inventory record? Tag ID, serial, model and purchase year, price and funding source, status, current student or cart, condition photos, and the charger and case in the kit.
How do you handle Chromebook repairs and loaner devices? Check the broken unit in with the fault noted, check a loaner out to the same student, and record the return leg - three movements, three records.
How should year-end Chromebook collection work? Work from the still-checked-out list, check kits in with condition noted, queue summer repairs from the damage log, and follow up the remainder by name.
The takeaway
A Chromebook fleet stays accounted for when identity and movement are both nailed down: a durable tag in the same place on every device, the tag paired to the serial once at rollout, and every issue, swap, repair and return recorded as it happens. Do that, and June’s collection becomes a checklist instead of an amnesty. The schools that manage it are not stricter - their records simply update at the moment devices move, which is the only time anyone truly knows where a device is.