What is IT asset management (ITAM)? A guide
Learn what IT asset management covers, how the IT asset lifecycle works, which data to track, and how to build...
Quick answer
An employee offboarding checklist should sequence the HR, identity, security, and equipment steps against a named owner for each, then go deep on the equipment half: identify assigned items, document instructions and condition, close each assignment, and keep unresolved returns visible.
Employee offboarding is where incomplete asset records become visible. A device may be listed under the wrong person, accessories may never have been recorded, a manager may expect a transfer, and a remote employee may need packaging and shipping instructions.
The equipment checklist is only one part of offboarding. Human resources, identity administration, security, payroll, legal, facilities, and department leadership may own separate actions. The asset process should coordinate with those owners without pretending to replace their controls.
This guide sequences the whole checklist so the equipment steps land in the right order, then covers the equipment half in the depth it actually needs. It is written from the IT and operations side, which is the half most offboarding checklists skip.
Most published offboarding checklists are a flat list of tasks. The order matters more than the list, because several steps become impossible if an earlier one has already run — the most common example being an account disabled before anyone read the assignment list off it.
A workable sequence, with the owner for each stage:
| When | Stage | Owner | Why it sits here |
|---|---|---|---|
| On notice | Confirm departure date, type, and access sensitivity | HR | Everything downstream is scheduled from this date |
| On notice | Produce the assigned-equipment and subscription list | IT or operations | Must happen while accounts and records are still intact |
| On notice | Decide return, transfer, or retention per item | Manager | Avoids collecting equipment the successor needs |
| Before last day | Issue return instructions, packaging, or drop-off plan | IT, operations, or facilities | Remote returns need lead time for shipping |
| Before last day | Plan knowledge transfer and reassign owned work | Manager | Unrelated to assets, but competes for the same final week |
| Last day | Collect equipment, inspect, and record condition | Receiving owner | Condition is only observable at handover |
| Last day | Revoke building access, keys, and badges | Facilities or security | Physical access is separate from digital |
| Last day | Disable accounts, sessions, and MFA | Identity administration | After the assignment list exists, not before |
| After last day | Reclaim or reassign licenses and subscriptions | IT | Billing continues until someone acts |
| After last day | Close or transfer assignments in the asset record | Asset system owner | Creates the evidence trail |
| After last day | Final pay, benefits, and any legal steps | HR, payroll, legal | Outside the asset process entirely |
| Ongoing | Track unresolved returns to a decision | Named manager | Exceptions must not expire quietly |
Three of those stages belong to HR, payroll, and legal, and this guide does not attempt to instruct them — it only shows where they sit so the equipment steps do not collide with them. The licenses row is covered separately in software license management, since a reclaimed seat and a returned laptop are different recovery problems.
The rest of this guide covers the equipment stages in detail.
Before a departure occurs, decide who owns each step:
| Step | Typical owner | Required result |
|---|---|---|
| Notify asset team | HR or manager | Authorized departure details and timing |
| Produce assignment list | IT or operations | Current assets, subscriptions, locations, and known accessories |
| Confirm business need | Manager and asset owner | Return, approved transfer, retention, or exception decision |
| Coordinate return | IT, operations, or facilities | Instructions, date, shipping or drop-off plan |
| Inspect and record | Receiving owner | Observed items, condition, accessories, date, evidence |
| Close or transfer | Asset system owner | Earlier assignments closed and next state recorded |
| Resolve exceptions | Named manager or policy owner | Documented next action and decision |
Do not send sensitive departure information to people who do not need it. The asset team needs enough notice to perform the recovery workflow, not the contents of an HR case.
Begin with the authoritative person record or assignment report. Include individually tracked equipment and the accessories the organization has chosen to control.
Look for:
Compare the asset register with other approved sources when needed. A device-management or identity system may reveal technical or access information, while the asset register preserves business custody and lifecycle history. Record discrepancies rather than silently changing the list to make the sources agree.
Copy this table into the offboarding ticket, asset review, or approved working document:
| Asset ID | Item | Serial | Expected accessories | Return status | Observed condition | Next location/state | Exception owner |
|---|---|---|---|---|---|---|---|
| AC-000184 | Dell Latitude 7450 | 9K2X71F | Charger, dock | Returned | Good | IT storage | — |
| Expected / Returned / Missing / Approved transfer |
Use controlled values for return status. Free-text notes can explain an exception, but they should not replace the status and owner needed to manage it.
Remote recovery adds shipping and custody transitions. Define:
A carrier tracking event is not the same as receiving and inspecting the correct asset. Keep the assignment or exception open until the organization's closing criteria are met.
A manager may ask to give the equipment directly to another employee. That can be valid when policy permits it, but it should remain a controlled transfer:
Do not simply replace the name in the current-custodian field. The earlier responsibility is part of the asset history.
Classify unresolved items by cause:
Use the pattern to improve receiving, deployment, and handoff controls. Offboarding should not be the first time the organization tries to establish who has an asset.
AssetCenter for IT teams connects people with their current and previous assets, subscriptions, and locations. The managing-people manual explains the person record and assignment actions, while the managing-assets manual explains assignments, events, condition updates, to-dos, and decommissioning.
AssetCenter does not disable accounts, revoke identity access, wipe devices, manage HR cases, or make legal or payroll decisions. Coordinate those actions through the approved specialist systems and owners.
The checklist depends on the person record existing before the departure notice does. The Microsoft Entra ID integration keeps People current from the directory groups already in use, so a leaver arrives in the review with their assignments attached instead of having to be found by hand. Automating the equipment half of offboarding covers that setup in full.
Select a current employee record with several representative assignments and walk through the checklist without changing anything. Confirm that the team can identify the equipment, accessories, return owner, exception path, and closing evidence.
Fix missing ownership now. A checklist is most useful when the operating record is already being maintained, not when it is introduced after the departure notice arrives.
Founder & CEO, AssetCenter
Learn what IT asset management covers, how the IT asset lifecycle works, which data to track, and how to build...
Build an IT asset lifecycle process from planning and receiving through deployment, support, recovery, sanitiz...
Learn how equipment checkout software tracks custody, returns and condition, which features matter, and when a...