Free asset register template for Excel — and the five columns everyone forgets
Every organisation needs one list of what it owns. Download a free Excel asset register template, see which columns actually earn their place, and learn where a spreadsheet register quietly stops being true.
In this article:
- The core columns
- The five columns everyone forgets
- Structure tips that save you later
- Where the spreadsheet register stops being true
Somewhere between the insurance renewal that asked "what exactly do you own?" and the auditor who asked it again, every organisation concludes the same thing: we need one list. Not the finance system's depreciation schedule, not the warehouse's memory — one register of the physical things the business owns, where they are, and what state they're in.
Start it in Excel. Genuinely — it's the fastest way to get from nothing to complete. Our free equipment database template gives you a working structure out of the box; this article explains the thinking behind the columns, so you can adapt it instead of trusting it blindly.
The core columns
| Column | Why it's there |
|---|---|
| Asset ID | One unique code per item, forever. This is the register's spine — every label, log and repair refers to it. Never reuse an ID, even after disposal. |
| Name + model | "Makita DHP482 drill", not "drill". Precision here is what makes duplicates visible. |
| Category | Power tools, AV, vehicles, IT… — the axis you'll filter and total by. Pick 8–15 categories, resist inventing forty. |
| Location | Where it normally lives. Site, building, room, van — whatever granularity you'd search by. |
| Responsible person | The single name that answers for the asset. Not "operations". |
| Purchase date + price | The base for insurance claims, depreciation and replace-or-repair calls. |
| Status | In use / in storage / in repair / retired. The column that keeps ghosts out of your totals. |
The five columns everyone forgets
These are the difference between a list and a register you can act on:
- Serial number. The only identifier the police, the insurer and the warranty desk all accept. Photograph it while the asset is new and clean.
- Condition. A simple scale — good / fair / poor / broken — reviewed when the asset is touched, not annually. Condition trends are your early-warning system; we've written about what condition data unlocks on the maintenance side.
- Warranty end date. The most expensive blank cell in most registers: repairs paid for out of pocket on assets still under warranty.
- Service interval. "Every 6 months" or "every 200 hours". Without it the register can't tell you what's overdue — and a register that can't generate a to-do list is just a memorial.
- Photo. One picture per asset settles more identification arguments than any text field, and doubles as condition evidence for insurance.
Structure tips that save you later
- One row per physical unit, not per model. Three identical drills are three rows with three IDs — because they'll live three different lives.
- A "retired" status, not a delete key. Removing rows destroys history exactly when you need it (disposal audits, insurance, theft reports).
- Data validation from day one. Dropdowns for category, location, condition and status. Free-text versions of those columns rot within a month ("AV", "A/V", "audio-video"…).
- Label the asset with its ID the day it enters the register — tape and marker beats nothing; printed QR labels mean anyone can pull up the record by pointing a phone at it.
Where the spreadsheet register stops being true
A register has one measure of success: does it still match reality in six months? Excel's weakness isn't building the register — it's keeping it true, because every change depends on a human remembering to type it. The pattern we see over and over:
- Assets move; the location column doesn't.
- Two people edit; one overwrites the other.
- Service intervals exist as text, but nothing fires when they lapse.
- Somebody borrows the projector; the register has no concept of "out".
The fix isn't discipline — it's connecting the register to the events that change it. In an equipment management system, the register updates itself: a checkout moves the asset and records the holder, a repair changes status, a service marks the interval done and schedules the next one. The spreadsheet columns don't disappear — they just stop depending on anyone's memory. (When you're ready, the register imports straight from the spreadsheet — the work you did in Excel is the migration.)
Until then: download the template, block out an afternoon with a label maker, and build the list. An imperfect register you own beats the perfect one you keep postponing.
Frequently Asked Questions
-
A single authoritative list of the physical assets an organisation owns — equipment, tools, vehicles, IT — with enough detail per asset to answer what it is, where it is, what condition it's in, what it's worth, and who is responsible for it.
-
Per asset — a unique ID, name, category, location, person responsible, purchase date and price, current condition, service requirements, and status (in use, in repair, retired). Serial numbers, warranty end dates and photos raise the register from list to evidence.
-
For building the first complete register, yes — a spreadsheet is the fastest way to get everything written down. It struggles as a living document — multiple editors, movement tracking, maintenance triggers and checkout history all fight the format. Build in Excel, then migrate when the register needs to stay true by itself.