# Asset Management

> The asset registry and everything built on it - hierarchies, condition, risk, FCI, floorplans, QR codes, and reporting.

Source: https://app.assetlab.ca/docs/asset-management

Asset Management is the foundation the rest of AssetLab stands on. Get the registry right and every other module - maintenance, projects, planning, AI - inherits clean data.

## What lives here

| Area | What it covers |
|---|---|
| [Assets](/docs/asset-management/assets) | The registry itself - records, statuses, types, lifecycle data |
| [Sites, buildings & locations](/docs/asset-management/locations) | The physical hierarchy assets live in |
| [Classifications](/docs/asset-management/classifications) | The system hierarchy - Uniformat-aligned classes, groups, systems |
| [Custom fields](/docs/asset-management/custom-fields) | Organization-specific attributes per asset type |
| [Condition assessments](/docs/asset-management/condition-assessments) | Condition history and degradation projection |
| [Risk & FCI](/docs/asset-management/risk-and-fci) | CoF × LoF risk scoring and facility condition index |
| [Floorplans](/docs/asset-management/floorplans) | PDF floorplans with your assets pinned on them |
| [QR codes](/docs/asset-management/qr-codes) | Printable labels and mobile scanning |
| [Documents](/docs/asset-management/documents) | Manuals, drawings, photos, warranties |
| [Dashboards](/docs/asset-management/dashboards) | Portfolio-level analytics |
| [Reporting](/docs/asset-management/reporting) | Custom reports and exports |

## The design principle

Every asset is positioned in **two hierarchies at once** - where it is (site → building → location) and what it is (system class → group → system). Costs, condition, risk, and forecasts all roll up along both axes, which is what lets one platform answer both "what does Arena B cost us?" and "what's our HVAC backlog portfolio-wide?"

If you haven't read [Core concepts](/docs/start/core-concepts), start there.

## Typical build-out order

1. Locations first - sites and buildings.
2. Confirm classifications match how your organization talks about systems.
3. [Import](/docs/start/importing-data) or create assets.
4. Add lifecycle data (install year, useful life, replacement cost) where planning matters.
5. Start condition assessments on your critical systems.
6. Turn on dashboards and let the data compound.