How to create an asset register: a practical guide
What goes into a useful asset register, how to structure it, and why most organisations discover the gaps at the worst possible moment.

An asset register is a record of what a business owns: the physical assets — equipment, furniture, machinery, vehicles, IT hardware — that have financial value and operational significance. It answers the question "what do we have, where is it, and what's it worth?"
Done properly, it's one of the most useful documents in an organisation. Done carelessly — which describes most of them — it's a spreadsheet that gets updated when something breaks and ignored the rest of the time.
The gap between a register that's genuinely useful and one that's technically present but practically useless comes down to structure. This guide covers what an asset register needs to contain, how to build it from scratch, and what the common mistakes are.
Why asset registers matter more than most organisations think
The immediate reason to maintain an asset register is financial: fixed assets need to be recorded for accounting purposes, depreciation needs to be calculated, and insurance policies need to cover what you actually own.
But the operational reasons are often more valuable. An organisation that knows exactly what it owns — and what condition each asset is in — can plan maintenance proactively rather than reactively, budget for replacement before things fail, and demonstrate compliance when it matters (fire risk assessments, regulatory inspections, lease-end dilapidations).
For property-intensive businesses — hotels, student accommodation operators, care homes, multi-site retailers — the asset register is also the foundation of any credible CapEx planning process. Without knowing what's in each property and how old it is, the replacement budget is a guess.
What a complete asset register contains
Most asset registers capture the basics. The ones that are actually useful capture more:
Identity fields — what is it?
- Asset name and category (furniture, electrical, IT, plant, vehicle, etc.)
- Manufacturer and model
- Serial number or asset tag reference
- Specification detail (dimensions, capacity, configuration)
Location fields — where is it?
- Property or site
- Building, floor, and room
- Zone within the room
Financial fields — what is it worth?
- Purchase price (original cost)
- Purchase date
- Supplier
- Depreciation method and rate
- Current book value
- Replacement cost (current market, not original)
Condition and lifecycle fields — how long will it last?
- Current condition (a simple rating: good, fair, poor, end-of-life)
- Expected service life (years from new)
- Estimated replacement year
- Last maintenance date
- Warranty status and expiry date
Compliance fields — what does it need to prove?
- Applicable standards or regulations
- Inspection dates
- Certificate references
The identity and financial fields are what most organisations capture. The condition and lifecycle fields are what make an asset register genuinely useful for planning rather than just reporting.
Building an asset register: the practical steps
Step 1: Agree the scope. Decide what categories of assets to include. Typically: fixed plant and machinery, IT equipment, vehicles, and in property-intensive businesses, furniture and fittings. Exclude consumables (items you'd buy again in months). For the purposes of a physical property like a hotel or care home, FF&E — furniture, fixtures and equipment — is the core category.
Step 2: Choose your format. For organisations with fewer than 200–300 assets, a well-structured spreadsheet works. Above that, or where multiple sites are involved, a database or dedicated asset management system becomes worth the investment. The key criterion: can the person responsible for this in three years navigate and update it without a briefing?
Step 3: Conduct a physical walk-through. Don't build the register from memory or existing documents. Walk every space in the property and record what's there. This will surface assets that aren't in any existing record and assets in existing records that no longer exist. Both categories matter.
Step 4: Populate the minimum viable fields. For each asset: name, location, manufacturer/model, purchase year, current condition, estimated replacement year. Get this done for every asset before adding more detail. Completeness matters more than depth at the initial capture stage.
Step 5: Add financial and compliance data. Once the physical record exists, layer in the financial data: purchase prices from invoices, depreciation calculations, current book values. Then add compliance data: warranty certificates, fire certificates for upholstered furniture, service records for plant.
Step 6: Assign ownership and set a review cycle. An asset register that isn't regularly reviewed decays. Assign one person (or role) as responsible for keeping it current. Set a minimum annual review cycle — more frequent for assets with active replacement programmes.
Common mistakes when building an asset register
Recording what you think you own rather than what you actually have. The purchase order says twelve conference chairs. The actual number in the room is eleven. Building the register from procurement records rather than physical inspection produces a record that's systematically wrong.
Aggregating what should be itemised. "Conference room furniture: £12,000" tells you almost nothing useful. "12 × stackable conference chairs, Orangebox Air, dark grey, 2021, £185 each, 7-year expected service life" tells you when they need replacing and what they cost to replace.
No condition assessment — just a list. A register that records what exists but not its condition is useful for accounting but not for planning. Knowing that you have forty bedroom armchairs is less useful than knowing that twenty of them are in poor condition and need replacing within eighteen months.
Using purchase cost without updating to replacement cost. Original purchase prices become progressively less accurate as years pass. For planning purposes, the cost that matters is today's replacement cost — which, in a period of materials inflation, can be significantly higher than what you paid. Registers that don't track this lead to replacement budgets that arrive under-funded.
Asset registers in hospitality and property management
For hotels, student accommodation operators, care homes, and similar property-intensive businesses, the asset register intersects with a specific requirement: the FF&E specification record that was created at the time of fit-out.
The specification record — assembled by the interior designer and procurement company during the project — contains precisely the detailed product information that a good asset register needs: manufacturer, model, reference, dimensions, compliance certificates. The problem is that this data is typically delivered in a format (PDF specification documents) that doesn't flow into an operational asset register without significant manual effort.
The opportunity is to bridge that gap at the point of handover: to take the structured specification data from the fit-out project and use it as the starting point for the property's live asset register. This transforms what is usually a one-off project document into an ongoing operational tool.
Controlbook is designed to do exactly this — maintaining the live FF&E record that carries specification data from fit-out through the property's operational life. Book a demo to see how it works.
Frequently asked questions
What's the difference between an asset register and a fixed asset register?
A fixed asset register typically refers specifically to the accounting record of capitalised fixed assets — items with a purchase cost above a certain threshold that are depreciated over time rather than expensed immediately. An asset register is a broader term that may include both capitalised fixed assets and lower-value items tracked for operational rather than accounting purposes.
Does an asset register need to be audited?
For accounting purposes, the fixed asset register is subject to the same audit scrutiny as other financial records. For operational asset registers, a formal audit isn't usually required, but a periodic physical verification — walking the property and checking that the register matches reality — is good practice. An unverified register will drift from accuracy within a few years.
How do I handle assets that span multiple sites?
Multi-site asset registers need a clear location hierarchy: organisation → property → building → floor → room. Every asset should have a location code that places it precisely in that hierarchy. Without this, the register is usable for financial reporting but not for operational planning, where knowing which specific building has the oldest furniture is the question that matters.
What format should an asset register be in?
For small organisations (fewer than 200 assets), a shared spreadsheet in a cloud service (Google Sheets, Excel Online) is practical. For larger organisations or multi-site operations, a database or dedicated asset management system provides better filtering, reporting, and access control. The format matters less than the discipline to keep it current.
How often should an asset register be updated?
Whenever an asset is added, disposed of, or significantly modified — and at minimum once a year as a full reconciliation exercise. For active FF&E replacement programmes, a rolling update process (logging each replacement as it happens) is more accurate than a once-a-year review that relies on memory.