Asset Registers
Part of Business asset register software
Testing ownership and location history
Run an asset handover sequence to check custodian, financial responsibility, location changes, corrections and recoverable history.
Test an asset register's history by moving one tagged item through several people and places, then asking someone else to reconstruct the sequence. Current custodian and location fields are only the starting point. The useful question is what changed, when, who recorded it and what supports a handover or physical check.
Define the roles
For this exercise, distinguish the financial owner responsible for the asset financially, the custodian expected to hold or use it, and the location where it is expected to be found. Decide how your business assigns financial responsibility; product field names and permitted values differ.
ServiceNow's documented asset record includes an “Assigned to” field, which identifies the person using or primarily responsible for the item. That field appears when the asset's state is In Use and is cleared for some state changes. Field availability also varies by asset type and installed components.
Snipe-IT records checkout and checkin. It permits checkout to a location but recommends retaining an accountable person. A location entry alone does not identify who accepted custody.
Asset Tracking Features Across Platforms
- ServiceNowUses ‘Assigned to’ field for custodian; clears on state change; supports financial ownership via asset type settings
- Snipe-ITTracks checkout/checkin; recommends assigning a custodian even when moving; requires setup for acceptance signature
- SortlyShows Activity History with dates and users; Move Summary tracks folder changes; retains history per pricing tier
Run a handover sequence
Use one fictional, uniquely tagged laptop. Agree on the expected history before a demonstration:
- Receive it at a stockroom with no staff custodian.
- Issue it to Employee A and record the handover.
- Move the laptop to another office without changing financial responsibility.
- Return it, then issue it to Employee B.
- Correct an intentionally wrong location while preserving a record of the correction.
After each action, inspect the current fields and earlier events. Ask whether a move changes the custodian, whether checkout changes the recorded location and whether a correction is visible as a new event. A field edit alone does not prove a physical transfer.
Snipe-IT documents recipient acceptance for configured asset categories. A physical signature requires another setting and the recipient's action.
Sortly's Activity History shows dates and associated users, and its Move Summary records movements between folders. Check whether the proposed account retains history for the period you need.
Ask questions about the past
Give a colleague the tag and a past date. Can they identify the recorded custodian and expected location then, and the event that changed each? Can they distinguish a planned move from a verified arrival? If an item is refused, found elsewhere or left with a former employee, ask how the discrepancy and its resolution are recorded.
A useful result is a coherent, recoverable sequence that another staff member can explain. Record any missing event, permission or retention period as a condition for selection.
Key Questions to Verify Asset History Integrity
- Can the past custodian and location be identified?Yes – if event logs are complete and timestamped
- Is a planned move distinguishable from a verified arrival?Yes – if both actions are recorded with user and date
- How is a refusal or discrepancy recorded?Via correction event or status update with notes
- Is there a recoverable sequence for a second staff member?Yes – if all handovers are documented with proof of acceptance
