What Should Employers Do When a Remote Employee Leaves? A Checklist

A remote employee leaves the company, and a few days later, a client asks for a document nobody can find. A colleague discovers that an important software account is still tied to the former employee’s email. A project deadline is approaching, but the person taking over has no idea what was promised to the client.

For a small business, even one of these problems can eat up hours. The manager has to track down files, IT has to sort out account access, and someone still needs to finish the work.

The trouble often starts before the employee leaves. Files have been saved in different places, responsibilities exist mostly in someone’s head, and nobody has checked which accounts need to be closed or transferred.

A few conversations and some basic planning can prevent much of that scramble.

Most employers remember to deal with company email. The less obvious accounts are easier to miss.

An employee might manage a client’s social media pages, have administrator access to a website, maintain a paid software subscription, or store project files in a personal workspace within a company platform. A list of approved software will not always capture every tool someone has used.

Ask the employee’s manager which systems are part of the job, then work with IT to review access. Include administrator permissions, shared folders, customer databases, billing platforms, and any accounts used to communicate with clients.

If the employee is the only administrator of an important service, transfer that responsibility before closing their account. Otherwise, the company could lose access to a tool it pays for or needs to keep running.

For a planned departure, IT can schedule most changes for the employee’s final day. If there is a credible security concern, access may need to be restricted sooner.

The Federal Trade Commission specifically advises businesses to have a procedure for ensuring that former employees no longer have access to sensitive information. Its guide to protecting personal information also recommends collecting company keys and other access items as part of the departure process.

Someone should check that each change has actually been made. It is not enough to send IT a request and assume the job is finished.

A project tracker can show completed tasks without telling the whole story. A client may be waiting for a reply, a proposal may need one last revision, or a manager may have promised a delivery date that nobody else knows about.

Before the employee leaves, ask them to walk through their current work with the person who will take it over.

Which projects are active? What deadlines are coming up? Are any clients waiting for an answer? Has anyone made a commitment that still needs to be honored? Where are the latest files?

The answers do not need to become a lengthy report. A shared document with project names, next steps, deadlines, and contacts may be enough. More complicated roles will need more detail.

Pay attention to work that happens outside the formal project system, too. An employee might handle a recurring monthly report, maintain a spreadsheet for a major client, or follow a process that nobody else has ever had to use.

Ask about those tasks directly. They are often the ones that cause confusion after a departure.

The person taking over should have time to review the handover and ask questions while the departing employee is still available.

A remote employee cannot simply leave a laptop on a desk at the end of the day. The company needs to arrange its return and keep track of what is still outstanding.

Start with the equipment register. Confirm which items the employee has, including laptops, phones, monitors, security keys, and any other company-owned devices. Agree on how they will be shipped or returned, who will cover the cost, and when they should arrive.

Keep the shipping reference and confirm delivery. For valuable devices, record serial numbers rather than relying on a general description.

There is another issue when employees use their own computers or phones. The company may need to remove work accounts or business data, but that does not give it an unrestricted right to inspect personal files.

Follow the company’s device policy and the privacy rules that apply to the employee. If the arrangement was never clearly documented, get appropriate advice before attempting to remove data.

Deleting an account too early can leave colleagues without documents they need. Keeping an ex-employee’s access open indefinitely creates a different risk.

Before closing an account, identify the business records that need to be retained. These might include client correspondence, proposals, contracts, project files, financial records, and emails documenting decisions that affect ongoing work.

Check the actual storage locations rather than assuming everything is in a shared drive. Microsoft’s guidance for removing a former employee from Microsoft 365 explains how administrators can block access while preserving business information and arranging access to former employees’ email and OneDrive content.

The details will depend on the systems the company uses, but the principle is the same: secure the account without losing records the business still needs.

Retention also deserves attention. Some records must be kept for legal or operational reasons; others should be deleted when there is no longer a legitimate reason to retain them. The FTC recommends knowing what information a business holds, limiting what it keeps, and disposing of unnecessary information securely.

How a company handles employee departures can also shape how people view it as an employer. Candidates increasingly use online sources and AI tools to research companies before applying. Read more about what AI tells candidates about your company before they apply.

If business documents are stored in a personal account, arrange an appropriate transfer. Do not copy an employee’s entire personal account just to recover a handful of work files.

HR may handle the paperwork, IT may remove access, and the manager may organize the handover. But when each department is responsible only for its own tasks, it is easy for something to slip through.

Choose one person to coordinate the departure. That person can delegate the work, but should know who is responsible for each item and whether it has been completed.

A simple checklist is usually enough:

The checklist should reflect the role. Someone who manages customer accounts may have access to client data and billing systems. A designer may need to hand over source files and design assets. A software developer may have access to code repositories and production systems.

A standard process helps, but the details matter just as much as the checklist itself.

Sometimes there is no time for a proper handover. An employee may resign unexpectedly, become unavailable, or leave under difficult circumstances.

In that situation, the company has to rely on the arrangements it made beforehand.

Keep business files in approved company storage. Make sure important systems have another authorized administrator where appropriate. Document recurring tasks and maintain a current record of company equipment.

It is also worth reviewing who can access sensitive information. The FTC recommends limiting access to people who need it for their jobs, rather than giving employees broad access by default.

These practices are useful even when nobody is leaving. If an employee is suddenly unavailable because of illness or an emergency, a colleague should still be able to find the necessary files and keep essential work moving.

The final working day is a poor time to discover that a client’s files are stored in an individual account or that nobody else can administer a critical service.

Start the handover early enough for the employee, manager, and IT team to deal with those details. Decide who will take over each project, check the records that need to be preserved, arrange equipment returns, and schedule the necessary access changes.

There is no need to turn every departure into a complicated exercise. The goal is to avoid leaving the remaining team with unanswered questions and work they cannot easily continue.

Ready to hire? Post your vacancy on Online.jobs and connect with remote candidates.