Asset Management
The register of every asset InspectAssets tracks, plus QR scanning and offline field work.
How assets relate to sites
Assets belong to sites. A site is a location; assets are the individual pieces of equipment, fixtures, or infrastructure at that location. Inspections are conducted against assets, so an asset must exist before it can be inspected.
Adding assets
- From Asset Management, choose Add Asset (or Add Enterprise Asset on plans that include enterprise asset records).
- Assign it to a site, set its initial condition, and complete the identifying details.
- Save. The asset joins the register and becomes available for inspection scheduling.
Users with export_asset_register can export the full register for analysis outside InspectAssets.
The Asset Passport
The Asset Passport is the complete record for a single asset — the view you'll land on when you scan an asset that has no inspection due. It brings together:
- Recent inspection history — the last inspections against this asset, with dates and outcomes. New assets show "No inspection has been completed or scheduled for this asset yet."
- Health records — point-in-time condition readings. Use Add Health Record to log one manually; inspections with an "Asset Health" field add them automatically.
- Conditions — the asset's current assessed state.
- Documents — manuals, certificates, and photos, via Add Document.
- Costs — maintenance and replacement spend, via Add Cost, which builds a running total for the asset.
- Lifecycle events — installation, relocation, decommission, via Add Event.
Why health records matter
A single health record isn't very useful; a series of them is. Logging consistently is what makes the Asset Health Trend chart and Smart Recommendations meaningful — both work from this history.
Scanning assets
Scan Asset opens your device camera to read an asset's QR code. It's the fastest route when you're standing in front of the equipment. What happens next depends on the asset's state:
| If the asset… | InspectAssets… |
|---|---|
| has a scheduled inspection | opens that inspection so you can start immediately |
| has no scheduled inspection | opens its Asset Passport |
| can't be matched to the code | shows "No asset or inspection returned" |
If the camera won't start — poor light, a damaged label, or denied camera permission — you can type the code manually into the same screen instead of abandoning the scan.
Requires conduct_inspection. Scanning exists to start inspections, so it's gated on the same permission.
The Offline Queue
Field sites frequently have no signal. Work you do offline is stored locally and uploaded when connectivity returns; the Offline Queue is where you monitor that. It shows your current online/offline state, counts of queued and failed items, and when the last sync succeeded.
Items are queued (waiting), synced (uploaded), or failed (rejected — open it to see the error and retry that one item). Full detail in Inspections → Working offline.
Pending items are not yet saved to the server
Anything still queued exists only in your browser. Clearing site data before it syncs will lose that work permanently.
Asset Operations
Users with view_asset_operations get a cross-portfolio operational view of asset activity, rather than working asset by asset through the register.