Laptops are the most mobile, most expensive, most personal equipment most companies own - and the easiest to lose track of. They go home with employees, travel to client sites, get swapped during repairs, and quietly change hands when someone leaves. This guide covers a tracking system that survives all of that: what to record per machine, how to label the fleet, and how a check-out model keeps every laptop attached to a name.
What you will learn
- Why laptops go missing
- What to record for every laptop
- Labelling the fleet
- Assignments: the check-out model
- Lifecycle: warranty, refresh, retirement
- Tools that make this easier
- FAQ
Why laptops go missing
Hardly any company loses a laptop in the dramatic sense. What actually happens is quieter:
- The record goes stale, not the laptop. A spreadsheet is updated at purchase and never again. Two role changes later, the “assigned to” column is fiction.
- Loaners never come back. A spare issued “for the week” while a machine is in repair becomes a second laptop nobody remembers issuing.
- Offboarding has no checklist line. The leaver returns a badge and a charger; the laptop is “somewhere in their home office” and the conversation never happens.
- Repairs and swaps break the chain. A machine goes to the repair shop, a replacement is issued, and the register now describes a fleet that doesn’t exist.
None of these are people problems. They are record problems - the fix is a register that gets updated by the workflow itself, not by someone remembering to edit a sheet.
What to record for every laptop
A useful laptop record answers four questions: what is it, what did it cost, what state is it in, and who has it. In practice:
| Field | Why it matters |
|---|---|
| Asset ID | Your own unique number - what the label shows and what people quote |
| Make, model, spec | Distinguishes the i5 from the i7 when someone says “a black ThinkPad” |
| Serial number | The proof for warranty claims, insurance, and police reports |
| Purchase date + price | Drives depreciation, refresh planning, and insurance value |
| Warranty end date | The difference between a free repair and a new machine |
| Status | In use, in storage, in repair, retired - so spares are findable |
| Current assignee | The single most-queried field in any laptop register |
| Condition notes + documents | Receipts, repair invoices, and damage photos in one place |
Record the serial number at purchase, before the machine is deployed. Reading it later means chasing the laptop you are trying to track.
Labelling the fleet
A label turns “a black laptop” into asset LT-0042 in two seconds. For laptops specifically:
- Use a QR asset tag with the asset ID printed beneath it. A QR code scanned with a phone camera can open the asset’s record directly - useful when IT isn’t at a desk. The printed ID is the fallback for over-the-phone conversations.
- Place it on the underside, near the hinge. Visible when you flip the machine, protected from daily wear, and away from vents.
- Label chargers and docks too, or accept that you’re buying new ones. A cheaper printed label is fine - the goal is “return this to IT”, not full history.
- Choose durable stock. Paper labels peel within a year of bag-friction; polyester or laminated labels survive the life of the machine.
Tip: label new machines as part of the imaging/setup step, so nothing reaches an employee untagged. Retro-labelling a deployed fleet is a one-time project; keeping up with new arrivals is a habit.
Assignments: the check-out model
The core discipline is simple: a laptop is either in storage or checked out to exactly one named person. No shared pools, no “the design team has it”.
A working checkout flow looks like this:
- Issue: when a laptop is handed over, record the assignment - who, when, and any due date if it’s a loaner. Bundle the monitor, dock, and bag into the same checkout during onboarding so the whole kit has one record.
- Transfer: when a machine moves between people, record it as a transfer, not as an edit to a name field. The history is what makes the record trustworthy.
- Return: at offboarding or refresh, check the machine back in and note its condition. The open-assignments list is your offboarding checklist - anything still out has a name attached.
- Review: scan the overdue and still-out list periodically. A loaner that’s three weeks past due is recoverable; one nobody noticed for a year usually isn’t.
This is also where laptops differ from most equipment: each one carries data. Tie your return step to your account-deactivation and wipe process, so the physical and digital sides of offboarding happen together.
Lifecycle: warranty, refresh, retirement
The register pays for itself at the ends of a laptop’s life, not the middle:
- Warranty: filter machines by warranty end date before paying for repairs - a surprising number of “broken, bin it” laptops are still covered.
- Refresh planning: purchase dates across the fleet tell you what next year’s replacement budget actually needs to be, instead of discovering thirty machines hit end-of-life in the same quarter.
- Retirement: mark retired machines rather than deleting them. The record of what happened to a data-bearing device - returned, wiped, recycled, sold - is exactly what a security review or GDPR question will ask for. Keep the disposal note attached to the asset.
Tools that make this easier
You can run all of the above in a spreadsheet, and many teams start there - the columns in the table above map directly. The failure mode is the update discipline: spreadsheets record states, not events, and nobody edits a sheet from the storage cupboard.
An asset management tool like AMPthilly bakes the workflow in: each laptop gets a profile with serial, purchase, warranty, and documents; checkouts and returns are recorded events with a full history; printable QR labels open the right record from any phone browser; and offboarding is a filtered view of what’s still out. The free plan covers 3 users and 25 assets - enough to pilot a real laptop register before paying anything.
FAQ
What is the best way to keep track of company laptops? Unique asset ID, durable label, serial number on record, and a named assignee for every machine that leaves storage. Assignment-as-an-event is the habit that keeps the register true.
How do I track which employee has which laptop? Check-out and return. Record issues and returns as events with dates, and the register always shows current holder and history - which is what offboarding and audits actually need.
Should I put asset tags on laptops? Yes - QR or barcode labels with the asset ID, on the underside near the hinge, on durable stock. Tag chargers and docks with simpler labels.
How often should laptops be audited? Full reconciliation once or twice a year, a check at every offboarding, and quarterly spot-checks if machines move often.
What should a laptop inventory include? Asset ID, make/model, serial, purchase date and price, warranty end, status, current assignee - plus condition notes and attached documents if you want the record to hold up later.
The takeaway
Laptop tracking fails at the moments laptops change hands, so build the system around those moments. Record machines fully at purchase, label them before deployment, treat every issue and return as an event, and let the open-assignments list drive offboarding. Do that, and “who has LT-0042?” is a lookup - not an investigation.