Nobody owns the iPad, and that is exactly the problem. Tablets enter organisations as shared kit - the demo unit, the site-survey device, the inspection tablet in the van, the classroom set, the one that runs the signup desk - and shared means everyone uses them while no one answers for them. A laptop has a person attached; a tablet has a vague collective memory that “it was in the meeting room”. This guide covers the borrowing discipline and the register that keep a tablet fleet findable.
What you will learn
- Shared by everyone, owned by no one
- The borrow-and-return loop
- What to record per tablet
- Labelling tablets and their cases
- Home locations and charging carts
- Batteries, OS support and replacement
- Tools that make borrowing painless
- FAQ
Shared by everyone, owned by no one
The tablet failure pattern is distinct from every other device:
- “The iPad” is nine iPads. Identical units in identical cases cannot be told apart in conversation, so reports of where one went are useless.
- Loans are micro-loans. A tablet is borrowed for a demo, a shift, a site visit - durations so short that recording the loan feels absurd, until the unit does not come back.
- They travel in vehicles. Field tablets live in vans and pool cars, where “returned” means “left on the passenger seat”. Fleet-style operations - municipal teams are a classic case - lose more tablets to vehicles than to people.
- Chargers are communal chaos. Units get plugged in wherever there is a free cable, so even present devices are not where anyone looks.
The cure is not stricter people; it is a loop where borrowing takes seconds and absence is visible at a glance.
The borrow-and-return loop
Run every use of a shared tablet through the same four-step loop:
- Scan to borrow. The borrower scans the unit’s label, the loan is recorded against their name with a due-back time. For a shift, the due-back is end of shift; for a project, a date.
- One name per loan. “The survey team took three” is not a record. Three units, three names - the person who signed, not the team they sit in.
- Return to the slot. A return is complete when the unit is back in its home slot, charging, with the loan closed.
- Chase from the overdue list. A loan a few hours overdue is a quick message; one discovered weeks later is a search party. Reading the list is part of closing the day.
The whole loop stands or falls on speed. If checkout takes longer than simply walking off with the device, people will walk off with the device.
What to record per tablet
| Field | Why it matters |
|---|---|
| Asset ID | Turns “an iPad” into unit TB-07 - the precondition for everything else |
| Make, model, storage | Generations look identical but differ in OS support and value |
| Serial number | The manufacturer’s identity for warranty and support |
| Home location / slot | Where the unit should be - what makes absence visible |
| Current borrower + due back | The live answer to “who has TB-07?” |
| Status | In use, in storage, in repair, retired - keeps the pool count honest |
| Case and accessories | The rugged case and pencil that belong with this unit |
| Purchase date + price | Predicts the battery and OS-support cliffs per buying wave |
| Setup / image notes | Which configuration the unit carries - kiosk, field kit, demo |
Recording the setup matters more for tablets than most devices: a pool mixes units configured for different jobs, and rebuilding one to the right state - from a documented baseline or golden image - requires knowing which state that was.
Labelling tablets and their cases
Tablet labelling has one rule and one complication. The rule: the label goes on the device, because cases swap. The complication: rugged cases hide the device entirely, so a label sealed inside armour identifies nothing.
- Put a durable QR label on the back of the tablet itself, off-centre so it avoids the camera and charging contacts.
- On units in rugged or wallet cases, add a matching printed ID on the outside of the case - the case label is for daily identification, the device label is the truth when cases get shuffled.
- Scanning the code with a phone camera should open the unit’s record: current borrower, home slot, condition. That is what makes the borrow loop fast enough to survive.
Tip: number the charging cart slots to match asset IDs - TB-07 lives in slot 7. An empty slot then names the missing unit by itself, and the end-of-day check becomes a glance instead of a stocktake.
Home locations and charging carts
Every shared tablet needs a home: a numbered cart slot, a labelled cupboard shelf, a dock in the van. Homes do two jobs: they make absence visible - an empty slot is a question with a name on it - and they end the charging chaos, because returning and charging become the same action. The end-of-day sweep becomes a glance. Fold a deeper reconciliation into your periodic IT inventory check, but the daily glance is what keeps the fleet intact.
Batteries, OS support and replacement
Tablets age on two clocks. The battery fades with daily charge cycles until a unit cannot survive a shift unplugged - the slow decline users report as “the bad one”. And OS support ends on the manufacturer’s timetable, after which a functional device stops receiving security updates - for anything handling work data, a retirement notice. Purchase dates in the register show when each buying wave hits these limits, so replacement becomes a planned budget line. Retire units formally - wiped, status set, disposal noted - rather than letting them haunt the cart.
Tools that make borrowing painless
A sign-out sheet or spreadsheet fails the speed test that shared devices impose: nobody updates a sheet for a twenty-minute borrow, so the record only captures the loans that were never the problem. The missing tablet is always the one taken in a hurry, which is exactly the loan the sheet never saw.
AMPthilly makes the loop scan-fast: each tablet has a profile with serial, home location, case and setup notes; a printed QR label opens that profile in any phone browser - no app install - where the unit can be checked out or returned on the spot; loans carry due dates and feed an overdue list; and every borrow, return and repair stays on the unit’s history. The free plan covers 3 users and 25 assets with no card, which fits a typical shared tablet pool with room to spare.
FAQ
How do you keep track of shared iPads and tablets? One ID and label per unit, a home slot for each, and every use run through a named check-out with a due-back time - even short ones.
What is the best way to run a tablet check-out system? Scan to borrow, scan to return, units back in numbered slots, overdue list checked daily. Convenience first, or people bypass it.
Should you label the tablet or its case? The tablet always; the case additionally when rugged armour hides the device label. Cases swap, devices are the truth.
How do charging carts help with tablet tracking? Numbered slots matched to asset IDs make absence self-evident - an empty slot names the missing unit.
When should tablets be replaced? When the battery stops lasting a shift or OS updates end, whichever comes first. Purchase dates in the register predict both.
The takeaway
Shared tablets stay findable when borrowing is faster than taking and absence is visible without counting. Label every unit, give it a numbered home, run each use through a scan-based loan with a name and a due-back, and read the overdue list daily. The iPad question then changes from “has anyone seen it?” to “slot 7, due back at four, signed out by Sam.”