A recent Delhi High Court order has highlighted a risk that many employees and startups often underestimate: the failure to return company property after termination can lead to criminal proceedings under Section 452 of the Companies Act, 2013. In a case reported this week, a former employee returned a laptop only after a criminal complaint was filed. The court declined to quash the process, allowing the case to proceed. This episode emphasizes that asset disputes are not just HR issues - wrongful withholding is a statutory offence with potential fines and, in some cases, imprisonment, alongside court orders to return the property.
For employees leaving under duress, emotions can run high - anger, confusion about final pay, fear of being ignored by managers. It's tempting to hold on to a device "until dues clear." However, this misstep can turn a messy exit into a legal fight. For founders and HR in startups, the other side is familiar: access revoked, assets missing, code frozen on a personal laptop. People on both sides often don't realize this can escalate to a criminal process. This ignorance fuels hostility, not resolution. The humane move is also the smart one: set expectations clearly before Day-1 and repeat them at Day-Last.
To tighten your off-boarding SOP, add a Section 452 acknowledgment in appointment letters, require a device and data checklist at separation, and link final settlement release to asset hand-back (with a fair dispute window). Keep asset registers current, run MDM/EDR for remote wipes, and secure IP assignments so code and content live in the repository, not on personal drives. If a dispute arises, consider a without-prejudice return protocol before escalating. And train line managers: threatening criminal action prematurely can backfire, but ignoring 452 exposure is not an option either. Balance firmness with process and document everything.
The question is, what would make your exit checklist so clear that no one is surprised on hand-back day? How will you protect company IP without making good-faith leavers feel criminalised?
For employees leaving under duress, emotions can run high - anger, confusion about final pay, fear of being ignored by managers. It's tempting to hold on to a device "until dues clear." However, this misstep can turn a messy exit into a legal fight. For founders and HR in startups, the other side is familiar: access revoked, assets missing, code frozen on a personal laptop. People on both sides often don't realize this can escalate to a criminal process. This ignorance fuels hostility, not resolution. The humane move is also the smart one: set expectations clearly before Day-1 and repeat them at Day-Last.
To tighten your off-boarding SOP, add a Section 452 acknowledgment in appointment letters, require a device and data checklist at separation, and link final settlement release to asset hand-back (with a fair dispute window). Keep asset registers current, run MDM/EDR for remote wipes, and secure IP assignments so code and content live in the repository, not on personal drives. If a dispute arises, consider a without-prejudice return protocol before escalating. And train line managers: threatening criminal action prematurely can backfire, but ignoring 452 exposure is not an option either. Balance firmness with process and document everything.
The question is, what would make your exit checklist so clear that no one is surprised on hand-back day? How will you protect company IP without making good-faith leavers feel criminalised?