Nobody Actually Knows Where the Laptops Are

Ask any IT team how many laptops the company owns and you will get a number, a short pause, and then a slightly different number. That pause is the whole subject. Every organisation has an asset register, and almost every one of them describes what someone intended to own rather than what is actually sitting in drawers, cupboards and kitchen tables across three offices.

The list is accurate on the day it is built

An asset register decays at every join and every leave, and the decay is never dramatic. A new starter is handed a spare from the cupboard and the row that says "spare" stays where it is. A machine is swapped under warranty and the record still carries the serial number that went back to the vendor. A contractor takes a device home for a project that quietly becomes a year. Nobody is lying. Each is a small shortcut taken by someone already late for something else, and six months of small shortcuts produce a document that is roughly 80 percent true and completely untrustworthy. The fix is less about counting than tying the record to an event: devices change hands when a person joins or leaves, so that process should write the register, not a Friday afternoon memory.

A missing laptop is not an inventory problem

When a device disappears, the first question is never where it is. It is what was on it, and when anyone last saw it. If the honest answer to the second is "sometime before March", you cannot answer a client, an insurer or a regulator, and you cannot tell a laptop left on a train from one that walked out with somebody's notice period. What saves you is boring paperwork: who signed for it, what date it came back, whether the disk was wiped and by whom, which ticket covers it. Most teams learn its value on the worst possible day, when a spreadsheet becomes evidence and the gaps stop being administrative and become a liability. Two fields do most of the work — assigned to, and last verified — but only if someone actually verifies them.

Licences are where the silence gets expensive

Software is where real money sits, and it fails in both directions. A project team needs thirty seats for a two-month push, the project ends, and the subscription renews for eleven more months because whoever requested it has moved on and nobody owns the renewal date. Multiply that across design tools, monitoring agents and three overlapping conferencing platforms, and the waste is a salary. The other direction is worse: an audit finds you running more seats than you bought, and the true-up arrives as an invoice with no negotiation room. The number that matters is not how many licences exist, it is how many are in use this week by a named person who still works here. Pulling that list quarterly takes an afternoon and pays for itself.

An honest list is a budget argument

Asset data has a second life most IT teams ignore. Finance does not want to hear that laptops are old; finance wants to hear that sixty machines pass their fourth birthday next year, that eighteen batteries are swelling, and that warranty cover expires on a specific date in a specific quarter. That turns a vague request for money into a plan with numbers attached. Teams that replace forty machines in one panicked quarter spend more and get worse hardware than teams that refresh predictably, because an emergency purchase is always the one with no negotiating room. Knowing the age distribution of your fleet is the difference between asking for a budget and being handed one.

Nobody will ever thank you for an accurate asset register. It produces no visible feature and no moment where a manager says well done. What it produces is the absence of one very specific bad afternoon: the audit you can answer, the laptop you can account for, the new starter whose machine already has their name on it. Then a device goes missing, and the gap between a two-minute answer and a two-week investigation is whether somebody kept the boring list current while nothing was going wrong.