Asset Assignment & Handover

Who has which asset right now — and how is handover recorded?

Custody is a history, not a field: each asset carries an assign-use-return handover record, so you can see who holds it now and who held it before. Asset requests can be raised on behalf of an employee, an organizational unit, or a project.

The sequence

4 steps

Request
An asset request is raised on behalf of an employee, unit, or project.
Assign
The handover records the assignment to the receiving party.
Use
Custody and location stay on record while the asset is in use.
Return
The return closes the handover, freeing the asset for reassignment.

How it works

The handover history records custody as states — assigned, in use, returned — accumulating over the asset’s life. When a laptop changes hands three times, the register shows three handovers, not just the latest name.

Assignment starts from a request, and requests are raised on behalf of someone: an employee, an organizational unit, or a project. That keeps the purpose of the issue attached to the record — an asset issued to a project is distinguishable from one issued to a person.

Return is a first-class step that closes the handover, after which the asset is available to assign again. Together with location records, the handover history answers both where an asset is and in whose hands.

Worth knowing

Assign-use-return historyCustody states accumulate per asset, preserving the full chain of hands.
On-behalf-of requestsRequests name an employee, organizational unit, or project as the beneficiary.
Current holder visibilityThe latest open handover answers who has the asset right now.
Return closes the loopReturned assets are explicitly back and assignable again.

What this touches

Next in Assets

All of Assets

See asset assignment & handover running in continON.

A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.

Request a demo

Asset Management overview