Asset assignment: who has which device?

"Who has this laptop?" is the question IT teams ask most often and answer with the most difficulty. In most companies the answer lives in a spreadsheet — one that was last updated six months ago.

The point of an asset module isn't to count inventory but to keep the link between an asset and a person alive.

Why a spreadsheet isn't enough

Three reasons. Nobody updates it — opening the file when a device changes hands is nobody's job. The employee can't see it — they don't know what's assigned to them, so they can't correct an error. And there's no history — who had a device previously is lost, and fault patterns can't be traced.

Those three define what an asset system has to solve: staying current, mutual visibility, and handover history.

Employee acknowledgement: the critical step

A one-sided assignment record leaves the door open to later disputes. The correct flow: IT assigns the device to a person, the person sees it on their own screen and acknowledges it. That acknowledgement is the digital equivalent of the paper handover form.

The step also cleans the data. If an employee sees a device they don't have, they object — and the error is fixed without waiting for a stock count.

Handover history

Who a device passed from and to, when, and in what condition should all be recorded. That has three concrete benefits: recurring faults become visible through the device's history, the last responsible person is known in case of loss, and depreciation or replacement planning rests on real data.

Being able to note the device's condition at handover — a scratched screen, a missing accessory — heads off most later arguments.

Which assets should be tracked?

Trying to track everything makes the system unusable. The practical threshold: assets that are assigned to a person and have value. Laptops, phones, vehicles, safety equipment, access cards, specialist tools.

Shared and inexpensive items — keyboards, cables, stationery — shouldn't enter the register; if they do, the record goes stale quickly and takes the credibility of the whole system with it.

The link to offboarding

Asset tracking is most useful the moment someone leaves. The first item on an exit checklist is usually "return assigned devices", and that list should be generated automatically from the asset records.

The same link works in reverse: during onboarding, the devices to be assigned are prepared in advance. We cover both in our onboarding article.

Stock counts

An annual physical count is the only way to test the system's accuracy. The discrepancies found are of two kinds: items in the system that can't be found physically, and items that exist physically but don't appear in the system.

The second is usually more common and points to a process problem: devices are being handed out before they're registered. The fix isn't more frequent counts but linking purchasing to the asset record.

Personal use and privacy

An asset record is personal data and shouldn't carry more than it needs. Who uses which device is something IT and the manager need to know; it doesn't have to be open to the whole company.

Features such as location tracking or usage monitoring on a device are a separate matter and require explicitly informing the employee under data protection law. The boundary between asset tracking and employee monitoring must be kept clear — we address that distinction in our compliance article.

Barcodes and serial numbers

In a company with fifteen identical laptops, a record saying "Dell laptop" is useless. Recording every asset with its serial number is the only real anchor for assignment; warranty tracking and insurance processes also depend on it.

Adding barcode labels speeds up counting but isn't essential. The real difference is whether the serial number is recorded: an inventory without them can't answer "which one was this?" during a count, and discrepancy analysis becomes guesswork.

The relationship with the ERP

Fixed-asset accounting already lives in the ERP. The intranet doesn't replace that record; it builds the employee-facing side — showing who has what, collecting acknowledgements, keeping handover history. Pushing an approved assignment change into the ERP is an integration matter and belongs to a second phase.

Measurement

• Acknowledgement rate — what share of assigned assets was acknowledged by the employee?
• Count discrepancy — the mismatch rate between the physical count and the system.
• Return time — the average days to collect devices after an exit.

The first shows whether the system is alive, the second process discipline, the third whether offboarding works. The rollout order is in the 90-day plan.