The asset owner is the person or department accountable for an asset: its budget, whether it is fit for purpose, and when it should be maintained, replaced or disposed of. The owner is usually a role or department, such as "Head of IT" or "Facilities", rather than the person using the item, who is the custodian.
"Owner" here means accountability inside the organization, not legal ownership. The organization owns the asset in law; the asset owner is the person who answers for it.
Asset owner vs custodian vs user
| Item | Asset owner | Asset custodian | Asset user |
|---|---|---|---|
| Answers for | Value, budget and lifecycle decisions | Physical care and whereabouts | Using it properly |
| Typical person | Department head, budget holder | Site manager, storekeeper, named employee | Whoever has it today |
| Approves | Purchases, major repairs, transfers, disposals | Day-to-day issue and return | Nothing; reports faults |
| At audit | Reviews and signs off exceptions | Finds the assets and explains gaps | Shows the item when asked |
On a small team one person can be owner, custodian and user. In larger organizations they are rarely the same, and the split is what makes accountability work.
Typical owner responsibilities
- Approving purchases, major repairs, transfers and disposals.
- Reviewing audit results and write-off requests for their assets.
- Setting policies: who may use or check out the assets, and where they may go.
- Planning replacement budgets from age, condition and cost history.
- Making sure every asset they own has a named custodian.
RACI example: IT laptops
| Activity | Owner (Head of IT) | Custodian (IT service desk) | User (employee) | Finance |
|---|---|---|---|---|
| Approve purchase | A | C | I | C |
| Register and tag | I | R | I | I |
| Issue to employee | A | R | I | I |
| Report fault | I | R | R | I |
| Annual verification | A | R | C | I |
| Dispose and wipe | A | R | I | C |
Record the hand-over with an IT asset handover form so the user acknowledges what they received.
Information asset owners in ISO 27001
In information security, ISO/IEC 27001 expects an organization to keep an inventory of information and associated assets, such as systems, data sets and devices, with an owner for each. That owner is responsible for classifying the asset, approving access and making sure it is protected. The idea is the same as the physical asset owner: one named person accountable for each asset.
Examples
- Hospital: clinical engineering owns infusion pumps and approves repair or replacement; the wards that use them are custodians.
- Construction: the plant manager owns the excavators; each site manager is custodian while a machine is on their site.
- School: the head of science owns the lab equipment; technicians are custodians.
Common mistakes
- Naming a person instead of a role, so ownership disappears when they leave.
- Owner and custodian blurred, so nobody approves disposals and items sit in storerooms for years.
- Owners who never see audit results for the assets they answer for.
Spreadsheet vs software
A spreadsheet can hold owner and custodian columns, but it cannot stop the wrong person editing them. Software ties ownership to permissions and records every change in an audit trail.
In Asetavo
Asetavo records a department and custodian on every asset, and many teams use the department as the owner. Check-outs record who holds an item and when it is due back (every plan). Roles and permissions control who can create, edit or delete assets and who sees finance fields, with Advanced RBAC on the Business plan.
