Moving your asset register off Excel without losing history
A spreadsheet is a perfectly good asset register right up until it is not. Here is how to tell which side of that line you are on, and how to move without losing what you already know.
Almost every IT team we meet runs the asset register in Excel. That is not a failure of discipline — for a long time it is genuinely the right tool. The question worth asking is not "should we be in a spreadsheet" but "has the spreadsheet stopped telling the truth".
Four signs it has
- You reconcile before an audit. If the register needs preparing, it is a document rather than a record.
- Only one person can update it confidently, and they are the bottleneck for every question.
- You have found the same serial number twice, or a machine assigned to somebody who left.
- Warranty and AMC dates are in there, and nobody has looked at them since the last renewal.
The cost is not the spreadsheet. It is the two hours before every audit, the laptop written off because nobody noticed the warranty had three weeks left, and the licence still being paid for somebody who left in March.
Why a better spreadsheet does not fix it
The spreadsheet drifts because updating it is a separate chore from the work that changes it. A laptop is reassigned in a hurry on Tuesday; the row gets updated on Friday, or it does not. No amount of data validation changes that, because the problem is not the format.
What fixes it is making the ticket and the device the same record, so the register updates as a by-product of work somebody was doing anyway. The engineer sends a machine for repair; its state changes because that is what sending it for repair means, not because somebody remembered.
Do not clean the spreadsheet first
This is the advice people find hardest to accept, and it saves the most time. Import the file as it is, read the error report, and fix what the error report points at.
A good importer will tell you, row by row, exactly what is wrong — duplicate serials, dates it cannot read, employees it cannot find. That list is a far better cleaning brief than your own sense of what is probably untidy, and it takes ten minutes instead of a weekend.
The order that works
- Import employees first. Assets reference people, not the other way round.
- Import assets with no assignments — just the kit, with serials.
- Check the counts against your own total, then spot-check twenty rows by hand.
- Then import assignments, or assign in bulk from the asset list.
- Only now start using it for new work.
Serial numbers are the anchor
Everything downstream — reconciling against an endpoint agent, matching a warranty claim, proving what somebody was given — hangs off the serial. Two rules: it must be unique across every status including disposed, and a machine with no readable serial gets an internal tag with a consistent prefix rather than a blank.
A register with several blank serials cannot be reconciled against anything, and you will not discover that until the first time you try.
What you keep from the old file
Everything that is a fact: serial, model, purchase date, value, who has it now. What you lose is the history you never recorded — who had it before, when it went for repair. That is unavoidable, and it is also the last time you will lose it.
Keep the original file, read-only, somewhere sensible. You will want it once, six months from now, to settle an argument about what something cost.
Depreciation, and why finance should be in the room
The IT asset count and the finance asset schedule are almost always two different numbers, and nobody notices until year end, when reconciling them becomes somebody's unpleasant week. The move off the spreadsheet is the cheapest opportunity you will get to make them agree, because you are touching every row anyway.
Ask finance for their schedule before you import. Match on invoice number where you can and on serial where you cannot. Where the two disagree, the disagreement is itself the finding — usually kit that was written off but is still in use, or kit that was bought and never recorded on either side. Import the purchase date, the cost excluding GST and the invoice number, note alongside each asset the depreciation finance already uses, and from then on both numbers start from the same records.
Keeping it accurate after the import
A register decays unless updating it is a by-product of work people were already doing. Two hooks do most of the work: issuing a device is part of onboarding, and recovering one is part of offboarding. Wire those on the first day, before the import is even finished, and the register stays roughly right on its own.
Then verify once a year rather than continuously. A physical audit of one category — laptops, usually — takes an afternoon and tells you whether the process is holding. If it is, do nothing else. If it is not, the gap will point at exactly which hook is being skipped.
What changes in the first month
- Assigning a device puts the handover document one click away, ready to print and sign.
- An exit cannot be closed while the kit is outstanding — and the override, when somebody uses it, is recorded.
- Warranty and AMC end dates sit on the dashboard and in reports rather than in somebody's memory.
- The question "who has that laptop" is answered in five seconds by anyone, not in an hour by one person.
The import template is the same file the importer expects, so what you download always loads cleanly. Download the template
Tagged: Asset Register · Templates