Unlocated Assets and Location Cleanup

Unlocated assets lack a reliable room, floor, area, or location assignment, often arriving from imports, old spreadsheets, API syncs, or quick manual entry. Rivolq holds them safely, but cleanup keeps floor plans, scanning, work orders, history, and reports trustworthy. If an asset is important enough to maintain, it should usually have a real location.

Why it matters

Accurate locations help users find equipment, pin assets, assign work to the right area, interpret dashboard and report counts, review history by room, floor, or building, avoid duplicate creation during imports, and understand dependency and spatial context. How the tree and the Unassigned node fit together is in Facilities and the location model.

Use the unlocated-assets page

Open the cleanup page from Assets to bulk assign missing locations. It lists assets that need a real location and lets you choose a target from the facility tree. Work in batches: review the asset name and facility, check its current location or holding state, pick the correct room, floor, or area, apply the changes, then fix any rejected rows individually. The page clears selected updates as you move between pages so stale picks do not misapply.

Choose the right target

Prefer the most specific reliable location. If you know the room, choose it; if only the floor, choose the floor and return later. Do not choose a system holding node just to make a warning disappear. The goal is a real operational location, not a filled field.

Imports and floor plans

Imports may carry blank, vague, or inconsistent locations; Rivolq keeps the import moving by holding unresolved records safely, but someone still has to reconcile them. After a large import, review blank locations, vague ones like unknown or shop, duplicate room names, wrong-facility assignments, and assets needing pins. Floor plans depend on location truth: an asset can only be pinned to a plan if its location sits under the floor or building that owns it. Clean the location first, then pin, as described in Placing and managing asset pins.

Rejected updates

A bulk update is rejected when the location is outside the asset's facility, is a system node, the asset is out of scope, or the change would break spatial integrity. Confirm the facility, choose a non-system location, check whether the asset is retired or duplicated, update the asset directly if it needs special handling, and retry only once the target is correct.