Employee Equipment Return Checklist for Offboarding

An employee equipment return checklist is the offboarding record that answers a simple question after someone leaves: what company equipment and software did they have, what came back, what is still missing, what changed status, and who reviewed the evidence? It should cover laptops, phones, monitors, docks, peripherals, security keys, badges, software licenses, and any assigned equipment that will otherwise disappear into email threads and memory.

The checklist matters because access offboarding and equipment return are often treated as separate worlds. IT disables accounts. HR closes the employee record. The manager says the laptop is “being shipped.” Finance still sees a software charge. A monitor is at the employee's home, a spare laptop is in transit, and nobody updates the asset register until leadership asks, “Did we get everything back?” For the account-side evidence, pair this with the employee offboarding evidence checklist.

A good checklist does not collect equipment by itself. It does not wipe devices, print shipping labels, locate laptops, or revoke access. It creates the custody evidence that lets the right people act and prove what happened.

Quick answer: what to track when equipment is returned

For every departing employee, track:

The checklist should make the state of each item boringly clear: returned, still expected, deliberately retained, damaged, lost, reassigned, or needing follow-up.

Why equipment return breaks during offboarding

Equipment return breaks because no one team owns the whole loop.

• IT knows which laptop and software were assigned.
• HR knows the end date.
• The manager knows what the employee was using day to day.
• Facilities or office operations may handle badges, monitors, docks, and storage.
• Finance may track purchase records and software charges.
• A shipping vendor may hold the return label or tracking number.
• The employee physically has the device.

When those facts stay separate, the offboarding can look complete while equipment evidence remains weak. Accounts are disabled, but the laptop is still with the leaver. The laptop is returned, but the asset status stays active. A license seat is freed, but nobody marks it unassigned. A phone is damaged, but the register has no note. A monitor is intentionally retained during a transition, but three months later nobody remembers why.

The fix is a single return record that starts from the person and branches into hardware, software, return state, and follow-up.

Start before the last day

The best equipment return checklist begins before the employee leaves. Waiting until the last day turns the process into a search. This is the asset-custody version of the broader asset ownership and custody problem.

As soon as the person is marked offboarding, pull their assigned records:

• hardware assets assigned to the person;
• software assets or licenses assigned to the person;
• accounts and systems they hold;
• remote equipment notes;
• manager-owned equipment or team-shared equipment in their custody;
• assets with unclear owner but likely assigned to them;
• recent purchases, replacements, or loaners.

Then confirm the list with the manager and, where appropriate, the employee. The question should not be “do they have anything?” It should be “here is what the register says they have; what is missing from this list?”

This changes the conversation. Instead of collecting from memory, the team verifies against a record. If the record is wrong, that is useful too. The first offboarding that exposes missing asset data makes the next one safer.

Hardware to include in the checklist

Do not limit the checklist to laptops. The smaller items are often the ones that disappear.

For the baseline hardware fields behind this pass, use the hardware asset register guide. If the person is remote, the custody workflow in how to track laptops and equipment for remote employees gives the review cadence and boundary notes.

Common hardware categories:

• laptops and desktops;
• phones and tablets;
• monitors;
• docks and docking stations;
• chargers and power adapters;
• keyboards, mice, headsets, webcams, and other peripherals;
• security keys, smartcards, tokens, or MFA hardware;
• ID badges, door fobs, access cards, and keys where IT or operations tracks them;
• external drives or removable storage;
• routers, hotspots, or remote-work networking kit;
• loaner equipment and spares;
• specialist devices such as test hardware, point-of-sale kit, or lab equipment.

For each item, use a stable identifier. The asset tag or serial number matters because “John's laptop” stops being helpful once John has left. If there is no asset tag, record the serial/service tag and create a follow-up to tag it or normalize the record later.

Software and licenses belong in the return pass too

Equipment return is not only physical custody. A departing employee may hold software licenses, SaaS seats, installed tools, or local license entitlements that need status changes.

For each assigned software record, decide whether it is:

• still active and reassigned;
• unassigned and available for reuse;
• cancelled;
• expired;
• replaced;
• retained temporarily with a named owner and review date.

Do not claim usage or license waste unless you have real usage data from an appropriate system. The asset record can show a license is unassigned because the holder left. It cannot prove how often the software was used unless a separate approved source supplies that fact. The safer software-record pattern is in the software asset register guide.

If the software renews, connect the decision to the renewal record. A freed seat may lower the renewal count. A cancelled license may require notice. A critical tool may need data export before the account is closed. Offboarding is often where asset, access, and renewal work meet.

The return-state model

A good checklist should avoid vague labels like “done” or “pending.” Use states that describe what is actually happening.

For hardware, useful return states include:

• Expected: the item is assigned and should be returned.
• Return arranged: shipping, courier, or in-person return is planned.
• In transit: return is underway.
• Received: item came back, but may still need inspection.
• Received with issue: item came back damaged or missing accessories.
• Retained with approval: item stays with the person temporarily or permanently for a documented reason.
• Lost: item is not recoverable or has been declared lost.
• Unknown: ownership or return state is unclear and needs investigation.

For the asset register status after the return, use the lifecycle state that describes the item now: spare, repair, retired, lost, active/reassigned, or another current status supported by the register. “Returned” is often not a final asset status. A returned laptop may become spare, repair, retired, or active with another employee. For more on these exception states, see lost, retired, and unassigned asset evidence.

That distinction prevents the register from becoming a history note instead of a current operating record.

What to record on the leaving date

On the leaving date, focus on disposition and evidence.

For each hardware item:

• confirm whether it was received, in transit, retained, lost, or still expected;
• record the date;
• record condition if known;
• note missing accessories;
• assign follow-up owner for inspection, wipe, repair, retirement, or reassignment;
• update the asset status once the next state is known.

For each software record:

• mark the license or seat as unassigned, reassigned, cancelled, expired, replaced, or still active with a reason;
• record status-change date;
• route renewal impact to the renewal owner;
• route access changes to the access/offboarding process;
• avoid storing secrets or full keys.

For the person/account record:

• mark the person offboarding or left;
• confirm account disposition is being tracked separately;
• note unresolved equipment return items;
• set review dates for any retained access or retained equipment.

The checklist should show which work is complete and which work is still open. Offboarding that hides open items is worse than offboarding that names them.

Remote employees: make shipping visible without over-collecting personal data

Remote work makes equipment return harder because the asset is not visible in the office. The checklist should record enough to manage custody without becoming a personal-address file.

For remote returns, capture:

• return method, such as courier, shipping label, office drop-off, or manager collection;
• return state, such as arranged, in transit, received, or delayed;
• tracking reference location, if stored in a shipping system;
• responsible owner for follow-up;
• date last checked;
• expected receipt date;
• exception note.

Do not over-collect home-address details in the asset record. Shipping systems and HR systems may already have authorized address information for their own purposes. The IT asset record usually needs a remote custody label, region or site context, tracking reference location, and status — not a pile of personal information copied into yet another system.

A practical note might say: “Return label issued by HR; tracking reference in shipping system; expected receipt 2026-08-04; IT to inspect on arrival.” That is enough for the asset register.

When equipment is damaged, missing, or deliberately retained

Exceptions need their own discipline.

Damaged equipment

Record the condition and next action:

• screen damaged;
• keyboard not working;
• missing charger;
• battery issue;
• needs inspection;
• repair owner;
• repair/vendor reference location;
• status changed to repair.

Do not turn the note into a dispute file. The asset register needs operational facts, not HR commentary.

Missing equipment

If equipment is missing, record:

• date noticed;
• last known assigned person;
• follow-up owner;
• escalation route;
• whether the item is still expected, unknown, or declared lost;
• status-change date;
• short evidence note.

A device marked lost with date and owner is stronger evidence than an active device nobody can find.

Retained equipment

Sometimes equipment is deliberately retained: a contractor keeps a device for a transition week, a founder keeps a phone during a board handover, or a remote employee has approved extended return timing.

Record:

• who approved retention;
• what is retained;
• why, in operational terms;
• review or return date;
• responsible owner;
• whether access remains and where it is tracked.

Do not let “temporarily retained” become permanent because nobody set a review date.

Connect equipment return with account offboarding

Equipment return and account offboarding should reinforce each other.

A person marked offboarding in a People & Accounts register should produce two lists:

1. accounts and access that need disposition;
2. hardware and software assets that need return, reassignment, cancellation, or status change.

The access work happens in the underlying systems. The equipment work happens through the physical return, inspection, wipe, repair, or reassignment process. The evidence record ties them together so the team can answer: did we handle the person, the accounts, and the assets?

This is especially important for shared and service contexts. A departing administrator may own a shared mailbox, vendor portal, service account, test phone, or software license that other people use. Offboarding should reassign responsibility before the person leaves, not discover later that “everyone used that account.”

Build the return packet managers can understand

A manager does not need raw asset tables. They need a simple packet:

• employee name or work identifier;
• end date;
• manager/accountable owner;
• equipment expected;
• equipment received;
• equipment still outstanding;
• software/licenses reassigned or unassigned;
• access review/offboarding status;
• open follow-up owner and date;
• final sign-off.

Keep the packet short. A useful summary might say:

“Five items expected: laptop, charger, phone, monitor, dock. Laptop and charger received 2026-07-30; monitor/dock in transit; phone retained until 2026-08-02 for MFA handover, approved by IT owner; software seats marked unassigned for design tool and support tool; access removal tracked separately.”

That is the kind of evidence a COO or HR lead can understand without logging into three systems.

The checklist itself

Use this as the working version.

Before the last day

• Mark person as offboarding.
• Confirm end date.
• Pull assigned hardware records.
• Pull assigned software/license records.
• Pull account/access records.
• Confirm records with manager.
• Identify remote equipment.
• Identify shared or team equipment in the person's custody.
• Identify security keys, badges, or access cards.
• Confirm return method for each physical item.
• Confirm which software seats or licenses should be reassigned, unassigned, or cancelled.
• Assign follow-up owner for shipping, inspection, wipe, repair, or reassignment.

On the leaving date

• Update return state for each hardware item.
• Record received date or expected return date.
• Record condition where known.
• Record missing accessories.
• Mark software/license disposition.
• Confirm any retained equipment has approval and review date.
• Confirm access/account changes are tracked in the access offboarding record.
• Capture open items with owner and date.

After receipt

• Inspect returned equipment.
• Route wipe/reset/reimage work through the proper device-management or IT process.
• Change asset status to spare, repair, retired, lost, active/reassigned, or another honest state.
• Update software license status to unassigned, reassigned, cancelled, expired, or replaced.
• Close shipping or return follow-up.
• Record final review/sign-off.
• Include unresolved exceptions in the next governance or management summary.

The checklist is finished when every item has a disposition, not when the person has left.

What not to record

The asset return record should stay narrow. Do not record:

• personal HR reasons for departure;
• performance or disciplinary notes;
• unnecessary home-address detail;
• passwords, recovery codes, or API keys;
• full license keys;
• private files or content from a returned device;
• employee activity or productivity data;
• legal conclusions about liability;
• payment-card data.

If a device needs wiping, inspection, forensics, repair, or legal handling, that work belongs in the appropriate system and process. The asset return checklist records the status and owner, not the private contents of the device.

How CertPilot fits, with the right boundaries

CertPilot's Assets Register can maintain the hardware and software side of this checklist: assigned person, asset tag or serial, location/site context, lifecycle status, software license status, purchase or renewal context, notes, CSV import/export, and count-only evidence gaps. The People & Accounts register can mark the person as offboarding or left, and Access Reviews can preserve the access-review evidence that runs alongside equipment return.

That turns the return process into a repeatable routine. The next leaver produces a visible worklist instead of a Slack thread. The next management check can see summary counts and open gaps instead of asking IT to reconstruct the story.

The boundaries are the trust point. CertPilot does not ship boxes, print labels, arrange couriers, locate devices, wipe laptops, lock endpoints, collect telemetry, discover assets, sync HR or directory systems, monitor employees, or remove access. It records the customer-maintained custody evidence your team enters or imports.

In short

• An employee equipment return checklist should track what equipment and software a leaver had, what came back, what is still open, and who reviewed it.
• Start before the last day by pulling assigned hardware, software, accounts, and remote custody notes from the person record.
• Use clear return states: expected, arranged, in transit, received, damaged, retained, lost, or unknown.
• Update the final asset status after return: spare, repair, retired, lost, active/reassigned, or unassigned for software.
• Keep HR detail, secrets, private content, and unnecessary personal data out of the asset record.
• CertPilot can help keep the custody evidence structured, but it does not perform shipping, wiping, device control, discovery, or access removal.

Frequently Asked Questions

What should be included in an employee equipment return checklist?

Include every assigned hardware item, software license, SaaS seat, security key, badge, accessory, return method, return date, condition, final asset status, follow-up owner, and evidence note. The checklist should show what was expected, what was returned, what remains open, and what was deliberately retained or marked lost.

Is equipment return part of IT offboarding or HR offboarding?

It is usually shared. HR owns the employment event and communication. IT owns asset and access records. Managers confirm what the employee used. Facilities or operations may handle badges and shipping. The checklist should connect those responsibilities instead of assuming one team has the whole picture.

How should remote employee equipment return be tracked?

Record the return method, return state, expected receipt date, tracking reference location, responsible owner, and date last checked. Avoid copying unnecessary home-address detail into the asset register. Use the shipping or HR system for sensitive address information where appropriate.

What status should a returned laptop have?

“Returned” is usually not the final lifecycle status. After inspection, the laptop should become spare, repair, retired, lost, or active/reassigned depending on its condition and next use. The asset record should show the current state, with notes preserving return context.

Should the checklist include wiping the device?

It should include the wipe/reset/reimage owner and status, but the wipe itself happens in the appropriate device-management or IT process. A general asset register should not contain private file contents, employee activity, or sensitive data from the device.

Does CertPilot automatically track or recover employee devices?

No. CertPilot's Assets Register is customer-maintained. It does not locate devices, collect endpoint telemetry, wipe or lock laptops, print shipping labels, arrange returns, discover assets, monitor employees, or remove access. It records the custody evidence your team maintains.