A spreadsheet versus an asset register, honestly

Nearly every IT asset register in India starts as a spreadsheet, and for a lot of companies that is still the correct answer. Here is where the line actually is, what changes when you cross it, and how to cross it without losing a month.

When the spreadsheet is right — and it often is

Under about a hundred assets, with one person maintaining it and no auditor asking questions, a spreadsheet beats software on every axis that matters. It costs nothing, everyone can already use it, it has no permissions to configure, and it does exactly what you tell it. Anyone who tells you a fifty-device company needs asset management software is selling asset management software.

It is also the right answer during a transition. A one-off audit, a migration, an office move: pull the data into a sheet, work on it there, and put the result back. Spreadsheets are an excellent scratchpad and a poor system of record, and confusing those two roles is the actual problem.

The four failures, in the order they arrive

A spreadsheet asset register does not degrade gradually. It fails in four distinct ways, and each one arrives at a fairly predictable size.

• History disappears. A cell is overwritten when a laptop changes hands, so the sheet knows who has it now and can never tell you who had it in March. The first time that matters is usually a lost device or an HR dispute, and by then it is too late.
• Concurrent editing corrupts it. Two people, one file, and either a lock nobody can break or a "copy of" that becomes the real one. Shared cloud sheets soften this but introduce a worse version: silent overwrites that nobody notices for weeks.
• Nothing is enforced. Dell, DELL, Dell Inc. and Dell India are four vendors to a spreadsheet. Warranty dates become text. A serial number gets a trailing space. Your counts are wrong in ways that are invisible until you pivot on them.
• It cannot connect to anything. The sheet does not know the laptop has an open ticket, that the person left last month, or that the warranty expires in eleven days. Every connection has to be made by a human remembering to look.

Where the line is

From what we see, the crossover is not a device count so much as the arrival of any one of four conditions. Roughly: more than about one hundred and fifty assets; more than one person maintaining the register; anyone outside IT asking for a report from it; or an audit, an ISO certification or a licence true-up in your next twelve months.

Below all four, stay in the spreadsheet and put the effort into keeping it accurate instead. Above any one of them, the spreadsheet is costing you more in reconciliation time than software would cost in licence fees, and it is usually not close.

What actually changes when you move

Not "better visibility", which means nothing. Five concrete differences, and it is worth checking whether any of them are things you currently need.

• Every change is a dated record rather than an overwrite, so assignment history, repairs and location moves are answerable years later.
• The asset is linked to the tickets raised against it, so a laptop with five tickets in six months is visible as a pattern instead of five unrelated annoyances.
• Warranty, AMC and licence renewals raise a ticket ahead of the date instead of depending on someone opening the sheet.
• Onboarding and offboarding drive the register: issuing and recovering a device is part of the checklist, which is the only way a register stays accurate.
• Purchase date and value live on the asset record, so the finance number and the IT number start from the same source instead of two spreadsheets.

What you give up

Honesty requires this section. You lose the ability to do anything you like in a cell. A structured register will refuse a value it does not understand, and there will be a week where that is infuriating — usually around a field you were using for three different purposes.

You also take on a maintenance obligation. A spreadsheet that is six months stale is obviously stale; a system that is six months stale looks authoritative and is therefore more dangerous. If nobody will own keeping it current, do not move. The tool does not create the discipline, it only rewards it.

And there is a real, if modest, cost. You are trading licence fees against reconciliation hours, and below the crossover the spreadsheet genuinely wins that trade. We would rather say so than sell you something that sits empty.

Moving without losing a month

The migration everyone dreads is mostly avoidable, because the thing that takes the time is not the import — it is deciding what is true. Do it in this order:

• Clean the sheet first, in the sheet. Normalise vendor names, fix date formats, strip stray spaces from serials, and delete rows for things you no longer own. This is the whole job; everything after it is mechanical.
• Import only the fields you will actually maintain. A register with eight accurate columns beats one with thirty, of which nine are guesses.
• Start with laptops and desktops. Get one category completely right before adding monitors, phones and peripherals.
• Wire offboarding to the register on day one, so it stops decaying while you are still finishing the import.
• Keep the spreadsheet read-only for a quarter. Nobody trusts a new register immediately, and having the old one to check against costs nothing.

The cost nobody counts

When people compare a spreadsheet against software they compare zero against a licence fee, and that is the wrong comparison. The spreadsheet has a cost; it is just paid in hours by whoever reconciles it, and those hours are invisible because they are spread across a year and buried inside somebody's existing job.

Count them once and the picture changes. The annual physical audit where two people walk the floor with a printout. The morning spent working out which of three versions of the file is current. The afternoon before a board meeting reconciling the IT count against the finance asset schedule. The renewal that lapsed because nobody opened the sheet in time, and the emergency purchase at a list price that followed. Most mid-size IT teams we have asked put it between six and fifteen days a year, which is real money at a loaded engineer rate.

That still does not automatically favour software. Below the crossover the hours are few enough that the trade genuinely goes the other way, which is exactly why the line above is drawn where it is rather than at zero.

A free template, if you are staying put

If you read the above and concluded that the spreadsheet is still right for you — which is a perfectly good outcome for this page — we publish the asset register template we would use, free, with no email address required. It has the columns worth having and the validation rules written down, and if you ever do move, the import maps its columns to ours in one step.