How to build an asset register

An asset register is the foundation of everything else in asset management. Tagging, check-outs, audits, maintenance and depreciation all depend on it. A well-designed register makes those processes simple. A poorly designed one — inconsistent categories, free-text locations, duplicate IDs — makes every one of them harder.

This guide walks you through building a register from scratch, or rebuilding one you have inherited: scope, ID scheme, fields, categories, locations, financial data, data-quality rules, data collection and the processes that keep it current.

What an asset register is

An asset register is a structured list of the assets an organization owns or controls, with one record per asset containing identification, location, custody, status, and financial and maintenance information.

Two audiences use it:

• Operations needs to know what exists, where it is, who has it and what condition it is in.
• Finance needs cost, depreciation and net book value for capitalized fixed assets.

A good register serves both from a single set of records. Separate operational and financial lists always drift apart.

Step 1: Define purpose and scope

Decide, in writing:

• Which assets are in scope. All capitalized assets? Also portable items below the threshold? Leased equipment? IT hardware only, or all equipment?
• Your capitalization threshold. Set by accounting policy — for example, items above a certain cost with a life of more than one year are capitalized. Items below it can still be tracked, flagged as non-capitalized.
• Which sites and entities are included, and whether each needs to be reported separately.
• Who owns the register — the person accountable for its accuracy.

A good rule: track anything that is valuable, portable, shared, or safety-critical, whether or not it is capitalized.

Step 2: Design the asset ID

Every asset needs a unique identifier that never changes and is never reused.

• Keep it meaningless. Do not encode location, department or category in the ID. Assets move; organizations restructure; the ID should survive both.
• Keep it short and unambiguous. A prefix and a sequence number, such as AST-004812, is ideal. Avoid characters easily confused, like O and 0, or I and 1, in any alphabetic part.
• Pad the number to a fixed length so IDs sort correctly.
• Print it in human-readable text on every tag, alongside any barcode, QR code or RFID encoding.

Record the manufacturer's serial number separately. It is not your ID, but it is invaluable for matching during reconciliation and for warranty claims.

Step 3: Choose your fields

Start with a core set and add category-specific fields only when you will actually use them. Every field you add is a field someone must maintain.

You can download a ready-made structure from the free asset register template.

Step 4: Build a category structure

Categories drive reporting, default depreciation settings and which fields apply. Design them carefully:

• Two levels are usually enough — for example, Vehicles › Light commercial or IT equipment › Laptops.
• Align top-level categories with your fixed-asset classes in the general ledger, so reports reconcile easily.
• Set defaults per category — useful life, depreciation method, maintenance intervals, tag type.
• Use a fixed list, never free text. "Laptop", "Laptops" and "Notebook" must not all exist.

Step 5: Model your locations

A location hierarchy lets you report at any level and scope audits precisely:

Site › Building › Floor › Room (or Zone)

Tips:

• Use the names people actually use, but keep them unique.
• Go only as deep as you need. If you never audit by room, stop at floor.
• Include non-building locations: vehicles, off-site storage, repair vendors, "in transit".
• If you plan to use RFID readers, design the hierarchy so each reader's coverage maps to a meaningful location or zone.

Step 6: Define custodians

Location answers where; custodian answers who. For portable equipment, custody often matters more. Decide whether custodians can be people, departments, projects or sites, and use a controlled list linked to your staff directory where possible. Every asset should have a responsible owner — even if it is a department head for shared equipment.

Step 7: Define statuses

Keep the status list short and unambiguous. A typical set:

• In stock — owned, not yet deployed.
• In use — deployed.
• Checked out — on loan with a due date.
• In maintenance — at repair or service.
• Missing — not found in an audit; under investigation.
• Disposed — sold, scrapped, donated or written off. Keep the record; never delete it.

Statuses should change through processes (check-out, work order, disposal), not by hand where you can avoid it. That is how the asset lifecycle becomes visible in the data.

Step 8: Capture financial data

For capitalized assets, record at acquisition:

• Cost — including directly attributable costs such as delivery and installation, per your accounting policy.
• In-service date — when the asset is ready for use; depreciation usually starts here, not at invoice date.
• Useful life and salvage value.
• Depreciation method — often defaulted from the category. See fixed asset depreciation explained.
• Book and tax treatment, if they differ.

For assets migrated from an older system, bring in cost and accumulated depreciation at a cut-off date, agreed with your accountant.

Step 9: Set data-quality rules

Decide what "complete" means and enforce it:

• Mandatory fields for every record: ID, description, category, location, status, custodian.
• Additional mandatory fields for capitalized assets: cost, in-service date, useful life, method.
• Controlled lists for category, location, status, custodian.
• Consistent formats for dates and currency.
• No duplicate serial numbers within a manufacturer.

Step 10: Collect the data

There are two sources, and you usually need both.

Desk-based: fixed-asset ledgers, purchase records, IT inventories, existing spreadsheets. These give you cost and dates but often have wrong or missing locations.

Walk-through: physically visit every area, tag each asset and record what you find. This gives you truth about existence and location.

The best approach is to prepare a draft register from desk sources, then verify it with a walk-through — effectively a first physical audit. Items in the draft that are not found, and items found that are not in the draft, become your first reconciliation list.

Tagging during the walk-through

Tag as you go: apply a pre-printed label, scan it, and link it to the matching record — or create a new record if the item was not in the draft. Take a photo. Record the serial number. See QR code asset tracking for label choices.

Special cases to decide up front

Every register runs into the same edge cases. Deciding them before data collection saves arguments later.

Parent and child assets

Some assets contain other trackable assets: a vehicle with a mounted generator, a server rack with servers, a test kit with several instruments. Decide whether the parts get their own records. A good rule: give a part its own record if it can be removed and used separately, has its own serial number, is maintained or calibrated separately, or has a materially different useful life. Link child records to the parent so that moving or disposing of the parent prompts a decision about the children.

Kits and sets

A set of tools that always travels together can be one asset with one tag, or several assets issued together. If items within the set get lost or replaced individually, track them individually and issue them as a group.

Low-value, high-volume items

Chairs, basic hand tools and similar items can overwhelm a register if every unit is recorded. Options include tracking them as a quantity at a location rather than individually, or recording only the categories that are genuinely at risk of loss. Be consistent: whichever option you choose, apply it per category.

Leased, rented and borrowed equipment

Record equipment you control but do not own — leased vehicles, rented plant, loaned demo units — so you can track and return it, but flag it clearly so it is never capitalized as your own. Record the lease or return date so it can be managed.

Assets with remote users

Laptops and phones issued to remote staff are rarely in any building you can audit. Record the person as custodian, and plan for remote verification — for example, periodic self-confirmation by scanning the asset's tag.

Description conventions

Descriptions are what people search for. Agree a simple pattern — for example, type, key attribute, model ("Laptop, 14-inch, Latitude 5440") — so that searching "laptop" finds all laptops, and avoid internal nicknames that newcomers will not know.

A worked example: first build for a small organization

Illustrative example. A training college with two buildings wants a register of equipment and furniture.

1. Scope: all capitalized assets (policy threshold set by finance) plus laptops, projectors and tools below the threshold. Leased photocopiers are tracked but flagged as leased.
2. IDs: COL-00001 onward, printed on polyester QR labels.
3. Categories: eight top-level categories aligned to the fixed-asset ledger, each with two to five subcategories.
4. Locations: college › building › floor › room, plus "off-site" and "at repair".
5. Desk sources: the fixed-asset ledger and the IT inventory produce a draft of about 600 records.
6. Walk-through: two pairs label and scan room by room over three days. They find 540 of the draft records, and 85 items not in the draft.
7. Reconciliation: 540 found + 60 not found = 600 draft records. The 60 not-found records and the 85 unregistered items are investigated; several turn out to be the same items with missing serial numbers, and the rest are resolved as disposals, additions or leased equipment.
8. Go-live: check-out is introduced for laptops and projectors, and a cycle-count calendar is set.

The result is a verified baseline rather than a copy of the old ledger — which is exactly what the first build should produce.

Step 11: Keep it current

A register is accurate on the day it is built and starts drifting the next day, unless every change in the physical world has a matching process:

Step 12: Governance

• Name a register owner accountable for accuracy.
• Restrict who can edit what with role-based permissions — not everyone should be able to change costs or dispose of assets. See RBAC.
• Keep an audit trail of every change.
• Review regularly — data-quality reports monthly, register accuracy after every audit.

Spreadsheet or software?

A spreadsheet can hold a small register maintained by one person. Once several people update it, assets move frequently, or you need scanning, history and access control, dedicated software pays for itself. Moving from Excel to asset management software covers the tipping points and migration steps.

Building your register in Asetavo

Asetavo's asset register provides the structure described in this guide: unique IDs, categories with defaults, a location hierarchy that also drives zones, custodians, statuses, photos and documents, and a full history on every asset — plus per-category custom fields from the Growth plan and warranty and contract tracking on Business. Tagging links QR, barcode, NFC and UHF RFID tags to records, including mobile commissioning during the walk-through. Financial fields feed depreciation, and everything exports to CSV or through the REST API.

If you already have a spreadsheet, our team imports it for you during onboarding — we map your columns with you and you verify the result before going live. The Starter plan is free for up to 100 assets — see pricing.