Recovering assets after resignation

Recovering assets after resignation is the operational chase to last working date (LWD): every assigned serial listed, appointment or courier booked, return dated, condition recorded, exceptions owned. It is not a second packing list. Itemized kit stays on the employee asset handover checklist. Last-week knowledge, access, and letters stay on the employee exit checklist. How resignation, notice, and LWD become facts stays on resignation, notice, and last working date. Settlement math stays on the full and final settlement process. Product surface: Dayzen asset management (assignment history, my-assets, handover/return photos) and pending returns shown on the FNF worksheet as status, not as a claim that you may withhold wages.

This is operational guidance, not legal advice. Whether any recovery amount is lawful, and whether any deduction may appear in wages, may depend on applicable law, contract, policy, or company practice. Verify with your HR and legal or SME team. Do not withhold wages as a tactic to force a laptop back. This page does not advise illegal withholding. Dayzen does not remotely wipe, GPS-track, or auto-recover devices.

Start from the register, not from memory

The chase list is the live assignments on that employee, plus anything still in their name from a repair or spare swap. Open the assignment history. Do not ask the manager to “list what they had” as the only source. Managers forget SIMs. Employees forget tokens. The register is the start; the handover checklist is the completeness pass (badge, keys, uniform — categories the register might never have if you never catalogued them). Run both. Do not run only the folk memory.

If the register is empty but the person clearly had a laptop, you have a prior assignment failure. Still recover the physical object. Create or complete the catalog row at return if you must, and treat that as a process defect to fix for the next issue — not as a reason to skip the appointment.

Include mid-life complexity: original in shop, spare in bag, accessories in a drawer. Recovery is finished only when each serial has a dated fate (returned, in shop with a named holder, lost with an owned exception). See repair and custody for how those states should have been written before exit. At exit you cannot invent history, but you can stop making it worse.

Work backwards from LWD

LWD is the last day you treat as in-office (or last day of authorised work if remote). Recovery wants the items in company hands on or before that day whenever you can. If notice is long, do not wait until the afternoon of LWD to book the desk. If notice is short, compress: same list, earlier booking, courier if they will not attend. The resignation article owns how LWD was set. This page executes kit against it.

Name an asset recovery owner. In a small company that may be the same person who runs the exit checklist. The hat still changes: last-week ops are many buckets; this bucket is physical property. Chat “please collect laptop” without a date, location, and serial list is not a plan.

Remote employees need a courier path, packing instructions, and a return photo/condition step on receipt — not a hope that the laptop will appear. Dayzen does not collect parcels. You still record the return when the parcel is in your hands and the serial matches.

The chase, in order

1. Freeze new issue. Do not hand them another spare on LWD week unless you like extra recovery. Repair exceptions stay owned.
2. Publish the list. Serials and types from the register, plus checklist categories still open. Employee should already see assignments on my-assets; send the same list, not a surprise novel.
3. Book handover. Time, place, or courier window, relative to LWD. Coordinate with access revoke so you do not lock a device you still need to inspect.
4. Receive and match. Serial to register. Condition written. Return photos if you use that practice; compare to issue photos when they exist.
5. Close or exception. Returned, or dated exception (lost, disputed, in transit, in shop) with an owner and a next date.
6. Surface status. Pending returns that remain open can appear on the FNF worksheet as pending-asset status. That tells settlement operators the kit is not clear. It is not a wage freeze instruction.

Acknowledgement at return is as important as at issue. “They left it at reception” without a name and time is how items bounce between reception and IT for a week.

Pending returns on FNF are status, not a deduction machine

Dayzen’s FNF worksheet can show pending asset returns next to other settlement lines (unpaid salary, leave encashment, notice recovery as you configure them). Read that row as: operations still have open kit. Finance and HR still decide what, if anything, is calculated as a recovery amount under your issued policy and what is actually paid. The product does not file, does not pay the bank, and does not make a deduction lawful by displaying a flag.

Do not tell operators to “hold the full and final until they panic.” Delay of settlement, and any set-off, may be constrained by contract and applicable law — you must verify; this article will not invent a nationwide rule. Separate three objects:

• Physical recovery — this page.
• Worksheet status — pending returns visible so nobody pretends kit is clear.
• Money — only if your reviewed policy and legal advice say a recovery line is appropriate. Not automatic. Not “the software said so.”

Lost-item cost arguments belong in a dated exception and, if needed, a conversation with SME support. They do not belong as an improvised last-day threat in the parking lot.

What you cannot do from the product

No automatic remote recovery. No remote wipe from Dayzen. No GPS. No MDM. If IT has their own fleet tools, they may have separate steps after you confirm the device is back — or, if a device is stolen, their own incident process. HR’s job remains the people-linked register and the appointment. Do not wait for a magic button. Do not promise the employee that “the system will lock the laptop tonight” unless IT actually operates that in their own stack — and even then, a locked laptop in a bag is not a returned laptop.

Do not delete the employee record to “clean” pending assets. Mark employment as your lifecycle process requires; keep assignment history. Deleting the person deletes the chase list.

A recovery board

Item	Owner	Done means
Assignment extract	Asset owner	Every live serial listed, including shop/spare
Checklist pass	Asset owner	Badge, keys, and other categories not only laptops
Handover slot	Exit owner + employee	Dated appointment or courier window before/on LWD
Receive	Return desk	Serial match, condition, photos if used
Exceptions	Named owner	Lost/disputed/in transit with a next date
FNF status	HR / payroll ops	Pending returns visible; no illegal withholding
Access coordination	IT / exit owner	Revoke sequenced with collection, not against it

What this page must not steal

Do not reprint the full exit checklist. Do not restate notice-period law. Do not turn FNF into this article; the settlement guide owns process and worksheet contents. Do not reprint the assignment tutorial except to say: if it was never assigned, recover anyway and fix cataloguing. Condition photo craft stays on its sibling; here you only require that return evidence is taken if that is your practice.

Failure modes

Starting the chase on LWD afternoon. Collecting the laptop and leaving the SIM. Demanding a device that is at a vendor shop without looking at the repair log. Holding salary in chat as leverage. Assuming Dayzen wiped the disk. Two lists (manager notes vs register) and a fight at reception. Marking FNF “cleared” while courier is in transit. Treating pending-return status as an automatic rupee deduction. Photographing the person instead of the device. Deleting my-assets access so they cannot even see what to bring, then blaming them for an incomplete bag. Issuing a new badge in the last week “because the old one failed” and forgetting both at the door.

Another failure: recovery owned by nobody because “IT collects hardware and HR collects badges.” Split the work if you must, but one exit owner confirms both subsets are dated.

When recovery is done

Done means every register serial and every checklist category is returned or has a dated exception with an owner. Done is not “they walked out.” Done is not “FNF paid.” You can finish kit recovery with settlement still open. You should not mark kit clear because payroll wants a clean worksheet. Status should stay pending until the bag matches the list.

If an exception ages past LWD, it remains an operations item. Keep chasing the object. Do not launder it into a silent deduction. If legal and policy later support a calculated recovery line, that decision is outside this chase script and belongs with SME review and the FNF process owner.

List what the register says they hold, collect it by LWD, photograph return if that is your practice, and show pending returns on the FNF worksheet as status. Not remote recovery. Not wage withholding. Checklist owns the item list. Exit checklist owns last week. Settlement guide owns money.

Run the same chase for internships and short contracts; mark true N/A with a name. Stop when serials have fates — not with a second FNF essay or a fake legal deduction recipe.